Table of Contents | ||
---|---|---|
|
...
Structure of the artefact
Section | Description |
---|---|
Scenario Strategic response model trigger | A defined external or internal event. Example: Proposed national safety legislation for hazardous freight. |
Impacted strategic drivers | One or more strategic objectives tagged as relevant to the trigger. |
Key organisation units | Units tagged as responsible, dependent, or impacted based on capability and service roles. |
Affected capabilities | Filtered based on alignment with strategic objectives or dependency relationships. |
Service dependencies | Services required to respond to or deliver the desired outcome of the scenario. |
Value streams engaged | End-to-end business processes likely to be activated or altered. |
Information requirements | Information assets needed to inform decisions or satisfy compliance. |
Stakeholders | Primary stakeholders affected, mapped to expectations, engagement plans, or risks. |
Policies and compliance | Policies that apply or must be created/updated. |
Performance measures | KPIs that will demonstrate scenario readiness or success. |
Initiative/program links | Existing or proposed initiatives addressing the scenario. |
What is a Trigger?
A Trigger is not a standalone structural element of an organisation but an external or internal event, condition, or hypothesis that causes the organisation to:
Mobilise capabilities,
Evaluate policies,
Adjust strategies,
Initiate new initiatives,
Coordinate across services and information flows.
In the Orthogramic Metamodel:
Trigger is a supporting artefact, not a domain.
It is only relevant in the context of a
BusinessScenario
(much like aJustification
supports a Strategy).
Example: Strategic Response Model Artefact
Scenario Strategic response model trigger: Mandatory introduction of AI-enabled safety compliance reporting
Strategic drivers:
...
To support structured scenario development, the Orthogramic Metamodel offers a growing catalogue of predefined triggers. Each trigger can be used to initiate a scenario composite artefact and is tagged with relevant business architecture domains.
Trigger Category | Example Triggers |
Regulatory or compliance | New legislation, compliance audit mandate, data sovereignty changes |
Technological change | AI rollout, cybersecurity breach, platform deprecation |
Environmental & safety | Natural disaster preparedness, climate risk disclosures, workplace injury reform |
Operational transformation | Business process outsourcing, shared services implementation, lean redesign |
Strategic re-alignment | Mergers and acquisitions, board-level strategic pivot, budget realignment |
Customer & stakeholder | Community expectations shift, digital service demand surge, key account loss |
Workforce & skills | Critical skill shortage, union action, remote work policy adoption |
Performance response | KPI threshold breach, repeated incident occurrence, audit fail |
Political or social | Public inquiry, ministerial intervention, social licence erosion |
Innovation-led opportunity | Grant funding availability, pilot program success, ecosystem partnership offer |
...
A canonical BusinessScenario
entity in the Orthogramic Metamodel with the following attributes:
Attribute | Type | Description |
---|---|---|
| UUID | Unique |
strategic response model ID | ||
| Text | Human-readable name of the |
strategic response model | ||
| Text | Summary of the |
strategic response model’s purpose and scope | ||
| Link to | Source event or condition |
| List of | Strategy elements influenced |
| List of | Impacted capabilities |
| List of | Value streams engaged |
| List of | Units with |
strategic response model-specific roles | ||
| List of | Services required or affected |
| List of | Key information entities involved |
| List of | Applicable rules or regulations |
| List of | Stakeholders affected or involved |
| List of | Metrics used to assess |
strategic response model success | ||
| List of | Programs or projects implementing the response |
This format ensures that the scenario definition is:
Declarative (not procedural or UI-specific),
Traceable (everything points to reusable metamodel entities),
Reusable (across tools, audits, planning activities).
Strategic Response Model JSON Schema
{
"$schema": "http://json-schema.org/draft/2020-12/schema",
"$id": "https://orthogramic.org/schema/business-scenario.json",
"title": "BusinessScenario",
"type": "object",
"required": ["id", "title", "trigger"],
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "Unique identifier for the Strategic Response Model"
},
"title": {
"type": "string",
"description": "Short name for the scenario"
},
"description": {
"type": "string",
"description": "Narrative summary of the scenario purpose and context"
},
"trigger": {
"$ref": "https://orthogramic.org/schema/trigger.json",
"description": "Trigger event or condition linked to this scenario"
},
"relatedDrivers": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Strategic drivers impacted by the scenario"
},
"affectedCapabilities": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Capabilities involved or stressed by the scenario"
},
"relatedValueStreams": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Value streams that must operate under the scenario"
},
"impactedUnits": {
"type": "array",
"items": {
"type": "object",
"required": ["unitId", "role"],
"properties": {
"unitId": {
"type": "string",
"format": "uuid"
},
"role": {
"type": "string",
"enum": [
"Owning unit",
"Utilising unit",
"Providing unit",
"Consuming unit",
"Custodian unit",
"Dependent unit",
"Supported unit"
]
}
}
},
"description": "Organisation units involved and their scenario-specific roles"
},
"servicesInScope": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Services affected, needed, or transformed by the scenario"
},
"dataDependencies": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Information assets or datasets involved"
},
"policiesInScope": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Policies that govern the scenario or require updating"
},
"stakeholders": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Stakeholders directly impacted or involved"
},
"kpis": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Performance metrics to track scenario success or readiness"
},
"linkedInitiatives": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Projects or programs that respond to the scenario"
}
}
}
...
Introducing a standalone Trigger
domain in the Orthogramic Metamodel with:
Attribute | Type | Description |
---|---|---|
| UUID | Unique ID |
| Text | Short name (e.g. “Cybersecurity Incident”) |
| Enum | From defined set (e.g. Technological, Regulatory, etc.) |
| Text | Explanation of why this trigger matters |
| List of | Optional reverse reference |
Trigger JSON Schema
{
"$schema": "http://json-schema.org/draft/2020-12/schema",
"$id": "https://orthogramic.org/schema/trigger.json",
"title": "Trigger",
"type": "object",
"required": ["id", "label", "category"],
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "Unique identifier for the trigger"
},
"label": {
"type": "string",
"description": "Short, human-readable name of the trigger"
},
"category": {
"type": "string",
"enum": [
"Regulatory or compliance",
"Technological change",
"Environmental & safety",
"Operational transformation",
"Strategic re-alignment",
"Customer & stakeholder",
"Workforce & skills",
"Performance response",
"Political or social",
"Innovation-led opportunity"
],
"description": "Classification of trigger context"
},
"description": {
"type": "string",
"description": "Expanded explanation of the trigger’s relevance"
},
"exampleScenarios": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Optional references to related BusinessScenario artefacts"
}
}
}