Diriger - RAIDSafe: The Asset Management PDCA Loop

DIRIGER / RAIDSAFE GOVERNANCE RESEARCH

RAIDSafe: The Asset Management PDCA Loop

One international standard... One management loop... Four field stages... Every job smarter than the last.

ISO 55000 is the international standard for asset management, and its 2024 editions are explicit about the shape of a competent asset management system: Plan, Do, Check, Act - a continuous loop wrapped in leadership and driven by continual improvement. For asset-intensive industries - energy networks, mining, utilities, infrastructure - the standard is not an abstraction. Regulators reference it in codes and determinations. Tender panels score against it. Boards claim alignment to it in annual reports.

Yet on the field floor, the loop breaks. Most asset-intensive organisations run PDCA at the management-system level - an annual asset management plan, a yearly management review, a periodic audit. Meanwhile, the work that actually creates or prevents harm happens DAILY. Executed by crews whose pre-start and hazard assessment processes connect to the management loop through a paper checklist.

"The strategic loop turns once a year. The operational loop has to turn once a day"

When the two loops don't connect, the organisation has a management system that describes governance and a field practice that doesn't deliver it.

Our previous insight, RAIDSafe: The Pattern of Failure Australian Safety Keeps Finding, analysed ten major Australian investigations and found the same four governance failures repeating ....

Risk Aggregation, Assumption Decay, Issue Escalation gaps, and Dependency Blindness.

Every one of those patterns is a PDCA failure at the operational level - a Check that never happened, an Act that never learned, a Plan that never saw the field. This insight sets out how RAIDSafe closes that gap by running the PDCA loop where the risk actually lives: at the job site, with the crew, with evidence captured as work happens.

“ISO 55000 describes the loop... RAIDSafe runs it - one job at a time, in the field, with evidence.”

PART-1: THE EVIDENCE

WHAT ISO 55000 ACTUALLY REQUIRES - AND WHERE THE LOOP BREAKS

The ISO 55000 family was revised in 2024. ISO 55000:2024 sets the vocabulary, overview and principles. ISO 55001:2024 states the requirements for an asset management system, structured - like all ISO management system standards - on the Plan-Do-Check-Act cycle: planning (clause 6), support and operation (clauses 7-8), performance evaluation (clause 9), and improvement (clause 10), all wrapped in leadership (clause 5). The 2024 revision sharpened the emphasis on outcomes: organisations must assess the effectiveness of the actions they take, not merely demonstrate that the actions exist.

That word - effectiveness - is where most organisations are exposed. The standard is explicit that each turn of the loop must be validated against evidence. Here is what that requires, and what the field practice of most asset-intensive organisations actually delivers:

Key Takeaways - Where PDCA Breaks in Field Practice

PLAN: ISO 55001 requires that asset management objectives translate into operational planning. Most organisations have a strategic asset management plan, but the field work order that mobilises a crew tomorrow does not reference it. The plan exists; the connection to the job does not.

DO: The standard requires operational control and competent implementation. Field hazard assessment is typically a static SWMS or checklist, completed from the car park, assessing the hazards on a form rather than the hazards at the site.

CHECK: ISO 55001 requires monitoring, measurement, and evaluation of performance - and the 2024 revision demands assessment of the effectiveness of actions taken. Most organisations evaluate this annually, retrospectively, in a management review. The evaluation of whether controls actually worked happens months after the threshold was crossed - if it happens at all.

ACT: The standard requires continual improvement fed by evaluation results. Improvement actions drawn from investigations and reviews routinely take years to reach field practice - and the incidents keep finding the same gap.

AWARENESS: None of this is a certification failure. Organisations achieve and maintain ISO 55001 certification while their field loop runs on paper. The standard requires the system to be effective; the audit samples the evidence. The daily loop between the management system and the job site is the blind spot.

The Patterns Writ Large

Read against the Pattern of Failure analysis, the connection is direct. The four failure patterns found across ten Australian investigations are what a broken operational PDCA loop looks like after the fact ....

