Nuclear energy
Work-package status checked against hold points, permits and documents; the authorised team records release decisions.

Service 04
At the peak of execution many contractors, disciplines and interfaces share the same areas. Issues are raised in several meetings and lost between them, work fronts start before they are ready, and decisions are taken before their consequences are known.
This service runs the project controls cycle during execution, using the project’s existing schedule, cost and site information, or the data from services 02 and 03 where they are ordered. Reporting, look-aheads, interfaces and issues are coordinated with the client’s project management office, and on larger projects from a Situation Room.
Reports, look-aheads, interfaces and forecasts run on the same data and the same weekly rhythm.
Each issue escalated with its consequences and options, and followed until it is closed.
Agreed prerequisites tracked for each work package, with gaps reported to the responsible team.
One controls cycle for the whole project, so readiness, interfaces and issues are reviewed together each week.
Weekly and period reports from the agreed project data, each with its data date and sources.
Progress monitored against the baseline, and forecasts updated as the work and the risks change.
Interfaces between contractors registered and tracked, and the readiness evidence for each work package reported before the client’s release decision.
Issues escalated to the responsible managers with consequences and options; decisions and actions followed until closed.
A coordination arrangement within this service, on site or virtual, working with the client’s project management office. The tools used are set out in the proposal.
Deliverables: integrated reports, issue, interface and decision registers, look-ahead schedules and action follow-up.
Situation Room · coordination board
Main works, week 32
Ready means the six listed prerequisites are recorded as met; it is not an instruction to start work. The six fields are an example, not a full release checklist. Work release, permits, technical acceptance and site safety remain with the client’s authorised personnel.
Open interfaces between contractors. Select a pair to see the items.
Raised1
Escalated2
Decided2
Closed1
The cycle is the same on every project. What has to be coordinated each week depends on the sector.
Work-package status checked against hold points, permits and documents; the authorised team records release decisions.
Simultaneous operations, tool move-in and hook-up coordinated daily across contractors and the owner’s teams.
Hall-by-hall readiness, energisation and commissioning coordinated across the M&E and testing contractors.
Interfaces between packages, possessions and traffic management coordinated, with decisions recorded against the contract.
Registers, reporting rhythm, data access and, where needed, the Situation Room set up with the team.
Look-ahead, readiness and interfaces reviewed with the contractors against the current schedule and forecast.
Issues taken to the responsible managers with their consequences and options, and decisions recorded.
Actions tracked until they are closed, and the integrated project report issued to the client each reporting period.
A coordination room, on site or virtual, where the current position, the look-ahead, the interfaces and the open issues are kept up to date and reviewed with the client’s project management office. It is part of this service on larger projects, not a separate product.
No. It works with the project management office and the responsible managers. Decisions, approvals and site safety remain with the client’s authorised personnel; Enncon runs the controls cycle and prepares the information each decision needs.
The proposal identifies the tools included in the service and any separate licence or hosting costs. The contract defines data ownership, software use rights, documentation, training and handover, together with any ongoing support.
Registers, reporting rhythm and access to the project data are agreed during mobilisation, and the cycle uses the project’s existing schedule, cost and site information, or the data of services 02 and 03 where they are ordered. Scope and team are agreed in the proposal.
Tell us what you are building and where you need support.