How does a Project System implementation unfold?

The implementation succeeds when archetypes, SAP objects, evidence, accounting outcomes, migration, and ownership remain aligned.

01
Discover
Catalogue archetypes, owners, financial outcomes, execution depth, integrations, reporting, and constraints.
Exit evidence: Named owner, approved decision, representative proof, reconciled result, and recorded risk.
02
Model
Define a reusable object model: WBS/network depth, coding, statuses, responsibility, planning, budget, and settlement roles.
Exit evidence: Named owner, approved decision, representative proof, reconciled result, and recorded risk.
03
Prototype patterns
Build representative B2A, customer, EAM-integrated, internal, and material-driven projects.
Exit evidence: Named owner, approved decision, representative proof, reconciled result, and recorded risk.
04
Configure foundations
Establish common profiles and controls, then layer integrations required by each archetype.
Exit evidence: Named owner, approved decision, representative proof, reconciled result, and recorded risk.
05
Test and reconcile
Test execution plus dates, commitments, actuals, revenue, recognition, settlement, journal, and closure.
Exit evidence: Named owner, approved decision, representative proof, reconciled result, and recorded risk.
06
Migrate and cut over
Classify open projects, map structures and statuses, migrate values and rules, and reconcile outcomes.
Exit evidence: Named owner, approved decision, representative proof, reconciled result, and recorded risk.
07
Govern the portfolio
Own templates, archetype decisions, enhancements, integrations, reporting definitions, and release changes.
Exit evidence: Named owner, approved decision, representative proof, reconciled result, and recorded risk.