Project controls and AI automation →
Once systems connect, the routine around them can be automated.
PMIS and ERP integration is an operating-model service that connects project controls systems, data standards and working routines before configuration decisions are made. It is for owners, PMOs and delivery teams that need systems such as Primavera P6, PMWeb, Deltek, PRISM G2, ISETIA and Nomitech to produce reliable records and decision-ready reporting.
The problem
Project systems are often implemented as a technology project and then handed to a delivery organisation whose working routines were never part of the design. The result is predictable: data is entered inconsistently or late, reporting is reconciled outside the platform, and a system that is technically live is operationally bypassed.That is a records problem, not merely a productivity problem. HKA's CRUX Insight research found sums in dispute averaged 33.4% of contract budgets across more than 2,200 projects. Notices, instructions, approvals and progress records need an operating routine to remain reliable years later. Project systems create value only when they reflect the delivery model, information ownership and control gates around the project.
Scope
Operating-model and requirements definition
Map delivery structure, information ownership, control gates and reporting obligations before platform decisions.
Enterprise scheduling architecture
Design Primavera P6 EPPM structures including EPS, OBS, WBS, coding, calendars, baselines, update rules and security model.
Data standards and integration design
Set common coding, master-data rules, interfaces, ownership and reconciliation points across schedule, cost, risk and document systems.
Platform configuration and workflow design
Translate the operating model into workflow and control requirements for PMWeb, PRISM G2, ISETIA, Nomitech and connected governance tooling.
Reporting architecture
Define what is produced, from which source, by whom and on what cadence; make enterprise roll-up a design requirement.
Adoption, training and handover
Build role-based training, runbooks, super-user support and a deliberate ownership transfer.
Method
- 01
Establish the operating model
Review delivery structure, decision rights, gates, reporting and contractual information requirements.
- 02
Audit systems and data
Identify what exists, what is actually used, workarounds and data quality at source.
- 03
Define standards before configuration
Agree coding, structures, master data and definitions.
- 04
Design routines, then configure
Fit the platform to accountable working routines, not the reverse.
- 05
Pilot on a real project
Use real users and a real reporting deadline rather than a sandbox.
- 06
Measure adoption and hand over
Test whether the routine is followed, then transfer runbooks and super-user responsibility.
What you get
Operating model and requirements definition
Governance-derived requirements, control gates and information ownership.
Systems and data audit
Current state, usage reality and data-quality findings.
Data standards specification
Coding, structures, master data, definitions and update rules.
Integration design
Interfaces, ownership and reconciliation points.
Configuration and reporting specification
Platform requirements, report inventory, sources, owners and cadence.
Training and adoption pack
Role-based curriculum, runbooks, support taper and handover.
What we need
- Current systems inventory, licences, versions and access model
- P6 database structure export, including EPS, OBS, coding, calendars and security
- Current reporting suite and manual steps behind it
- Contractual information and reporting requirements
- Organisation chart with information ownership
- Previous implementation documentation
- Data residency, confidentiality and IT security constraints
- Vendor and support contracts already in place
Engagement
Engagement length and composition depend on the question, the available records and the required decision date. An initial discussion establishes scope; no published prices or generic duration promises are used.
| Engagement shape | Suitable where | Typical duration |
|---|---|---|
| Systems and data audit | An organisation that suspects its PMIS is being bypassed. | Confirmed after scope and record review |
| Operating-model and requirements definition | Pre-procurement or pre-configuration work. | Confirmed after scope and record review |
| Implementation advisory alongside a vendor | Where a vendor holds the build contract. | Confirmed after scope and record review |
| Enterprise scheduling design and rollout | P6 EPPM across a multi-project portfolio. | Confirmed after scope and record review |
| Adoption and capability programme | Post-go-live rescue or a planned adoption phase. | Confirmed after scope and record review |
Scope limits
- Software licence resale or vendor contracting.
- Infrastructure, hosting or IT security implementation.
- Custom software development outside the project-controls scope.
- Ongoing platform administration unless specifically retained.
Frequently asked questions
The operating-model work is the constant: standards, ownership, routines and adoption determine whether a configured system is used. The precise configuration role is agreed for each platform and engagement.
Primavera P6 and P6 EPPM, PMWeb, Deltek Acumen, PRISM G2, ISETIA and Nomitech, alongside the reporting and governance tools connected to them.
Usually. The diagnosis often finds that the configuration reflects a process the delivery team does not follow. The remedy is to establish the actual routine, then align configuration, standards and adoption to it.
No. Licensing is arranged directly between the client and the vendor or its partner, keeping advisory work independent of the platform’s commercial interest.
Contract administration runs through these systems. Where notices, instructions, approvals and progress records are bypassed, the contemporaneous record weakens and the consequence may emerge years later in a claim.
Initial discussion
Discuss a pmis and erp integration challenge.
Share the project context, the decision required and the records available. The first conversation is used to establish whether the work is a fit.
Software licensing is arranged directly between the client and the vendor or its partner. Advice is independent of any platform’s commercial interest.
Last reviewed: August 2026