Oum Cloud Application Services Implementation Approach SDG

ORACLE UNIFIED METHOD
CLOUD APPLICATION SERVICES

IMPLEMENTATION APPROACH
SOLUTION DELIVERY GUIDE
Release 2.0
June 2013
OUM Cloud Application Services Implementation Approach Solution Delivery Guide, Release 2.0
Copyright © 2012, 2013, Oracle and/or its affiliates. All rights reserved. This document is provided for information
purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be
error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including
implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this
document. This document may not be reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of
Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Authors: Oracle's Global Methods Team

CONTENTS
C H A P T E R 1 Introduction ................................................................................................ 1-1
What is the OUM Cloud Application Services Implementation

Approach?..............................................................................................1-2
How to Use This Guide ..........................................................................1-3

Contributors .....................................................................................1-3
Your Feedback is Requested ..........................................................1-3
C H A P T E R 2 Approach Overview ................................................................................... 2-1
Scope .....................................................................................................2-2
Objectives ..............................................................................................2-3
Approach Overview................................................................................2-4
Core and Optional Tasks .......................................................................2-6

Core and Optional Tasks in the OUM Cloud Application
Services Implementation Approach ................................................2-6
Task Selection Guidelines...............................................................2-6
Important Concepts................................................................................2-7
Division of Responsibility.................................................................2-7
Project Management .......................................................................2-7
Iterative Prototyping Workshops .....................................................2-8
C H A P T E R 3 Project Start Up (PS) Phase ..................................................................... 3-1
Project Start Up Phase Objectives ........................................................3-2
PS.ACT.RBC – Review Bid and Contract (Core) ..................................3-5

Activity/Task Group .........................................................................3-5
Work Product...................................................................................3-5
Prerequisites....................................................................................3-5
Approach .........................................................................................3-6
Roles and Responsibilities ..............................................................3-6
PS.ACT.RPAC – Review Project Assets with Client (Core) ..................3-7
Work Product...................................................................................3-7
Prerequisites....................................................................................3-7
Global Methods Contents i

Approach......................................................................................... 3-7
Roles and Responsibilities.............................................................. 3-8
PS.ACT.VSSOS – Validate Scope and Stakeholders (Core) ............... 3-9
Activity/Task Group......................................................................... 3-9
Work Product .................................................................................. 3-9
Prerequisites ................................................................................... 3-9
Approach....................................................................................... 3-10
Roles and Responsibilities............................................................ 3-10
PS.ACT.DW – Develop Workplan (Core)............................................ 3-11
Activity/Task Group....................................................................... 3-11
Work Product ................................................................................ 3-11
Prerequisites ................................................................................. 3-11
Approach....................................................................................... 3-11
PS.ACT.DSPB – Develop Staff Plan and Budget (Core) .................... 3-12
Work Product ................................................................................ 3-12
Prerequisites ................................................................................. 3-12
Approach....................................................................................... 3-12
PS.ACT.CPMP – Create Project Management Plan (Core) ............... 3-14
Work Product ................................................................................ 3-14
Prerequisites ................................................................................. 3-14
Approach....................................................................................... 3-15
PS.ACT.EPI – Establish Project Infrastructure (Core) ........................ 3-16
Work Product ................................................................................ 3-16
Prerequisites ................................................................................. 3-16
Approach....................................................................................... 3-16
C H A P T E R 4 Plan (A) Phase ............................................................................................4-1
Plan Phase Objectives .......................................................................... 4-2
STM.050 – Conduct Kick-Off Meeting (Core) ....................................... 4-6

Work Product .................................................................................. 4-6
Prerequisites ................................................................................... 4-6
Approach......................................................................................... 4-6
TR.050 – Train Project Team (Optional) ............................................... 4-7
Work Product .................................................................................. 4-7
Prerequisites ................................................................................... 4-7
Approach......................................................................................... 4-7
WM.070 – Schedule Workshops (Core)................................................ 4-8
Contents ii OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Work Product...................................................................................4-8
Prerequisites....................................................................................4-8
Approach .........................................................................................4-8
WM.010 – Create Detailed Plan for Current Release (Core) ..............4-10
Activity/Task Group .......................................................................4-10
Work Product.................................................................................4-10
Prerequisites..................................................................................4-10
Approach .......................................................................................4-10
Roles and Responsibilities ............................................................4-11
RD.011.1 – Review In-Scope High-Level Business
Processes (Core) .................................................................................4-12
Work Product.................................................................................4-12
Prerequisites..................................................................................4-12
Approach .......................................................................................4-12
MC.040.1 – Gather Setup Information (Core) .....................................4-13
Work Product.................................................................................4-13
Prerequisites..................................................................................4-13
Approach .......................................................................................4-13
TA.030 – Conduct Integration Workshop (Core) .................................4-15
Work Product.................................................................................4-15
Prerequisites..................................................................................4-15
Approach .......................................................................................4-15
CV.010 – Conduct Data Load Workshop (Core) .................................4-17
Work Product.................................................................................4-17
Prerequisites..................................................................................4-17
Approach .......................................................................................4-17
DO.010 – Define Documentation Requirements and
Strategy (Optional)...............................................................................4-19
Work Product.................................................................................4-19
Prerequisites..................................................................................4-19
Approach .......................................................................................4-19
OCM.015 – Identify Process Change Candidates (Optional)..............4-21
Work Product.................................................................................4-21
Prerequisites..................................................................................4-21
Approach .......................................................................................4-21
Global Methods Contents iii

OCM.035 – Create Change Plan (Optional) ....................................... 4-22
Work Product ................................................................................ 4-22
Prerequisites ................................................................................. 4-22
Approach....................................................................................... 4-22
OCM.065 – Provide Stakeholder / End User Analysis
Guidance (Optional) ............................................................................ 4-23
Work Product ................................................................................ 4-23
Prerequisites ................................................................................. 4-23
Approach....................................................................................... 4-23
WM.050.1 – Conduct Implementation Checkpoint (Core) .................. 4-24
Work Product ................................................................................ 4-24
Prerequisites ................................................................................. 4-24
Approach....................................................................................... 4-24
A.PEC.TSK – Manage Project Execution (Core) ................................ 4-26
Work Product ................................................................................ 4-26
Prerequisites ................................................................................. 4-26
Approach....................................................................................... 4-27
A.PGM.TSK – Program Management (Optional) ................................ 4-28
Work Product ................................................................................ 4-28
Prerequisites ................................................................................. 4-28
Approach....................................................................................... 4-28
C H A P T E R 5 Prototype (B) Phase ...................................................................................5-1
Prototype Phase Objectives .................................................................. 5-2
MC.060.1 – Perform Initial Setup (Core) ............................................... 5-8

Work Product .................................................................................. 5-8
Prerequisites ................................................................................... 5-8
Approach......................................................................................... 5-8
TE.020 – Prepare Validation Scripts (Core).......................................... 5-9
Work Product .................................................................................. 5-9
Prerequisites ................................................................................... 5-9
Approach......................................................................................... 5-9
MC.070 – Conduct Workshops and Prototype Configuration (Core).. 5-11
Contents iv OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Work Product.................................................................................5-11
Prerequisites..................................................................................5-11
Approach .......................................................................................5-11
MC.040.2 – Capture and Prioritize Additional Configurations (Core)..5-13
Work Product.................................................................................5-13
Prerequisites..................................................................................5-13
Approach .......................................................................................5-13
MC.050.1 – Update Setup Documentation (Core)...............................5-14
Work Product.................................................................................5-14
Prerequisites..................................................................................5-14
Approach .......................................................................................5-14
MC.063 – Conduct Configuration Familiarization Session (Core).......5-16
Work Product.................................................................................5-16
Prerequisites..................................................................................5-16
Approach .......................................................................................5-16
DS.140.1 – Prepare Detailed Technical Specification –
Fusion (Optional) .................................................................................5-18
Work Product.................................................................................5-18
Prerequisites..................................................................................5-18
Approach .......................................................................................5-18
DS.140.2 – Prepare Detailed Technical Specification – Client
Systems (Optional) ..............................................................................5-20
Work Product.................................................................................5-20
Prerequisites..................................................................................5-20
Approach .......................................................................................5-21
CV.027.1 – Perform Data Mapping (Optional).....................................5-22
Work Product.................................................................................5-22
Prerequisites..................................................................................5-22
Approach .......................................................................................5-22
CV.053 – Populate Data Load Templates with Client Data (Core) .....5-23
Work Product.................................................................................5-23
Prerequisites..................................................................................5-23
Approach .......................................................................................5-23
MC.060.2 – Apply Setup Changes (Core) ...........................................5-24
Global Methods Contents v

Work Product ................................................................................ 5-24
Prerequisites ................................................................................. 5-24
Approach....................................................................................... 5-24
MC.065.1 – Validate Setup Changes (Core)....................................... 5-26
Work Product ................................................................................ 5-26
Prerequisites ................................................................................. 5-26
Approach....................................................................................... 5-26
MC.050.2 – Document Functional Security (Core) ............................. 5-27
Work Product ................................................................................ 5-27
Prerequisites ................................................................................. 5-27
Approach....................................................................................... 5-27
MC.085 – Prepare Reports (Core) ...................................................... 5-29
Work Product ................................................................................ 5-29
Prerequisites ................................................................................. 5-29
Approach....................................................................................... 5-29
MC.050.3 – Update Setup Documentation (Core) .............................. 5-30
Work Product ................................................................................ 5-30
Prerequisites ................................................................................. 5-30
Approach....................................................................................... 5-30
MC.060.3 – Implement Workflows (Optional) ..................................... 5-31
Work Product ................................................................................ 5-31
Prerequisites ................................................................................. 5-31
Approach....................................................................................... 5-31
MC.060.4 – Implement Notifications (Optional) .................................. 5-32
Work Product ................................................................................ 5-32
Prerequisites ................................................................................. 5-32
Approach....................................................................................... 5-32
MC.060.5 – Implement FastFormulas (Optional) ................................ 5-33
Work Product ................................................................................ 5-33
Prerequisites ................................................................................. 5-33
Approach....................................................................................... 5-33
MC.060.6 – Implement FlexFields (Optional)...................................... 5-34
Contents vi OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Work Product.................................................................................5-34
Prerequisites..................................................................................5-34
Approach .......................................................................................5-34
MC.060.7 – Implement Localizations (Optional)..................................5-35
Work Product.................................................................................5-35
Prerequisites..................................................................................5-35
Approach .......................................................................................5-35
MC.060.8 – Implement Composer Updates (Optional) .......................5-36
Work Product.................................................................................5-36
Prerequisites..................................................................................5-36
Approach .......................................................................................5-36
MC.065.2 – Validate Setup Changes (Optional) .................................5-37
Work Product.................................................................................5-37
Prerequisites..................................................................................5-37
Approach .......................................................................................5-37
RD.011.2 – Update Business Processes (Core) .................................5-38
Work Product.................................................................................5-38
Prerequisites..................................................................................5-38
Approach .......................................................................................5-38
TE.027.1 – Update Validation Cases (Core) .......................................5-39
Work Product.................................................................................5-39
Prerequisites..................................................................................5-39
Approach .......................................................................................5-39
IM.050.1 – Implement Integration Packages – Fusion (Optional) .......5-40
Work Product.................................................................................5-40
Prerequisites..................................................................................5-40
Approach .......................................................................................5-40
IM.050.2 – Implement Integration Packages – Client
Systems (Optional) ..............................................................................5-42
Work Product.................................................................................5-42
Prerequisites..................................................................................5-42
Approach .......................................................................................5-42
IM.050.3 – Load and Validate Data to Client Systems (Optional) .......5-44
Global Methods Contents vii

Work Product ................................................................................ 5-44
Prerequisites ................................................................................. 5-44
Approach....................................................................................... 5-44
TE.045 – Validate Integration Packages (Optional) ............................ 5-46
Work Product ................................................................................ 5-46
Prerequisites ................................................................................. 5-46
Approach....................................................................................... 5-46
CV.065.1 – Load, Reconcile and Validate Data (Core) ...................... 5-47
Work Product ................................................................................ 5-47
Prerequisites ................................................................................. 5-47
Approach....................................................................................... 5-47
OCM.145 – Provide Change Impact Assessment
Approach (Optional) ............................................................................ 5-48
Work Product ................................................................................ 5-48
Prerequisites ................................................................................. 5-48
Approach....................................................................................... 5-48
WM.050.2 – Conduct Implementation Checkpoint (Core) .................. 5-50
Work Product ................................................................................ 5-50
Prerequisites ................................................................................. 5-50
Approach....................................................................................... 5-50
B.PEC.TSK – Manage Project Execution (Core) ................................ 5-51
Work Product ................................................................................ 5-51
Prerequisites ................................................................................. 5-51
Approach....................................................................................... 5-52
B.PGM.TSK – Program Management (Optional) ................................ 5-53
Work Product ................................................................................ 5-53
Prerequisites ................................................................................. 5-53
Approach....................................................................................... 5-53
C H A P T E R 6 Validate (C) Phase ......................................................................................6-1
Validate Phase Objectives .................................................................... 6-2
OCM.165 – Facilitate Change Enablement Plan (Optional) ................. 6-6

Work Product .................................................................................. 6-6
Prerequisites ................................................................................... 6-6
Approach......................................................................................... 6-6
Contents viii OUM Cloud Application Services Implementation Approach Solution Delivery Guide
CV.065.2 – Load, Reconcile and Validate Data (Core) .........................6-7
Work Product...................................................................................6-7
Prerequisites....................................................................................6-7
Approach .........................................................................................6-7
MC.060.9 – Apply Setup Changes (Core) .............................................6-8
Work Product...................................................................................6-8
Prerequisites....................................................................................6-8
Approach .........................................................................................6-8
MC.050.4 – Update Setup Documentation (Core).................................6-9
Work Product...................................................................................6-9
Prerequisites....................................................................................6-9
Approach .........................................................................................6-9
RD.011.3 – Update Business Processes (Core) .................................6-10
Work Product.................................................................................6-10
Prerequisites..................................................................................6-10
Approach .......................................................................................6-10
TE.027.2 – Update Validation Cases (Core) .......................................6-11
Work Product.................................................................................6-11
Prerequisites..................................................................................6-11
Approach .......................................................................................6-11
TE.105 – Prepare Users for Validation (Core).....................................6-12
Work Product.................................................................................6-12
Prerequisites..................................................................................6-12
Approach .......................................................................................6-12
TE.070 – Conduct End-to-End Review (Core) ....................................6-13
Work Product.................................................................................6-13
Prerequisites..................................................................................6-13
Approach .......................................................................................6-13
DO.070 – Publish User Guide (i.e., Job Aid) (Optional) ......................6-15
Work Product.................................................................................6-15
Prerequisites..................................................................................6-15
Approach .......................................................................................6-15
DO.075 – Publish Admin Guide (Optional) ..........................................6-17
Global Methods Contents ix

Work Product ................................................................................ 6-17
Prerequisites ................................................................................. 6-17
Approach....................................................................................... 6-17
TR.080 – Prepare Training Material (Core)......................................... 6-19
Work Product ................................................................................ 6-19
Prerequisites ................................................................................. 6-19
Approach....................................................................................... 6-19
TR.085 – Translate Training Material (Optional)................................. 6-21
Work Product ................................................................................ 6-21
Prerequisites ................................................................................. 6-21
Approach....................................................................................... 6-21
TR.095 – Conduct Train-the-Trainer Workshops (Core)..................... 6-23
Work Product ................................................................................ 6-23
Prerequisites ................................................................................. 6-23
Approach....................................................................................... 6-23
C WM.050.3 – Conduct Implementation Checkpoint (Core)............... 6-24
Work Product ................................................................................ 6-24
Prerequisites ................................................................................. 6-24
Approach....................................................................................... 6-24
C.PEC.TSK – Manage Project Execution (Core) ................................ 6-26
Work Product ................................................................................ 6-26
Prerequisites ................................................................................. 6-26
Approach....................................................................................... 6-27
C.PGM.TSK – Program Management (Optional)................................ 6-28
Work Product ................................................................................ 6-28
Prerequisites ................................................................................. 6-28
Approach....................................................................................... 6-28
C H A P T E R 7 Transition (D) Phase...................................................................................7-1
Transition Phase Objectives.................................................................. 7-2
TS.050 – Migrate Configuration to Production (Core)........................... 7-5

