Nicholas king oracle epm migration and upgrade

Copyright © 2009 Rolta International, Inc., All Rights Reserved
Oracle EPM Migration and Upgrade
A Complete Solution

 Why Upgrade / Migrate?
 Critical Success Factors & Considerations
 Migrations vs. In-Place Upgrades
 Migration Methodology
 Sample Timeline
 Questions
Oracle EPM Migration and Upgrades

Support Compliance
System Integration
Functionality Exposure
Scalability / Performance
Improved / Consistent User Interface
Reusability of Business Logic (Dimensions, Calculation Rules)
Improved Maintenance & Administration Features
Licensing and Ongoing Support
Centralize Development and Administration Functions (Center of
Excellence)
Oracle EPM Migration and Upgrade: Why Upgrade?

In order to facilitate a controlled Hyperion upgrade, organizations must
manage requirements from both the business & technical communities.
Critical Success Factors
 Migrate the existing applications and objects while maintaining business
functionality
 Minimize outage to reduce impact to business users
 Cultivate knowledge of new environment (new modules, feature functionality)
 User acceptance testing and sign off
 Instantiate the competency to manage and administer the Hyperion Solutions
 Create/Modify existing processes in order to leverage improved architecture
 Establish/Re-align Support Team expectations
Oracle EPM Migration and Upgrade: Keys to Success

With the technical innovations delivered through System 9 / Release 11 comes unsurpassed scalability and
performance. In order to achieve this benefit the underlying architecture is distributed and as such more
complex then previous Hyperion releases. IT must be conscious of the role they will play going forward in
jointly administering and maintaining the upgraded environment.
“What does each side want from a migration and implementation?”
Technical Support Needs
 Knowledge and understanding of the environment (HW and SW)
 Well-defined support activities and roles
 Clear definition of system availability expectations
Business Support Needs
 Education of existing and new functionality
 Confidence in stability, availability, and accuracy of upgraded solutions
 Establishment of administration/maintenance jurisdiction (IT & Business)
Keys to Success: Support Paradigm Shift

Business Knowedge
The financial close
process
Dimension and Hierarchy
knowledge
How to tie out the data
What points of view to use
for testing and fact finding
When or if this feature was
working last
Detailed ETL flow
Knowledge of how the
product modules interact
Functional product
knowledge
IT Knowledge
How to read logs, interact
with web application
servers, databases, and
client/server applications
Review server / network /
database status to
pinpoint issues
24/7 support infrastructure
Backups / recovery
procedures
Security and Enterprise
Authentication
Administrative view of the
entire end to end system
Keys to Success: Technical & Business Support

Varying Architectural Configurations
Different Technical Standards
Multiple Hyperion Application and User Interface Configurations
Degree of Solution Customization / Complexity
Extent of Upgrade/Migration
Availability of Productivity Tools and Utilities
Resource Availability
Degree of Architectural Sophistication
Service Level Agreement (SLA) Requirements
Security Requirements
“Even though the scope of upgrades and migrations can vary greatly, there
is a methodology with a core set of activities that should be followed.”
Considerations: Every Upgrade / Migration is Different

In-Place Upgrades
Upgrade software over existing version
leveraging the same hardware
Pros:
Reduces implementation time
Eliminates need for new hardware
Reduces chance for application corruption
Cons (unless Hosting Service is Leveraged):
Extends outage
Compromises ability to recover/roll-back
Complicates audit & validation of upgraded
solution
Migration And Upgrade
Software installation on net new hardware with
associated migration of business applications
Pros:
Minimizes system outage
Supports validation of upgraded systems
Facilitates parallel environment during
transition period
Leverages provisioning of upgraded HW
Cons:
Procurement and configuration of new
Hardware
Requires support of two environments
(temporarily); resource constraints
Oracle EPM Migration and Upgrade: Two Approaches

p. 9
Summary
• Evaluate Goals and Expectations
• New Development
• Consolidation of Systems
• Implementation of New Features
• Conversion Team will evaluate the Current State
• Inventory of Automation Scripts
• Inventory of Essbase objects
• Inventory or Applications (Planning, Essbase, FDM, other)
• Security
• Plan the Implementation Strategy
Key Deliverables
• Inventory of Applications
• Inventory of Report Objects
• Inventory of Scripts
• Final Project Plan and Project Schedule
Milestones
• Scope Solidified
• Project Plan Adjustments
The Migration Assessment Phase consists of the tasks associated with scoping the migration
effort. Through the facilitation of focused, fact-finding meetings targeted at the technical
architecture, supporting database, integration with external systems, reporting/user interface,
and security the remaining effort associated with the Migration Project is scoped.
Migration
Assessment
Installation Migration
Validation &
Stabilization
Training &
Learning
Sessions
Oracle EPM Migration and Upgrade: Phase Detail