Assumption Decay is a Check failure. Controls were assumed effective because they had worked before - battery backups, gas ventilation, ride maintenance - with no scheduled validation against current conditions. A loop that never turns cannot detect an assumption going stale.
Issue Escalation gaps are a Check failure. Twenty-seven methane exceedances were logged but never escalated into an operational stop. Logging is not checking; a finding without escalation to closure is a loop that stops at the first arrow.
Risk Aggregation failure is a Plan and Check failure. Four interacting faults at Callide C, each assessed in isolation, never assessed as a combined scenario. The loop must aggregate, not merely list.
Dependency Blindness is a Plan failure. Ventilation, gas monitoring and longwall operations, each managed competently in silos, never mapped as an integrated chain with owners.

The investigations did not find organisations without a management system. They found organisations whose management system loop and whose field practice loop never touched. ISO 55000 gives the architecture for the connection. The industry needs a way to run it at job level, daily, with evidence.

Trending Governance Goals

Asset-intensive industries are converging on goals that map one-to-one onto a functioning PDCA loop ....

Dynamic Risk Aggregation: living risk profiles that combine multiple hazards, conditions and indicators into a single escalating assessment - the Check that catches the combined scenario.
Assumption Validation at Scale: scheduled, evidence-based validation of critical controls against current operating conditions - a Check that runs continuously, not annually.
Automated Issue Escalation: tracking with escalation triggers based on thresholds, patterns and trends - closing the loop on every finding.
Dependency Mapping and Ownership: explicit ownership of the connections between systems, processes and teams - planned before the job, not reconstructed after it.
Evidence-Based Regulatory Defence: contemporaneous, timestamped evidence of dynamic risk assessment and governance decisions - documented information that satisfies ISO 55001 clause 7.5 and the regulator with the same record.
AI-Augmented Decision Support: AI not replacing human judgement but surfacing patterns, aggregating risks and flagging assumption decay before it becomes critical - with the crew's hands on the pen.

PART-2: THE FRAMEWORK FOR CHANGE AND THE SHIFT REQUIRED

FROM ONE ANNUAL LOOP TO TWO CONNECTED LOOPS

The shift required is not a new standard. It is a second loop, run at field tempo, connected to the first.

The strategic loop - asset management objectives, capability planning, management review - turns annually and is well served by existing ISO 55001 practice.

The operational loop - arrive, capture, assess, decide, work, verify, learn - must turn with every job, and it is here that most organisations run on paper.

The two loops connect through evidence. Every field capture, assessment, sign-off and validation is documented information (clause 7.5) that the strategic loop consumes:

Management review (clause 9.3) evaluates field evidence instead of management anecdotes;
Improvement (clause 10) is fed by validated field learnings instead of retrospective investigation findings.
And when the field loop learns - when the RAID Situation Register records how risks were actually managed, which assumptions held, which issues were resolved, which dependencies nobody had considered - the next job's Plan is smarter than the last one's.

“The strategic loop turns once a year... The operational loop must turn once a day... RAIDSafe is the second loop.”

The Safety Assessment Maturity Gap

Most organisations operate at Level 1 or Level 2 in this maturity: paper pre-starts, static SWMS, retrospective audits. The gap to Level 4-5 - dynamic, AI-assisted, integrated governance - is not incremental. But neither is it a three-year transformation. It is a loop, and loops can be started.

"The goal is not to digitise the paper checklist. It is to replace the checklist with intelligence."

PART-3: AN EXECUTABLE SOLUTION

RAIDSafe: THE ASSET MANAGEMENT LOOP (SHORT INTERVAL MANAGEMENT)

RAIDSafe is an AI-native governance platform built for asset-intensive industries. Its usage model runs the PDCA loop at field tempo, with Verification and Validation wrapping the loop as the improvement engine. The loop: Plan - Do - Check - Act, every job, with the evidence trail as a by-product of doing the work.

Stage 1 - PLAN: Arrive and observe the job

Work orders and crew capability are reviewed and related before anyone lifts a tool. The RAIDSafe configuration already knows who you are, where you are, what the job entails, and how you should proceed. At the site: pre-start and site access checks - induction status, permit-to-work validity, exclusion zones, environmental conditions, Dial Before You Dig utility locations if required - and emergency preparedness: muster point, first aid, emergency contacts. Then crew input: the crew confirms potential hazards and flags what the AI may miss. Human-in-the-loop is not a concession to the standard; it is clause 7.3 - competence and awareness - working as designed.

