1. Enterprise 365
General overview

2. Agenda
• Business needs
• Most common objectives
• Solution Areas
• Security
• Integration
• Reporting & Data Visualization
• Data
• Cleaning
• Migration
• Maintaining
• General User Needs
• General recommendations
• Getting information
• Kick-off meeting
• Launching on production
• Trainings

3. Most common
objectives
Business needs

4. • Process enhancement – (SalesLegalMarketingetc…)
• Process automatization – (Auto NotificationBillingLoyalty programetc…)
• Reporting enhancement – (FinancialSupply ChainSalesetc…)
• Security – (Leak of informationInformation restrictionetc…)
• Time reduction – (Call CentersRetailE-commerceetc…)
• Data consolidation – (New solution is designed to become a SINGLE entry
point)
• Real time data – (Operational needsMonitoringetc…)

5. Security
Leak of information Information restriction

6. General approaches
• Information leakage
• Give only that piece of information that is needed for a
business role
• Avoid extra information sharing through “data export”
• Information falsification
• Control information changing through “Information
history”
• Automate as much as it possible. Avoid maximum
“manual’ interaction with data
• Information separation
• Between roles
• Between departments
• Between units
• Between organizations
Needs
• UI-based security
• Role is used to (hidedisplay) different parts of interface
• Role-based security
• Entity level access
• Role management is respected
• Company Hierarchy-based security
• Role based + subdivision based access
• Record-based security
• Restriction on (CRUD) operations
• Very difficult model. Uses within big enterprise products
Suggestion: be ready to cover “action
restriction” based on roles!

7. Example

8. Integration
Data consolidation Time Reduction

9. Purposes you need you know
Suggestion: try to use already developed
solutions for integrations from external vendors!
Possible issues you might have
• Data integration
• Ensures that information in multiple systems is kept
consistent.
• Vendor independence
• Extracts business policies or rules from applications and
implements them in the Enterprise Application system, so
that even if one of the business applications is replaced
with a different vendor's application, the business rules
do not have to be re-implemented.
• Common interface
• Providing a single consistent access interface to these
applications and shielding users from having to learn to
use different software packages.
Provided by - WIKI
• Other systems are not ready yet
• It means - no ready interfaces with detailed description
• To much rework
• Customer security policy
• Dev’s have to now about customer infrastructure as much
as they can
• Very high risk having problems on deployment stage
• No vision about architecture and
interaction between applications
• It can influence terms of the project

10. Reporting &
Data visualization
Process enhancement Real time data

11. Reporting
• Predefined dashboards for different
roles based on security level
• It helps to get answers quickly
• Internal staffCustomers
• Must be based on short period of time
to avoid performance issues
• Dayweek – depends on data amount
• Uses by C-level and decision-makers
mostly
Data visualization
• It might be intended for
• VendorsCustomersInternal staff
• Get as many reports examples as you
can (document analysis)
• Reports have to answer questions
• Try to build customizable solutions, to
cover customer needs fast
• Try to understand further path of report
life after is has been generated
• It can be prepared for other systempeopleetc…
• Is this reasonable to implement UI for
reports at the first stage of application?
• It might be enough to have exported data in Excel. Suggestion: Try to move reports into a
different subproject if it possible.

12. Examples

13. Data:
Cleaning Migration Maintaining
Transition requirements

14. Support Old
Clean
Maintain
• ImportExport
• Integration
Redesign Old
Clean
Migrate
Maintain
• ImportExport
• Integration
From scratch
Migrate
Maintain
• ImportExport
• Integration
• Let a customer know about it!
• What and why it is needed!
• Prepare a customer for it!
• How who when ?
• Define sources for data migration at the beginning!
• Docs – excelWord and other silly sources
• Other Software

15. Data maintenance
• Without correct data the application is nothing!
• Be aware of maintenance process.
• How?
• By whom?
• How often?
• It is always a separate module!
• Start to talk about at the beginning!
• Discuss continuous delivery and data saving on production
• Customer doesn't want to “Remove” all his data after each release or hot
fix!!!
• It will increase efforts to cover these needs.

16. Example

17. General User Needs
Features

18. Need Solution Comment
The user needs to be able to find certain record
visually quickly
Data Grid The user sees a list of record with header (like Excel)
The user must be able to find certain record
quickly
Quick search within an entity
Within a list of ContactsAccountsInvoicesEtc…
By NamePhone NumberDescription…
The user must have an ability to filter data based
on different criteria
Simple and Advanced filter
Simple Filter on Grid (Like Excel). Advanced Filter has to
be developed as a separate solution.
The user needs to make quick calls to the
customer
Integration with third-party software
AsteriskCiscoSkypeSkype For BusinessEtc.
The user clicks on a phone number.
The user has to be able to populate “lookup”
attributes quickly
Autocomplete lookup field
Autocomplete may work based on different attributes
from this entity.
The user has to be able to customize some parts
of a system, to make work more efficient
• Data Views
• Filters
• Dashboards (DiagramViewMapEtc…)
The amount of workers inside international companies
are huge! You cannot build one solution for everyone.
Different people on one position can use different
approaches.
The user needs to be able to see information
about related entity at one screen
Related view based on Lookup information
At a “Phone Call Card”, the user selects “person’ and
information about this person appears in a related view.
The user must be able to work with data in
hierarchical structure
Hierarchical structure with data grid
(viewedit)
Is used for financial information.
Work with: Revenue plan Actual Revenue Etc
The user must be able to leave comments Text editor It is used almost anywhere.

19. General
recommendations
Some comments from my experience

20. Kick-off
meeting
Who is who
Approaches
Getting
information
Document
Analysis
Onsite
Launching on
production
Be inside
Trainings
Think about
documentation

21. USA HQ
Toll Free: 866-687-3588
Tel: +1-512-516-8880
Ukraine HQ
Tel: +380-32-240-9090
Bulgaria
Tel: +359-2-902-3760
Germany
Tel: +49-69-2602-5857
Netherlands
Tel: +31-20-262-33-23
Poland
Tel: +48-71-382-2800
UK
Tel: +44-207-544-8414
EMAIL
info@softserveinc.com
WEBSITE:
www.softserveinc.com
Q&A