p. 10
Activities
• Review Business Goals and Expectations
• Meet with Business and Technology Owners to understand
expectations of the Project
• Define the project success factors
• Evaluate opportunities for Improvement
• Consolidation of Applications or Systems
• Rationalization of current state
• Implementation of new applications
Deliverables
• Revised Project Charter and Project Objectives
Tips
• Nothing is “out of scope” yet; all ideas are welcome
• Be open to new options and new ways of doing things
Migration Assessment Installation Migration
Validation &
Stabilization
Training &
Learning
Sessions
Migration
Assessment
Goals &
Expectations
Goals &
Expectations Define Roles
Define Roles
Phase Detail: Migration Assessment
Inventory
Inventory

p. 11
Activities
• Inventory of Applications / Cubes
• Automation Scripts
• Filters and Groups
• Variables
• Calc Scripts, Load Rules, and Reports
• MaxL / esscmd Scripts
• Inventory of Report Objects
• Inventory of Security
• Review Usage Volumes and Performance Requirements
Tools
• .NET application that inventories Essbase Cubes, Filters,
Groups, Variables, Partitions, and Objects
• Inventory of Report Objects Tools (Perl/SQL)
• Inventory of Security Tools Reports (Perl/SQL)
• .NET application that inventories users and groups
Tips
• This is a point in time inventory. New Development after the
inventory will not be captured
• Data Refresh occurs often on a Monthly or Daily Cycle.
Some items may change between the inventory and actual
migration
• Verify security is not done at a user level
Validation &
Stabilization
Training &
Learning
Sessions
Migration
Assessment
Goals &
Expectations
Goals &
Define Roles
Inventory
Inventory

p. 12
Migration
Assessment
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Define Roles for Client Team and Project Team Members
• Compile detailed worksheet for tracking object migration
through the migration lifecycle
• Define Project Team and Client Team Hyperion Administrators
• Define Development members on Client Team
• Document and Define Testing Responsibilities and defect
tracking processes
Tools
• Excel
• MS Project
• Frequent Communication
Tips
• Integrate the Reporting and Essbase Development teams in
the Migration Approach and provide detailed tasks to foster
the knowledge growth of the new application
• Work closely with the technical support teams to define the
needs and support techniques necessary to support the
application upon project completion
Goals &
Expectations
Goals &
Define Roles
Inventory
Inventory

p. 13
Migration
Assessment
Validation &
Stabilization
Training &
Learning
Sessions
Review
• Has the scope changed?
• Has the project schedule been completed and approved?
• Have budget requirements been changed and approved?
• Have roles and resources been identified?
• Has the technical infrastructure been architected and approved?

p. 14
Summary
• Establish target hardware platform
• Install supporting services (i.e. database services, web services,)
• Install appropriate versions of the Foundation Services
• Install relevant modules of the BI+ platform
• Integrate Hyperion shared services with external services (i.e. database
services, web services, security services, etc.)
• Validate environment
Key Deliverables
• Target Hardware Environment Established
• Support services installed
• System Foundation Services installed
• System BI+ modules installed
Milestones
• Environment validated
• Integration with Active Directory
• Applications functional
The Installation Phase is denoted by the activities associated with creation of an environment prepared as the
target of the migrated objects. Once the target environment is established, extensive review and testing of each
component is necessary.
Migration
Assessment
Validation &
Stabilization
Training &
Learning
Sessions

p. 15
InstallationInstallation
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Pre-install tasks:
• Review Node Setup (Disk, Network, Swap/Memory, 64 bit?)
• Create Relational Databases
• DCOM, Internet Information Services, ASP .NET ?
• Service Accounts / Privileges
• Oracle Client Software
• Web Application Server
• SSL Certificates
• Load Balancer Setup
Tools
• Ping
• Nslookup
• Telnet
Tips
• Pre Installation Tasks are very important – finding issues
now is easy – troubleshooting a Hyperion problem caused
by an underlying issue will be tedious.
• Hyperion is heavily coupled with the OS – Operating System
issues reveal themselves in hard to find ways.
Phase Detail: Installation
EPM Installation
EPM InstallationPre-
Installation
Pre-
Installation Client Tools
Client Tools