Work Product .................................................................................. 7-5
Prerequisites ................................................................................... 7-5
Approach......................................................................................... 7-5
Contents x OUM Cloud Application Services Implementation Approach Solution Delivery Guide
CV.065.3 – Load, Reconcile and Validate Data Loads in
Production (Core)...................................................................................7-6
Work Product...................................................................................7-6
Prerequisites....................................................................................7-6
Approach .........................................................................................7-6
TE.120 – Conduct Final Validation Review with Users and
Stakeholders (Core)...............................................................................7-7
Work Product...................................................................................7-7
Prerequisites....................................................................................7-7
Approach .........................................................................................7-7
TR.100 – Conduct End-User Training (Core) ........................................7-9
Work Product...................................................................................7-9
Prerequisites....................................................................................7-9
Approach .........................................................................................7-9
TS.052 – Implement Support Infrastructure (Core) .............................7-10
Work Product.................................................................................7-10
Prerequisites..................................................................................7-10
Approach .......................................................................................7-10
TS.058 – Verify Production and Operational Readiness (Core)..........7-11
Work Product.................................................................................7-11
Prerequisites..................................................................................7-11
Approach .......................................................................................7-11
TS.060 – Begin System Use (Core) ....................................................7-13
Work Product.................................................................................7-13
Prerequisites..................................................................................7-13
Approach .......................................................................................7-13
D.PEC.TSK – Manage Project Execution (Core) ................................7-14
Work Product.................................................................................7-14
Prerequisites..................................................................................7-14
Approach .......................................................................................7-15
D.PGM.TSK – Program Management (Optional) ................................7-16
Work Product.................................................................................7-16
Prerequisites..................................................................................7-16
Global Methods Contents xi

Approach....................................................................................... 7-16
C H A P T E R 8 Sustain (E) Phase .......................................................................................8-1
Sustain Phase Objectives ..................................................................... 8-2
PS.005 – Manage Transition to Steady-State Operations (Core)......... 8-4

Work Product .................................................................................. 8-4
Prerequisites ................................................................................... 8-4
Approach......................................................................................... 8-4
PS.140 – Plan for Next Release (Core) ................................................ 8-5
Work Product .................................................................................. 8-5
Prerequisites ................................................................................... 8-5
Approach......................................................................................... 8-5
PS.065 – Post Go-Live Support (Core) ................................................. 8-6
Work Product .................................................................................. 8-6
Prerequisites ................................................................................... 8-6
Approach......................................................................................... 8-6
OCM.265 – Perform Change Completion Check Point (Optional)........ 8-7
Work Product .................................................................................. 8-7
Prerequisites ................................................................................... 8-7
Approach......................................................................................... 8-7
E.PEC.TSK – Manage Project Execution (Core) .................................. 8-8
Work Product .................................................................................. 8-8
Prerequisites ................................................................................... 8-8
Approach......................................................................................... 8-9
E.PGM.TSK – Program Management (Optional) ................................ 8-10
Work Product ................................................................................ 8-10
Prerequisites ................................................................................. 8-10
Approach....................................................................................... 8-10
C H A P T E R 9 Project Closure (PC) Phase......................................................................9-1
Project Closure Phase Objectives......................................................... 9-2
PC.ACT.GA – Gain Acceptance (Core) ................................................ 9-4

Work Product .................................................................................. 9-4
Contents xii OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Prerequisites....................................................................................9-4
Approach .........................................................................................9-4
PS.ACT.CPC – Close Processes and Contract (Core) .........................9-5
Work Product...................................................................................9-5
Prerequisites....................................................................................9-5
Approach .........................................................................................9-5
PS.ACT.DLLAP – Document Lessons Learned and Archive
Project (Core).........................................................................................9-7
Work Product...................................................................................9-7
Prerequisites....................................................................................9-7
Approach .........................................................................................9-7
APPENDIX A Work Breakdown Structure ......................................................................A-1

How to Read the Work Breakdown Structure ................................ A-1
OUM Cloud Application Services Implementation
Approach WBS ............................................................................... A-1
Global Methods Contents xiii

CHAPTER
1 Introduction
T he OUM Cloud Application Services Implementation Approach Solution Delivery

Guide provides an overview of the approach, phases, activities and tasks that define
the OUM Cloud Application Services Implementation approach. The information in
this guide enables project managers, and project team members, to better understand
the full scope of an OUM Cloud Application Services implementation, and to plan and
execute those engagements.
Global Methods Introduction 1 - 1

What is the OUM Cloud Application Services Implementation Approach?
The Oracle® Unified Method (OUM) Cloud Application Services Implementation
Approach is Oracle’s lightweight approach for implementing Fusion Applications running
on a cloud infrastructure. It emphasizes an out-of-the-box approach and adoption of best
practices inherent in the Fusion Application products as a foundational element of the
approach.
Introduction 1 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
How to Use This Guide
The OUM Cloud Application Services Implementation Approach Solution Delivery Guide
contains general information about using this approach for Fusion Applications Cloud
implementation projects.
Contributors
Catherine Anderson, Steve Angelo, Anthony Bartolotto, Rob Boucher, David Burke, Terry
Chan, Bruce Dehner, Dave Edgecomb, Khaled Eldarawy, Mark Garlen, Peter Hammond,
Lieven Heymans, Sriram Krishnan, Jason Livingston, Linda Lowitz, Won Park, Tushar
Roy, Alok Sahay, Tim Sent, Tom Spitz, Ken Thompson, Louann Weaver, Marco van der
Peet, Eric Wendlandt
Your Feedback is Requested

Global Methods values and appreciates your comments as an Oracle practitioner and
reader of this guide. As we write, revise, and evaluate our documentation and other
delivery materials, your comments are the most valuable input we receive. If you would
like to contact us regarding comments on this manual, or other OUM Cloud Application
Services Implementation Approach materials, please use the following email address:
mailto:ominfo_us@oracle.com
Global Methods Introduction 1 - 3

CHAPTER
2 Approach Overview
T he OUM Cloud Application Services Implementation Approach is being introduced to

support the implementation of Fusion Applications running on a cloud infrastructure.
It provides a lightweight, nimble approach for Fusion SaaS implementations.
While the approach does not adhere to the work breakdown structure previously defined
for the OUM Implement Focus Area views, it does embody many of the principles on
which OUM is based.
Global Methods Approach Overview 2 - 1

Scope
The OUM Cloud Application Services Implementation Approach is applicable to Fusion
Applications implementations running on a cloud infrastructure that leverage Fusion
Applications fixed scope offerings from Oracle Consulting and Oracle’s implementation
partners, as a starting point.
While the focus of the approach is on the rapid implementation of the functionality within
the predefined boundaries of the Fusion fixed scope offerings, selected for
implementation, the approach also includes support for selected, additional services
(beyond the scope of the those offerings) including, additional configurations, additional
data loads, additional integrations, etc.
Approach Overview 2 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Objectives
The objectives of the OUM Cloud Application Services Implementation Approach follow:
• Rapid design, configuration and deployment of an initial release of the software

solution consisting of standard functionality within the predefined boundaries of
the Fusion Applications fixed scope offerings selected for implementation.
• Emphasis on getting clients up and using the new system in less time and at a
lower cost.
• Maximize use of best practices inherent in the product.
• Implementation of standard business rules, standard integrations and standard
data loads.
• To the extent possible, implementation of additional functionality and custom
integrations, etc. (that is, additional services) should be addressed in subsequent
releases.

Approach Overview
The diagram below depicts the key activities that describe the OUM Cloud Application
Services Implementation Approach. While it clearly does not reflect all of the activities
that might be performed during an engagement, it does represent the “Top Level Flow” of
activities that define the approach.
The approach is comprised of 5 phases – Plan, Prototype, Validate, Transition and

Sustain.
The Plan phase is the first phase in the OUM Cloud Application Services Implementation
Approach and is critical for establishing a positive impression, and setting appropriate
expectations, with the client. During this phase, a kick-off meeting is held to orient the
entire project team to the project objectives and how the project will be conducted.
Workshops for gathering setup information and disseminate information regarding the
integrations and data loads are scheduled. A detailed plan for the current release is
prepared and applicable business processes reviewed. Previously scheduled workshops
to gather initial setup information are conducted, as well as workshops to communicate
Fusion integration concepts and data conversion options.
At the outset of the Prototype phase, the Staging Environment is configured using the
initial setup values collected during the Plan phase. An initial set of prototyping
workshops are then conducted with a focus on reviewing the standard functionality as
configured in the Staging Environment, collecting feedback, prototyping refinements and
capturing and prioritizing additional configuration settings.
Client personnel have responsibility for updating the Fusion Business Processes and
validation cases, as necessary, to reflect the resulting configuration.
If custom data loads, or integrations, are within the scope of the project, technical
specifications are also prepared, and the integrations built, during the Prototype phase.
Data load templates are populated with Client data and subsequently uploaded to the
Staging Environment.
A second set of prototyping sessions conducted during the Prototype Phase is focused
on applying and validating configuration changes, which may include extensible items
such as workflows, notifications, FastFormulas, FlexFields, localizations and composer
updates, as well as validating required integrations and data loads.
Activities during the Validate phase include the entry of any additional configuration
changes in the Staging Environment and the validation of those values. If necessary,
business processes and test cases are again updated to reflect the resulting state of the
environment and sample client data is loaded in preparation for an end-to-end review.
The end-to-end review conducted in the Validate phase is intended to validate the final
configuration, which will be used to configure the Production Environment in the next
phase. During the end-to-end review, a series of validation cases are executed to
validate the proper functioning of the software solution. The test cases should also
exercise the client data that has been loaded to the Staging Environment using the data
load templates to validate that the data has been loaded properly.
A train-the-trainer event is also held in the Validate phase to prepare designated client
personnel to train end users during the next phase in preparation for the new system
being placed in use.
The Transition phase focuses on moving the new software system and the organization
to active use. The validated configuration is migrated to the Production Environment, the
client data is loaded, and a final review is conducted with users and stakeholders to help
ensure that the new environment is ready for use. A production and operational
readiness assessment is made as a final checkpoint and the Transition phase concludes
with the new system being placed in use.
The Production phase begins active use of the system and, during the phase, the
transition to steady-state operations is managed. A key activity in the Production phase
is planning for the next release and making provisions for the appropriate maintenance
and governance of the new system.

Core and Optional Tasks
Cloud Application Services implementation projects may range from simple projects
involving only the configuration of standard functionality to more complex projects
requiring custom integrations, complex workflows, additional data loads, etc.
Core and Optional Tasks in the OUM Cloud Application Services Implementation Approach
The core tasks in the OUM Cloud Application Services Implementation Approach define
the minimum set of steps necessary to implement the functionality contained within the
predefined boundaries of Fusion Applications fixed scope offerings from Oracle
Consulting, or Oracle’s implementation partners. You may also need to include several
other tasks in your project depending on your specific circumstances. For example, if
your project includes custom integrations, or additional training or documentation
requirements, you may need to include several optional tasks that support those
additional services. A good test during project planning is to walk through the core tasks
and assess whether they will be sufficient to meet the project’s needs. If not, begin
considering optional tasks. This planning process should help create an efficient project
approach.
Task Selection Guidelines

Determining which optional tasks to include in the project plan is ultimately the
responsibility of the project manager. To assist you in making your determinations, a
number of optional task criteria, which serve as indicators for inclusion of related optional
tasks, have been identified. Use the optional task criteria, included in the task overview
for all tasks identified as optional, to determine which optional tasks to include in your
project.
Important Concepts
There are several key concepts that are important to understand in order to fully
appreciate the OUM Cloud Application Services Implementation Approach. These
concepts include:
• Division of Responsibility
• Project Management
• Iterative Prototyping Workshops
Division of Responsibility
Another key concept related to the OUM Cloud Application Services Implementation
Approach is the division of responsibility between Oracle and client resources. To help
achieve a lower implementation cost, a number of activities performed during the project
are shared between Oracle and client personnel. Where appropriate, some activities are
assigned solely to client resources, such as extracting data from client legacy systems.
Refer to the Responsibilities section of each phase chapter for a listing of the tasks by
responsibility. Each task description also contains a Roles and Responsibility section
delineating who is responsible for the completion of that task.
Project Management
The OUM Cloud Application Services Implementation Approach includes Project
Management Start Up, Execution and Control, and Project Closure tasks consistent with
the OUM Manage Focus area.
The above illustration demonstrates how the Project Management phases are integrated
with the OUM Cloud Application Services implementation phases to fully document the
OUM Cloud Application Services Approach. The Project Start Up phase typically begins

prior to the Plan phase, although, with very small projects, these phases may overlap.
The Project Execution and Control tasks are executed during the implementation phases,
and the Project Closure phase is conducted after the last implementation phase of the
project.
Because Cloud implementations tend to be smaller and less complex than the average
traditional OUM implementation, the OUM Cloud Application Services Approach Project
Management tasks are associated with the OUM Manage activity level to better scale to
the project management needs of an OUM Cloud implementation.
To simplify, and convey that the OUM Cloud Application Services Approach project
management tasks are not intended to be performed in a serial manner; activities are
included to group the project management tasks. These activities are unique to the OUM
Cloud Application Services Approach and do not relate to any structure in OUM Manage.
Project management in an OUM Cloud Application Services implementation is not

significantly different from project management in a traditional on-premises
implementation. The key difference is the depth of detail to which the project
management tasks and associated work products are produced. The OUM Cloud
Application Services Approach Solution Delivery Guide highlights the key steps to be
completed for each project management task. For more detailed task guidance,
approach information and deliverable templates, please refer to OUM Manage.
The activities and tasks generally associated with project management along with project
management leading practices; remain critical to any implementation project. The OUM
Cloud Application Services Approach draws upon this knowledge but also includes some
task steps and terms geared to Cloud implementations and not included in OUM
Manage. For example, the “Develop Workplan” task description includes references to a
high-level workplan and a release plan. Although OUM Manage does not use the term
release plan in its equivalent task guidance, the concept of creating an Implementation
Plan (i.e. high-level workplan) and an Iteration Plan (i.e. release plan) is described.
As with other OUM projects, managers should adhere to standard operating procedures
and customer-facing project management practices when executing an OUM Cloud
Application Services project, commensurate with the size and complexity of the
engagement.
Iterative Prototyping Workshops

Like other OUM approaches, the OUM Cloud Application Services Implementation
Approach takes an iterative approach to development and deployment of Fusion
Applications solutions. Iterative prototyping workshops are conducted during the
Prototype Phase to incrementally refine and validate the configuration that best meets
the client’s business needs.
During the iterative prototyping sessions, the full set of functionality selected for
implementation is partitioned into smaller subsets of that functionality. Each prototyping
workshop then concentrates on one or more of the smaller segments to refine and
validate that component of the overall solution, while taking into account any
dependencies inherent in other, related components. Each increment is considered in a
logical order until the overall solution has been reviewed, refined and validated.
CHAPTER
3 Project Start Up (PS)

Phase
T he goal of the Project Start Up phase is to review and agree on the scope of the
project with the client and to provide a clear framework for how the project will be
delivered.
A key output of the Project Start Up phase, the Project Management Plan, documents the
overall approach to the project including what needs to be done, who will do it and how
the project will be governed.
A critical success factor is a strong commitment to perform the project from the client. A
forum should be established to share the project status, risk and issues with the client
and obtain feedback.
Global Methods Project Start Up (PS) Phase 3 - 1

Project Start Up Phase Objectives
The objectives of the Project Start Up phase follow:
• Statement of work is reviewed and agreement with client obtained
• Project plan (including planned releases) is completed and base lined for project
planning and control
• Parties agree to their commitment related to the project
• Project budget is reviewed and finalized
• Project is staffed
• Infrastructure is established for issue, risk, problem tracking, configuration

management and scope change procedures
• Quality assurance tasks are planned
• Project team orientation is conducted
Project Start Up Phase Activities

The Project Start Up phase is comprised of the following activities:
• Review Bid and Contract
• Review Project Assets with Client
• Create Project Governance, policies and supporting infrastructure
Key Work Products

The key work products of the Project Start Up phase are as follows:
Work Product Description

Reviewed Project Assets The Reviewed Project Assets is a
result of the contract and project
approach being reviewed with the
client to arrive at a common
understanding of the project scope and
objectives.
Project Start Up (PS) Phase 3 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Validated Scope
The Validated Scope work product is a
result of validating that the contract
scope accurately reflects the contract
and the expectations of the client.
High-Level Project Workplan The High-Level Project Workplan

depicts the tasks that need to be
executed during the course of the
project. The high-level workplan
identifies the planned releases, but
may not contain the details of the
releases at this time.
Staff Plan and Budget The Staff Plan and Budget is

developed in conjunction with
developing the High-Level Project
Workplan. Using the contract and High
Level Project Workplan as input, the
project manager develops the staff
plan and the project budget.
Project Management Plan

The Project Management Plan defines
the governance approach to project
management by identifying how the
processes identified within OUM
Manage will be planned, executed and
controlled, monitored, and reported on.
Tasks and Work Products

