Nuclear energy
Equipment, documents, work orders and inspection records linked, so reported status traces to controlled records.

Service 02
On a large project the schedule, the models, procurement, cost and site records each live in their own system. Reports are assembled by hand from exports, site progress reaches planning and cost control days or weeks late, and a change in one place is not seen where it matters.
This service maps the agreed source records to the relevant equipment, documents, activities, quantities and cost codes. Validation checks identify missing, duplicate and conflicting records, and unresolved exceptions remain visible, with an owner and an agreed action. Reports show the data date, source and validation status, and each source system remains the authority for its own records.
Dashboards and reports read from validated data and stay current as it changes.
A late delivery or a design change shows in the activities, milestones and cost it affects.
Integrations run in the client’s environment or on agreed EU hosting, documented for handover.
Agreed source records are linked to the equipment, activity and cost line they belong to, refreshed at agreed intervals, subject to source-system access and data availability.
Primavera P6, BIM models, engineering documents, procurement, cost and ERP systems and site records, read where they already live.
Equipment, documents, activities, quantities and cost linked through common codes, with scripted checks on every update.
Built on the project database, so reporting no longer depends on manual consolidation.
How a delay or change in one area affects activities, cost and milestones in others.
Integrations documented so they can be maintained and extended as the project develops.
Deliverables: the project database and its validated links, dashboards and automated reports, and documentation so the integrations can be maintained and extended.
Project database · workspace
Main works, week 32
Select a component
Fields complete: the share of required fields filled in each source. A record can carry several exceptions, so exceptions are not subtracted from the record count.
Also affected: hall 2 HVAC commissioning, which needs permanent power.
Assumptions: installation has 2 weeks of float and handover 1 week, treated as independent illustrative buffers, not a validated network. Extended site costs of €0.12m per week of handover delay; other costs are not included.
The integration method is the same on every project. Which records matter most depends on what drives the dates in each sector.
Equipment, documents, work orders and inspection records linked, so reported status traces to controlled records.
Tool deliveries, move-in routes and hook-up linked to the schedule, with information from many departments in one database.
Long-lead equipment followed from order to energisation, hall by hall, against the activities that need it.
Measured quantities, site diaries and payment applications linked, so progress, cost and valuation agree.
Systems, data owners and reporting needs mapped, and the data model and first reports agreed.
Sources connected and records linked through common codes for equipment, activities and cost.
Scripted checks flag missing, duplicate and conflicting records before anything is reported.
Dashboards and reports run at the agreed update interval; documentation and handover follow the proposal and contract.
No. Primavera P6, the ERP, the BIM and document platforms and the site tools stay in place. The integration reads from them and links their records; it does not replace the systems the teams already use.
In the client’s environment, or on EU hosting agreed for the project. Confidentiality terms, access permissions and a secure transfer method are agreed before any data is shared, and data ownership and the handover of data and tools are set out in the contract.
SQL databases and Python for import, linking and validation, and a project-specific web application where reporting, data entry or review workflows are needed. The choices follow the client’s IT standards. The proposal identifies the tools included and any separate licence or hosting costs; the contract defines software use rights, documentation, training, handover and any ongoing support.
A discovery phase comes first, to map the systems and agree the data model. The first reports follow from the first connected sources, and the timing is agreed in the proposal.
Tell us what you are building and where you need support.