Cloud Implementation Scoping

Guidelines, Deliverables Reusable Assets,

Assumptions & Constraints
Scoping Guidelines

2
High Impact Factors Impacting Estimations
• Quantified Features & Functionality based Scoping - No More Modular (see next)
• Number of of Business Processes Implemented
• Number of of Distinct Roles
• Global or Large Multi-Site Projects
• Deployment Planning ( No of Releases/ Phases/ Regions)
• Localizations (Languages, Currencies)
• Additional Prototype and System Test Cycles
• No of Environments (Multi-pillar Environment requires more than 2 pods)
• No & Complexity of Conversions & Interfaces
• Custom Development – Extensibility
• Change Management activities
Scope (Application)- Example
Item included in scope
Enterprise structures
Work Structures
Security
Countries
Languages in addition to English
Additional Data Fields
Payroll, Salary and element
Employment Conracts stored
Portrait Gallery
Workflows
Quantified Features & Functionality based Scoping - No More
Modular
Descriptions
•Configure customer specific organizations:
•Up to two (2) Legal Entities
•Up to two (2) Data Groups
•Up to two (2) Business Units
•Configure Up to one (1) Ref Data Set, Set Assignments (set ID)
•Configure one (1) Enterprise
•Position & Grade – Not recommended
•10 Jobs defined as required by the user and can extend by user as
applicable
•Load one file of jobs, locations, departments
Up to four (4) customer specific Roles : HR Manager, HR Specialist,
Employee, Manager,
Only one(1) Country is included in the scope.
Only one(1) Language is included in the scope.
Up to one (1) Data Field
1 each
No
Load one (1) file of Portraits
Configure up to one (1) Workflow
4
 EXAMPLE - Scope – Core HCM – Process based Scoping
Processes in scope
Personnel Administration
Add person
Enable worker
Manage Employment
information
Manage personal information
Promote worker
Transfer worker
Terminate worker
Report on Personnel data
Social Network
Manage Social Profile
Manage Connections
Manage Social Groups
Item included in scope
Enterprise structures
Work Structures
Security
Countries
Languages in addition to English
Additional Data Fields
Payroll, Salary and element
Employment Conracts stored
Portrait Gallery
Workflows
Descriptions
• Configure customer specific organisations:
• LegalEntities_HCM, DATAGroups, Bus Groups
• Configure , data Sets Set Assignments (set ID)
• Configure one (1) Enterprise
• Position & Grade – Not recommended
• Ten (10) Jobs defined as required by the user, can be extended by user as applicable
• Load one file of jobs, locations, departments
HR Manager, HR Specialist, Employee, Manager,
One (1) each
No
Load one (1) file of Portraits
5
Assumptions

6
 Key Assumptions Categories
FIXED SCOPE
• Cloud Environment & Upgrade
OFFERING FOR
ORACLE FUSION
• Customer Users
TALEO CLOUD

• Training, testing & Change management

• Oracle Support & Methodology
• Location & Language
• Reports
• Data migration

7
 Key Assumptions – Cloud Environment & Upgrades
FIXED SCOPE
• Upgrade
OFFERING of Fusion Application during project is out of the scope of the project
FOR and subject to CRs
ORACLE FUSION
• Implementation
TALEO CLOUD is for Oracle Cloud Services hosted by Oracle Corporation
• Oracle would be responsible for providing and managing Test and Production environment
• In the SaaS deployment model, two project environments are available: a Staging and a Production
environment. Oracle Cloud Services Team will be responsible for hosting these two zones
• Single sign-on solution should be evaluated and factored in separately
• The Customer will have procured appropriate Cloud Application license subscriptions prior to project
start.
• All “Configure” activities and workshops are executed on the same environment (Staging environment)

8
 Key Assumptions – Customer Users
FIXED SCOPE
• Key Users
OFFERING FOR for each Business area are identified before the project commencement. The
ORACLE FUSIONwill be available during the implementation
key users
TALEO CLOUD
• There will be a Customer project manager to lead Customer staff’s efforts. A small and
tight project organization will be established.
• Customer project members are available for workshops and output reviews. These will
be experienced and empowered business and IT users to work closely with Partner's
consultants according to project plan (some full-time allocation may be necessary at
times).
• A small Project team is formed and empowered to make decisions
• Key business for each business area are identified before the project commencement.
The key users will be available during the implementation.

9
 Key Assumptions – Training, Testing & Change mgmt.
FIXED SCOPE
• Training is based on generic training material, delivered using a classroom
OFFERING FOR
ORACLE FUSION
based on “train the trainer” approach in a single location with a maximum of
TALEO CLOUD
10 attendees.
• System testing will be limited to only those items included in this scope of
work.
• Performance Testing and Change Management is not included.
• Organization change Management and end user training will be customer’s
responsibility

