Oracle Fusion Analytics Implementation Series: Rollout Readiness

• Gather reviews from all stakeholders for a successful project evaluation.
• Create a report with actual project timelines, costs, and resources for a proper evaluation.
• Ensure all tests are complete.
• Plan for change management and user training.
• Communicate the timelines to the stakeholders and business leaders.
• Develop a contingency plan in case of any delay.

Note: If a prebuilt phase is rolled out, there are fewer evaluation requirements.

The application functional administrators and power users review the functional requirements and ensure they are satisfied.

The Fusion Analytics service administrator reviews and ensures that all non-functional requirements, e.g., network, database, and security, are satisfied.

Note: If a prebuilt phase is rolled out, there are fewer success criteria to evaluate.

• Ensure the overall success criteria, determined in the implementation planning stage, are clear, precise, measurable, and satisfactorily attained.
• Ensure phase-specific criteria are fulfilled for the rollout phase. For instance, initial rollouts of prebuilt content and customization phases have different criteria.

My Oracle Support is the initial point of contact for all product support needs.

If issues are encountered with the product, file a Service Request (SR) so that Oracle Analytics support can assist in resolution. The  Oracle support contact details are available in the Fusion Analytics welcome email.

Review these also:

• Customer Access Support
• How to Add a Support Identifier to a My Oracle Support User Account
• What to do now that you have your Support Identifier [VIDEO]

Fusion Analytics provides quarterly application updates with the control and flexibility to choose when to apply the update. Oracle applies critical security patches automatically and has zero downtime. The auto-update process updates the data model, adds new content, and updates existing content. The process preserves activated functional area data pipelines and resets the other data pipelines to a Saved status.

See About Application Updates and Update Your Application.

You can view notifications displayed on the Fusion Analytics Data Configuration page when application updates are available for major releases (quarterly basis), patches (monthly basis), and emergency fixes (as needed). Plan and communicate decisions on when these are applied.

Ensure that release update activities align with the overall governance and compliance policies.

Evaluate the following customization topics:

• Approach
• Backup and Rollback
• Capacity
• Data Augmentation
• OCI Environment
• Performance
• Release and Patching
• Security
• Semantic Model Extensions
• Custom Report Content
• Support
• User Acceptance

Evaluate and ensure that:

• The phased approach was used for the prebuilt and customization phases.
• The scope of the customization phase was limited as much as possible to a subset of functional areas.
• The scope of the customization phase was limited to a single Fusion Analytics application, e.g., ERP.
• A Previous phase, containing only prebuilt content with the same scope, was rolled out successfully into the production environment.
• An ATE (Additional Test Environment) was procured for user acceptance and performance testing before beginning the customization phase.
• Best practices and recommendations were followed when customizing workbooks, extending the semantic model, and augmentating data.
• If a partner was involved, their implementation team had training, experience, and certification in Fusion Analytics.
• The Fusion Analytics Implementation Guide was used to plan the project.
• Fusion Analytics customizations leveraged Fusion Cloud Applications custom data, security, and reporting.

Evaluate and ensure that:

• There is a backup and rollback plan for customizations.
• A customization rollback test was performed successfully.
• Backup procedures were developed for custom schemas in the ADW.
• The development, ATE, and production environments were backed up before beginning the customization phase.
• The ATE was refreshed and restored from the production environment.
• The relevant functional areas in the development environment were restored from the production environment.
• Copies of prebuilt semantic model objects were created with custom prefixes.
• Copies of prebuilt catalog folders were created with custom prefixes.
• Custom folders were created with custom prefixes.
• Custom tables and columns in the ADW were created with custom prefixes for easy identification, e.g., WC_<table_name>.

Evaluate and ensure that:

• The Oracle Enterprise Cloud Platform Sales Manager was engaged to help analyze consumption patterns and plan additional capacity.
• ADW utilization, OCPUs, and storage were monitored and tracked.
• OAC utilization was monitored and tracked.
• If additional capacity was required:
  • An ATE (Additional Test Environment) was procured and scaled up.
  • The production environment was also scaled up.
  • The increased capacity allows for projected data and user growth.

Evaluate and ensure that:

• All options were reviewed to select the best solution for each augmentation.
• The relevant data augmentation documentation and spreadsheets were consulted for best practices.
  • Implementation Guide: Data Augementation
  • About Augmenting Your Data
  • ERP Data Augementation
  • HCM Data Augementation
  • SCM Data Augementation
  • CX Data Augementation
• Prebuilt Fusion Analytics components were leveraged including:
  • Prebuilt Entities and Attributes
  • Custom Data Configurations
  • Dimension Aliases
  • Fusion Analytics Connectors
  • Security Configuration Functional Area Pipelines
• Custom prefixes were used for custom schema, table, and column names.
• Custom fact tables were joined to all relevant dimension tables.
• Custom dimension tables were joined to all relevant fact tables.
• Custom primary-key column values were populated. Primary key columns cannot contain null values.
• Custom data loads not managed by Oracle were synchronized with Fusion Analytics pipelines.

Evaluate and ensure that:

• Customizations to OCI (Oracle Cloud Infrastructure) elements did not affect existing Fusion Cloud Applications operations if using the same cloud account for both.
• Customizations to OCI elements did not affect existing Fusion Analytics operations. These include:
  • Identity Domain or Identity Cloud Service (IDCS) settings.
  • Policies and policy rules.
  • Service limits and quotas.
  • Compartment structures.

Evaluate and ensure that:

