Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

...

The standardized taxonomy also supports governance and auditability by ensuring that triggers are documented according to consistent criteria, making it easier to trace decision-making patterns over time.

Trigger Catalogue

Triggers are classified using the Trigger Catalogue, which defines accepted types of triggers.

The trigger catalogue provides a curated and expanding set of predefined triggers that can be used to initiate strategic responses. Each trigger is tagged to relevant business architecture domains, enabling efficient strategic response planning and alignment across organisational activities.

Each strategic response triggered using this catalogue links back to relevant Orthogramic Metamodel domains—such as capabilities, services, initiatives, and stakeholders—to produce a dynamic view of organisational readiness and response.

Common Trigger Catalogue types include:

...

Regulatory: New or updated legislation or compliance obligations.

...

Performance Insight: Metrics indicating deviation from expected outcomes.

...

Risk: Identified operational, financial, or strategic risks.

...

Opportunity: Market, partnership, or innovation opportunities.

...

Mandate: Governmental or internal directives.

...

.

Linking to Rationales

Triggers can lead to multiple Rationales. Each Rationale references the originating trigger and justifies a different response path. This many-to-one structure allows a single trigger to influence several domains. See: Rationale

...

See: https://github.com/Orthogramic/Orthogramic_Metamodel

Schema properties

Field

Type

Required

Description

Example

triggerID

string (uuid)

Yes

Unique identifier for the trigger

"TRG-EXT-2025-01"

label

string

Yes

Short, human-readable name of the trigger

"New Regulatory Mandate"

description

string

No

Expanded explanation of the trigger's relevance

"Mandate issued by the national regulator requiring compliance with new safety standards"

primaryCategory

string (enum)

Yes

Primary classification of trigger context

"Regulatory_Compliance"

subcategory

string

No

More specific classification within the primary category

"Safety Standards Update"

origin

string (enum)

Yes

Whether the trigger originates from inside or outside the organization

"External"

timeHorizon

string (enum)

No

The temporal nature of the trigger

"Medium_Term"

impactLevel

string (enum)

No

The potential significance of the trigger

"High"

detectionDate

string (date)

No

Date when the trigger was identified

"2025-04-19"

sourceReference

string

No

Reference to source document, report, or authority identifying the trigger

"https://regulator.gov/mandate2025"

relatedTriggers

array of string (uuid)

No

References to other related triggers

["TRG-EXT-2025-02"]

strategicResponseReferences

array of string (uuid)

No

References to related strategicResponseModel artefacts

["SRM-2025-001", "SRM-2025-002"]

...