10
 Key Assumptions – Methodology & Support
FIXED SCOPE
• Oracle Unified Method for cloud would be used as base for the project
OFFERING FOR
ORACLE FUSION
execution
TALEO CLOUD

• Implementing any requirement, which is not a standard feature of the product,

will not be binding on Partner. The same will be agreed on based upon on
comments received from Oracle using the My Oracle Support
• At the end of the project all the open service requests will be transferred to
the customer technical team for further follow up, resolution and closure

11
 Key Assumptions – Language & Locations
FIXED SCOPE
• The project execution will be done using an onsite-offshore mix model. Project
OFFERING FOR
ORACLE FUSION
delivery will be conducted with limited on-site visits. Most services will be
TALEO CLOUD
provided from our location. The exact mix of on-site and off-site services will
be determined after pre-analysis work is done.
• All development and documentation will be done in English language.
• All key users of client would be available at common location for all project
execution activities including Key User Training and Testing.

12
Reporting Assumptions
• List of seeded Oracle Fusion Reports will be shared with the client
• In case of custom report requirements,
 The requirements are identified well in advance.
 The client will provide the report samples with report columns,
parameters, conditions as part of the requirement. Any clarifications that
shall be required will be sought by Partner.
 Data (setup and conversion and input on report layout) will be delivered
by customer in the layout required by Partner.
• The reports will be developed using OTBI and BI Publisher tools available
within Oracle Cloud
• Different format of the report output will be considered as a separate
report

1
3
 Data Migration Assumptions
• Customer needs to provide the data in the format submitted by the partner for transactional and master data
migration.
• Customer will assume the responsibility for Data extraction from legacy system, data cleaning & mapping and
filling in the format submitted by Partner for master & transactional data
• Fusion Cloud Service only supports File Based Loader for data loads. Automated interfaces are not available and
any data to be uploaded to Fusion will require a manual intervention for creation of the data as per the file
based loader templates.
• Customer will assume the responsibility of any data migration objects that are not supported by Oracle’s FBDI
or ADFDi templates
• Partner will give clarifications of what data is required in what format in one of the meetings organized for
same. Post that, client will assume the responsibility to provide the data requested in timely manner and
format requested after necessary validations and checks. The same data shall be loaded in test environment
and key users shall be responsible for sanity testing of the data
• Customer will assume the responsibility of mapping legacy system account codes with the Oracle account codes
and accordingly have to fill up the templates for data migration/data collections provided by Partner

1
4
Client Responsibilities

1
5
Client Responsibilities
 Client to finalize license agreements and get staging environment provisioning from Oracle for the
cloud applications prior to start of the project
 Arrange for a Project Executive Sponsor and Project Steering Committee
 Assign a Project Manager to lead your staff’s efforts
 Assign experienced and empowered Business and IT users to work closely with Partner
consultants according to project plan (some full-time allocation may be necessary at times).
 Perform independently various project tasks according to project plan such as: (a) Provide data in
format specified by Partner b) Customer side of Integration c) Perform UAT d) End user Training
 Process & policy standardization across the organization has to be done by the customer prior to
start of the engagement
 Provide timely sign off of the deliverables within the timeframe agreed upon before start of
engagement
 Handle Change Management
 Communicate project status to entire organization on timely basis
 Train End users – (Cloud Follows the Train the trainer approach)

1
6
Project Deliverables

1
7
Project Deliverables by Description

Project Phase Deliverable Name Brief Description

Design Project Plan (Charter) A plan that describes the tasks and timelines for all project activities.
The project charter would include further details of the project mission
Design Project Charter
statement, approach, plan, scope and execution.
List of Questions in order to understand the business processes and
Design HLA Questionnaire
configuration requirements
Design Data Templates Templates for collecting Data to be migrated to the Fusion Application
Configure Business Process Walkthrough(CRP) Application Configured to the Business Process Walkthrough
Configure Business Processes Document Solution write-ups with descriptions of business processes in scope
Prioritisation method is used to decide which requirements must be
Configure MoSCoW List
completed first and which must come later or will not be completed at all
Configure Train the Trainer Application configured on the Stage Environment for Key User Training
Configure Training Material Training Manuals for the Key Users for application familiarization
Configure Test Scripts Test scripts that will form the basis of End to End review
Transition Configuration Workbook(Optional) Document detailing how the Application is Configured
Transition Configured Production Environment Production System configured as per the agreement and SoW

1
8
Quiz !

Oracle Confidential –
Internal/Restricted/Highly Restricted