The tasks and work products for this phase are:
ID Task Name Work Product Required When
PS.ACT.RBC Review Bid and Contract Confirmed Bid and Contract Always
PS.ACT.RPAC Review Project Assets with Client Reviewed Project Assets Always
PS.ACT.VSSOS Validate Scope and Stakeholders Validated Scope Always
PS.ACT.DW Develop Workplan High-Level Project Workplan Always
PS.ACT.DSPB Develop Staff Plan and Budget Staff Plan and Budget Always
PS.ACT.CPMP Create Project Management Plan Project Management Plan Always
PS.ACT.EPI Establish Project Infrastructure Project Infrastructure Always

Responsibilities
The Oracle Implementation team has primary responsibility for the following tasks in this
phase:
• PS.ACT.RBC Review Bid and Contract
• PS.ACT.VSSOS Validate Scope and Stakeholders
• PS.ACT.DW Develop Workplan
• PS.ACT.DSPB Develop Staff Plan and Budget
• PS.ACT.CPMP Create Project Management Plan
• PS.ACT.EPI Establish Project Infrastructure
The Oracle Implementation team and the client have a shared responsibility for the
following tasks in this phase:
• PS.ACT.RPAC Review Project Assets with Client
PS.ACT.RBC – Review Bid and Contract (Core)
The Review Bid and Contract should be one of the first things that the project manager
will do after being assigned to the project. This task bridges the gap between the Bid
Preparation process and Project Start Up.
Activity/Task Group
Review Bid and Contract
Work Product
Confirmed Bid and Contract – The Confirmed Bid and Contract is the result of the
project manager reviewing the executed contract and related bid material and committing
to deliver the scope under the terms and budget included in the contract. The following
may be included components:
• Reviewed Bid Material
• Confirmed Presence of Key Organizational Risks
• Identified Stakeholders
• Reviewed Contract
• Reviewed Contract work product Schedule
• Commitment to Deliver Engagement
Prerequisites
You need the following for this task:
Prerequisite Usage
Contract and associated Collective and ancillary documents such as vendor agreements, contract/labor
documentation agreements, system requirements documentation, Board-level directives and
communications, and requests for proposal. These documents assist in the
identification of the business drivers for the project and provide details on the
scope of the project; the modules purchased, the agreements, and so on.
Bid document Describes scope and requirements of proposed services.

Approach
When performing this task, consider the following:
• Review final contract and bid material by accessing internal bid system and/or by
obtaining material generated from the Cloud estimating tool.
• Review contract estimates and approved bid Profitability Workbook including

labor, non-bill expenses and staff plan
• Review MSA/contract for terms and conditions and any exceptions which may
include special billing instructions, expense guidelines, receipt requirements
• Familiarize yourself with Project Risks identified at bid time
• Address any disconnects and/or commit to deliver contract
Roles and Responsibilities

The Oracle Implementation team has primary responsibility for this task.
PS.ACT.RPAC – Review Project Assets with Client (Core)
As soon as feasible, the project manager will review the contract, project scope, key
project milestones and project approach with the client. This includes making any
necessary updates to the contract and project approach so it can be reflected in the
High-Level Project workplan and Project Management Plan prior to the project kickoff
Activity/Task Group
Review Project Assets with Client
Work Product
Reviewed Project Assets – The Reviewed Project Assets is a result of the contract and
project approach being reviewed with the client to arrive at a common understanding of
the project scope and objectives.
Prerequisites
Prerequisite Usage
Confirmed Bid and Contract The Confirmed Bid and Contract is the result of the project manager reviewing
the executed contract and related bid material and committing to deliver the
scope under the terms and budget included in the contract. The contract,
including terms and conditions, assumptions and obligations should be reviewed
with the client.
Approach
• Establish contact between client and Project Manager
• Review contract scope and conditions with client
• Review key project milestones and outputs with the client
• Set expectations regarding the project approach, planned releases and rollouts
• Obtain client resource commitments to attend in-scope workshops
• At a high-level, introduce project approach including risk, issue, problem

resolution

The Oracle Implementation team and the client have a shared responsibility for this task.
PS.ACT.VSSOS – Validate Scope and Stakeholders (Core)
Most likely, the project manager will be validating the engagement scope in conjunction
with Reviewing the Bid and Contract and Developing the Workplan. This task should
reflect any detailed scoping items and requirements that may have been uncovered when
the contract assets were reviewed with the client. The goal of Validating the Scope and
Stakeholders is to ensure that all of these artifacts consistently and accurately represent
the contracted scope.
Additionally project scope needs to be validated and specified in detail. This is especially
critical where the scope has been vaguely written into the contract.
While the Review Bid and Contract task is primarily focused on having the project
manager understanding and accept the contracted project scope, this task focuses on
detailing the scope and validating that related project artifacts, particularly the project
workplan, reflect the accepted scope.
During this task, completeness of the stakeholder analysis conducted during the bid
cycle will be verified and refined. Having a complete list of key stakeholders will help to
further define the scope and will be a key input into the communication plan.
Activity/Task Group
Review Scope, Workplan and Budget
Work Product
Validated Scope – The Validated Scope work product is a result of validating that the
contract scope accurately reflects the contract and the expectations of the client.
Prerequisites
Prerequisite Usage
Bid Material Describes scope and requirements of proposed services.
scope under the terms and budget included in the contract. The confirmed Bid
and Contract is referenced in order to validate that all other communication of
scope is in alignment with the contract scope.
Reviewed Project Assets The Reviewed Project Assets is a result of the contract and project approach
being reviewed with the client to arrive at a common understanding of the project
scope and objectives.

Approach
• Understand project scope and review generated project plan to make sure it is
consistent (i.e. optional scope items have associated tasks within plan)
• Document all assumptions concerning scope, resources, user participation, sign-

off, issues resolution, QA.
• Identify key players and determine appropriate communications

PS.ACT.DW – Develop Workplan (Core)
In this task, the project manager completes the project workplan. The project workplan
denotes all the tasks and activities to be performed by the team in order to deliver on the
project scope and objectives. The project plan may include client activities or
placeholders to represent client activities in which the project is dependent on.
The baseline project workplan should identify planned releases, but may not detail the
tasks for each release at this time.
Activity/Task Group
Work Product
High-Level Project Workplan – The High-Level Project Workplan depicts the high-level
tasks that need to be executed during the course of the project. The high-level workplan
identifies all planned releases, but may not contain the details of the releases at this time.
Prerequisites
Prerequisite Usage
Validated Scope The Validated Scope work product is a result of validating that the contract
scope accurately reflects the contract and the expectations of the client.
Approach
• Tailor generated workplan to better fit the flow of the implementation
• Determine the content of the Releases
• Create initial high-level project workplan (implementation plan)


PS.ACT.DSPB – Develop Staff Plan and Budget (Core)
In this task, the project manager uses the High-Level Project Workplan as input to
develop the staff plan and the project budget.
Activity/Task Group
Work Product
Staff Plan and Budget – The Staff Plan and Budget is developed in conjunction with
developing the High-Level Project Workplan. Using the High Level Project Workplan as
input, the project manager develops the staff plan and the project budget.
Prerequisites
Prerequisite Usage
scope under the terms and budget included in the contract. When the staff plan
and budget are created, the original contract budget and financial information
should be referenced and followed.
High-Level Project Workplan The High-Level Project Workplan depicts the high-level tasks that need to be
executed during the course of the project. The high-level workplan identifies the
planned releases, but may not contain the details of the releases at this time.
Staffing is based on the tasks included in the project workplan and the project
budget is, in large part, a result of the staffing.
Approach
• Staff Project by securing project resources based on tailored workplan
• Validate/Revise Project Budget based on actual resource assignments
• If this is a fixed price contract, the budget is fixed and likely will not change. If
additional services are included (T&M), the project budget may need adjustments
based on assigning actual resources levels to the Project plan


PS.ACT.CPMP – Create Project Management Plan (Core)
This task prepares the governance model for the project including the key plans that are
used to manage the project.
The Project Management Plan (PMP) is not intended to be a large, complex plan.
Rather, it is meant to clearly and concisely explain how the project will be governed,
planned, executed and controlled.
The PMP should provide an overall project management roadmap or framework and may
reference the detailed project management process-level plans. For example, your
Project Workplan, may be managed using a scheduling tool (e.g., MS Project) and
referenced rather than included in the PMP
The PMP is often a conceptual work product meaning that each of its components may
be developed separately with the PMP only providing links or references to the various
plans corresponding to the Manage processes. The content of the PMP should be fit for
purpose -- appropriate for the size and complexity of the engagement.
Activity/Task Group
Create Project Governance, Policies and Supporting Infrastructure
Work Product
Project Management Plan – The Project Management Plan defines the governance
approach to project management by identifying how the critical, strategic areas of the
project will be planned, executed and controlled, and monitored and reported on.
Prerequisites
Prerequisite Usage
Reviewed Project Assets The Reviewed Project Assets is a result of the contract and project approach
being reviewed with the client to arrive at a common understanding of the project
scope and objectives.
Staff Plan and Budget The Staff Plan and Budget is developed in conjunction with developing the High-
Level Project Workplan. Using the High Level Project Workplan as input, the
project manager develops the staff plan and the project budget.
Approach
• Establish project governance
• Determine the process for:
o Change Control
o Financial Management
o Risk Tracking and Resolution
o Issue Tracking and Resolution
o Problem Tracking and Resolution
o Quality standards Project standards including naming conventions and

standard look and feel, quality reporting
o Configuration control and release management
o Standard communications - to whom, what format and frequency
o Project documentation archiving policy and process
o Process for on-boarding resources
o Procurement process
o Execution of planned quality checkpoints and validations


PS.ACT.EPI – Establish Project Infrastructure (Core)
In this task, you set up the system and tools needed to conduct the project.
Activity/Task Group
Create Project Governance, Policies and Supporting Infrastructure
Work Product
Project Infrastructure – The Project Infrastructure details the system and tools needed
to conduct the project.
Prerequisites
Prerequisite Usage
Project Management Plan The Project Management Plan defines the governance approach to project
management by identifying how the critical, strategic areas of the project will be
planned, executed and controlled, and monitored and reported on.
Develop Staff Plan and Budget The Staff Plan and Budget is developed in conjunction with developing the High-
Level Project Workplan. Using the High Level Project Workplan as input, the
project manager develops the staff plan and the project budget.
Approach
• Establish/review project infrastructure to support the project approach including

risk, issue, problem and configuration management systems
• Set up time, expense and billing (invoice) tracking processes
• Validate Cloud set up and that the appropriate environment(s) is in place
• Establish client access to project infrastructure as dictated by the project
• Establish procedure for procuring goods and contracted Services (if appropriate)

CHAPTER
4 Plan (A) Phase
T he goal of the Plan phase is to align the project team with the project’s goals and
objectives, gather setup data, and prepare a detailed plan for the remainder of the
project.
Following confirmation of the project scope and objectives, and the preparation of a high-
level Project Workplan in the Project Start Up Phase, a kickoff meeting is held in the Plan
phase to orient the entire team to the project’s goals, objectives, and protocols to be
followed during the project.
During the Plan phase, a series of workshops are scheduled to gather initial setup
information and review the approach, or approaches, that will be employed to address
required integrations and the loading of legacy data. A detailed plan for the current
release is also prepared and shared with team members.
Global Methods Plan (A) Phase 4 - 1

Plan Phase Objectives
The objectives of the Plan phase follow:
• Conduct Kick-off Meeting.

• Schedule workshops.
• Prepare Detailed Release Plan
• Gather initial setup information.
• Familiarize client with data load and integration scope and strategy.
Plan Phase Task Groups

The Plan phase is comprised of the following Task Groups:
• Prepare Project Team

• Release Planning
• Gather Setup Information
• Conduct Technical Workshops
• Documentation
• Cloud Adoption – Plan
• Executive Checkpoint
Key Work Products

The key work products of the Plan phase are as follows:
Detailed Release Plan The Detailed Release Plan contains a

network of interdependent tasks
representing all work, with staff work
assignments and schedules for the
current release.
Completed Setup Questionnaires The Completed Setup Questionnaires

contain the configuration information
for the functionality that is in-scope for
the project. The setup questionnaires
are used to configure the Staging
Environment in preparation for the
prototyping workshops in the Prototype
phase.
Plan (A) Phase 4 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Integration Strategy The Integration Strategy documents

the high-level requirements for each
integration point and outlines the
Fusion integration concepts which will
be utilized to satisfy the integration
requirements
Data Load Strategy The Data Load Strategy documents

the high-level requirements for each
data load and outlines the Fusion data
load tools and functions that will be
utilized to satisfy the data load
requirements.

STM.050 Conduct Kick-Off Meeting Kick-Off Meeting Always
TR.050 Train Project Team Trained Project Team Project Team training has
been requested as an
additional service.
WM.070 Schedule Workshops Workshop Schedule Always
WM.010 Create Detailed Plan for Current Detailed Release Plan Always
Release
RD.011.1 Review In-Scope High-Level Reviewed Business Processes Always

Business Processes
MC.040.1 Gather Setup Information Completed Setup Questionnaires Always
TA.030 Conduct Integration Workshop Integration Strategy Always
CV.010 Conduct Data Load Workshop Data Load Strategy Always
DO.010 Define Documentation Documentation Requirements and Project-specific

Requirements and Strategy Strategy documentation has been
requested as an
additional service.
OCM.015 Identify Process Change Process Change Candidate List Cloud Adoption Services
Candidates have been requested as
an additional service.

OCM.035 Create Change Plan Change Enablement Plan Cloud Adoption Services
have been requested as
OCM.065 Provide Stakeholder / End User Stakeholder / End User Analysis Cloud Adoption Services
Analysis Guidance Tools and Techniques have been requested as
WM.050.1 Conduct Implementation Implementation Checkpoint Always

Checkpoint Meeting/Approval to Proceed
A.PEC.TSK Manage Project Execution Managed Project Assets Always
A.PGM.TSK Program Management Managed Program Project is part of a larger

program
Responsibilities
phase:
• TR.050 Train Project Team (Optional)
• WM.070 Schedule Workshops
• WM.010 Create Detailed Plan for Current Release
• MC.040.1 Gather Setup Information
• TA.030 Conduct Integration Workshop
• CV.010 Conduct Data Load Workshop
• DO.010Define Documentation Requirements and Strategy (Optional)
• OCM.015 Identify Process Change Candidates (Optional)
• OCM.035 Create Change Plan (Optional)
• OCM.065 Provide Stakeholder / End User Analysis Guidance (Optional)
• WM.050.1 Conduct Implementation Checkpoint
• A.PEC.TSK Manage Project Execution
• A.PGM.TSK Program Management (Optional)
• STM.050 Conduct Kick-Off Meeting
• RD.011.1 Review In-Scope High-Level Business Processes

STM.050 – Conduct Kick-Off Meeting (Core)
In this task, plan and conduct a Project Kick-Off meeting to orient the team to the project.
If warranted, similar orientation meetings can be given for new team members that join
the project after kick-off. This meeting will help streamline the on-boarding process,
communicate the project objectives and structure, and begin to develop cohesion among
the team.
Work Product
Kick-Off Meeting – The Kick-Off Meeting is conducted to orient the project team and
communicate to them the project objectives and structure.
Activity/Task Group
Prepare Project Team
Prerequisites
Prerequisite Usage
Approach
• Allow each team member to introduce themselves and the role they will play on
the project.
• Capture any issues and concerns that cannot be addressed during the meeting
and establish a plan to respond back to the team.

TR.050 – Train Project Team (Optional)
In this task, you conduct learning events for the project team. The scope of the training
should be determined by the pre-defined project team training developed for the fixed
scope offerings that are in-scope for the project (If available), or the project team training
specified in the contract.
Δ If Project Team training has been requested as an additional

service for your project, you should perform this task.
Activity/Task Group
Prepare Project Team
Work Product
Trained Project Team – The Trained Project Team represents all members of the team
who have participated in the learning events intended to give them the knowledge and
skills they need to perform their roles on the team.
Prerequisites
Prerequisite Usage
scope of the project; the modules purchased, the agreements, and so on.
Approach
• Project team training should cover tools, applications, and all knowledge and skill
areas deemed necessary for the effective functioning of the team.


WM.070 – Schedule Workshops (Core)
In this task, you schedule a series of workshops aimed at gathering initial setup
information, as well as those needed to disseminate, and gather, information regarding
the integrations and data loads in-scope for the project.
Activity/Task Group
Release Planning
Work Product
Workshop Schedule – The Workshop Schedule lists the workshops that are planned for
gathering setup information and addressing the integrations and data loads that are in-
scope for the project. It specifies the date, time, duration, objectives, and required
participants for each workshop.
Prerequisites
Prerequisite Usage
Reviewed Business Processes The Reviewed Business Processes identifies the business processes in scope
for the project for which workshops must be scheduled.
Approach
• Establish order of workshops based on Reviewed Business Processes.
• Determine how many workshops will be required for each business process area
and how the work will be divided up across those workshops.
• Identify the client personnel required for each of the planned workshops and
obtain their availability.
• Prepare the schedule and have it reviewed and approved by the client.

