CAP·EXE · Execution & Field Quality · A module of CAP·PATH, the Capital Project Management Platform
CAP·EXE carries the plan to site: a shift look-ahead cut from the current schedule and issued by crew, commissioning and startup planned by system with the packages tied to the systems they finish, and progress claimed on a phone or a printed sheet and verified by the owner. What the field found is on the record the same hour, and the same claims feed earned value overnight.
The plan goes to site, and the site answers back.
The problem
The schedule is updated weekly from what the contractor reports. The look-ahead is a spreadsheet. The systems list lives with commissioning. Each works until the month they disagree, and that is the month the in-service date moves.
Nobody can say which work was actually issued to which crew, so nobody can say whether the crew that is behind was ever sent.
The job is ninety percent complete by area and no system can be handed to commissioning, because nothing tied the packages to the systems they finish.
The contractor claims it, the schedule takes it, and the gap between claimed and true surfaces at mechanical completion.
A quality issue or a field change waits for the paperwork, and the decision it needed arrives after the crew has moved on.
What it does
The look-ahead knows a constraint is open, the system knows a package is still open, and the handover gate knows a punch item is still counted. Each of those is usually a different spreadsheet.
The planner cuts the next shifts from the schedule and issues them by contractor and crew.
Cut the next two to six shifts from the schedule you keep here. Every line carries its crew, a named owner coordinator, and the holds the platform knows: an isolation not in, a permit not reviewed, a hold point, materials not arrived, an open change, an inspection plan not issued, a system not released. Issuing freezes it and renders the sheets.
Once an issue stands, a claim on work that was not issued is refused, with the way to ask. The request goes to the coordinator for that work, who hears at once; approving it adds the line. The gap between what was sent and what was worked closes at the source.
Each crew gets a printed sheet with a box per shift for percent, hours left, crew, delay, and a note, a line for the foreman’s signature, and a code. A foreman with no account scans the code and reports from a phone, or the sheet is keyed in. The coordinator’s initials are recorded as validated on paper.
An administrator or the planning lead uploads the current schedule export, or the scheduler’s script pushes it. The team confirms its coding once and later copies carry it forward. The copy’s age reads on every page that uses it, amber past a day in execution. It is kept current, never scored: a score takes a review.
Commissioning and startup planned by system, with the packages tied to the systems they complete.
Process systems and their utilities, each with its commissioning and startup steps and targets that move when the start moves. Commissioning’s own spreadsheet or project file imports, and nothing is written until you apply it.
Each package names the systems its work completes, proposed from the schedule’s codes and the equipment tags and confirmed by a person. The gates view lists the packages planned to finish after their system’s turnover target, while there is still time to re-sequence.
A system cannot be turned over while a package on it is open, an A punch item is open, or a completion form is unsigned. The board says which, and the last signature turns it over.
Where the project meets the running plant, the order of locks and blinds is held by the record.
A package states the isolation it needs, or that none is required and why. A confined space entry needs a positive isolation at the equipment, or a recorded deviation.
A blind goes in only once the valves are locked and the make-safe steps are reported done. Those locks release only once every blind is verified. A blind comes out only under the valves locked again. Each refusal names what blocks it, and operations can pass one with a reason that is kept.
Each step proposes the permit kinds it needs, and operations reviews them by package. The review is stamped against the steps as they stood, so any later change to a step reads proposed again.
A phone, a tag, or a poster at the gate: the finding is on the record before the crew leaves it.
A quality issue, a field observation, an RFI, a punch item, or a field change, raised on a phone with a photo and a line, from the job or from the tag on the equipment. With no signal it waits on the phone and sends itself.
A contractor’s worker scans the poster at the gate and reports a safety observation, a near miss, a quality issue, or a lesson with no sign-in. Sending without a name is the default for safety. Every entry is held until your site team accepts it into the register, and a severe near miss reaches them at once.
The crew calls the hold point when it is ready and the notice clock starts: yellow past notice, red past the hours you set. Who may release it is a rule, never the caller.
Progress claimed at the work, verified by the owner, and read as earned value by morning.
Two minutes at shift end: the steps by quarter, hours by craft, and one delay code. It works offline and sends when the signal is back.
The named coordinator validates the crew’s claim. A contractor never verifies its own, and you can choose to count verified claims only. Validated progress goes back to your scheduling tool as a file.
Issued, claimed, validated, done, slipped, and disputed, with hours remaining and delays by code, read from the same lines the crews worked. The daily meeting walks it rather than rebuilding it.
Systems · startup
The systems view holds commissioning and startup by system, with the packages that feed each one and the gates they have to meet.
Statuses here are reported by a named person · your permit-to-work system stays the authority
Where the line sits
This is safety-adjacent work, so the line is drawn where it belongs. The platform plans, sequences, and tracks what named people report. It authorizes nothing. A status here reads ‘reported by’, never ‘proven safe’.
What changes
How it fits
CAP·SCP (Scope Management), CAP·PLN (Planning, Estimating & Materials) and CAP·EXE (Execution & Field Quality) are one add-on to the CAP·PATH subscription, per site, and one add-on covers both the capital and the turnaround door a site holds. The gated work process, the portfolio, governance, risk, cash forecasting, lessons, the readiness indicator, and the role guides are in the base platform.
CAP·PLN releases the packages this module issues, and the cost control one-pager covers how the claims made here become earned value. Completion forms and the punch list, already part of the platform, close the work by system.
We load the schedule, bring your systems in, and cut the first look-ahead with your construction lead.