Improve

Purpose

Evaluate event outcomes, preserve technical knowledge, implement corrective actions and improve future asset and shutdown performance.

Scope

Final performance consolidation — cost, schedule, safety, scope and quality
Post-event review and technical failure/condition review
Benefits realisation verification
Asset and maintenance strategy updates
Process improvement action implementation
Final event report, archive and return of learning to the STO lifecycle

Phase Gate

Every phase closes at a formal phase gate. Work may proceed to the next phase only when the accountable authority accepts the required outputs, the outstanding conditions and the residual risks. The gate is a decision, not a formality — an unaccepted gate means the event is not ready to move on.

Process Steps

01
Consolidate Final Event Performance
Intent
Create one verified record of actual event performance against approved objectives and baselines.
Inputs
- Final schedule status
- Cost actuals and commitments
- Scope and change records
- Safety and environmental records
- Quality and rework information
- Production and ramp-up results
- Contractor and resource data
- Event objectives and KPIs
Actions
- Reconcile final scope completed, deferred and added
- Reconcile final cost and outstanding commitments
- Calculate final schedule and milestone performance
- Confirm actual shutdown-to-production duration
- Consolidate safety, environmental and quality outcomes
- Consolidate labour, productivity and contractor information
- Consolidate start-up, ramp-up and asset-performance results
- Validate data with accountable functions
- Explain significant variance against baseline
- Secure final performance dataset
People
Planning and Controls Lead consolidates data. Shutdown Manager approves it. Finance, Operations, Maintenance, HSE, Quality, Commercial and Reliability validate applicable results.
Process
Final reporting retains the original baseline and separately records approved changes. Unfavourable results are not removed through retrospective rebaselining.
Technology
Scheduling system, cost platform, CMMS, incident system, historian and business intelligence dashboard.
What Good Looks Like
- Results are traceable to approved data sources
- Baseline, changes and actuals are distinguishable
- Variance explanations identify causes
- Technical and business outcomes are both included
What Bad Looks Like
- Only positive KPIs are reported
- Cost commitments are omitted
- Original baselines are overwritten
- Final performance differs between reports
Outputs
- Final Performance Dataset
- Final cost and schedule reports
- Scope reconciliation
- KPI results
- Variance analysis
02
Conduct the Post-Event Review
Intent
Identify what occurred, why it occurred and what must be sustained or changed for future events.
Inputs
- Final Performance Dataset
- Shift reports and meeting records
- Incident and quality records
- Scope and change history
- Contractor and workforce feedback
- Start-up and asset findings
- Previous lessons and commitments
Actions
- Compare planned outcomes with actual outcomes
- Identify practices that worked well
- Identify failures, delays, rework and control weaknesses
- Separate immediate causes from underlying system causes
- Review planning, readiness, execution and start-up performance
- Review contractor and stakeholder feedback
- Review whether previous lessons were implemented
- Define proposed corrective and improvement actions
- Assign preliminary owners and priorities
- Record evidence and decisions without assigning blame
People
Shutdown Manager chairs the review. Representatives from all event functions, shifts and key contractors participate. An independent facilitator may support major reviews.
Process
The review focuses on systems, decisions and controls. Individual performance scoring is outside this process.
Technology
Workshop platform, event dashboard, incident system, action register and document repository.
What Good Looks Like
- Evidence is reviewed from all phases
- Frontline and contractor experience is represented
- Positive practices are captured as well as failures
- Findings lead to specific actions
What Bad Looks Like
- The review becomes a blame session
- Only senior leaders attend
- Discussion relies on memory rather than evidence
- Generic lessons are repeated after every event
Outputs
- Post-Event Review Record
- Lessons Learned Register
- Proposed improvement actions
- Positive-practice register
- Issues requiring formal analysis
03
Complete Technical Failure and Condition Review
Intent
Use shutdown findings to improve understanding of asset condition, failure behaviour and remaining life.
Inputs
- Equipment condition findings
- Removed parts and failure evidence
- Inspection and measurement records
- Commissioning baseline data
- Failure history
- FMECA and RCM information
- Deferred and emergent work
Actions
- Review significant wear, damage and degradation findings
- Compare actual condition with predicted condition
- Inspect retained components and samples
- Confirm or revise failure modes and mechanisms
- Identify recurring and common-cause failures
- Assess remaining life and future intervention need
- Initiate RCFA where required
- Identify design, operating or maintenance improvements
- Update asset risk and health information
- Define follow-up monitoring requirements
People
Reliability Engineer leads the review. Maintenance, Operations, Engineering, Inspection, laboratories, vendors and technical specialists contribute.
Process
Physical evidence is retained until required technical reviews are complete. Conclusions must distinguish confirmed causes from hypotheses.
Technology
Reliability database, CMMS, laboratory systems, condition-monitoring platform and engineering analysis tools.
What Good Looks Like
- Actual findings improve future intervention intervals
- Failure evidence is preserved
- Unexpected degradation triggers analysis
- Asset strategies are updated from evidence
What Bad Looks Like
- Removed parts are discarded before examination
- Findings remain only in work-order comments
- Assumptions are reported as confirmed causes
- The next shutdown repeats the same inspection uncertainty
Outputs
- Asset Condition Review
- Failure-analysis actions
- Revised remaining-life estimates
- Follow-up monitoring plan
- Updated asset risk profile
04
Verify Benefits Realisation
Intent
Determine whether the shutdown achieved its approved business, operational, compliance and reliability objectives.
Inputs
- Event objectives and success criteria
- Start-up and production data
- Asset performance and condition data
- Safety and compliance records
- Final event cost
- Benefits-realisation register
- Pre-event performance baseline
Actions
- Review each approved objective
- Verify the required evidence and measurement period
- Compare pre-event and post-event performance
- Confirm statutory and integrity outcomes
- Calculate realised and outstanding benefits
- Identify objectives not achieved
- Identify unintended positive or negative outcomes
- Assign actions for incomplete benefits
- Report verified results to the Sponsor
- Transfer long-term monitoring to the accountable function
People
Event Sponsor is accountable. Reliability, Operations, Finance, Maintenance, HSE and Projects verify relevant benefits.
Process
Benefits are not claimed solely because work was completed. Evidence must demonstrate the intended outcome.
Technology
Business intelligence dashboards, historian, CMMS, finance system, reliability platform and benefits register.
What Good Looks Like
- Benefits are measured against pre-approved criteria
- Asset and business outcomes are both reviewed
- Unachieved benefits produce follow-up actions
- Long-term measures have permanent owners
What Bad Looks Like
- Completion is reported as benefit realisation
- Financial benefits lack supporting assumptions
- Poor post-event performance is excluded
- No one monitors outcomes after closure
Outputs
- Benefits Realisation Report
- Objective achievement status
- Outstanding-benefit actions
- Post-event performance baseline
- Sponsor acceptance
05
Update Asset and Maintenance Strategies
Intent
Incorporate event learning into future maintenance tasks, inspection intervals, overhaul strategies and asset investment decisions.
Inputs
- Technical Failure and Condition Review
- Benefits Realisation Report
- Work-order history
- Reliability analyses
- Commissioning baseline
- Deferred and follow-up work
- Updated asset risk profile
Actions
- Review RCM and FMECA assumptions
- Revise preventive and predictive maintenance tasks where justified
- Revise inspection and overhaul intervals
- Update condition-monitoring limits and routes
- Update bills of materials and repairable strategies
- Update standard jobs and labour estimates
- Initiate redesign or capital improvements
- Update remaining-life and replacement forecasts
- Update the 10-year outlook and five-year portfolio
- Communicate approved strategy changes
People
Reliability Manager is accountable. Reliability Engineers, Maintenance, Operations, Engineering, Planners, Supply and Asset Management participate.
Process
Strategy changes require technical evidence, controlled approval and implementation in the source system. A lesson is not complete until normal work systems change.
Technology
CMMS, reliability platform, asset strategy system, document management and capital portfolio system.
What Good Looks Like
- Future work reflects actual shutdown findings
- Ineffective tasks are changed or removed
- Intervals are based on evidence
- Portfolio dates respond to revised asset condition
What Bad Looks Like
- Lessons remain in the final report only
- Standard jobs repeat known errors
- Strategy changes are discussed but not loaded to the CMMS
- Next-event scope is copied unchanged
Outputs
- Updated Maintenance Strategies
- Updated RCM and FMECA records
- Revised standard jobs
- Updated lifecycle and portfolio forecasts
- Approved improvement projects
06
Implement Process Improvement Actions
Intent
Convert lessons learned into controlled changes to shutdown standards, tools, systems, competence and behaviours.
Inputs
- Lessons Learned Register
- Post-Event Review
- Incident and quality investigations
- Contractor feedback
- Audit findings
- Approved improvement priorities
Actions
- Convert each lesson into a specific action
- Define the required process or system change
- Assign an accountable owner and due date
- Prioritise by risk, recurrence and value
- Update procedures, templates and checklists
- Update training and competency requirements
- Update digital workflows and data standards
- Pilot major changes where appropriate
- Verify implementation evidence
- Confirm effectiveness before closing the action
- Escalate overdue or ineffective actions
People
Shutdown Governance Owner is accountable. Process Owners implement changes. HSE, Quality, Planning, Operations, Maintenance, Training, Digital and Supply support applicable actions.
Process
An action is not closed when a document is issued. Closure requires proof that the change is operating and has addressed the original issue.
Technology
Action tracking system, document control, learning management system, workflow platform and audit tools.
What Good Looks Like
- Actions change normal work practices
- Owners and due dates are visible
- Effectiveness is verified
- Improvements are ready before the next relevant event
What Bad Looks Like
- Lessons are copied into a register and forgotten
- Actions state only “communicate” or “be more careful”
- Documents change without training users
- Actions close without effectiveness evidence
Outputs
- Implemented Improvement Actions
- Updated procedures and templates
- Updated training and workflow controls
- Effectiveness verification records
- Remaining-action escalation report
07
Issue and Archive the Final Event Report
Intent
Create the authoritative event record and preserve information required for compliance, reliability analysis and future shutdown planning.
Inputs
- Final Performance Dataset
- Post-Event Review
- Technical and benefits reports
- Improvement action status
- Work, quality, safety and commissioning records
- Financial and contract closure information
Actions
- Summarise event purpose, scope and outcomes
- Report actual safety, schedule, cost, scope and quality performance
- Report start-up, production and asset-performance outcomes
- Summarise major variance causes
- Summarise technical findings and deferred risks
- Record lessons and improvement commitments
- Record benefits-realisation status
- Obtain functional verification and Sponsor approval
- Archive the report and supporting records
- Apply retention, security and confidentiality requirements
- Communicate relevant findings to stakeholders
People
Shutdown Manager prepares the report. Event Sponsor approves it. Functional owners verify their data. Document Control archives the record.
Process
The final report must be supported by controlled evidence. Sensitive information is distributed according to approved access and retention requirements.
Technology
Document management system, records repository, CMMS, business intelligence platform and electronic approval workflow.
What Good Looks Like
- One authoritative report contains traceable results
- Supporting records can be retrieved
- Conclusions distinguish evidence from opinion
- Future planners can reuse the knowledge
What Bad Looks Like
- Several conflicting final reports exist
- Source data are not retained
- Report preparation begins months after knowledge disperses
- Confidential or statutory records are stored incorrectly
Outputs
- Approved Final Event Report
- Archived event record
- Records index
- Stakeholder communication
- Formal event knowledge package
08
Return Learning to the STO Lifecycle
Intent
Close the improvement loop by incorporating verified learning into long-term plans and the next relevant shutdown event.
Inputs
- Final Event Report
- Implemented improvement actions
- Updated asset strategies
- Revised portfolio information
- Outstanding benefits and risks
- Future shutdown forecasts
Actions
- Review the 10-year intervention outlook
- Review the 5-year shutdown portfolio
- Review the 2-year integrated schedule
- Update future event timing and duration assumptions
- Identify scope candidates for the next event
- Transfer deferred and follow-up work into the CMMS
- Transfer verified lessons into future charters and plans
- Confirm outstanding actions have permanent owners
- Brief future Sponsors and Shutdown Managers
- Obtain final lifecycle closure approval
People
Asset Manager is accountable for strategic integration. Shutdown Manager transfers event knowledge. Reliability, Operations, Maintenance, Projects, Planning and Finance update applicable systems.
Process
The STO lifecycle is continuous. Event closure is achieved only when learning, deferred work and revised asset needs have entered the controlling business and maintenance systems.
Technology
CMMS, portfolio system, asset strategy platform, scheduling system, lessons database and document repository.
What Good Looks Like
- The next event begins with verified knowledge
- Portfolio timing reflects actual asset condition
- Deferred work remains visible and risk controlled
- Improvement commitments survive team changes
What Bad Looks Like
- Every shutdown begins by recreating previous information
- Deferred work is forgotten
- Portfolio assumptions remain unchanged despite new evidence
- Lessons depend on individuals remaining in the organisation
Outputs
- Updated 10-Year Asset Intervention Outlook
- Updated 5-Year Shutdown Portfolio
- Updated 2-Year Integrated Shutdown Schedule
- Next-event scope candidates
- Phase 06 Gate Approval
- Closed STO Lifecycle

Key Performance Indicators

KPI	Why It Matters	How To Measure	World Class	Benchmark	Typical
Post-event review held within 4 weeks	After four weeks the team has dispersed and the detail is gone — the review becomes folklore.	Events with a documented review inside 4 weeks ÷ total events.	—	100% of events	—
Improvement actions closed on time	Lessons that never become closed actions are the reason the same problems recur every event.	Actions closed by due date ÷ actions raised.	—	>90%	—
Asset strategies updated from event findings	Opening an asset is the best condition data you will ever get — not using it wastes the outage.	Assets with revised PM/strategy ÷ assets where findings warranted a change.	—	100% of applicable assets	—
Benefits verified against the charter	Unverified benefits let poor events be reported as successes.	Objectives measured with evidence ÷ objectives declared in the charter.	—	100% of stated objectives	—
Next-event scope candidates transferred to the CMMS	Deferred work that leaves the system reappears as a breakdown.	Deferred/follow-up items raised in the CMMS ÷ items recorded at closure.	—	100% of deferred work	—