WM.010 – Create Detailed Plan for Current Release (Core)
In this task, you determine, organize, estimate, link, and schedule all of the tasks
representing the work to be performed on the current release. This task can be
performed with varying degrees of scope, rigor, and detail, depending on the
circumstances in which it is used. It can be used for forecasting, estimating, planning and
impact analysis.
Activity/Task Group
Release Planning
Work Product
Detailed Release Plan – The Detailed Release Plan contains a network of

interdependent tasks representing all work, with staff work assignments and schedules,
for the current release.
Prerequisites
Prerequisite Usage
Approach
• Have changes been identified during the implementation, which impact the
release plan?
• Have the client’s priorities been revised?
• Are there other factors impacting the release plan?

RD.011.1 – Review In-Scope High-Level Business Processes (Core)
In this task, you provide a walkthrough of the major business processes that are in scope
for the project and define the priority for implementation.
Activity/Task Group
Gather Setup Information
Work Product
Reviewed Business Processes – The Reviewed Business Processes identifies the

business processes in scope for the project and determines the priority for
implementation.
Prerequisites
Prerequisite Usage
Approach
• Use the standard Fusion Applications Process Models as the basis this review.

MC.040.1 – Gather Setup Information (Core)
In this task, you conduct scheduled workshops aimed at collecting input for the setup
questionnaires and wizards. Prior to these interviews, the implementation team should
have received the client documentation related to the procedures and processes within
the project’s scope. These are mainly used to confirm the teams’ understanding of the
client’s processes.
Activity/Task Group
Gather Setup Information
Work Product
Completed Setup Questionnaires – The Completed Setup Questionnaires contain the

configuration information for the functionality that is in-scope for the project. The setup
questionnaires are used to configure the Staging Environment in preparation for the
prototyping workshops in the Prototype phase.
Prerequisites
Prerequisite Usage
for the project and determines the priority for implementation.
Workshop Schedule The Workshop Schedule lists the workshops that are planned for gathering setup
information and addressing the integrations and data loads that are in-scope for
the project. It specifies the date, time, duration, objectives, and required
Approach
• Workshops for gathering setup information should be conducted in the order

scheduled based on the Reviewed Business Processes.
• Have setup questionnaires been forwarded to the client before the workshop?
• Have completed questionnaires containing preliminary values been received by

the implementation team?

TA.030 – Conduct Integration Workshop (Core)
In this task, you conduct a workshop to explain the Fusion integration concepts and
define an integration strategy to interface with legacy systems.
Activity/Task Group
Conduct Technical Workshops
Work Product
Integration Strategy – The Integration Strategy documents the high-level requirements

for each integration point and outlines the Fusion integration concepts which will be
utilized to satisfy the integration requirements.
Prerequisites
Prerequisite Usage
Approach
• Which integrations are considered in-scope for the fixed scope offerings included
in the project?
• Are there any additional pre-built or custom integrations that have been
requested by the client?
• Which Fusion integration approaches are appropriate for the integrations in

scope?

CV.010 – Conduct Data Load Workshop (Core)
In this task, you conduct a workshop to explain the data conversion tools and functions
within Fusion and determine the data conversion options to be used for the data loads in
scope.
Activity/Task Group
Conduct Technical Workshops
Work Product
Data Load Strategy – The Data Load Strategy documents the high-level requirements
for each data load, and outlines the Fusion data load tools and functions, which will be
utilized to satisfy the data load requirements.
Prerequisites
Prerequisite Usage
Approach
• Which data loads are considered in-scope for the fixed scope offerings included
in the project?
• Are there any additional pre-built or custom data loads that have been requested
by the client?
• Which Fusion data load tools and options are appropriate for the data loads in
scope?

DO.010 – Define Documentation Requirements and Strategy (Optional)
In this task, you outline the overall requirements for creating user documentation and
specify the work products to be produced. You also identify the strategy you will use for
publishing project-specific documentation.
Δ If Project-specific documentation has been requested as an

additional service for your project, you should perform this
task.
Activity/Task Group
Documentation
Work Product
Documentation Requirements and Strategy – The Documentation Requirements and

Strategy identifies the project-specific documentation that must be published and the
strategy for publishing that documentation.
Prerequisites
Prerequisite Usage
Approach
• Has the client requested project-specific documentation as an additional service?
• Which process areas are included in the scope of the project and what priority
has been assigned to those process areas by the client?
• Which process areas require user documentation or job aids?
• What strategy, tools, or techniques will be employed to develop and deploy the
required user documentation?

OCM.015 – Identify Process Change Candidates (Optional)
In this task, you Identify candidate processes/procedures for change based on the
documentation provided by client, catalog such candidate processes, and communicate
the change impact areas to the client.
Δ If Cloud Adoption Services have been requested as an

task.
Activity/Task Group
Cloud Adoption - Plan
Work Product
Process Change Candidate List – The Process Change Candidate List contains the
client’s current processes or procedures which have been identified as candidates for
change based on the standard functionality supported by the off-the-shelf products in
scope for the project.
Prerequisites
Prerequisite Usage
Approach
This section is not yet available.


OCM.035 – Create Change Plan (Optional)
In this task, you create a plan for enabling changes to the client processes/procedures
that have been identified as needing to be changed in order to align with processes
supported by the off-the-shelf functionality, which is in scope for the project.

task.
Activity/Task Group
Work Product
Change Enablement Plan – The Change Enablement Plan outlines a plan of action,
which will enable the client organization to implement and adopt changes to their internal
processes, which are required in order to align those processes with those supported by
the off-the-shelf functionality of the software in scope for the project.
Prerequisites
Prerequisite Usage
Process Change Candidate List The Process Change Candidate List contains the client’s current processes or
procedures which have been identified as candidates for change based on the
standard functionality supported by the off-the-shelf products in scope for the
project.
Approach

OCM.065 – Provide Stakeholder / End User Analysis Guidance (Optional)
In this task, you conduct a change enablement kickoff and orientation workshop and
provide the client change lead with worksheets, sample PowerPoints for analysis output,
and guidance on integration to the overall implementation plan.

task.
Activity/Task Group
Work Product
Stakeholder/End User Analysis Tools and Techniques – The Stakeholder/End User

Analysis Tools and Techniques provides the client change lead with the necessary tools
and methods necessary to conduct a Stakeholder/End User Analysis and apply the
results to the overall implementation project.
Prerequisites
Prerequisite Usage
Approach


WM.050.1 – Conduct Implementation Checkpoint (Core)
In this task, you review the key work products completed during the phase with the client,
verify that the phase objectives have been met, confirm the next steps to be taken, and
obtain approval to proceed with the next phase.
Activity/Task Group
Executive Checkpoint
Work Product
Implementation Checkpoint Meeting/Approval to Proceed – The Implementation

Checkpoint Meeting/Approval to Proceed provides an opportunity to review the work
completed during the phase with the client, confirm the next steps and obtain the
approval to proceed with the next phase of the implementation.
Prerequisites
Prerequisite Usage
Completed Setup Questionnaires The Completed Setup Questionnaires contain the configuration information for
the functionality that is in-scope for the project. The setup questionnaires are
used to configure the Staging Environment in preparation for the prototyping
workshops in the Prototype phase.
Integration Strategy The Integration Strategy documents the high-level requirements for each
integration point and outlines the Fusion integration concepts which will be
Data Load Strategy The Data Load Strategy documents the high-level requirements for each data
load and outlines the Fusion data load tools and functions, which will be utilized
to satisfy the data load requirements.
Approach
• Have the key work products for the phase been completed and reviewed?
• Have the objectives set out for the phase been achieved?
• Have the next steps been determined and confirmed?

A.PEC.TSK – Manage Project Execution (Core)
In this task, the execution of the project is managed. This includes using the policies,
standards, and procedures delineated in the Project Start Up phase, performing the
necessary reviews and measurements to validate that the project is being executed
according to the project management plan.
It also includes comparing actual performance with planned performance, analyzing

variances, evaluating possible alternatives, and taking appropriate corrective action as
needed.
The Manage Project Execution is made up of many ongoing tasks. An ongoing task is
defined as a task that occurs continuously throughout a project, rather than at a specific
pre-defined time. The ongoing tasks occur as needed and do not include dependencies
among the tasks or with the execution method tasks.
Activity/Task Group
Project Management
Work Product
Managed Project Assets – Reviewed project progress, analyzed variances and updated
management plans and policies.
Prerequisites
Prerequisite Usage
executed during the course of the project. The high-level workplan identifies all
planned, executed and controlled, and monitored and reported on
Project Infrastructure The Project Infrastructure details the system and tools needed to conduct the
project.
Detailed Release Plan The Detailed Release Plan contains a network of interdependent tasks
representing all work, with staff work assignments and schedules for the current
release.
Approach
• Update the high-level project workplan to reflect any changes in business

process priorities and other information gained during the project
• Document lessons learned
• Track project actuals
• Adjust project workplan, staff and budget as necessary
• Adjust project approach (PMP) as necessary
• Review the key outputs for the phase with client and obtain agreement or
acceptance (for fixed price projects)
• Verify that phase objectives have been met and confirm next steps


A.PGM.TSK – Program Management (Optional)
Some Cloud application service implementations may be managed as part of a larger
program. When this is the case, then the implementation will need to be managed at
both the project and the program level.
Δ If your project is part of a larger program, you should perform

this task.
Activity/Task Group
Project Management
Work Product
Managed Program – Reviewed program objectives, progress, and program

Prerequisites
Prerequisite Usage
planned releases, but may not contain the details of the releases at this time. If
the implementation is part of a program, then project workplan may include
additional program related task and activities.
planned, executed and controlled, and monitored and reported on. If the
implementation is part of a program, then the project management plan may
reference how the program is executing, controlling, monitoring and reporting on
the progress of this implementation in the context of the entire program.
Approach
When Program Management is included in the project, it is recommended that you
reference the “Program Management Method (PGM) Handbook” which can be found in
the OUM Method Pack on the OUM Manage Homepage.

CHAPTER
5 Prototype (B) Phase
T he goal of the Prototype phase is to demonstrate the standard functionality as

configured in the Staging Environment and iteratively refine the solution.
The phase is characterized by two iterations, or cycles, of prototyping workshops. The

first iteration is focused prototyping, refining and validating the configuration of standard
functionality. The second iteration expands the scope of the prototyping workshops to
include the validation of extensible items, such as workflows and notifications, as well as
integrations and data loads.
At the outset of the Prototype phase, the initial setup information, which was gathered
during the Plan phase, is used to configure the Staging Environment. An initial series of
workshops are then conducted to demonstrate the standard functionality (as configured
in the Staging Environment) and collect feedback on additional configurations and
refinements. Any additional configurations identified are prioritized and entered and
reviewed during the subsequent set of Prototype phase workshops.
Following the entry of any setup changes, a second series of prototyping workshops are
conducted to demonstrate and validate the functionality associated with extensible items,
integrations, and data loads. When additional services for pre-built or custom
integrations or data loads are in scope for the project, optional tasks related to data
mapping and preparation of technical specifications may also be executed. Custom
components associated with non-standard reports, data loads or custom integrations are
built and tested, and client legacy data is loaded and validated.
During the Prototype phase, client personnel may be tasked with cleaning and obtaining
legacy data in preparation for loading, as appropriate. The phase then culminates with
an implementation checkpoint to verify that phase objectives have been achieved and
approval to proceed obtained.
Global Methods Prototype (B) Phase 5 - 1

Prototype Phase Objectives
The objectives of the Prototype phase follow:
• Perform initial setups in the Staging Environment.

• Conduct workshops to Iteratively prototype and validate the configuration of
standard functionality.
• Validate the functionality associated with extensible items, integrations, and data
loads.
Prototype Phase Task Groups

The Prototype phase is comprised of the following Task Groups:
• Prototype Configuration - Iteration 1

• Prepare Integration Details
• Prepare for Data Loads
• Prototype Configuration - Iteration 2
• Implement Extensible Elements
• Update Business Process Models and Test Cases
• Implement Integration Packages
• Validate Data Load – Prototype
• Cloud Adoption – Prototype
Key Work Products

The key work products of the Prototype phase are as follows:
Validated Configuration The Validated Configuration verifies

that all setup data, including the
additional and revised configuration
values, have been entered in
accordance with the revised setup
documentation.
Prototype (B) Phase 5 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Validated Integration Packages The Validated Integration Packages

represent the implemented
integrations, which have been
validated to function as expected, in
accordance with the design.
Validated Data The Validated Data is the client data

that has been loaded to the
staging/testing environment via the
data load templates or other means
and validated to correctly reflect the
legacy data in the format required by
the new system.

MC.060.1 Perform Initial Setup Configured Prototype (Staging) Always

Environment
TE.020 Prepare Validation Scripts Validation Scripts Always
MC.070 Conduct Workshops and Reviewed Prototype Always

Prototype Solution
MC.040.2 Capture and Prioritize Additional MoSCoW List Always

Configurations
MC.050.1 Update Setup Documentation Setup Documentation Always
MC.063 Conduct Configuration Configuration Familiarization Always

Familiarization Session Session
DS.140.1 Prepare Detailed Technical Detailed Technical Specification - Custom reports, additional
Specifications - Fusion Fusion data loads, or custom
integrations are requested
as additional services.
DS.140.2 Prepare Detailed Technical Detailed Technical Specification – Custom reports, additional
Specifications - Client Legacy Client Systems data loads, or custom
Systems integrations are requested
as additional services.

CV.027.1 Perform Data Mapping Data Mapping Pre-built data loads,

custom data loads, pre-
built integrations or
custom integrations have
been requested as
additional services.
CV.053 Populate Data Load Templates Populated Data Load Templates Always
With Client Data
MC.060.2 Apply Setup Changes Configured Prototype/Staging Always

Environment
MC.065.1 Validate Setup Changes Validated Configuration Always
MC.050.2 Document Functional Security Functional Security Documentation Always
MC.085 Prepare Reports Developed Reports Always
MC.060.3 Implement Workflows Configured Workflows Complex, custom

workflows are requested
as an additional service
MC.060.4 Implement Notifications Configured Notifications Complex, custom

notifications are
requested as an
additional service
MC.060.5 Implement FastFormulas Configured FastFormulas FastFormulas are

requested as an
additional service
MC.060.6 Implement FlexFields Configured Flexfields Complex, custom

FlexFields are requested
as an additional service
MC.060.7 Implement Localizations Implemented Localizations Localizations are

requested as an
additional service
MC.060.8 Implement Composer Updates Implemented Composer Updates Composer updates are
requested as an
additional service
MC.065.2 Validate Setup Changes Validated Configuration Always
RD.011.2 Update Business Processes Future Process Model Always
TE.027.1 Update Validation Cases Updated Validation Cases Always
IM.050.1 Implement Integration Packages Custom Components Custom integrations are

- Fusion requested as additional
services.
IM.050.2 Implement Integration Packages Custom Components Custom integrations are

- Client Systems requested as additional
services.
IM.050.3 Load and Validate Data to Client Validated Data Custom integrations are
Systems requested as an
additional service for your
project, which require
data to be loaded to client
systems.
TE.045 Validate Integration Packages Validated Integration Packages Custom integrations are
requested as additional
services.
CV.065.1 Load, Reconcile & Validate Data Validated Data Always
OCM.145 Provide Change Impact Change Impact Assessment Cloud Adoption Services
Assessment Approach Approach have been requested as
an additional service for
your project.

B.PEC.TSK Manage Project Execution Managed Project Assets Always
B.PGM.TSK Program Management Managed Program Project is part of a larger

program.
Responsibilities
phase:
• MC.060.1 Perform Initial Setup
• TE.020 Prepare Validation Scripts
• MC.070 Conduct Workshops & Prototype Configuration
• MC.040.2 Capture & Prioritize Additional Configurations
• MC.050.1 Update Setup Documentation
• DS.140.1 Prepare Detailed Technical Specifications – Fusion