p. 16
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Review Pre-Installation Tasks for Accuracy
• Foundation Services Applications installed on Servers
• Financial Management applications, etc installed on servers
• Enabled SSL for Web Analysis – web layer only (if applicable)
• VM Ware installation for Web Components (if applicable)
• Load Balancing Configuration (if applicable)
• Notes on Memory Changes
• Notes on Heap Size
• Notes on Swap Settings
• Relevant Patches / Readme concerns?
Tools
• Fusion Installer
• Oracle Installer (if applicable)
Tips
• Validate the functionality of all components before
beginning migration. It is difficult to troubleshoot a
migration issue if the system was not known to be
functioning correctly before the migration started.
EPM Installation
Installation
Pre-
Client Tools

p. 17
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Develop a Deployment Strategy for
• Essbase Add-In
• Smart View
• Web Analysis
• FDM Workbench
• HFM Client
• EAS Client / Web
• Financial Reporting Studio
• Essbase Studio
• Test Compatibility with Existing Office Products, Client Web
Browsers, and other desktop software
• Test network connectivity – on the servers, on the intranet,
through VPN, remote sites
Tools
• Enterprise Package Deployment Software
• keytool
• MS Excel
Tips
• The Essbase Add-in is installed from the Fusion Installer.
This package is a little over 2 GB so consider how to deliver
efficiently.
• Smart View can be downloaded directly from the Workspace
but requires administrative rights to install
• Often times, new environments means new URLs. How will
the Smart View connections be updated on client machines
• Must have proper lead time to script enterprise software
installation packages for users who need Hyperion software
• The Web Analysis JRE requires admin access on client
machine, only specific JVM versions supported
• SSL Certificate needs installed on every clients PC who will
access Web Analysis
EPM Installation
Installation
Pre-
Client Tools

p. 18
Validation &
Stabilization
Training &
Learning
Sessions
Review
• Have all required products been installed and configured?
• Has system validation been completed to ensure a “working system”?
• Have all environments, necessary for the next phase, been completed? For example, can we
start testing in Production and bring the Test Environment on-line later?
• Has the client software distribution been planned and tested?

p. 19
Summary
• Migrate Report Repository Objects
• Migrate Analytic Services (Essbase) objects
• Configure new data sources for reports and report objects
• Update Essbase Load and management routines
• Apply new security model and reconciliation activities
Key Deliverables
• Migrated Essbase Cubes and support routines
• Migrate Report Objects
• Migrated Security Structures
Milestones
• Environment Ready for Migration
• Analytic Services (Essbase) ready for data
validation
• QA and Testing Activities are ready to begin
The Migration Phase consists of the activities needed to transfer the objects from the legacy environment. This
phase has crucial transformation activities associated with security, provisions, and data access, that are
significantly more sophisticated than the legacy system.
Migration
Assessment
Validation &
Stabilization
Training &
Learning
Sessions

p. 20
Validation &
Stabilization
Training &
Learning
Sessions
Security Intro
Many Layers of Security:
MigrationMigration
Phase Detail: Migration
Layer Migration Method
Users and Groups (Native & LDAP/MSAD) CSSImport/Export & Lifecycle Management
Shared Services Provisioning CSSImport/Export & Lifecycle Management
Application Level Security Application Specific
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM

p. 21
Validation &
Stabilization
Training &
Learning
Sessions
Security Layer 1 – Users and Groups
Goal: Convert the CSSExport format into valid LCM Import format
MigrationMigration
Common Input / Output Format
#userid,provider,login_name,first_name,last_name,description,email,internal_id,passwordadmin,
Native Directory,admin,admin,,Administrative
hypadmin,Native Directory,hypadmin,ADMIN,user,,,b0ff0d64f03bc7d7:-63b85a69:11e521b18f
a:abd,{SHA}7zNBJSaWP3SEbucHWLNrcK1JET8=
#group
id,provider,name,description,internal_id
AllPlanningUsers,Native Directory,AllPlanningUsers,,05ba5f0967ff4f2c:-23a91ad5:120d8a87dfb:-76fc
tgroup1,Native Directory,tgroup1,,05ba5f0967ff4f2c:3d577042:128d125d051:-74de
#group_children
id,group_id,group_provider,user_id,user_provider
AllPlanningUsers,,,user1,Native Directory
CSSExport
# EXPORT OPERATIONS
export.fileformat=csv
export.file=../../SharedServices/output/expUsersGroups.csv
export.user.filter=*
export.group.filter=*
Life Cycle
Management
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM

p. 22
Validation &
Stabilization
Training &
Learning
Sessions
Security Layer 2 – Provisioning
Goal: Convert the CSSExport format into valid LCM Import format using LCM Export as an
example
• CSSExport from Source System
• LCM Export from Target System (Formatting Guide):
How do you keep security changes in sync?
MigrationMigration
#provisioning
project_name,application_name,role_id,product_type,user_id,user_provider,group_id,group_provider
Hyperion System 9 BI+,Hyperion System 9 BI+:clhypr.com:6800::1,Reporting and Analysis Global Administrator,HAVA-9.3.1,admin,Native
Directory,,
Hyperion System 9 BI+,Hyperion System 9 BI+:clhypr0com:6800::1,Data Editor,HAVA-9.3.1,admin,Native Directory,,
#provisioning
project_name,aduct_type,user_id,user_provider,group_id,group_provider
Reporting and Analysis,Reporting and Analysis,Provisioning pplication_name,role_id,proManager,HUB-9.5.0,admin,Native Directory,,
Reporting and Analysis,Reporting and Analysis,Reporting and Analysis Administrator,HAVA-9.5.0,admin,Native Directory,,
Reporting and Analysis,Reporting and Analysis,Reporting and Analysis Global Administrator,HAVA-9.5.0,admin,Native Directory,,
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM

p. 23
Validation &
Stabilization
Training &
Learning
Sessions
Security Layer 3 – Application Security
Goal: Sync application security tables with the authoritative Shared Services provisioning,
ensure granular application level security carries over
Planning Example:
ProvisionUsers.cmd /ADMIN:admin /PASS:pass /A:BalSheet
UpdateUsers.cmd localhost admin pass BalSheet
MigrationMigration
Workspace Example:
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM

p. 24
Validation &
Stabilization
Training &
Learning
Sessions
Essbase
Features
• Files (.otl, .rpt, .csc, .rul)
• Data
Migration Methods
• Use EAS to copy one application to another, Import level 0 data and calc
• Automation using scripting
Considerations
• Consolidating Security Model From Essbase Native Mode to Shared Services
• How to “resync” the applications during the effort such as during QA, user acceptance testing phases
• Large number of applications and long data/calc times would lend itself to a more scripted method
• Preserve “input level” data vs. an “all data” export
• ETL process needs update to interface with new system (data flows, scripts, backups)
MigrationMigration
• Filters
• Partitions
• Security
• Application /
Database Properties
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM

p. 25
Validation &
Stabilization
Training &
Learning
Sessions
Planning
Features
• Forms
• Security
Migration Method
1.Create an empty(shell) planning application with same specifications of the original
2.Replace the relational database associated with the empty app with the data from the source application
3.Planning Web Prompts to update the app upon first Login to application
4.Update Security
Considerations
• Changes to Forms, Dimensions, Security require complete redo of the process
• May be easier to keep track manually of any changes
• Security
MigrationMigration
• Dimensions
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM

p. 26
Validation &
Stabilization
Training &
Learning
Sessions
Business Rules
Features
• Rules
• Security
Migration Methods
• Using EAS, Export Objects to .xml
• Using EAS, Do a Repository Migration
• Direct Relational Database Manipulation
Considerations
• After importing you must change the old host name references (Locations…etc)
• Case sensitive
MigrationMigration
• Sequences
• Locations
• Projects
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM

p. 27
Validation &
Stabilization
Training &
Learning
Sessions
Reporting
Features
• Reports - Financial Reports,
Interactive Reports, Web Analysis
• Data sources
Migration Methods
• In Workspace Export / Import Financial Reports
• Migration Utility
• Manual
Considerations
• Import/Export does not transfer security or Web Analysis Documents, IR, or Files (PDFs, Images…etc)
• Migration Utility does not do v9 to v11
• Updating Data Sources for Reports
MigrationMigration
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM
• Files
• Security

p. 28
Validation &
Stabilization
Training &
Learning
Sessions
HFM
Features
• Data, Metadata, Forms/Grids
• Rules, Lists, Journals
Migration Methods
• Use HFM Workbench to Export and Import
each Application
• Copy relational into new environment and run
schema update utility
Considerations
• Relational Database Restores can take a long time
• Cluster issues may arise with server names
MigrationMigration
FDM
Features
• Maps, Security, Data, Metadata, Scripts
Migration Methods
1.Create empty “shell” apps in target environment
2.Overwrite the relational database with source data
3.Copy file system application data from source to target
4.Run schema update utility upsSchemaUpdateDM.exe
Considerations
• Microsoft Excel must be installed on the server
• FDM Scripts may need modified for new Adapters and
API Method changes
Essbase
Essbase
Security
Security
Planning
Planning
Business Rules
Business Rules
Reporting
Reporting
HFM / FDM
HFM / FDM

