Overview: Guidance for Client-Side Project Managers from the EPMI Team
- Cloud EPM implementations eliminate on-prem infrastructure but introduce new project risks, including environment provisioning delays, automation hosting needs, and monthly update timing.
- Early coordination with technical and business teams is essential for environment setup, EPM Automate/Integration Agent hosting, and update testing.
- Project managers must adapt their plans for SaaS-specific factors, educate users on cloud access, and assign admin responsibilities appropriately.
Six Project Management Considerations for EPM
When planning your project timeline for an Oracle Cloud EPM SaaS implementation, there are important differences from traditional on-premise deployments.
Ideally your implementation partner’s project management team wants to equip you with the right expectations so you can proactively manage these factors, keep your plan realistic, and avoid avoidable delays. The following six project management considerations are crucial for organizations to optimally adopt Oracle Cloud EPM.
While the cloud removes the burden of provisioning hardware and managing infrastructure, it introduces new considerations that can impact your schedule, dependencies, and stakeholder readiness.
1. Oracle’s Monthly Update Cycle
Cloud EPM environments are updated on a fixed monthly schedule:
- Test: First Friday of the month
- Production: Third Friday of the month
During the gap between these updates, your environments are on different versions, which can block migrations or cutovers.
Action Step
-
Avoid scheduling migrations during the “out-of-sync” period.
-
If timing is tight, submit a skipUpdate command in EPM Automate to allow for migration activities with in sync environments.
-
Educate your team: unlike large, infrequent on-prem upgrades, these monthly updates are smaller but still require testing in Test to catch issues before they hit Production.
2. User & Admin Education on Update Management
With monthly updates come frequent small changes. These can introduce subtle functional impacts. New features will not be automatically enabled; organizations have to opt-in and run tests to ensure proper performance.
Action Step
- Assign owners to review Oracle’s monthly update documentation.
- Encourage testing or use automated test scripts for core business processes.
- Set up a process to raise Support Requests quickly if unexpected behavior appears in Test.
3. Environment Provisioning: Who Gets the Email?
The problem? That email may go to someone outside of the typical admin or IT function — and they may not realize its importance.
Risks if unaddressed:
- Delayed access to environments
- Missed prototype deadlines
- Knock-on delays to build and testing
Action Step
Identify the recipient of the provisioning email early. Confirm they understand what it is and the urgency of acting on it.
4. Cloud Access Is Different — and Easier
Users accustomed to on-prem systems may expect VPN or network access requirements. For Oracle Cloud EPM, all they need is an internet connection and browser. However, we understand some cloud customers prefer elevated security and can require access via virtual desktops.
Action Step
- Incorporate access training into your onboarding plan.
- Reinforce that this change enables greater flexibility and supports faster adoption.
Want to learn more about the EPM implementation process?
Watch the EPMI YouTube PM Playlist
5. No On-Prem Servers? Adjust for EPM Automate & Integration Agents
If your organization has fully migrated away from on-prem servers, you’ll need an alternative plan for hosting EPM Automate and (if required) the Integration Agent. These tools are often essential for automations, data loads, and integrations.
Action Step
- Engage your integration resources early to confirm hosting strategy.
- Coordinate with both functional and technical client teams to validate approach and security requirements.
- Build in lead time — skipping this step can cause delays to system integration testing.
6. Shifting Admin Duties to the Business
In Cloud EPM, many traditional IT admin functions — like metadata updates, user provisioning, or running rules — can now be performed by functional users.
Action Step
- Identify the right individuals to own these tasks.
- Provide targeted admin training for both technical and business resources to foster collaboration.
EPM Project Management FAQs
What’s the biggest difference between managing a Cloud EPM project and an on-prem project?
In the cloud, you don’t need to provision physical servers, but you must manage SaaS-specific considerations like Oracle’s monthly update cycle, environment provisioning emails, and alternate hosting for EPM Automate or the Integration Agent.
Can environment provisioning delays really impact the project timeline?
Yes. If the setup email goes unnoticed, you may lose days or weeks of access. This can push back prototyping, build, and testing. Identifying the recipient early prevents these delays.
Do we need IT involvement if admin tasks shift to business users?
Yes, but in a different capacity. IT often still plays a role in integrations, security, and governance. However, more day-to-day tasks (like metadata updates or user provisioning) may move to functional business users.
How do we minimize risk from Oracle’s monthly updates?
Plan around update windows, avoid migrations during “out-of-sync” periods, and test core processes in the Test environment after the first Friday update to catch issues before Production updates.
What kind of training should users and admins expect?
Users need guidance on accessing cloud applications and adapting to frequent small updates. Admins—both technical and business—need targeted training on update management, provisioning, and shared responsibilities across teams.