Primavera P6 is authoritative for the approved schedule. The cost system governs its own accounts. The model carries objects and quantities. Field records show what was actually completed. Power BI communicates the result.
The failure begins when a report quietly treats one of those systems as the owner of everything.
Federation without replacement
A governed project-control layer keeps each system in its proper role and connects them through stable identities: WBS elements, activities, work packages, model objects, cost accounts, and evidence records. That makes schedule progress and earned value explainable instead of merely visible.
The core questions are simple:
- Which approved activity controls this object or work package?
- Which quantity and rule generated the earned value?
- Which field evidence supports the claimed completion?
- Which baseline and data date were used?
- Who reviewed and approved the result?
A controlled chain
The workflow is: source data, normalization, deterministic reconciliation, exception handling, analysis, and authorized approval. AI may help find inconsistencies or assemble a review package, but it does not approve progress or rewrite the baseline.
That is the purpose of interoperability in iPDM Pro: not to replace P6 or the cost system, but to preserve the links that make a project-control decision defensible.