Content Comparison

...

• A trigger: drawn from the shared trigger catalogue

• A rationale object: structured and detailed, replacing simple references

• One or more affected domains: such as policy, initiatives, or capabilities

• Impacted organisational units: using defined role types

• Response actions: steps taken or planned

• Expected outcomes: anticipated benefits or changes in performance

Rationale object

Each response includes a rationale object that captures the justification for action. It replaces previous references to rationaleId and allows richer traceability and reasoning. See Rationales

...

Field

...

Description

...

rationaleTitle

...

A short name for the rationale

...

description

...

A detailed explanation of the reasoning behind the response

...

driverType

...

Categorises the driver (e.g. Regulatory, Risk, Market, Insight)

...

sourceDocument

...

Reference to the originating insight, regulation, or analysis

...

relatedKPIs

...

KPIs that the response is intended to influence or improve

...

priorityLevel

...

Trigger catalogue

Responses reference a trigger selected from a standardised catalogue of events, trends, or insights. This ensures consistency in classifying causes of change and enables systemic analysis across responses.

...

Each unit listed includes a description of how it is impacted, ensuring traceability to structure and accountability.

Example

Trigger: Regulation 10.15/F—Mandatory Near Miss Reporting
Rationale:

...

...

{
  "rationaleTitle": "Compliance with Regulation 10.15/F",
  "description": "Federal regulation mandates improved near-miss reporting. The goal is to enable predictive analytics to reduce preventable incidents.",
  "driverType": "Regulatory",
  "sourceDocument": "FRA Bulletin 2025/04",
  "relatedKPIs": ["Near Miss Capture Rate", "Incident Prevention Rate"],
  "priorityLevel": "High"
}

Affected domains: Policy, Capabilities, Performance
Impacted units:

• Track Safety Division – Owning

• Risk & Compliance – Custodian

• Regional Safety Teams – Supported by

Response actions:

• Define new reporting protocols

• Train field inspectors

• Deploy incident management tool enhancements

Expected outcome:

• 80% near-miss reporting coverage within 12 months

• Reduction in preventable incidents by 20% by end of 2026What is a Trigger?

Example: Strategic Response Model Artefact

This section presents a detailed example of a strategic response model, illustrating how a specific trigger—such as the mandated use of AI in compliance reporting—activates relevant strategies, units, capabilities, and initiatives. It demonstrates the practical application of the artefact in real-world organisational strategic responses.

Strategic response model trigger: Mandatory introduction of AI-enabled safety compliance reporting
Strategic drivers:

• Reduce regulatory breach risk

• Improve transparency in safety inspections

Key units:

• Safety Technology Division (owning unit of AI capability)

• Operations (utilising unit for inspection automation)

• Legal & Risk (dependent on compliance datasets)

Capabilities:

• AI-driven compliance reporting (owned by Safety Tech)

• Digital field inspection (provided by Operations)

• Safety data analytics (supported by Risk & Legal)

Services:

• Compliance assurance service

• Safety incident triage

Value streams:

• Rail infrastructure incident response

• Annual compliance certification

Information:

• Real-time safety telemetry

• Historical incident database

Stakeholders:

• Federal Transport Regulator

• Union of Track Workers

Policies:

• Data transparency policy

• AI auditing standards

Performance KPIs:

• % of safety incidents auto-classified

• Mean response time to compliance events

Initiatives:

• AI for Safety Program (current)

• Transparent Audit Framework (proposed)

Relationship with Rationales

...

"driverType": {
"type": "string",
"enum": [
"Regulatory change",
"Customer demand shift",
"Operational risk",
"Technology obsolescence",
"Performance shortfall",
"Cost pressure",
"Workforce change",
"Stakeholder expectation",
"Market opportunity"
],
"description": "High-level driver category that provides the basis for the rationale."

}

Rationale object

Each response includes a rationale object that captures the justification for action. It replaces previous references to rationaleId and allows richer traceability and reasoning. See Rationales

Definition of strategicResponseModel as a composable artefact

This section formalises the strategic response model as composable within the Orthogramic Metamodel. It outlines the attributes required to define a model, including associated triggers, organisational roles, information dependencies, and KPIs, supporting reuse and integration across governance and planning tools.

...