Maddern Capital & Projects
Shutwise

Shutdown and Turnaround Suite

Every work pack ready before gas off.

From work order to gas on in one place.

The event's scope loaded and held from the scope freeze, every work pack built to the standard and checked before it reaches the field, and the planning driving the shutdown program and the cost estimate — then the contractors' work recorded on a phone, witnessed, accepted and handed back to operations. One record from the first work order to gas on, and the next event starts from it.

  • Shutdowns
  • Turnarounds
  • Outages
Shutdown dashboard TRAIN 2 MAJOR · 6 WEEKS TO GAS OFF
Packs issued
142
of 186 in scope
With QA/QC
11
awaiting review
Site approved
82%
gate target 80%

Readiness S-curve

Gate targets Approved Forecast
Gate 1 Gate 3 On site
1
Pack per work order, with every trade's steps in it — no separate packs to reconcile
8
QA/QC checks every pack passes before it goes to the site approver
P6
The program out as a native XER, and the updated XER read back for progress
0
Logins a late or emergent work reviewer needs: they review from their own email link

The platform

Four stages. One record. From scope to handover.

A shutdown is usually run from a workbook, a folder of packs, a P6 file, an estimate spreadsheet and a pile of completed forms, each describing the event as it was when someone last updated it. Shutwise keeps them as one record: the work order planned once drives the pack, the program, the estimate and the completion record.

Stage 01

Scope and Readiness

The event's scope loaded from its workbook, held from the scope freeze, and measured against each readiness gate — so the question "are we ready?" has a number, not an opinion.

  • Every work order becomes a pack, classified, with its scope decision
  • New, changed and dropped work orders previewed before anything is saved
  • Planners, QA/QC reviewers and site approvers nominated, the work shared out by load
  • Readiness gates with targets, an S-curve and a one-page management report
  • Each work order's planning tasks and maturity measured against every gate
  • Late, emergent and removed work only through a costed scope change
Stage 02

Work Pack Planning

One pack per work order for every trade, built to the standard, checked by QA/QC and approved before it is issued — started from SAP, from the last shutdown's pack, or from a guided build.

  • Read from SAP or its print; the planning sent back to SAP when done
  • A guided build that asks what decides the plan and writes the operations, hazards and PPE
  • Repeat work started from the pack planned for the same equipment last time
  • Task sheets with every trade's steps, photographs and mark-up
  • A flange register giving each joint its gasket, studs and torque
  • The equipment found and circled on the P&IDs and plot plan — scanned drawings included
Stage 03

Program and Estimate

The planned work orders drive the shutdown program and the cost estimate, so neither is built twice and both firm up as the planning does.

  • Gas off to gas on with every operation, crews levelled and the critical path
  • Primavera P6 out as a native XER, and progress read back from it
  • From category norms to planned hours at contract rates, the estimate class following
  • Baseline, budget, change requests and a P10–P90 risk analysis
  • Crew limits and crashing, priced against the duration
  • Actual hours against the plan, saved as a benchmark for the next event
Stage 04

Execution and Completion

Contractors work the pack on a phone; the client's QA/QC witnesses it, accepts it and hands the plant back to operations with the record complete.

  • A contractor portal opened from the pack's QR code, with or without signal
  • Steps signed off, joints recorded, photographs and punch items as the work goes
  • Hold and witness points, witnessed on a phone and listed in an inbox
  • Materials picked, packed and collected into the contractor's custody
  • Acceptance with a completion record, and PRCO and TECO set in SAP
  • Ready for start-up and the Operations Handover Certificate

The work pack

Built to the standard, checked before it reaches the field.

A pack is only as good as the last person who checked it. Shutwise builds each one to the same layout so a contractor always finds things in the same place, works out what it can from what the planner has already entered, and lists what is missing before QA/QC sees it.

  1. 01
    The work order Read from SAP, from its print, or from a filled development sheet — its operations, materials and work centres in words, each explained.
  2. 02
    The plan for every trade Scaffold, crane and lift, isolation, gas testing, hot work, inspection, testing: the guided build asks, and the steps, hazards, PPE and materials follow.
  3. 03
    Drawings marked up The equipment tag is found on each P&ID and the plot plan, read by OCR from a scan, and circled for the planner to confirm.
  4. 04
    QA/QC, then site approval Eight checks by someone other than the builder, a review register closed, then the nominated site approver signs it off.
  5. 05
    Issued to each contractor A master copy for the client, and a copy for each contractor with its own part to sign and a QR code to the live pack.

Scope control

Late work is costed before it is approved.

From the scope freeze, work comes into or goes out of the scope only through a scope change. Each one is priced from the estimate and placed in the program before anyone is asked to decide, so the reviewers see what it costs and what it does to gas on — not just what it is.

A late work request Now With the change
Gas off to gas on
From the levelled program, with the request's work orders in it.
5.0 days 6.0 days
On the critical path
Whether the new work moves gas on.
— yes
The work order
Its type's norm until it is planned; the planner can enter the cost instead.
— AUD 32,000
Levelling and contingency
The crews' idle shift time, and the event's contingency on both.
— AUD 5,840
The owner's team for the extra day
Counted only where gas on moves.
— AUD 18,500
Event Lead first

One person looks before everyone does