• MC.060.2 Apply Setup Changes
• MC.065.1 Validate Setup Changes
• MC.050.2 Document Functional Security
• MC.085 Prepare Reports
• MC.050.3 Update Setup documentation
• MC.060.3 Implement Workflows
• MC.060.4 Implement Notifications
• MC.060.5 Implement FastFormulas
• MC.060.6 Implement FlexFields
• MC.060.7 Implement Localizations
• MC.060.8 Implement Composer Updates
• MC.065.2 Validate Setup Changes
• IM.050.1 Implement Integration Packages – Fusion
• OCM.145 Provide Change Impact Assessment Approach
• B.PEC.TSK Manage Project Execution
• B.PGM.TSK Program Management
The client has primary responsibility for the following tasks in this phase:
• DS.140.2 Prepare Detailed Technical Specifications - Client Legacy Systems
• RD.011.2 Update Business Processes
• CV.053 Populate Data Load Templates With Client Data
• TE.027.1 Update Validation Cases
• IM.050.2 Implement Integration Packages - Client Systems
• IM.050. 3 Load and Validate Data to Client Systems
• TE.045 Validate Integration Packages
• CV.027.1 Perform Data Mapping
• CV.065.1 Load, Reconcile & Validate Data

MC.060.1 – Perform Initial Setup (Core)
In this task, you configure the Staging Environment according to completed setup
questionnaires defined in the Plan phase.
Activity/Task Group
Prototype Configuration – Iteration 1
Work Product
Configured Prototype/Staging Environment – The Configured Prototype/Staging

Environment is a Fusion Applications environment, generally the Staging Environment,
which has been configured according to the completed setup questionnaires.
Prerequisites
Prerequisite Usage
Approach
• Utilize Functional Setup Manager and Setup Wizards, as applicable.
• Includes enabling of the Fusion Integration Layer.
• Verify setups and update setup documentation, as necessary.

TE.020 – Prepare Validation Scripts (Core)
In this task, you prepare demo scripts/test scripts for use in validating the setups, and
related functionality, during the prototyping workshops. If predefined scripts are available
for the functionality in question, update them as necessary instead of preparing new
scripts.
Activity/Task Group
Work Product
Validation Scripts – The Validation Scripts consist of the set of test scenarios, that each
includes a number of test steps, which will be executed during the configuration
prototyping workshops and end-to-end review.
Prerequisites
Prerequisite Usage
Approach
• Identify the functionality to be validated
• Collect any predefined demo scripts/test scripts available for the functionality in
question
• Verify that scripts are aligned with setup values contained in the Completed
Setup Questionnaires

MC.070 – Conduct Workshops and Prototype Configuration (Core)
In this task, you conduct workshops to demonstrate the standard functionality as
configured in the prototype/Staging Environment.
Activity/Task Group
Work Product
Reviewed Prototype – The Reviewed Prototype is the result of conducting a series of

workshops intended to demonstrate the standard functionality as configured in the
prototype/Staging Environment.
Prerequisites
Prerequisite Usage
Configured Prototype/Staging The Configured Prototype/Staging Environment is a Fusion Applications

Environment environment, generally the Staging Environment, which has been configured
according to the completed setup questionnaires.
Validation Scripts The Validation Scripts consist of the set of test scenarios, that each includes a
number of test steps, which will be executed during the configuration prototyping
workshops and end-to-end review.
Approach
• Leverage applicable Fusion Application Process Models as a starting point for

the prototyping workshop sessions.
• Keep track of client feedback during the prototyping workshop sessions.
• Determine how many iterations are required to prototype all functional areas
included in the project scope.

• Additional and revised configurations identified during these sessions may be
implemented and prototyped as part of a subsequent iteration of this task.

MC.040.2 – Capture and Prioritize Additional Configurations (Core)
In this task, you document and prioritize any revised or additional configuration settings
required by the customer, which have been identified during the prototyping sessions.
Activity/Task Group
Work Product
MoSCoW List – The MoSCoW List is a prioritized list of the high-level requirements valid
for the application system that is being implemented, which contains the revised or
additional configuration requirements identified during the prototyping sessions.
Prerequisites
Prerequisite Usage
Reviewed Prototype The Reviewed Prototype is the result of conducting a series of workshops
intended to demonstrate the standard functionality as configured in the
Approach
• Prioritize the additional configuration requirements.
• Update the Setup Questionnaires to reflect the changes to the setup values.
• Place the prioritized additional configuration requirements in the MoSCoW List,

indicating whether each is within the agreed upon scope for the current release.


MC.050.1 – Update Setup Documentation (Core)
In this task, you prepare and update documentation of the client’s chosen setup
options/values to reflect any revised setups, or additional configuration requirements
identified during the configuration prototyping workshops.
Activity/Task Group
Work Product
Setup Documentation – The Setup Documentation defines the detailed setup

parameters that have been proven to support the future business processes.
Prerequisites
Prerequisite Usage
MoSCoW List The MoSCoW List is a prioritized list of the high-level requirements valid for the
application system that is being implemented, which contains the revised or
Approach
• Does the Setup Documentation address mandatory or optional setups?
• Does the Setup Documentation address common setups across applications?
• Does it address key flexfields, descriptive flexfields, navigation to the screen,

justification for selected options, maintenance consolidation (if any) and date of
last update?
• Does it include the impact of any setup changes in the course of the
implementation?

MC.063 – Conduct Configuration Familiarization Session (Core)
In this task, you walk through the configuration of the new system as it currently stands
with the entire project team (client and Oracle Implementation team members). The walk
through is intended to familiarize the project team with the specific configuration options
and values selected by the client as of the completion of the first prototyping iteration,
and to educate them on how to make changes to the configuration throughout the rest of
the project, and after go-live.
Activity/Task Group
Work Product
Configuration Familiarization Session – The Configuration Familiarization Session

familiarizes the project team with the system configuration as it stands after the first
prototyping iteration in the Prototype Phase, and acquaints them with how to make
configuration changes during the remainder of the project, and after the system is placed
in use.
Prerequisites
Prerequisite Usage
Reviewed Prototype The Reviewed Prototype is the result of conducting a series of workshops
intended to demonstrate the standard functionality as configured in the
Setup Documentation The Setup Documentation defines the detailed setup parameters that have been
proven to support the future business processes.
Approach
• The configuration at the conclusion of the first prototyping iteration serves as a

baseline for the configuration moving forward
• Are there appropriate controls in place regarding who is able to make changes to
the configuration?
• Have guidelines been established and communicated regarding when approvals

are necessary prior to a change being made and who must approve them?

DS.140.1 – Prepare Detailed Technical Specification – Fusion (Optional)
In this task, you prepare the detailed technical specifications from a Fusion Applications
perspective based on the results of the integration and data load workshops and
associated follow-on work.
Δ If pre-built data loads, custom data loads, pre-built integrations

or custom integrations have been requested as additional
services for your project, you should perform this task.
Activity/Task Group
Prepare Integration Details
Work Product
Detailed Technical Specification - Fusion – The Detailed Technical Specification -

Fusion pulls together all design elements for a component into a single document so that
they can be easily assessed against each other, against the design guidelines, and
against the requirements.
Prerequisites
Prerequisite Usage
Future Process Model The Future Process Model describes the future business process that the
business executes in response to triggering events as a set of one or more
activities.
Approach
• Provide a technical overview.
• Describe the building blocks.
• Define Data Load design.
• Define integration design.
• Maintain issues list.

The Oracle Implementation team has primary responsibility for this task...

DS.140.2 – Prepare Detailed Technical Specification – Client Systems
(Optional)
In this task, you prepare the detailed technical specifications from a client legacy system
perspective based on the results of the integration and data load workshops and
associated follow-on work.

Activity/Task Group
Prepare Integration Details
Work Product
Detailed Technical Specification – Client Systems – The Detailed Technical

Specification – Client Systems pulls together all design elements for a component into a
single document so that they can be easily assessed against each other, against the
design guidelines, and against the requirements.
Prerequisites
Prerequisite Usage
activities.
Approach
• Provide a technical overview.
• Describe the building blocks.
• Define Data Load design.
• Define integration design.
• Maintain issues list.

The client has primary responsibility for this task.

CV.027.1 – Perform Data Mapping (Optional)
In this task, you create a detailed conversion mapping from the source legacy system to
the target application and an extract file layout to be used for extraction of the data from
the source system.

Activity/Task Group
Prepare for Data Loads
Work Product
Data Mapping – The Data Mapping defines the key assumptions, mapping between
source and target, and mapping rules and logic that is needed to create the conversions
and interfaces necessary to support the solution. It is intended to provide the developer
with the necessary information for writing accurate conversion, transformation and load
logic.
Prerequisites
Prerequisite Usage
Approach
• The Conversion Mapping component provides a table that shows to which table
and column the legacy system data fields map in Oracle.

The client and Oracle Implementation team share responsibility for this task.
CV.053 – Populate Data Load Templates with Client Data (Core)
In this task, you populate the specified data load templates with client data from legacy
systems and prepare the data for loading to the new Oracle system.
Activity/Task Group
Prepare for Data Loads
Work Product
Populated Data Load Templates – The Populated Data Load Templates contain the
client data that’s been obtained from the legacy systems and prepared for loading to the
new Oracle system.
Prerequisites
Prerequisite Usage
Data Mapping The Data Mapping defines the key assumptions, mapping between source and
target, and mapping rules and logic that is needed to create the conversions and
interfaces necessary to support the solution. It is intended to provide the
developer with the necessary information for writing accurate conversion,
transformation and load logic.
Approach
• Data should be populated in accordance with the predefined data load templates.
• Data obtained from client source systems should be cleansed prior to loading.


MC.060.2 – Apply Setup Changes (Core)
In this task, you update the configurations in the Prototype/Staging Environment based
on the results of initial prototyping workshop sessions conducted in the Prototype Phase.
You enter additional setups, as well as revisions to earlier setup values, based on the
feedback received during the initial prototyping workshops (i.e. MC.070 Conduct
Workshops & Prototype Configuration).
Activity/Task Group
Work Product
Configured Prototype/Testing Environment – The Configured Prototype/Testing

Environment is the Staging Environment, which has been updated to reflect additional
and revised setup values for validation/testing in the second iteration of prototyping in the
Prototype phase.
Prerequisites
Prerequisite Usage
Reviewed Prototype The Reviewed Prototype provides results of prototyping conducted in the
Prototype Phase.
MoSCoW List The MoSCoW List contains a high-level, prioritized list of the additional
configurations identified during the prototyping sessions.
Approach
• Identify new or revised configuration settings that have not previously been
applied and prototyped.
• Have additional configurations (beyond those included as part of the fixed scope
offerings in scope) been identified?
• Update the Staging Environment with the new and/or revised configurations.

MC.065.1 – Validate Setup Changes (Core)
In this task, you verify that the updated configuration reflects the revised setup
documentation per the changes made following the prototype sessions.
Activity/Task Group
Work Product
Validated Configuration – The Validated Configuration verifies that the additional and
revised configuration values have been entered in accordance with the revised setup
documentation.
Prerequisites
Prerequisite Usage
Configured Prototype/Testing The Configured Prototype/Testing Environment is the Staging Environment,

Environment which has been updated to reflect additional and revised setup values for
validation/testing in the second prototyping iteration of the Prototype phase.
Approach
• Review the updated setup values in the Staging Environment and verify that they
have been made in accordance with the latest version of the setup
documentation.

MC.050.2 – Document Functional Security (Core)
In this task, you gather role and function information and relate them to the functional
security needed to support the business processes.
Activity/Task Group
Work Product

parameters that have been proven to support the selected alternative.
Prerequisites
Prerequisite Usage
Prototype Phase.
Approach
• Does the security structure naturally support the business processes?
• Endeavor to minimize the number of separate roles required


MC.085 – Prepare Reports (Core)
In this task, you prepare BI Publisher and other reports as required, based on the initial
round of configuration prototyping.
Activity/Task Group
Work Product
Developed Reports – The Developed Reports are BI Publisher and other reports
requested by the client.
Prerequisites
Prerequisite Usage
Prototype Phase.
Approach
• Do any of the delivered BI Publisher Reports contain the required data

elements?
• If so, can the layout be customized to satisfy the requirement?
• Additional steps may be required to run your report.


In this task, you update documentation of the client’s chosen setup options/values to
reflect any revised setups, or additional configuration requirements identified during the
second iteration of configuration prototyping workshops.
Activity/Task Group
Work Product

parameters that have been proven to support the future business processes.
Prerequisites
Prerequisite Usage
Validated Configuration The Validated Configuration verifies that the additional and revised configuration
values have been entered in accordance with the revised setup documentation.
Approach
• Have all changes to the configuration been validated and documented?

MC.060.3 – Implement Workflows (Optional)
In this task, you implement Workflows as required, based on the initial round of
configuration prototyping.
Δ If Workflows have been requested as an additional service for

your project, you should perform this task.
Activity/Task Group
Implement Extensible Elements
Work Product
Configured Workflows – The Configured Workflows are the standard or customized

workflows implemented in the Staging environment.
Prerequisites
Prerequisite Usage
Prototype Phase
Approach
• Customized workflows should be prepared in accordance with the Oracle Fusion

Applications Extensibility Guide.


MC.060.4 – Implement Notifications (Optional)
In this task, you implement notifications as required, based on the initial round of
Δ If Notifications have been requested as an additional service

for your project, you should perform this task.
Activity/Task Group
Work Product
Configured Notifications – The Configured Notifications are the standard or customized

notifications implemented in the Staging environment.
Prerequisites
Prerequisite Usage
Prototype Phase
Approach
• Customized notifications should be prepared in accordance with the Oracle

Fusion Applications Extensibility Guide.

MC.060.5 – Implement FastFormulas (Optional)
In this task, you implement FastFormulas as required, based on the initial round of
Δ If FastFormulas have been requested as an additional service

Activity/Task Group
Work Product
Configured FastFormulas – The Configured FastFormulas are the FastFormulas

implemented in the Staging environment.
Prerequisites
Prerequisite Usage
Prototype Phase
Approach


MC.060.6 – Implement FlexFields (Optional)
In this task, you implement FlexFields as required, based on the initial round of
Δ If FlexFields have been requested as an additional service for

your project, you should perform this task.
Activity/Task Group
Work Product
Configured Flexfields – The Configured Flexfields are the Flexfields implemented in the
Staging environment.
Prerequisites
Prerequisite Usage
Prototype Phase
Approach

MC.060.7 – Implement Localizations (Optional)
In this task, you implement Localizations as required, based on the initial round of
Δ If Localizations have been requested as an additional service

Activity/Task Group
Work Product
Implemented Localizations – The Implemented Localizations are the localizations

Prerequisites
Prerequisite Usage
Prototype Phase
Approach


MC.060.8 – Implement Composer Updates (Optional)
In this task, you implement Composer Updates as required, based on the initial round of
Δ If Composer Updates have been requested as an additional

service for your project, you should perform this task.
Activity/Task Group
Work Product
Composer Updates – The Implemented Composer Updates are the composer updates
Prerequisites
Prerequisite Usage
Prototype Phase
Approach

MC.065.2 – Validate Setup Changes (Optional)
In this task, you verify that the updated configuration reflects the revised setup
documentation per the changes made following the prototype sessions.
Δ If configurable extensible elements requiring validation have

been requested as an additional service for your project, you
should perform this task.
Activity/Task Group
Work Product
Validated Configuration – The Validated Configuration verifies that all setup data,
including the additional and revised configuration values, have been entered in
accordance with the revised setup documentation.
Prerequisites
Prerequisite Usage
Configured Prototype/Testing The Configured Prototype/Testing Environment is the Staging Environment,

Environment which has been updated to reflect additional and revised setup values.
Approach
• Review the updated setup values in the Staging Environment and verify that they
have been made in accordance with the latest version of the setup
documentation.


RD.011.2 – Update Business Processes (Core)
In this task, you update the Fusion Applications business process models as necessary
to reflect the results of the prototyping workshops.
Activity/Task Group
Update Business Processes and Test Cases
Work Product
Future Process Model – The Future Process Model describes the future business
process that the business executes in response to triggering events as a set of one or
more activities.
Prerequisites
Prerequisite Usage
Validated Configuration The Validated Configuration verifies that all setup data, including the additional
and revised configuration values, have been entered in accordance with the
updated setup documentation.
application system that is being implemented, which has been updated to reflect
the additional configuration requirements identified during the prototyping
sessions.
Approach
• Use the Fusion Applications process models as a starting point.
• Update the standard Fusion Applications process models to reflect the

processes the client will employ with the new system.

TE.027.1 – Update Validation Cases (Core)
In this task, you revise the Validation Scripts to align them with the final business
processes.
Activity/Task Group
Update Business Processes and Test Cases
Work Product
Updated Validation Cases – The Updated Validation Cases consist of the set of test
scenarios, that each includes a number of test steps, which should be executed during
the end-to-end solution review.
Prerequisites
Prerequisite Usage
activities.
Approach
• The scope of testing is described through a number of test types that are
performed during the end-to-end solution review, the test items that should be
tested, and the features that should be tested.