p. 29
Validation &
Stabilization
Training &
Learning
Sessions
MigrationMigration
Review
• Are all “in scope” applications and objects migrated?
• Are all applications and objects accessible to the Functional Testing Team?
• Review outstanding issues, are there any that prevent Functional Testing from beginning?

p. 30
Summary
• Conduct Functional Testing
• Conduct User Acceptance Testing
• Conduct System Testing
• Conduct Performance Testing
• Conduct Disaster Recovery Testing (if Applicable)
Key Deliverables
• Testing Sign-Off
• User Sign-Off
• Environments ready to be introduced to Production
Milestones
• Completion of UAT
• Completion of System Testing
• Production Go / No Go Decision
The Validation & Stabilization Phase consists of the activities necessary to keep the environment stable and
performing without user interventions. The environment is complex and when Load Balancing and Clustering are
employed, it takes many people using the system to shake out all the possible configuration issues and
performance inconsistencies.
Migration
Assessment
Validation &
Stabilization
Training &
Learning
Sessions

p. 31
Validation &
Stabilization
Training &
Learning
Sessions
Activities
Application Functional Testing
• Function Test each migrated Application
• Does it Calc, Consolidate, Execute, etc
• Function Test Reporting Functionality and High-Level Accuracy
• Email Alerting and Notification
• Remediation of Issues
Environment Functional Testing
• Test each node in our Application Server Clusters individually
• Bring up one node at time to validate
• Test each load balanced server & service
• Bring up one channel at time to validate
• Test SSL Certificate with each Application
• Workspace
• Interactive Reporting
• Web Analysis
Tools
• Oracle Performance Management Applications
Tips
• Better to spend an extra week in Functional Testing than
leave a bad first impression in UAT.
• Configuring Web Analysis with SSL requires a client
resident token registered in the JRE. It’s all documented but
a bit tricky
Phase Detail: Stabilization
Functional
Testing
Functional
Testing UAT
UAT
System Testing
System Testing
Perf Testing
Perf Testing Disaster
Recovery Testing
Disaster
Recovery Testing
Validation and StabilizationValidation and Stabilization

p. 32
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• User Testing of Workspace and EPM Applications
• Administer and Developer Testing of EAS, Shared Services, and
Development Studios
• Remediation of Issues
Tools
• Oracle Performance Management Applications
Tips
• When reviewing of Reports, Spreadsheets, and other data
reporting tools bringing the legacy system reports and the
new system reports side by side, makes validation easier.
• A bad user experience in UAT can leave a lingering
impression on the new system so proceed with caution.
Functional
Testing
Functional
Testing UAT
UAT
System Testing
System Testing
Perf Testing
Recovery Testing
Disaster
Recovery Testing

p. 33
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Test Data Movement outside of EPM Applications
• CRON Jobs to land flat files
• ETL / ODI Routines
• Test Automation Routines
• Startup/Shutdown Scripts
• Hierarchy Management Automation
• System Monitoring
• Server Level monitoring (CPU, Memory, Disk, etc)
• Application Availability (HTTP Requests)
Tools
• ETL Tools
• Cron, FTP, Shell Scripts, Batch Scripts
• HP Openview, Zennoss, CA Unicenter TNG
Tips
• Most ETL processes and Data Management routines will
need to be duplicated so they can load the legacy system as
well as the “to be” systems for 30 – 60 days.
Functional
Testing
Functional
Testing UAT
UAT
System Testing
System Testing Perf
Testing
Perf
Testing Disaster
Recovery Testing
Disaster
Recovery Testing

p. 34
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Conduct Performance Testing to evaluate system response
times and environment metrics
• Adjust Heap Sizes, Memory Allocation, CPUs, and Swap settings
to establish increased stability and reduce response times.
Tools
• Performance Monitors
• HP Load Runner
• Neotsys NeoLoad
Tips
• When Using Load Runner with Hyperion reports, record
using be sure to use “URL Based scripts” in the recording
options.
Functional
Testing
Functional
Testing UAT
UAT
System Testing
System Testing
Perf Testing
Recovery Testing
Disaster
Recovery Testing