Every late, emergent or removal request goes to the Event Lead first, who sends it on to the reviewers or returns it to the planner with a note — so the reviewers' time goes on requests worth their time.

No login needed

Reviewers decide from an email link

Operations, maintenance, integrity and reliability review at the same time, each from a link of their own, and the Plant Manager approves once every review is in. Each review and the decision go into the change register.

Program and estimate

The planning drives the program and the cost.

A program and an estimate built separately from the packs describe a shutdown nobody is planning. In Shutwise each planned work order's operations are the program's activities and the estimate's hours, so a change to the plan moves both, and each says how far it can be trusted.

The program

Levelled crews and the critical path

Gas off, run-down, isolations and blinding, every work order's operations, mechanical completion, leak test and gas on. Task hours carry a non-productive factor, and each trade's crew is levelled within float so it is as small as the duration allows.

Primavera P6

Out as an XER, and back again

The program exports as a native P6 file with its calendars, resources and relationships. During the event the updated XER is read back, compared activity by activity, and can run the program on P6's dates.

The estimate

An estimate that knows its class

Each work order is priced at its category norm until it is planned, then from its own operations at contract trade rates, with cranes, equipment and materials. The class and range follow how much is planned, with prompts for what to firm up next.

Duration

Cost against duration

Crew limits and crashing, every combination priced against the production lost per day, with camp, flights and buses from the levelled crews — and the chosen one applied as the program.

Commercial confidentiality

Each contractor sees only its own part.

A shutdown has several contractors on the same work orders, and the client's rates and estimate are its own commercial information. Each contractor is issued and sees only what is its to do, enforced on the server before the page or the PDF is built.

Information Client Contractor
The work pack Master copy, every trade Its own copy: its steps to sign, the other trades' in grey with who does them
Rates, estimate and budget Full visibility Never shown
Other contractors' QA forms, joints and photographs All of them Never shown
Revisions Who has opened each revision What changed, and a receipt for the revision it holds
Materials Status, kitting and custody Its kit: scan the slip and record collecting it
Work submitted Accept it, or return it item by item Submits its own part; never chooses a status

The contractor's environment

The crew gets a pack that works on a phone.

A printed pack goes out of date the day it is revised, and a form filled in on paper is typed up twice. The contractor's portal is the pack, live: what to do, in order, and a place to record it as it is done.

QR code

From the printed copy to the live pack

Every contractor copy carries a QR code to its work order in the portal: the steps to sign, the full-size drawings and documents, and what changed in the latest revision.

Without signal

Saved for offline, sent when it can be

A work order saved for offline keeps its page, joints, QA forms and drawings on the phone. What is recorded without signal waits in an outbox and is sent in order when there is signal again.

Sequence

Who each step waits on

Each step shows the other trade's step before it, live, and the next trade is told when its wait is over — so a fitter is not standing at a scaffold nobody has tagged.

Joint records

Every flanged joint, recorded on the spot

Checklist, flange gaps and torque at each stage, the calibrated tool picked by serial, and photographs — witnessed by the client's QA/QC on a phone, or returned with the reason.

Found work

A defect raised where it is found

Extra work or a defect, with a photograph, goes to the client to raise as a priced change request or to decline — not into a notebook.

Their own branding

Their mark on their work

The client's logo on its packs, and the contractor's on the copies issued to it, beside MCP's mark. Uploaded once, printed on every pack and record after.

Completion and handover

The plant handed back with the record already complete.

The handover dossier is usually assembled after start-up from whatever came back. In Shutwise it is built as the work closes: each area shows what is accepted, what is open and what is still in place, and is offered to operations only when it is done.

Back to service, by area. Overrides, inhibits and bypasses, car seals and locked valves, and every blind in and out are each verified by operations on their register, and the area's return to service checklist shows what is still in place.
  1. 01
    Submitted complete The contractor's supervisor submits its part when the work is recorded. Work not done yet, such as scaffold strip, is carried as a punch item with its reason.
  2. 02
    Witnessed The client's QA/QC witnesses each joint and QA form as it is recorded, from an inbox of everything waiting on them, oldest first.
  3. 03
    Accepted Exceptions first, then accepted: the completion record is filed in the pack and the order set practically complete in SAP.
  4. 04
    Ready for start-up The checklist answered by its accountable roles, with what Shutwise already knows beside each line, then the start-up approval.
  5. 05
    Handed to operations Operations accept the area on the Operations Handover Certificate, filed with every work order in it.

Hold points hold the work where the client says. Nothing else does: what is missing is listed for the reviewer, not used to stop the crew.

QA/QC PHILOSOPHY · MCP SHUTWISE

Evidence and assurance

Built for the audit after the shutdown, not just the shift.

Traceability

Every decision attributed

Sign-offs, reviews, approvals, witnessing, scope changes and revisions are recorded against the person and the moment, so a work order can be reconstructed long after the event.

Records

The completion record in the pack

Each accepted work order files its completion record — steps, joints, QA forms, gas tests, photographs and punch items — in its own pack, beside the revision it was worked to.

Confidentiality

Terms agreed before anything else

Everyone who signs in agrees to the confidentiality and acceptable-use terms first, and each acceptance is kept: who, when and which wording.

Deployment

Hosted, maintained, tested

Delivered as a hosted service on AWS in Sydney, with files encrypted at rest and a full regression suite run on the production database engine before every deployment.