IM.050.1 – Implement Integration Packages – Fusion (Optional)
In this task, you build the custom components needed to implement the integrations, data
loads and extensions documented in the Detailed Technical Specifications for Fusion.
Δ If custom integrations are requested as an additional service

Activity/Task Group
Implement Integration Packages
Work Product
Custom Components – Fusion– The Custom Components – Fusion consist of the

actual program code for the integrations, data loads and extensions identified in the
Detailed Technical Specifications for Fusion.
Prerequisites
Prerequisite Usage
Detailed Technical Specifications The Detailed Technical Specification - Fusion pulls together all design elements
- Fusion for a component into a single document so that they can be easily assessed
against each other, against the design guidelines, and against the requirements.
Approach
• Review detailed design documents.
• Code modules.
• Integrate custom modules.
• Perform initial unit tests.
• Perform initial integration tests.

IM.050.2 – Implement Integration Packages – Client Systems (Optional)
In this task, you build the custom components needed to implement the integrations, data
loads and extensions documented in the Detailed Technical Specifications for client
systems.

Activity/Task Group
Work Product
Custom Components – Client Systems – The Custom Components – Client Systems

consist of the actual program code for the integrations, data loads and extensions
identified in the Detailed Technical Specifications for client systems.
Prerequisites
Prerequisite Usage
Detailed Technical Specifications The Detailed Technical Specification – Client Systems pulls together all design
– Client Systems elements for a component into a single document so that they can be easily
assessed against each other, against the design guidelines, and against the
requirements.
Approach
• Review detailed design documents.
• Code modules.
• Integrate custom modules.
• Perform initial unit tests.
• Perform initial integration tests.

IM.050.3 – Load and Validate Data to Client Systems (Optional)
In this task, you load data to client systems, when it is required to support the Fusion
deployment model and associated integrations. For example, if core HR functionality is
deployed in Fusion, but Learning Management resides in an EBS, SuccessFactors or
Taleo system, employee hires, terms and job changes will need to be fed from Fusion to
the legacy system.

for your project, which require data to be loaded to client
systems, you should perform this task.
Activity/Task Group
Work Product
Validated Data – Client Systems – The Validated Data – Client Systems is data that
has been loaded to the client system via a file or other integration means and validated to
correctly reflect the Fusion data in the format required by the client system.
Prerequisites
Prerequisite Usage
utilized to satisfy the integration requirements
Detailed Technical Specification – The Detailed Technical Specification – Client Systems pulls together all design
Client Systems elements for a component into a single document so that they can be easily
requirements.
Custom Components – Client The Custom Components – Client Systems consist of the actual program code
Systems for the integrations, data loads and extensions identified in the Detailed
Technical Specifications for client systems.
Approach

TE.045 – Validate Integration Packages (Optional)
In this task, you validate the proper functioning of implemented integrations.

Activity/Task Group
Work Product
Validated Integration Packages – The Validated Integration Packages represent the

implemented integrations, which have been validated to function as expected, in
accordance with the design.
Prerequisites
Prerequisite Usage
Custom Components – Fusion The Custom Components – Fusion consist of the actual program code for the
integrations, data loads and extensions identified in the Detailed Technical
Specifications for Fusion.
Custom Components – Client The Custom Components – Client Systems consist of the actual program code
Systems for the integrations, data loads and extensions identified in the Detailed
Technical Specifications for client systems.
Approach

CV.065.1 – Load, Reconcile and Validate Data (Core)
In this task, you load client data into the staging environment. This is performed as part of
the second cycle of prototyping performed in the Prototype Phase. Initially, you convert
sufficient data in each information category for test purposes, at the same time making
visible any inconsistencies or inadequacy in the legacy data.
Activity/Task Group
Validate Data Load - Prototype
Work Product
Validated Data – The Validated Data is the client data that has been loaded to the
staging/testing environment via the data load templates or other means and validated to
correctly reflect the legacy data in the format required by the new system.
Prerequisites
Prerequisite Usage
Populated Data Load Templates The populated data load templates provide the extracted client data in the format
required by the new system.
Custom Components Custom components related to custom data loads provide the necessary support
for loading related client data.
Approach
• This task should be iterated until the data load process has been proven.
• Problems with production data are usually invisible until the data load processes
have been run.
• It is assumed that data has been cleansed, but you should look for potential data
issues as part of this process.

The client and Oracle Implementation team have a shared responsibility for this task.

OCM.145 – Provide Change Impact Assessment Approach (Optional)
In this task, you provide the client change lead with the approach, method and artifact for
the analysis of process change and assessment of impact and risk.

task.
Activity/Task Group
Cloud Adoption - Prototype
Work Product
Change Impact Assessment Approach – The Change Impact Assessment Approach

equips the client change lead with the tools and guidance required to conduct an analysis
of the process changes identified and make an assessment of the associated impact and
risk.
Prerequisites
Prerequisite Usage
Process Change Candidate List The Process Change Candidate List contains the client’s current processes or
procedures which have been identified as candidates for change based on the
standard functionality supported by the off-the-shelf products in scope for the
project.
Stakeholder / End User Analysis The Stakeholder/End User Analysis Tools and Techniques provides the client
Tools and Techniques change lead with the necessary tools and methods necessary to conduct a
Stakeholder/End User Analysis and apply the results to the overall
implementation project.
Approach
• This task is aligned with stakeholder analysis (A.140).
• Incorporate updates based on impact assessment.
• Conduct 'model' change enablement workshop.
• Refine the change enablement plan.

WM.050.2 – Conduct Implementation Checkpoint (Core)
Work Product
Implementation Checkpoint Meeting/Approval to Proceed – The Executive

Prerequisites
Prerequisite Usage
Validated Configuration The Validated Configuration verifies that all setup data, including the additional
and revised configuration values, have been entered in accordance with the
updated setup documentation.
Validated Integration Packages The Validated Integration Packages represent the implemented integrations,
which have been validated to function as expected, in accordance with the
design.
Validated Data The Validated Data is the client data that has been loaded to the staging/testing
environment via the data load templates or other means and validated to
Approach

B.PEC.TSK – Manage Project Execution (Core)

needed.
Activity/Task Group
Project Management
Work Product
Prerequisites
Prerequisite Usage
Project Infrastructure Project Infrastructure
release.

Approach


B.PGM.TSK – Program Management (Optional)

this task.
Activity/Task Group
Project Management
Work Product

Prerequisites
Prerequisite Usage
Approach

CHAPTER
6 Validate (C) Phase
T he goal of the Validate phase is to conduct an end-to-end review of the final solution
including any additional configurations, integrations, extensions and client legacy
data.
During the Validate phase, additional configurations required by the client that have not
previously been reviewed, are applied to the Staging Environment and validated An end-
to-end review of the final solution is conducted using established validation cases, which
have been revised to reflect the client’s solution.
During the Validate phase, preparations are made to train a cadre of instructors from the
client’s personnel ranks to teach the end users. One or more train-the-trainer session(s)
is/are conducted to equip those selected to train the end user community in the use of
the new system.
Like the Prototype phase, this phase culminates with an implementation checkpoint to
verify that phase objectives have been achieved and approval to proceed obtained.
Global Methods Validate (C) Phase 6 - 1

Validate Phase Objectives
The objectives of the Validate phase follow:
• Apply final setup changes to the Staging Environment

• Load, reconcile and validate data loads in Staging Environment.
• Confirm solution to be migrated to Production.
• Prepare Training Material (client responsibility).
• Prepare Users for Validation.
• Conduct Train-the-Trainer sessions.
Validate Phase Task Groups

The Validate phase is comprised of the following Task Groups:
• Cloud Adoption – Validate

• Validate Data Load – Validate
• Prepare for End-to-End Review
• End-to-End Review
• Documentation
• Training
Key Work Products

The key work products of the Validate phase are as follows:
Validated Data The Validated Data is the client data

that has been loaded to the
staging/testing environment via the
data load templates or other means
and validated to correctly reflect the
legacy data in the format required by
the new system.
End-to-End Review Results The End-to-End Review Results are

the findings of the end-to-end review of
the application system. It should
validate that the applications work in a
way that is consistent with what the
users expect.
Validate (C) Phase 6 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Trained Trainers The Trained Trainers have learned

what they need to succeed in training
the end users. This knowledge covers
system literacy, procedural, and
business skills.

OCM.165 Facilitate Change Enablement Change Enablement Plan Cloud Adoption Services
Plan have been requested as
CV.065.2 Load, Reconcile and Validate Validated Data Always

Data
MC.060.9 Apply Setup Changes Configured Prototype/Staging Always

Environment
RD.011.3 Update Business Processes Future Process Model Always
TE.027.2 Update Validation Cases Updated Validation Cases Always
TE.105 Prepare Users for Validation Prepared Users Always
TE.070 Conduct End-to-End Review End-to-End Review Results Always
DO.070 Publish User Guide (i.e. Job Aid) User Guide Project-specific
documentation has been
requested as an
additional service
DO.075 Publish Admin Guide Admin Guide Project-specific

documentation has been
requested as an
additional service
TR.080 Prepare Training Material Train-the-Trainer Training Material Always
TR.085 Translate Training Material Translated Train-the-Trainer Material Training materials must
be translated into other
languages

TR.095 Conduct Train-the-Trainer Trained Trainers Always

Workshops

C.PEC.TSK Manage Project Execution Managed Project Assets Always
C.PGM.TSK Program Management Managed Program Project is part of a larger

program
Responsibilities
phase:
• MC.060.9 Apply Setup Changes
• MC.050.4 Update Setup Documentation
• DO.070 Publish User Guide (i.e., Job Aids) (Optional)
• DO.075 Publish Admin Guide (Optional)
• C.PEC.TSK Manage Project Execution
• C.PGM.TSK Program Management
• OCM.165 Facilitate Change Enablement Plan (Optional)
• RD.011.3 Update Business Processes
• TE.027.2 Update Validation Cases
• TE.105 Prepare Users for Validation
• TE.070 Conduct End-to-End Review
• TR.080 Prepare Training Material (except where requested as an additional

service)
• TR.085 Translate Training Material
• TR.095 Conduct Train-the-Trainer Workshops Material (except where requested

as an additional service)
following task in this phase:
• CV.065.2 Load, Reconcile and Validate Data

OCM.165 – Facilitate Change Enablement Plan (Optional)
In this task, you review and provide a survey questionnaire for end user readiness
assessment

task.
Activity/Task Group
Cloud Adoption - Validate
Work Product
Change Enablement Plan – The Change Enablement Plan outlines the plan of action
needed to implement the changes required to achieve organizational readiness with the
new system and addresses the communication of that plan to the entire organization.
Prerequisites
Prerequisite Usage
Change Impact Assessment The Change Impact Assessment Approach equips the client change lead with
Approach the tools and guidance required to conduct an analysis of the process changes
identified in order to make an assessment of the associated impact and risk.
Approach
• Provide access to survey tool for deployment period and deploy survey.
• Assist the Client change lead in preparing a preliminary Communication plan and
matrix (Excel worksheet and our general communication planning framework).
• Provide the Client change lead with an end user Training Plan tool and
artifact (Excel worksheet and training assessment framework).

CV.065.2 – Load, Reconcile and Validate Data (Core)
In this task, you load the extracted client data into the staging/testing environment.
Initially, you convert sufficient data in each information category for test purposes, at the
same time making visible any inconsistencies or inadequacy in the legacy data.
Activity/Task Group
C.TG.DL Validate Data Load - Validate
Work Product
staging/testing environment via the data load templates or other means and validated to
Prerequisites
Prerequisite Usage
Approach
• This task should be iterated until the data load process has been proven.
• Problems with production data are usually invisible until the data load processes
have been run.
• It is assumed that data has been cleansed, but you should look for potential data
issues as part of this process.


MC.060.9 – Apply Setup Changes (Core)
In this task, you update the configurations in the Prototype/Staging Environment to reflect
any final changes as a result of the prototyping workshop sessions conducted in the
Prototype Phase. You enter additional setups, as well as revisions to earlier setup
values, based on the feedback received during the prototyping workshops.
Activity/Task Group
C.TG.PR Prepare for End-to-End Review
Work Product
Configured Prototype/Testing Environment – The Configured Prototype/Testing

Environment is the Staging Environment, which has been updated to reflect additional
and revised setup values for validation/testing in the Validate phase. It is comparable to
a System Test environment.
Prerequisites
Prerequisite Usage
Updated MoSCoW List The Updated MoSCoW List contains a high-level, prioritized list of the additional
Approach
• Identify new or revised configuration settings that have not previously been
applied.
• Have additional configurations been identified?
• Update the Staging Environment with the new and/or revised configurations.

In this task, you update the setup documentation in order to reflect any final changes
made the system configuration.
Activity/Task Group
Work Product

parameters that have been validated during the Prototyping sessions.
Prerequisites
Prerequisite Usage
Reviewed Business Processes The reviewed Business Processes reflect all of the business processes in scope
as they will be implemented in the Production Environment. The supporting
setup document describes the associated setup parameters.
values have been entered in accordance with the revised setup documentation
Approach
• Review the results of the latest Prototype session
• Update any existing setup document with the parameters, user-defined codes,
and other setups that were validated during the latest Prototype session


RD.011.3 – Update Business Processes (Core)
In this task, you update the business process models as necessary to reflect the results
of the prototyping workshops.
Activity/Task Group
Work Product
Future Process Model – The Future Process Model describes the future business
process that the business executes in response to triggering events as a set of one or
more activities. Following this update of the process models, they should reflect all of the
business processes in scope as they will be implemented in the Production Environment.
Prerequisites
Prerequisite Usage
Updated MoSCoW List The Updated MoSCoW List is a prioritized list of the high-level requirements
valid for the application system that is being implemented, which has been
updated to reflect the additional configuration requirements identified during the
prototyping sessions.
Approach
• Use the process models that were updated in the Prototype phase as a starting
point.
• Update the process models to reflect the processes the client will employ with
the new system, including those related to any additional configurations applied
in the Validate phase.

TE.027.2 – Update Validation Cases (Core)
In this task, you revise validation/test cases to align them with the final business
processes.
Activity/Task Group
Work Product
Updated Validation Cases – The Updated Validation Cases consist of the set of test
scenarios, that each includes a number of test steps, which will be executed during the
end-to-end review.
Prerequisites
Prerequisite Usage
activities. Following this update of the process models, they should reflect all of
the business processes in scope as they will be implemented in the Production
Environment.
Approach
• The scope of the validation is described through a number of test types that are
performed during the end-to-end review, the items that should be validated, and
the features that should be validated.


TE.105 – Prepare Users for Validation (Core)
In this task, you provide basic training to users programmed to participate in the End-to-
End Review.
Activity/Task Group
Work Product
Prepared Users – The Prepared Users have been trained on the new system and are
able to conduct the End-to-End Review for their business process area.
Prerequisites
Prerequisite Usage
activities. Following this update of the process models, they should reflect all of
the business processes in scope as they will be implemented in the Production
Environment.
Approach
• The training necessary for users to perform their end-to-end review tasks.
• Instructions on how to read a validation scenarios and how to perform the end-to-
end review.

TE.070 – Conduct End-to-End Review (Core)
In this task, you conduct end-to-end review, by executing the validation cases
documented earlier in the project and using the converted client data. It is comparable to
a System Test.
Activity/Task Group
C.TG.ER End-to-End Review
Work Product
End-to-End Review Results – The End-to-End Review Results are the findings of the
end-to-end review of the application system. It should validate that the applications work
in a way that is consistent with what the users expect.
Prerequisites
Prerequisite Usage
Validated Configuration Before the End-to-End Review can start, the configuration of the
Prototype/Testing Environment must be validated.
Validated Data After the data loads have been validated, the data is ready for use in the End-to-
End Review.
Updated Validation Cases The Updated Validation Cases are used when performing the End-to-End
Review.
User Guide Users should follow and validate the User Guide during the End-to-End Review.
Approach
• Have final configuration settings been applied and validated?
• Has the necessary client data been loaded to the prototype/testing environment
and validated?
• Have required custom components been integrated into the prototype/testing

environment?

• Have validation cases been updated to reflect additional and revised
configuration settings and custom components?

DO.070 – Publish User Guide (i.e., Job Aid) (Optional)
In this task, publish a User Guide, or Job Aid, that defines a set of detailed procedures for
using the applications.