p. 35
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Delete an application (Essbase, HFM, Planning) and restore from
Backup
• Fail Single Nodes in the environment to ensure functionality and
evaluate user impact if the system has multiple nodes
• Design and execute a disaster recovery plan from Production
Environment to Disaster Recovery Environment (if Applicable)
Tools
• Database Backup and Restore Routines
• CSS Import/Export Tools
Tips
• IT and Business Management need to agree on the Service
Level Agreements and the acceptable outages. Extremely
High Availability usually come with a high price tag. Be sure
proper expectations are set and planned for accordingly.
• It is much better for everyone to test these items under a
“no pressure” situation than at month end or year end
pressure.
Functional
Testing
Functional
Testing UAT
UAT
System Testing
System Testing Perf
Testing
Perf
Testing Disaster
Recovery Testing
Disaster
Recovery Testing

p. 36
Validation &
Stabilization
Training &
Learning
Sessions
Review
•Has Functional Testing completed?
•Has User Acceptance Testing completed?
•Has System Testing completed?
•Has Performance Testing completed?
•Has Disaster Recovery Testing completed?
•Are there any “show stopper” issues?

p. 37
Summary
• Familiarize the Development Staff with the new environments,
development tools, and naming conventions
• Work with the System Support Staff on the new architecture and
support requirements
Key Deliverables
• Session to demonstrate changes to existing tools
like Reports, Web Analysis, Interactive Reporting
and new tools
• Sessions to explain Shared Services, EAS, and
general provision management
• Provide Documentation and instruction to Support
Staff
Milestones
• Go Live
• First Month Processing Begins
• First Month Processing Ends
Training & Learning Sessions is a service whereby we work with your existing staff to increase their knowledge
of the new functionality in System 9 or Release 11 as well as changes to the existing development and
administrative processes. We will schedule multiple sessions with functional and support groups to show new
features and tips as well as answer questions.
Migration
Assessment
Validation &
Stabilization
Training &
Learning
Sessions

p. 38
Training & Learning SessionsTraining & Learning Sessions
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Start turnover of support issues to the support staff and assist
only as necessary
• Complete and Deliver Environment Configuration information
• Status Page
Tools
• Documentation and Working Sessions
• Services(port) & Server Monitoring
• Status Page
Tips
• As the system becomes more stable, work with the Support
Staff to perform schedule system restores as well as
functions during system testing
• Make sure the support staff “buys in” to the transfer of
responsibility completion. This activity can make or break
the success of the implementation as it reflects on the
stability of the overall system
Phase Detail: Learning Sessions
System Support
System Support
New Features
New Features

p. 39
Validation &
Stabilization
Training &
Learning
Sessions
Activities
• Security Administration
• Demonstrate Capabilities of Lifecycle Management (LCM)
• Review Workspace repository
• Review HFM / Planning applications within Workspace
• Create Reports – FR, Web Analysis, Interactive
• Build and Demonstrate a Sample PowerPoint, Word and Excel,
Smart View Document
• Demonstrate EIS Connectivity
Tools
• Interactive Reporting Studio
• Web Analysis Studio
• Smart View
• Integration Service
Tips
• Make sure all groups “buy in” to the transfer of
responsibility upon completion. This activity can make or
break the success of the implementation.
• If the users can not use the tools, it is a reflection of a poor
implementation
System Support
System Support
New Features
New Features

p. 40
Validation &
Stabilization
Training &
Learning
Sessions
Review
• Is the user community ready for the application?
• Do they understand the changes and enhancements that will be in the final products?
• Is the System Support and Development team comfortable with the new system?

The timeline depicted above is an example of a typical Hyperion System 9 or Release 11 migration. It is intended to provide an overview of this type
of effort. Subsequent to the completion of the Migration Assessment Phase, a detail timeline will be delivered describing the migration effort.
Key Phases
Approximate Timeline
Week
1
Week
2
Week
3
Week
4
Week
5
Week
6
Week
7
Week
8
Week
9
Week
10
Week
11
Week
12
Migration Assessment
Installation
Migration
Validation & Stabilization
Training & Learning Sessions
Go Live
During the Migration Assessment Phase a detailed
description of the remaining phases is established
Project Approach: Key Phases & Timeline
p. 41

Nicholas king oracle epm migration and upgrade

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Nicholas king oracle epm migration and upgrade

Similar to Nicholas king oracle epm migration and upgrade (20)

Recently uploaded

Recently uploaded (20)

Nicholas king oracle epm migration and upgrade