Stage 2 - DO: Capture and assess the workspace

A baseline capture - a photograph of the job site taken from within RAIDSafe, and additional angles where the risk hides. Assessment tasks are generated automatically for the space actually photographed. The crew reviews the hazards RAIDSafe identifies as potential risks, checks the recommendations, and checks policy and business rules. Revised recommendations and corrective actions are applied straight back onto the workspace. High or Critical risks that cannot be immediately addressed are raised as issues - owned, not parked.

Stage 3 - CHECK: Is it safe to commence work?

A revised capture snaps the addressed state of the workspace, and the addressed state is re-assessed. This is where RAIDSafe's dynamic risk history and risk aggregation operate: excavation, wet weather and a live cable are one hazard, not three. Recommendations and business rules are re-checked against the new state. The inherent risk score falls to residual as controls are applied - the moment that matters, with the evidence staying on the record. Go/No-Go criteria and stop-work authority are determined before sign-off, not after. The RAIDSafe procedure is signed off, and the crew is instructed on the safety controls and measures before work activity begins.

Stage 4 - ACT: Commence work and monitor controls

Work proceeds under the agreed controls while RAIDSafe continuously monitors the workplace situation for change triggers >> weather turns, new contractor arrives, scope shifts, an unplanned hazard appears. If the scope of the job changes, the loop cycles back to Plan. No shortcuts, no drift.

Verification & Validation - the loop's improvement engine

Wrapping the loop is the V&V layer. Verification: hazard containment and risk mitigation monitored at regular intervals - or end of day on carry-over. Validation: did we do what we said we were going to do? At completion of the day or the job, the RAID Situation Register takes the day's learnings - risks and how they were actually managed, assumptions and whether they held, issues raised, owned and resolved, and dependencies nobody had considered: better data, other systems, weather. In ISO 55001 terms, this is clause 9 (performance evaluation) and clause 10 (improvement) executed at job tempo. The standard's Act is improvement; RAIDSafe's V&V layer is where that improvement happens. Every job makes the system smarter. That is the Act of the loop.

Six Capability Modules Mapped to ISO 55001

Risk Aggregation Intelligence: AI combines multiple risk indicators (operational, environmental, asset condition, crew capability) into a single dynamic risk profile that updates as conditions change. Not a static matrix; a living assessment. ISO 55001-2024: Clause 6.1 (planning), 8.1 (operational planning and control)
Assumption Validation Engine: Critical assumptions are scheduled for validation, tracked against current conditions, and flagged for decay. When an assumption crosses the validation threshold, it triggers automatic reassessment and escalation. ISO 55001-2024: Clause 9.1 (monitoring, measurement, analysis, evaluation)
Issue Escalation and Tracking: Issues are captured, classified, and tracked against automatic escalation rules. Patterns are detected across issues. Twenty-seven methane exceedances would trigger an escalation before the twenty-eighth. Two years of weather damage would trigger a structural assessment before a repair attempt. ISO 55001-2024: Clause 8.1, 10.2 (nonconformity and corrective action)
Dependency Mapping and Monitoring: Critical dependencies between systems, processes, and teams are mapped as integrated chains. Each connection has an owner. When one link in the chain changes, the entire dependency is reassessed. ISO 55001-2024: Clause 6.1, 8.1
Governance Intelligence Dashboard: Real-time governance performance by operation, contractor, asset type, and portfolio. Principal visibility into contractor governance behaviour. Trend analysis across all four RAID pillars. ISO 55001-2024: Clause 9.3 (management review) with live field evidence
Investigation Pattern Learning: Structured capture of investigation findings as governance patterns. Lessons from Callide C, Grosvenor, Dreamworld, and North Goonyella are codified into the system's decision architecture. The platform learns from every investigation so that the same pattern does not repeat. ISO 55001-2024: Clause 10.3 (continual improvement)

Value Proposition

Diriger's RAIDSafe's alignment to ISO Standards is no accident; both RAID and PDCA are often-used constructs of the ISO 55000 Asset Management framework.