task.
Activity/Task Group
C.TG.DO Documentation
Work Product
User Guide – The User Guide describes a business procedure and provides detailed
instructions for using the applications in response to day-to-day business events.
Prerequisites
Prerequisite Usage
Future Process Model The Validated Configuration verifies that the additional and revised configuration
Validated Configuration The Completed Setup Questionnaires contain the configuration information for
the functionality that is in-scope for the project.
Approach
• The User Guide introduces the user to the purpose of procedures and then
explains the detailed steps and options needed to perform the business task or
transactions.
• Project documentation should be brief and concise.
• The tone of the documentation should be simple and straightforward, rather than
academic or technical.
• Anticipate questions that the user may ask regarding a procedure, and answer
them. As you document these procedures, compare the current and future

approach and add more detailed explanations to the areas that may be confusing
to a user.
• Write the documentation to the level of the targeted audience. If you are
documenting a technical process, include technical details; if you are
documenting a business process, only include technical details if they are
necessary to convey a concept.
• Use diagrams and charts to explain broad or complex concepts. For example, a
paragraph containing many conditions may be more easily understood when the
information is presented in a table or chart.

DO.075 – Publish Admin Guide (Optional)
In this task, publish an Administrative Guide that describes administrative tasks and
processes specific for the customer’s implementation.

task.
Activity/Task Group
C.TG.DO Documentation
Work Product
Admin Guide – The Admin Guide is focused at customer administrators, and describes
administrative tasks and processes specific to the customer’s implementation. It can
contain for example manual data imports that need to be performed on a regular basis
(e.g. for data migration) or specific checks that need to be performed in the application
when a functional issue occurs on configured functionality. It does not describe standard
application administration tasks.
Prerequisites
Prerequisite Usage
Detailed Technical Specifications The Detailed Technical Specification - Fusion pulls together all design elements
- Fusion for a component into a single document so that they can be easily assessed
against each other, against the design guidelines, and against the requirements.
Detailed Technical Specifications The Detailed Technical Specification – Client Systems pulls together all design
– Client Systems elements for a component into a single document so that they can be easily
requirements.
Validated Integration Packages The Validated Integration Packages represent the implemented integrations,
which have been validated to function as expected, in accordance with the
design.
Approach

TR.080 – Prepare Training Material (Core)
In this task, you prepare the training materials needed to conduct a Train-the-Trainer
session for the client personnel identified to teach the end user community.
Activity/Task Group
C.TG.TR Training
Work Product
Train-the-Trainer Training Material – The Train-the-Trainer Training Material consists

of the materials (PowerPoint slides, UPK scripts, etc.) needed to train a cadre of client
personnel who have been designated to teach the end user community how to use the
new system.
Prerequisites
Prerequisite Usage
User Guide The User Guide describes a business procedure and provides detailed
Future Process Model The Future Process Model describes the business processes that the business
executes in response to triggering events as a set of one or more activities.
Approach
• The Train-the-Trainer training materials should address all standard functionality

in scope for the fixed scope offerings included in the project, as well as any
additional configurations and extensions.
• Tailor the existing training materials to reflect the new procedures derived from
the business process changes and the custom extensions, if appropriate.
• The Train-the-Trainer materials are used to equip the designated trainers to be

successful in training the end user community.

The client generally has primary responsibility for this task. However, the Oracle
Implementation team may take responsibility for this task, if requested as an additional
service.
TR.085 – Translate Training Material (Optional)
In this task, you translate the training materials needed to conduct a Train-the-Trainer
session for each language that is in scope for the current release.
Δ If Training Materials must be translated into other languages,

you should perform this task.
Activity/Task Group
C.TG.TR Training
Work Product
Translated Train-the-Trainer Training Material – The Translated Train-the-Trainer

Training Material consists of the materials (PowerPoint slides, UPK scripts, etc.), which
have been translated into the local language(s) required for the current release.
Prerequisites
Prerequisite Usage
User Guide The User Guide describes a business procedure and provides detailed
Future Process Model The Future Process Model describes the business processes that the business
executes in response to triggering events as a set of one or more activities.
Approach
• Begin with the Train-the-Trainer materials that have already been developed for
the primary language of the project
• Translate the PowerPoint slides, UPK scripts, etc into each required language
based on the prioritization described in the MoSCoW list.


TR.095 – Conduct Train-the-Trainer Workshops (Core)
In this task, you train the client personnel who will be training the end users.
Activity/Task Group
C.TG.TR Training
Work Product
Trained Trainers – The Trained Trainers have learned what they need to succeed in
training the end users. This knowledge covers system literacy, procedural, and business
skills.
Prerequisites
Prerequisite Usage
Train-the-Trainer Training The Train-the-Trainer training material is used to train the designated trainers on
Material the new system and equip them to provide training to the end users.
Approach
• Monitor the pulse and progress of the train-the-trainer events as they unfold, to
make sure that the momentum and quality are maintained.

The client generally has primary responsibility for this task. However, the Oracle
Implementation team may take responsibility for this task, if requested as an additional
service.

C WM.050.3 – Conduct Implementation Checkpoint (Core)
Activity/Task Group
C.TG.EC Executive Checkpoint
Work Product
Implementation Checkpoint Meeting/Approval to Proceed – The Implementation

Prerequisites
Prerequisite Usage
End-to-End Review Results The End-to-End Review Results is the application system that has been
reviewed to verify that the applications work in a way that is consistent with what
the users expect.
Validated Configuration The Validated Configuration verifies that the configuration values have been
entered in accordance with the revised setup documentation.
Trained Trainers The Trained Trainers have learned what they need to succeed in training the end
users. This knowledge covers system literacy, procedural, and business skills.
Approach

C.PEC.TSK – Manage Project Execution (Core)

needed.
Activity/Task Group
Project Management
Work Product
Prerequisites
Prerequisite Usage
project.
release.
Approach



C.PGM.TSK – Program Management (Optional)

this task.
Activity/Task Group
Project Management
Work Product

Prerequisites
Prerequisite Usage
Approach

CHAPTER
7 Transition (D) Phase
T he goal of the Transition phase is to deploy the new system into the organization. All
the elements must come together to transition successfully to active system use.
During Transition, the configuration that was validated during the Validate phase is
moved to the Production Environment and client legacy data is loaded, reconciled and
validated.
A final validation review is conducted with users and stakeholders to verify that the
system is ready for use, an assessment is made of operational readiness, and the phase
culminates with the new system being placed into use.
Global Methods Transition (D) Phase 7 - 1

Transition Phase Objectives
The objectives of the Transition phase follow:
• Configure the Production Environment.

• Load, reconcile and validate data loads in the Production Environment.
• Conduct Final Validation Review.
• Verify Production and Operational Readiness.
• Begin system use.
Transition Phase Task Groups

• Prepare for Transition

• Final Validation
• Training
• Transition to System Use
Key Work Products

The key work products of the Transition phase are as follows:
Validated Production Environment The Validated Production Environment

represents the final review of the
Production Environment by the client to
ensure its’ readiness for use.
Production and Operational Readiness The Production and Operational

Verification Readiness Verification consists of
checklists and optionally, a quality
assurance review that allows you to
verify production readiness.
System in Use The System in Use is a system for

which you have verified that all aspects
of the system are operational and
active use is achieved.

Transition (D) Phase 7 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
TS.050 Migrate Configuration to Configured Production Environment Always

Production
CV.065.3 Load, Reconcile and Validate Validated Data Always

Data Loads in Production
TE.120 Conduct Final Validation Review Validated Production Environment Always

with Users & Stakeholders
TR.100 Conduct End-User Training Skilled Users Always
TS.052 Implement Support Support Infrastructure Always

Infrastructure
TS.058 Verify Production and Production and Operational Always

Operational Readiness Readiness Verification
TS.060 Begin System Use System in Use Always
D.PEC.TSK Manage Project Execution Managed Project Assets Always
D.PGM.TSK Program Management Managed Program Project is part of a larger

program
Responsibilities
phase:
• TS.050 Migrate Configuration to Production
• D.PEC.TSK Manage Project Execution
• D.PGM.TSK Program Management
• TR.100 Conduct End User Training
• TS.052 Implement Support Infrastructure
• TE.058 Verify Production and Operational Readiness
• TS.060 Begin System Use

• CV.065.3 Load, Reconcile and Validate Data Loads in Production
• TE.120 Conduct Final Validation Review with Users and Stakeholders
TS.050 – Migrate Configuration to Production (Core)
In this task, you migrate the validated configuration to the Production Environment.
Activity/Task Group
D.TG.PT Prepare for Transition
Work Product
Configured Production Environment – The Configured Production Environment is

complete once the application setups are applied to the Production Environment.
Prerequisites
Prerequisite Usage
Setup Documentation The Setup Documentation defines the detailed setup parameters that have been
validated.
End-to-End Review Results The End-to-End Review Results is the application system that has been
reviewed to verify that the applications work in a way that is consistent with what
the users expect.
Approach
• Use the setup documentation and applicable tools, such as Fusion Functional
Setup Manager, as appropriate to configure the Production Environment with the
validated and reviewed configuration values.
• Review the setups in the Production Environment to ensure that they have been
migrated correctly.
• Involve the client in reviewing the setups in production.


CV.065.3 – Load, Reconcile and Validate Data Loads in Production (Core)
In this task, you load the extracted client data into the Production Environment.
Activity/Task Group
D.TG.PT Prepare for Transition
Work Product
Production Environment via the data load templates or other means and validated to
Prerequisites
Prerequisite Usage
Validated Data The validated data from the Validate phase reflects the successful completion
and validation of uploaded client data from the previous trial data load iterations.
Approach
• During the Transition phase, the initial load of the production database is typically
carried out after the Production Environment is set up.
• A checklist and log of the data loads that were executed on the production
database should be provided and the correctness of the loads should be verified.

TE.120 – Conduct Final Validation Review with Users and Stakeholders (Core)
In this task, you review configured Production Environment with users and stakeholders.
Activity/Task Group
D.TG.FV Final Validation
Work Product
Validated Production Environment – The Validated Production Environment

represents the final review of the Production Environment by the client to ensure its’
readiness for use. It is comparable to a User Acceptance, in that it effectively represents
the client’s willingness to proceed with system use.
Prerequisites
Prerequisite Usage
Configured Production The Configured Production Environment is complete once the application setups
Environment are applied to the Production Environment.
Validated Data The Validated Data is the client data that has been loaded to the Production
Environment via the data load templates or other means and validated to
Approach
• Have acceptance criteria been established?
• Does the Production Environment meet the acceptance criteria?


TR.100 – Conduct End-User Training (Core)
In this task, the client trainers provide training in the use of the system to the other end
users.
Activity/Task Group
D.TG.TR Training
Work Product
Skilled Users – Users have learned what they need to succeed in their new roles. This
knowledge covers system literacy, procedural, and business skills
Prerequisites
Prerequisite Usage
Configured Prototype/Staging This environment will be used to conduct the training

Environment
Trained Trainers The client Trainers will be deliver the training to the end users
Approach
• What specific tasks each group of user will need to perform on the system?
• Pay special attention to how the users daily tasks will change, especially if the
related business process has been updated
• Be sensitive to the fact that some users will welcome the change, whilst other
may initially be resistant to change
• Be sensitive to the fact that some users might find being in a training
environment confronting


TS.052 – Implement Support Infrastructure (Core)
In this task, you activate the support personnel and procedures for the new business
system and review requirements for support-related services from software suppliers,
contractors, help desks, and other support services.
Activity/Task Group
D.TG.TS Transition to System Use
Work Product
Support Infrastructure - The Support Infrastructure addresses call and response

tracking, links to external support mechanisms or sources and the understanding of
performance metrics by support personnel (response, history retention, follow-up,
accuracy, audit, etc.)
Prerequisites
Prerequisite Usage
Skilled Users Users will need to understand the processes for logging support calls, and the
expected response time period
Approach
• It is important to rehearse the support procedures. You can simulate various

types of support calls and evaluate whether the expected response time,
accuracy of the resolutions, and the general flow of the process are adequate to
support the request volume. This is also a good opportunity to test default
support mechanisms, after-business-hours support, and supplier support
hotlines.
• The establishment of a robust and capable internal and vendor external support
infrastructure is critical to the success of the project

TS.058 – Verify Production and Operational Readiness (Core)
In this task, you verify that all teams and required operational procedures are in place
and are ready to use the system
Activity/Task Group
Work Product
Production and Operational Readiness Verification – The Production and Operational

Readiness Verification consists of checklists and optionally, a quality assurance review
that allows you to verify production readiness.
Prerequisites
Prerequisite Usage
Validated Production Environment The Validated Production Environment represents the final review of the
Production Environment by the client to ensure its’ readiness for use. It is
comparable to a User Acceptance, in that it effectively represents the client’s
willingness to proceed with system use.
Approach
• Have key users should gone through the Production Environment setup and data
to confirm that every screen can be accessed and all reports print successfully?
• Have all testing activities been closed?
• Have users been trained and are the ready to use the new system in the
execution of their responsibilities?
• Is the necessary support infrastructure in place?


TS.060 – Begin System Use (Core)
In this task, you begin production use of the new system.
Activity/Task Group
Work Product
System in Use – The System in Use is a system for which you have verified that all
aspects of the system are operational and active use is achieved.
Prerequisites
Prerequisite Usage
Production and Operational The Production and Operational Readiness Verification consists of checklists
Readiness Verification and optionally, a quality assurance review that allows you to verify production
readiness.
Approach
• The best way to begin using the new system is to control the initial transactions
and entries.
• Bring up departments or sets of related transactions in sequence to permit

focused attention on limited areas until they are stabilized.


D.PEC.TSK – Manage Project Execution (Core)

needed.
Activity/Task Group
Project Management
Work Product
Prerequisites
Prerequisite Usage
project.
release.
Approach



D.PGM.TSK – Program Management (Optional)

this task.
Activity/Task Group
Project Management
Work Product

Prerequisites
Prerequisite Usage
Approach

CHAPTER
8 Sustain (E) Phase
T he goal of the Sustain phase is to effectively manage the transition to steady-state

operations and plan for the next release.
The Sustain phase marks the last phase of the implementation and the beginning of the
system support cycle. During this phase a workshop is conducted to develop a roadmap
that addresses plans for the next release, ongoing maintenance and sustainability of the
system, and the establishment of organizational structures and processes to provide
adequate governance of the new system.
Global Methods Sustain (E) Phase 8 - 1

Sustain Phase Objectives
The objectives of the Sustain phase follow:
• Manage Transition to Steady-state Operations.

• Plan for Next Release.
• Provide Post-Go Live Support.
Sustain Phase Task Groups

• Stabilization and Planning

• Cloud Adoption – Sustain
Key Work Products

The key work products of the Sustain phase are as follows:
Steady-State Operations Steady-State Operations exist when

the system has achieved a stable
state. Daily use of the system has
become routine and disruptions that
may have characterized the initial
stage of operation have receded.
Updated MoSCoW List and Release Plan The Updated MoSCoW List and
Release Plan provide a high-level,
prioritized list of the requirements that
remain and the plan for the achieving
them.

PS.005 Manage Transition to Steady- Steady-State Operations Always

State Operations
PS.140 Plan for Next Release Updated MoSCoW List and Release Always
Plan
Sustain (E) Phase 8 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
PS.065 Post Go-Live Support Post Go-Live Support Always
OCM.265 Perform Change Completion Change Enablement Checklist Cloud Adoption Services
Check Point have been requested as
E.PEC.TSK Conduct Roadmap Workshop Manage Project Execution Always
E.PGM.TSK Program Management Managed Program Project is part of a larger

program
Responsibilities
phase:
• PS.065 Post Go-Live Support
• E.PEC.TSK Manage Project Execution
• E.PGM.TSK Program Management
• OCM.265 Perform Change Completion Check Point
• PS.005 Manage Transition to Steady-State Operations
• PS.140 Plan for Next Release

PS.005 – Manage Transition to Steady-State Operations (Core)
In this task, you monitor the client's transition to routine operations and assist as
necessary to achieve steady-state operations.
Activity/Task Group
E.TG.SP Stabilization and Planning
Work Product
Steady-State Operations – Steady-State Operations exist when the system has

achieved a stable state. Daily use of the system has become routine and disruptions that
may have characterized the initial stage of operation have receded.
Prerequisites
Prerequisite Usage
System in Use The System in Use is the system, which has been placed into active operation.
Approach
• Have users been adequately trained on the use of the new system to perform
their functions?
• Is there a clearly communicated process for reporting issues and escalating

them, if necessary?
• Are follow-on releases planned, or are there enhancements that would contribute
to improved operations?

