Go Live

Planning your rollout to users is essential for a successful Fusion Analytics implementation. This includes assessing system readiness, preparing your user community, scheduling go-live, and preparing for an audit. By adequately preparing for go-live, you can establish a solid foundation for the rollout of Fusion Analytics.

Complete these tasks:
  • Prepare the production environment - As a service administrator, you can create the production environment along with the development and additional test environments simultaneously. This avoids last-minute issues and provides sufficient time for unanticipated events. You must:
    • Ensure your Fusion Analytics production environment is in place. This means configurations are enabled, users are set up, and data security roles are turned on. It also means all the content is migrated.
    • Update the production environment with the latest release and align with the development environment release version to facilitate migration activities. If required, keep resources ready for migration.
    • Ensure all the configurations and migrations are complete.
    • Ensure the descriptive flex fields configuration migration is complete.
    • Confirm that there are no open issues.
    • Confirm that the Fusion Analytics URL is accessible.
  • Establish collaboration - As a project manager, establish colloration between all parties. Successful Fusion Analytics implementations revolve around building a mutual understanding of the goals and objectives of the implementation. It is crucial for everyone, from the sponsor to end users, to be in synchronization. Everyone needs a clear understanding of the implementation plan, its benefits, and what to expect during the Fusion Analytics implementation process.
  • Prepare the business users - As business leads and service administrators, prepare your business users because this is a crucial task for successful application go-live and adoption. You must engage users at the outset of the project, and at key milestones, especially during user acceptance testing. Have a plan for business user preparation, training, and revised operating procedures communication and confirm that the plan is executed before go-live. Share the go live plans with the user community. Ensure that the user community is well aware of the organizational support process and reaches out to the core implementation team for assistance. This helps ensure a smooth go-live experience. Review the sample plan to onboard the Fusion HCM Analytics users, see Plan for Onboarding Fusion HCM Analytics Users.
  • Prepare organizational communication - The implementation team should assess organizational preparation for go-live readiness early and frequently. It must communicate early and often regarding each activity's status, readiness, completeness, and maturity to the project stakeholders and the steering committee. Based on this information, the executive sponsor must communicate with a focus on the benefits to the organization and what's in it for the business users. The project manager must:
    • Set up a communication plan for project stakeholders.
    • Ensure that the solution has been validated.
    • Assign at least one person whose priority is to respond to inbound communications.
    • Ensure organizational change control processes are in place.
    • Plan to mitigate external dependencies across the organization.
    • Create Post Go-Live standard operating procedures.
    • Confirm that a change management process is in place.
    • Plan for user training and adoption.
    • Plan to review accessibility requirements.
    • Create a monitoring and maintenance routine for production.
    • Build excitement and set expectations.
    • Conduct user demos of the Fusion Analytics application navigation and functionality. Makes these demos a part of organization communication events to promote data-driven culture.
    • Build metrics to show alignment with organization goals, and arrange display monitors across organization premises to showcase the organization's broad key metrics tracking adoption.
    • Recommend users to set up and use mobile application features to view the refreshed data daily and host office hours sessions with business users to clarify open questions to drive adoption.
    This task requires:
    • Service Administrator
    • Change Management Team
    • Project Management Team
    • IT Support Team

    See Accelerate Oracle Fusion Analytics customer journey.

  • Schedule the rollout - Communicate the schedule to the impacted business units.
  • Support go live - Plan for the first few weeks after your Fusion Analytics implementation goes live for the core implementation team to provide go-live support. The goal of the go-live support is to have the implementation team quickly address any issues as the business users start to use the service.
  • Track usage - As the implementation and business leaders, plan to consistently track the system using the Usage Tracking workbook that offers user-level audit reports. To keep an audit log of users who have logged in to the system, Fusion Analytics service administrators can use the Usage Analytics page. This capability is essential for protecting the organization's data by identifying roles that have access to sensitive information. The sensitive data identifier enhances the user logging experience by producing audit logs that show which users have access to sensitive data. This feature is particularly beneficial for organizations that have multiple roles with varying levels of access to certain data and require detailed auditing to track users who have accessed sensitive information. To maintain segregation of duties between roles, Fusion Analytics service administrators can download the security duty roles assignment report in the non-production and production environments to view all the duties assigned to a role. You can configure this report to run on any collection of roles.
  • Consult the audit logs - As a service administrator and security administrator, consult the different audit logs that you can generate for troubleshooting purposes.

Use the checklist to confirm that the action items are planned for. See Go Live Checklist.