Standards Alignment Made Evident: ISO 55001 alignment moves from an annual assertion to a daily, demonstrable practice - with the evidence trail produced by the work itself.
Regulatory and Insurance Alignment: contemporaneous, timestamped evidence of dynamic risk assessment, assumption validation and issue escalation - the documented information the 2024 revision expects, in the format auditors and regulators actually ask for.
Audit Preparation Liberated: the evidence trail for management review and certification audits accumulates as a by-product of field work, not as a annual documentation sprint.
Productivity Liberation: replace manual governance administration - register updates, assumption reviews, issue tracking - with AI-assisted workflows, recovering 15-20% of safety governance capacity for operational decision-making.
Knowledge Retention and Transfer: the governance patterns, risk indicators and decision heuristics of experienced safety leaders are captured into a system that improves with every assessment.
Patterns Surfaced: across every investigation, near-miss, and operational change - the failures the Pattern of Failure analysis found are the patterns a live loop is designed to catch before the threshold is crossed.

TAKING ACTION:

"This is NOT a 3-Year Governance Transformation"

- RAIDSafe meets you where you are and scales with your internal capability.
- The loop starts on the first job: capture, assess, decide, work, verify, learn.
- The evidence trail for ISO 55001 alignment accumulates from day one.
- The cost of one catastrophic failure - in fines, shutdown, reputation and lives - typically funds the initiative for a decade.
- The question is not whether your asset management plan references ISO 55000. It is whether your field loop turns - daily, with evidence.

“A management review tells you what happened last year. RAIDSafe tells you what is happening on this job ... Right Now ... with the Crew's hands on the pen”

DIRIGER / RAIDSAFE GOVERNANCE TOOL

10-Rule RAID Governance Maturity Scorecard

A 45-minute diagnostic workshop tool. Gather evidence. Be honest. Score each rule. Map RED rules to capability layers. Re-run quarterly.

How to use this scorecard ....

1. Assemble your safety, operations, and governance teams (4-8 people).

2. For each rule, present evidence not opinion. If you cannot prove it, it is RED.

3. Score: YES = GREEN, NO = RED, N/A = AMBER (mark for future review).

4. Map all RED rules to Diriger capability layers for a targeted remediation roadmap.

5. Re-run quarterly to track maturity progression.

The Scorecard Questions

1. Does every field job plan trace to an asset management objective (clause 6.2) - and can you show the connection in the work order?

2. Is a photograph of the actual workspace captured before and after controls are applied - not a form completed from the car park?

3. Is residual risk scored after controls are applied, with the inherent-to-residual movement on the record?

4. Are combined scenarios assessed - do excavations, weather and live services get aggregated, or listed separately?

5. Are Go/No-Go criteria and stop-work authority determined before sign-off, not after the incident?

6. Are change triggers defined - weather, contractors, scope - and does a trigger force the job back to Plan?

7. Are verification intervals defined for hazard containment on carry-over work?

8. Is validation - did we do what we said we would do - recorded at end of day or job completion?

9. Does the RAID Situation Register (risks, assumptions, issues, dependencies) feed the next job's planning?

10. Can your management review (clause 9.3) call up field evidence from this morning - not last quarter's sample?

REFERENCES

ISO 55000:2024 - Asset management - Vocabulary, overview and principles (Second edition, July 2024). International Organization for Standardization.
ISO 55001:2024 - Asset management - Asset management system - Requirements (Second edition, 2024). International Organization for Standardization.
ISO 55002:2018 - Asset management - Management systems - Guidelines for the application of ISO 55001. International Organization for Standardization.
ISO 55001:2024 revision analysis - key updates including effectiveness assessment of actions taken. Public certification body and standards commentary, 2024-2025.
Diriger - RAIDSafe: The Pattern of Failure Australian Safety Keeps Finding (Diriger Insights, 2026). Ten Australian investigations analysed against four RAID governance patterns.
Diriger RAID Governance Framework: Adaptive Governance for Asset-Intensive Industries (2024-2026).
Diriger RAIDSafe Platform Architecture and Capability Specification (2026).

DISCLAIMER
This insight describes an alignment between the RAIDSafe usage model and the PDCA structure of the ISO 55000 family of standards. It does not assert certification, compliance or endorsement by the International Organization for Standardization or any certification body, and it does not assert that any specific software product would have prevented the incidents referenced in the companion Pattern of Failure insight. Not legal, safety engineering or certification advice. Respects the victims and their families.