PS.140 – Plan for Next Release (Core)
In this task, you conduct a workshop with client personnel to review the results of the
recently completed release and plan for next release.
Activity/Task Group
Work Product
Updated MoSCoW List and Release Plan – The Updated MoSCoW List and Release
Plan provide a high-level, prioritized list of the requirements that remain and the plan for
the achieving them.
Prerequisites
Prerequisite Usage
Updated MoSCoW List The Updated MoSCoW List provides a high-level, prioritized listing of the
requirements.
Final Release Plan The Final Release Plan contains the finalized listing of the planned releases and
describes the content of each release.
Approach
• Have the objectives of the previous release been achieved?
• Have the client’s objectives for the next release changed?
• Does the revised Release Plan reflect the client’s current priorities?


PS.065 – Post Go-Live Support (Core)
In this task, you provide Post Go-Live Support as specified in the contract.
Activity/Task Group
Work Product
Post Go-Live Support – Post Go-Live Support consists of monitoring and responding to
problems and issues throughout the post-production support period, as specified in the
contract.
Prerequisites
Prerequisite Usage
System in Use The System in Use is the system, which has been placed into active operation
Approach
• Create a system or process to effectively maintain the production system and

respond to users’ requests.

OCM.265 – Perform Change Completion Check Point (Optional)
In this task, you verify the effectiveness of the change enablement plan, which was put
into action.

task.
Activity/Task Group
Cloud Adoption - Sustain
Work Product
Change Enablement Checklist – The Change Enablement Checklist documents the

findings of the change completion check point.
Prerequisites
Prerequisite Usage
Change Enablement Plan The Change Enablement Plan outlines the plan of action needed to implement
the changes required to achieve organizational readiness with the new system.
Approach


E.PEC.TSK – Manage Project Execution (Core)

needed.
Activity/Task Group
E.TG.PM Project Management
Work Product
Prerequisites
Prerequisite Usage
project.
release.
Approach


E.PGM.TSK – Program Management (Optional)
Activity/Task Group
E.TG.PM Project Management
Work Product

Prerequisites
Prerequisite Usage
Approach

CHAPTER
9 Project Closure (PC)

Phase
T he goal of the Project Closure phase is to close the project from an administrative
and contractual standpoint.
Global Methods Project Closure (PC) Phase 9 - 1

Project Closure Phase Objectives
The objectives of the Project Closure phase follow:
• Validate that the project work products are complete
• Gain final sign-off
• Collect documents for reuse and retention
• Close contract and processes
Project Closure Phase Activities

The Project Closure phase is comprised of the following activities:
• Project Closure
Key Work Products

The key work products of the Project Closure phase are as follows:
Final Acceptance Certificate Certificate verifying that the contracted

project scope was delivered.
Closed Processes and Contract Contract and related project processes

are closed.

PC.ACT.GA Gain Acceptance Final Acceptance Certificate Always
PS.ACT.CPC Close Processes and Contract Closed Processes and Contract Always
PS.ACT.DLLAP Document Lessons Learned and Lessons Learned and Archived Project Always
Archive Project
Project Closures (PC) Phase 9 - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Responsibilities
phase:
• Gain Acceptance
• Close Processes and Contract
• Document Lessons Learned and Archive Project

PC.ACT.GA – Gain Acceptance (Core)
In this task, you validate the project scope was delivered per the contract.
Activity/Task Group
PC.ACT Project Closure
Work Product
Final Acceptance Certificate – The Final Acceptance Certificate verifying that the
contracted project scope was delivered.
Prerequisites
Prerequisite Usage
scope of the project; the modules purchased, the agreements, and so on. The
contract and associated documentation is validated against to determine if
contractual scope was delivered.
Approach
• Validate with client that project scope was delivered.
• If Fixed Price, gain acceptance from the client on the overall project. (Note:
make sure that client acceptance is documented on all outstanding project work
products

PS.ACT.CPC – Close Processes and Contract (Core)
In this task, the contract and the project processes for each of the project management
processes are closed.
Activity/Task Group
Work Product
Closed Processes and Contract – The Closed Processes and Contract closes the
contract and the project processes for each of the project management processes.
Prerequisites
Prerequisite Usage
scope of the project, the modules purchased, the agreements, and so on. The
contract and associated documentation is validated against to determine if
contractual scope was delivered.
Final Acceptance Certificate The Final Acceptance Certificate verifying that the contracted project scope was
delivered.
Approach
• Release staff
• Close Project Processes (Project Financials, Issue, Risk, and Problem logs, and
other infrastructure process)
• Close Contract

PS.ACT.DLLAP – Document Lessons Learned and Archive Project (Core)
In this task, the project manager compile the lessons learned documented during project
execution and control, and the project is archived.
Activity/Task Group
Work Product
Lessons Learned and Archived Project – The Lessons Learned and Archived Project
is a consolidation of the lessons learned throughout the project and contains the archived
project documentation for reuse and retention.
Prerequisites
Prerequisite Usage
Final Acceptance Certificate The Final Acceptance Certificate verifying that the contracted project scope was
delivered.
Approach
• Document Lessons Learned (Note: Documenting Lessons Learned is an on-

going activity. At this point, the Lessons Learned from the project should be
consolidated)
• Archive project documentation following project archiving standards and

guidelines
• Submit final reports such as Project Engagement Summary


APPENDIX
A Work Breakdown Structure

T his appendix provides listing of the work breakdown structure (WBS) for the OUM
Cloud Application Services Implementation Approach.
How to Read the Work Breakdown Structure

The OUM Cloud Application Services Implementation Approach WBS is comprised of
three elements: phases, activities/task groups, and tasks. Each element is indicated
graphically as shown in the following legend:
A Plan Phase
A.TG.TR Prepare Project Team Activity/Task Group
STM.050 ♦Conduct Kickoff Meeting Task
OUM Cloud Application Services Implementation Approach WBS

The following is a listing of the OUM Cloud Application Services Implementation
Approach work breakdown structure.
Phase Activity/Task Task ID Task Name Work Product

Group
Project Start Up [PS]
PS.ACT Review Bid and Contract
PS.ACT.RBC Review Bid and Contract Confirmed Bid and Contract
PS.ACT Review Project Assets with Client
PS.ACT.RPAC Review Project Assets with Reviewed Project Assets
Client
PS.ACT Review Scope, Workplan and Budget
Global Methods Work Breakdown Structure A - 1

Group
PS.ACT.VSSOS Validate Scope and Validated Scope
Stakeholders
PS.ACT.DW Develop Workplan High-Level Project Workplan
PS.ACT.DSPB Develop Staff Plan and Budget Staff Plan and Budget
PS.ACT Create Project Governance, policies and supporting infrastructure
PS.ACT.CPMP Create Project Management Project Management Plan
Plan
PS.ACT.EPI Establish Project Infrastructure Project Infrastructure
Plan [A]
(A.TG.TR) Prepare Project Team
STM.050 Conduct Kick-Off Meeting Oriented Project Team
TR.050 Train Project Team Trained Project Team
(A.TG.PL) Release Planning
WM.070 Schedule Workshops Workshop Schedule
WM.010 Create Detailed Plan for Current Detailed Release Plan
Release
(A.TG.GS) Gather Setup Information
RD.011.1 Review In-Scope High-Level Reviewed Business Processes
Business Processes
MC.040.1 Gather Setup Information Completed Setup
Questionnaires
(A.TG.TW) Conduct Technical Workshops
TA.030 Conduct Integration Workshop Integration Strategy
CV.010 Conduct Data Load Workshop Data Load Strategy
(A.TG.DO) Documentation
DO.010 Define Documentation Documentation Requirements
Requirements and Strategy and Strategy
(A.TG.CA) Cloud Adoption - Plan
OCM.015 Identify Process Change Process Change Candidate List
Candidates
OCM.035 Create Change Plan Change Enablement Plan
OCM.065 Provide Stakeholder / End User Stakeholder / End User Analysis
Analysis Guidance Tools and Techniques
(A.TG.EC) Executive Checkpoint
WM.050.1 Conduct Implementation Implementation Checkpoint
(A.TG.PM) Project Management
A.PEC.TSK Manage Project Execution Managed Project Assets
Prototype [B]
(B.TG.PC1) Prototype Configuration - Iteration 1
Work Breakdown Structure A - 2 OUM Cloud Application Services Implementation Approach Solution Delivery Guide
Group
MC.060.1 Perform Initial Setup Configured Prototype/Staging
Environment
TE.020 Prepare Validation Scripts Validation Scripts
MC.070 Conduct Workshops & Prototype Reviewed Prototype
Configuration
MC.040.2 Capture & Prioritize Additional Updated MoSCoW List
Configurations
MC.050.1 Update Setup Documentation Setup Documentation
MC.063 Conduct Configuration Configuration Familiarization
Familiarization Session Session
(B.TG.ID) Prepare Integration Details
DS.140.1 Prepare Detailed Technical Detailed Technical Specification
Specifications - Fusion - Fusion
DS.140.2 Prepare Detailed Technical Detailed Technical Specification
Specifications - Client Legacy – Client Systems
Systems
(B.TG.DL) Prepare for Data Loads
CV.027.1 Perform Data Mapping Data Mapping
CV.053 Populate Data Load Templates Populated Data Load Templates
With Client Data
(B.TG.PC2) Prototype Configuration - Iteration 2
MC.060.2 Apply Setup Changes Configured Prototype/Staging
Environment
MC.065.1 Validate Setup Changes Validated Configuration
MC.050.2 Document Functional Security Functional Security
Documentation
MC.085 Prepare Reports Developed Reports
MC.050.3 Update Setup Documentation Setup Documentation
(B.TG.EE) Implement Extensible Elements
MC.060.3 Implement Workflows Configured Workflows
MC.060.4 Implement Notifications Configured Notifications
MC.060.5 Implement FastFormulas Configured FastFormulas
MC.060.6 Implement FlexFields Configured Flexfields
MC.060.7 Implement Localizations Implemented Localizations
MC.060.8 Implement Composer Updates Implemented Composer
Updates
MC.065.2 Validate Setup Changes Validated Configuration
(B.TG.BP) Update Business Process Models and Test Cases
RD.011.2 Update Business Processes Future Process Model
TE.027.1 Update Validation Cases Updated Validation Cases
(B.TG.IP) Implement Integration Packages

Group
IM.050.1 Implement Integration Packages Custom Components - Fusion
- Fusion
IM.050.2 Implement Integration Packages Custom Components – Client
- Client Systems Systems
IM.050.3 Load and Validate Data to Client Validated Data
Systems
TE.045 Validate Integration Packages Validated Integration Packages
(B.TG.VL) Validate Data Load - Prototype
CV.065.1 Load, Reconcile & Validate Data Validated Data
(B.TG.CA) Cloud Adoption - Prototype
OCM.145 Provide Change Impact Change Impact Assessment
Assessment Approach Approach
(B.TG.EC) Executive Checkpoint
(B.TG.PM) Project Management
B.PEC.TSK Manage Project Execution Managed Project Assets
Validate [C]
(C.TG.CA) Cloud Adoption - Validate
OCM.165 Facilitate Change Enablement Change Enablement Plan
Plan
(C.TG.DL) Validate Data Load - Validate
(C.TG.PR) Prepare for End-to-End Review
MC.060.9 Apply Setup Changes Configured Prototype/Staging
Environment
MC.050.4 Update Setup documentation Setup Documentation
RD.011.3 Update Business Processes Future Process Model
TE.027.2 Update Validation Cases Updated Test Cases
TE.105 Prepare Users for Validation Prepared Users
(C.TG.ER) End-to-End Review
TE.070 Conduct End-to-End Review End-to-End Review Results
(C.TG.DO) Documentation
DO.070 Publish User Guide (i.e., Job User Guide
Aids)
DO.075 Publish Admin Guide Admin Guide
(C.TG.TR) Training
TR.080 Prepare Training Material Train-the-Trainer Training
Material
Group
TR.085 Translate Training Material Translated Train-the-Trainer
Material
TR.095 Conduct Train-the-Trainer Trained Trainers
Workshops
(C.TG.EC) Executive Checkpoint
(C.TG.PM) Project Management
C.PEC.TSK Manage Project Execution Managed Project Assets
Transition [D]
(D.TG.PT) Prepare for Transition
TS.050 Migrate Configuration to Configured Production
Production Environment
Loads in Production
(D.TG.FV) Final Validation
TE.120 Conduct Final Validation Review Validated Production
with Users & Stakeholders Environment
(D.TG.TR) Training
TR.100 Conduct End-User Training Skilled Users
(D.TG.TS) Transition to System Use
TS.052 Implement Support Support Infrastructure
Infrastructure
TS.058 Verify Production & Operational Production & Operational
Readiness Readiness Verification
TS.060 Begin System Use System in Use
(D.TG.PM) Project Management
D.PEC.TSK Manage Project Execution Managed Project Assets
Sustain [E]
(E.TG.SP) Stabilization and Planning
PS.005 Manage Transition to Steady- Steady-state Operations
state Operations
PS.140 Plan for next Release Updated MoSCoW List and
Release Plan
PS.065 Post Go-Live Support Post Go-Live Support
(E.TG.CA) Cloud Adoption - Sustain
OCM.265 Perform Change Completion Change Enablement Checklist
Check Point
(E.TG.PM) Project Management
E.PEC.TSK Manage Project Execution Managed Project Assets
Project Closure [PC]

Group
(PC.ACT) Project Closure
PC.ACT.GA Gain Acceptance Final Acceptance Certificate
PS.ACT.CPC Close Processes and Contract Closed Processes and Contract
PS.ACT.DLLAP Document Lessons Learned and Lessons Learned and Archived
Archive Project Project

Oum Cloud Application Services Implementation Approach SDG

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oum Cloud Application Services Implementation Approach SDG

Uploaded by

Copyright:

Available Formats

ORACLE UNIFIED METHOD

CLOUD APPLICATION SERVICES

Authors: Oracle's Global Methods Team

C H A P T E R 1 Introduction ................................................................................................ 1-1

What is the OUM Cloud Application Services Implementation

How to Use This Guide ..........................................................................1-3

C H A P T E R 2 Approach Overview ................................................................................... 2-1

Core and Optional Tasks .......................................................................2-6

C H A P T E R 3 Project Start Up (PS) Phase ..................................................................... 3-1

Project Start Up Phase Objectives ........................................................3-2

PS.ACT.RBC – Review Bid and Contract (Core) ..................................3-5

Global Methods Contents i

C H A P T E R 4 Plan (A) Phase ............................................................................................4-1

Plan Phase Objectives .......................................................................... 4-2

STM.050 – Conduct Kick-Off Meeting (Core) ....................................... 4-6

Global Methods Contents iii

C H A P T E R 5 Prototype (B) Phase ...................................................................................5-1

Prototype Phase Objectives .................................................................. 5-2

MC.060.1 – Perform Initial Setup (Core) ............................................... 5-8

Global Methods Contents v

Global Methods Contents vii

C H A P T E R 6 Validate (C) Phase ......................................................................................6-1

Validate Phase Objectives .................................................................... 6-2

OCM.165 – Facilitate Change Enablement Plan (Optional) ................. 6-6

Global Methods Contents ix

C H A P T E R 7 Transition (D) Phase...................................................................................7-1

Transition Phase Objectives.................................................................. 7-2

TS.050 – Migrate Configuration to Production (Core)........................... 7-5

Global Methods Contents xi

C H A P T E R 8 Sustain (E) Phase .......................................................................................8-1

Sustain Phase Objectives ..................................................................... 8-2

PS.005 – Manage Transition to Steady-State Operations (Core)......... 8-4

C H A P T E R 9 Project Closure (PC) Phase......................................................................9-1

Project Closure Phase Objectives......................................................... 9-2

PC.ACT.GA – Gain Acceptance (Core) ................................................ 9-4

APPENDIX A Work Breakdown Structure ......................................................................A-1

Global Methods Contents xiii

T he OUM Cloud Application Services Implementation Approach Solution Delivery

Global Methods Introduction 1 - 1

Your Feedback is Requested

Global Methods Introduction 1 - 3

T he OUM Cloud Application Services Implementation Approach is being introduced to

Global Methods Approach Overview 2 - 1

• Rapid design, configuration and deployment of an initial release of the software

Global Methods Approach Overview 2 - 3

The approach is comprised of 5 phases – Plan, Prototype, Validate, Transition and

Global Methods Approach Overview 2 - 5

Task Selection Guidelines

• Iterative Prototyping Workshops

Global Methods Approach Overview 2 - 7

Project management in an OUM Cloud Application Services implementation is not

Iterative Prototyping Workshops

3 Project Start Up (PS)

Global Methods Project Start Up (PS) Phase 3 - 1

• Statement of work is reviewed and agreement with client obtained

• Parties agree to their commitment related to the project

• Project budget is reviewed and finalized

• Infrastructure is established for issue, risk, problem tracking, configuration

• Quality assurance tasks are planned

• Project team orientation is conducted

Project Start Up Phase Activities

• Review Bid and Contract

• Review Project Assets with Client