• A dedicated ATE (Additional Test Environment) was scaled up if necessary for performance and concurrency testing.
• The production environment was scaled up if necessary to match the ATE.
• Concurrency testing simulated the expected number of users in the next 90 days.
• Functional requirements were met during performance and concurrency testing, including:
  • Custom queries were completed within resource time and size limits.
  • Custom query response times during concurrency testing.
  • Single-user response times using custom security profiles for both authors and consumers.
• Non-functional requirements were met during performance and concurrency testing, including:
  • A full data load using prebuilt and custom data pipelines.
  • Incremental data loads using prebuilt and customized data pipelines.
  • SQL query response times in custom security predicates.
  • Network latency tests
• The concurrency, performance, and network test results were shared with Oracle.
• If there are open performance issues, the following information was shared with Oracle Support:
  • The ADW (Autonomous Data Warehouse) AWR (Automatic Workload Repository) reports.
  • OAC session logs.
  • Networking logs.
  • The issues affect both the production and ATE environments.
  • The impacts on a single user, a group of users, and all users.

Evaluate and ensure that:

• The development, ATE, and production environments are on the same release and patch level.
• The customized environment is not impacted by new releases and patches.

Evaluate and ensure that:

• Prebuilt security configurations were leveraged as much as possible (especially relating to HCM).
• The Upload Center was leveraged to upload security assignments into the prebuilt security context tables.
• Security assignments for custom attributes were loaded into a custom warehouse table.
• Users were assigned to custom security assignments that secure custom data, the semantic model, and reporting objects.
• Custom security assignments protected access to custom subject areas, reporting content, and data.
• Custom user groups were granted appropriate permissions.
• Network access control and security lists secured access to customizations.
• Network threat testing was performed, and all services were protected from unauthorized access.

Evaluate and ensure that:

• Custom subject area elements are secured using Fusion Analytics Object Permissions.
• Custom semantic model objects were developed according to best practices and prebuilt design principles, e.g., using the IN clause in security filters. See Semantic Model Extension Best Practices.

Evaluate and ensure custom report development follows the best practices noted in these documents.

• Common Report Authoring Tips
• Report Authoring Tips for Oracle Fusion ERP Analytics
• Report Authoring Tips for Project Analytics
• Report Authoring Tips for Oracle Fusion HCM Analytics
• Report Authoring Tips for Oracle Fusion SCM Analytics and Fusion PROC Analytics
• Report Authoring Tips for Oracle Fusion CX Analytics

Custom report content is stored in a catalog containing shared folders.
Evaluate and ensure:

• The custom hierarchical shared folder tree structure is modeled after the prebuilt Oracle shared folder structure. For example, the Oracle shared folder tree has:
  • The root node is named Oracle.
  • First-level folders named after application pillars:
    • Oracle ERP
    • Oracle HCM
    • Oracle SCM
    • Oracle CX
• The custom shared folder tree structure contains a similar structure. For example:
  • The root node is named Custom.
  • First-level folders named after application pillars:
    • Custom ERP
    • Custom HCM
    • Custom SCM
    • Custom CX
• The custom shared folder tree uses inheritance to pass permissions to lower levels.
• The Fusion Analytics Service Administrator has exclusive read-write access to the root (no parent) folder.
• The Fusion Analytics Service Administrator inherits read-write privileges to the entire tree via inheritance.
• Prebuilt groups and application duty roles are leveraged as much as possible.
• Custom application roles follow prebuilt best practices ( duty roles ).
• Users are assigned to prebuilt and custom groups that contain prebuilt and custom duty roles.
• Read-write access to first-level pillar folders is granted to pillar-designated functional-administrator and specific author duty roles.
• Read-only access to first-level pillar folders is granted to pillar-designated consumer duty roles.

Evaluate and ensure that:

• Audit, network, and diagnostic logs were enabled to assist internal and Oracle support activities.
• Outstanding customization issues are within allowable severity limits.
• If there are open severity-one SRs (service requests) related to customizations, the following were shared and specified:
  • The Fusion Analytics OCID (Oracle Cloud Infrastructure Identifier), the number of concurrent users, and the number of ADW and OAC OCPUs.
  • A document summarizing customizations.
  • Any recent environment changes, e.g., patching, upgrade, Fusion T2P, that might have contributed to the issue.
  • For dashboard issues:
    • Affected workbooks, canvases, visualizations, analyses, and key metrics.
    • Workbook and analysis session logs containing logical and physical SQLs.
    • Exports of workbooks and archives of analyses.

Evaluate and ensure that:

• The Fusion Analytics CSM (Customer Success Manager) assisted in developing a successful user adoption plan.
• Custom subject areas were available to appropriate user groups.
• Custom visualizations were available to appropriate user groups.
• Custom data was available to appropriate user groups.
• Unaffected prebuilt content was re-accepted.
• Custom metrics were validated.
• Query response times were accepted.
• All users, including those with different security profiles, accepted custom content.
• The proper use of the folder and the shared folder structure was explained to the authors.
• Custom data was available to appropriate user groups.

Evaluate and ensure that:

• The phased approach is used for the migration.
• The source and production environment are on the same release and patch level.
• The production environment was successfully backed up.
• Bundles are successfully imported into Production.
• The data pipelines for the phase are activated in the production environment and completed successfully.
• Application roles are assigned to relevant user groups.
• Users are assigned to appropriate groups and security contexts.
• Subject area contents are visible to the appropriate users.
• Catalog folders and reporting objects are available to the appropriate users.
• Data is available to the appropriate users.
• Single-user author and consumer tests have confirmed Fusion Analytics data and objects are secured appropriately.