Meet the Authors

Key Takeaways What you need to know
  1. Standard SAP EPPM plans one project at a time, so multi-project forecasting has traditionally meant a custom project of five to nine months, Platinum DB says.

  2. AI-Accelerated EPPM builds portfolio forecasting with accelerators and AI-assisted engineering in a dedicated environment, then places the result in the customer’s own SAP system.

  3. Customers gain capabilities standard EPPM does not offer, including multi-project forecasting and scenario planning, letting planners forecast across a whole portfolio.

Executives who oversee large capital programs expect their project data to answer forward-looking questions about cash flow, forecast misses, and which projects to prioritize.

In SAP Enterprise Portfolio and Project Management (EPPM), standard configurations handle project-level planning and control well. But getting portfolio-level answers has usually required time-consuming custom work.

AI-Accelerated EPPM is Platinum DB’s answer to that forecasting gap in standard SAP EPPM: a way of building the capability with accelerators and AI-assisted engineering, then placing the result in the customer’s own SAP system.

Explore related questions

In an interview with SAPinsider, Anthony DeRosa, president and founder of Platinum DB, described the shortfall in one sentence: “The big gap is all around forecasting.”

The Forecasting Gap in Standard EPPM

The gap starts with EPPM’s standard screens. DeRosa says “the standard screen only does one project at a time,” while the customers he works with want to load and forecast 25 or 50 projects together, grouped by plant, location, or project manager.

Those customers keep budgets, actuals, and forecasts in spreadsheets and want to make quick changes. A planning tool that takes too long loses them, he warns.

Organizations in data centers, utilities, energy, transportation, manufacturing, mining, and healthcare often run hundreds of active projects at once. Together the projects can contain thousands of work breakdown structure (WBS) elements, the units that carry a project’s costs and schedules. Their programs span multiple years, with annual capital budgets from $100 million to several billion dollars. At that scale, leadership asks:

  • What will portfolio cash flow look like over the next 24 months?
  • Which programs will miss the forecast?
  • What is our estimate at completion (EAC) by portfolio?
  • How will delays affect annual spending targets?
  • What happens if funding is cut by 10%?
  • Which projects should be accelerated or deferred?

Standard SAP EPPM does not make it easy for managers to answer these questions. And closing that capability gap has traditionally required a custom development project, which can take five to nine months from requirements through to deployment.

The associated costs and technical debt have led many organizations to settle for forecasting capability short of what they needed, DeRosa says.

How Platinum DB Delivers the Forecasting Capability

Platinum DB’s response starts with limiting how much custom work is needed at all.

AI-Accelerated EPPM begins with a process assessment, capability mapping, and a standard-fit analysis, so custom work happens only where standard SAP falls short.

SAP’s native tools, such as EPPM cost plan versions and SAP Analytics Cloud planning, suit customers who want standard EPPM planning with the fastest adoption, though features vary by edition and release. Partner add-ons suit customers who need a packaged estimate-to-complete and EAC tool, once edition, license, and roadmap fit are confirmed. A custom build suits customers whose forecast rules are specific to the business.

When a custom build is justified, it starts from Platinum DB’s library of proven accelerators for capital forecasting, including spend curves; portfolio analytics, including program forecasting; and resource forecasting. DeRosa says the layouts and analytics for planning, budgeting, and forecasting are “included in the accelerator” too.

The build can include an estimate-to-complete and EAC engine, SAP Analytics Cloud or Fiori views, and early-warning alerts, and it needs clean structures, plans, and actuals.

AI then shortens the engineering, with senior SAP consultants guiding and reviewing the work. Design, build, testing, and documentation run in parallel instead of in sequence, which, in the firm’s view, removes the stages that stretched traditional projects. A consultant signs off each change under change control.

What AI-Accelerated EPPM Customers Gain

Customers receive the output of work that Platinum DB runs in a dedicated environment of its own, a large SAP S/4HANA system connected to AI tools. “We don’t stick the AI into their system,” DeRosa notes, although a customer that wants it there can have it.

Delivery is faster than traditional custom development, with project timelines typically 50% to 70% shorter, depending on scope. DeRosa describes a quick EPPM project as three months, and says customers see the capability in the first workshop. He compares it to buying a car: the customer asks to see it, and “You can drive this thing right now.”

Costs fall with reduced consulting, testing, and documentation effort, while quality rises through consistent standards, stronger documentation, and traceability. Customers gain Platinum DB capabilities that standard EPPM does not offer: multi-project forecasting, portfolio-level forecasting, and multi-project scenario planning.

That means moving from one project at a time to many at once, which lets planners forecast across a whole portfolio. DeRosa says that is where Platinum DB creates value.

Platinum DB has started deploying the approach with a customer that wanted a quick, low-budget deployment of standard EPPM but whose goals could not be met out of the box. The challenge, DeRosa explains, is how to “solve that gap and still stay within the timeline.”

In Platinum DB’s view, forecasting is where many EPPM programs stall. With its approach, it becomes where they deliver their most visible value, without the long custom-development timeline.

What This Means for SAPinsiders

Forecasting decides what portfolio systems deliver. Executives ask for cash flow, completion cost, and funding-cut scenarios across every project, while the standard screens plan one project at a time. When planning stays in spreadsheets, the system holds the records while the decisions run somewhere else.

Less custom work changes what organizations settle for. Custom development has carried costs and technical debt that led many organizations to settle for forecasting capability short of what they needed. Starting from accelerators and a standard-fit check narrows what has to be built, and with it the compromise.

Where the AI runs becomes a delivery question. A partner can run AI-assisted engineering in its own environment, hand the customer the output, and have a consultant sign off each change. Where the AI sits and who answers for its output then become part of how an SAP project is described.