Skip to main content

Domain Attributes Summary

This page provides a quick reference for the core attributes of the 24 Triodian Metamodel domains. Use it as a lookup when modeling or implementing integrations; each domain page documents the full attribute set.

How to Use This Reference​

Each domain section lists:

  • Core Attributes — The record's identifier, every required attribute (✓ in the Required column) and the main optional attributes, with names, types and descriptions taken from the domain's schema
  • Key Enumerations — The values the schema allows for selected categorical attributes, in camelCase. Many come from the shared lists in common.schema.json, such as maturityLevel, frequency, timeHorizon and the four-point low, medium, high, critical scale
  • Element types — Named element records under the schema's definitions, where the domain has them
  • Primary Relationships — Typical cross-domain relationships, using the 37 relationship types of cross-domain-relationship.schema.json. Relationships run from source to target; Information, Performance, Product and Service never act as the source

Every record rejects fields its schema does not define ("additionalProperties": false), so attribute names must be spelt exactly as shown.

Core Domains​

Organization​

Schema: organization.schema.json · Identifier: organizationID · Domain page

AttributeTypeRequiredDescription
organizationIDString✓Unique identifier for the Organization
orgTitleString✓The name or title of the Organization
orgTypeEnum✓Type of organization
countryString✓The country where the organization is headquartered or primarily operates
descriptionString✓A detailed explanation of what the Organization entails
legalStructureEnum✓The legal structure of the Organization
legalNameStringFormal legal name of the organization
structureTypeEnumType of organizational structure
geographicScopeEnumGeographic scope of operations
missionStatementStringThe mission of the Organization
organizationUnitsArray[Object]Sub-organization units within this organization

Enumerations:

  • structureType: 20 values, including functional, divisional, matrix, hierarchical, flatHorizontal, regional …
  • geographicScope: local, regional, national, multinational, continental, global, crossBorder, virtual, regionalBloc, emergingMarkets, developedMarkets, asiaPacific, europeMiddleEastAfrica, americas

Organization Unit (organizationUnit)​

AttributeTypeRequiredDescription
orgUnitIDString✓Unique identifier for the organization unit
orgUnitTitleString✓The name or title of the Organization unit
descriptionString✓A detailed explanation of what the Organization unit entails
purposeString✓The intended purpose or function of the Organization unit within the Organization
ownerString✓The individual or team responsible for the Organization unit
higherOrganizationUnitStringThe Organization or Organization unit above in the Organization hierarchy
parentOrgUnitIDStringID of the organization unit directly above this one (omit for a top-level unit)
subOrganizationUnitsArray[String]Sub-Organization units directly below this Organization unit
subOrgUnitIDsArray[String]IDs of the organization units directly below this one
rolesStringSpecific roles within the Organization unit

Primary Relationships: Organization accountableFor Capabilities; Organization delivers Services; Organization implements Initiatives


Stakeholder​

Schema: stakeholder.schema.json · Identifier: stakeholderID · Domain page

AttributeTypeRequiredDescription
stakeholderIDString✓Unique identifier for the Stakeholder
titleString✓Name/title of stakeholder
tTypeEnum✓Position relation to organization
descriptionString✓Detailed explanation
roleStringResponsibilities and interests
orgUnitTitleStringMost closely linked org unit
orgUnitIDStringID of the organization unit (see orgUnitTitle)
stakeholderCategoryEnumBroad stakeholder classification
influenceLevelEnumDegree of influence on organization
interestLevelEnumLevel of interest in organization
engagementFrequencyEnumHow often engagement occurs
relatedStakeholderIDsArray[String]IDs of related Stakeholders
stakeholderRequirementsArray[Object]Specific requirements from stakeholder

Enumerations:

  • influenceLevel: highInfluence, mediumInfluence, lowInfluence
  • interestLevel: highInterest, mediumInterest, lowInterest
  • engagementFrequency: continuous, realTime, hourly, daily, weekly, monthly, quarterly, semiAnnually, annually, eventDriven, onDemand, adHoc

Element types: stakeholderRequirement (identified by requirementID; requires title, description, purpose; its riskLevel uses the four-point scale low, medium, high, critical)

Primary Relationships: Stakeholder accountableFor Capabilities; Stakeholder responsibleFor Information; Stakeholder informs Strategy


Capabilities​

Schema: capability.schema.json · Identifier: capabilityID · Domain page

AttributeTypeRequiredDescription
capabilityIDString✓Unique identifier for the Capability
titleString✓The name or title of the Capability
descriptionString✓A detailed explanation of what the Capability entails
purposeString✓The intended purpose or function within the Organization
ownerString✓The individual or team responsible for the Capability
orgUnitTitleStringThe organization unit(s) to which the Capability is linked
orgUnitIDStringID of the organization unit (see orgUnitTitle)
capabilityCategoryEnumBroad categorization of capability type
maturityLevelEnumCurrent maturity level of the Capability
targetMaturityLevelEnumDesired future maturity level
criticalityEnumBusiness criticality level
parentStringHigh-level Capability that encompasses this capability
parentCapabilityIDStringID of the higher-level Capability that encompasses this one
childCapabilityIDsArray[String]IDs of the Capabilities that fall under this one
relatedCapabilityIDsArray[String]IDs of related Capabilities

Enumerations:

  • capabilityCategory: coreBusiness, supporting, enabling, strategic, foundational, distinctive
  • maturityLevel: initial, repeatable, defined, managed, optimizing
  • criticality: low, medium, high, critical

Element types: capabilityFunction, capabilityComponent, capabilityProcess (listed in capabilityFunctions, capabilityComponents, capabilityProcesses)

Primary Relationships: Capability enables Value Stream; Capability depends on Technology; Organization accountableFor Capability


Value Stream​

Schema: value-stream.schema.json · Identifier: valueStreamID · Domain page

AttributeTypeRequiredDescription
valueStreamIDString✓Unique identifier for the Value Stream
titleStringThe name or title of the Value Stream
descriptionStringA detailed explanation of what the Value Stream entails
purposeStringThe intended purpose or function of the Value Stream within the Organization
ownerStringThe individual or team responsible for the Value Stream
orgUnitTitleStringThe Organization unit(s) to which the Value Stream is linked
orgUnitIDStringID of the organization unit (see orgUnitTitle)
maturityLevelEnumThe current maturity level of the Value Stream
relatedValueStreamIDsArray[String]IDs of related Value Streams

Enumerations:

  • maturityLevel: initial, repeatable, defined, managed, optimizing

Value Stream Stage (valueStreamStage)​

AttributeTypeRequiredDescription
stageIDString✓Unique identifier for the Value Stream stage
stageTitleStringName/title of the Value Stream stage
parentValueStreamStringThe Value Stream it belongs to
parentValueStreamIDStringID of the Value Stream this stage belongs to
descriptionStringWhat the stage entails
valueItemsStringSpecific outputs or benefits generated in the stage
enablingCapabilityStringCapability that enables this stage
enablingCapabilityIDStringID of the Capability that enables this stage
inputsStringRequired resources/information
outputsStringDeliverables/results produced

Primary Relationships: Capability enables Value Stream; Value Stream delivers to Stakeholder; Value Stream informs Performance


Information​

Schema: information.schema.json · Identifier: informationID · Domain page

AttributeTypeRequiredDescription
informationIDString✓Unique identifier for the Information asset
titleString✓The name or title of the Information asset
descriptionString✓A detailed explanation of what the Information asset contains
purposeString✓The intended purpose or function within the Organization
ownerString✓The individual or team responsible for the Information asset
orgUnitTitleStringThe organization unit(s) to which the Information asset is linked
orgUnitIDStringID of the organization unit (see orgUnitTitle)
informationCategoryEnumBroad categorization of information type
informationTypeEnumSpecific type of information
dataClassificationEnumSecurity and sensitivity classification
dataOwnerStringParty accountable for the information asset
dataStewardStringParty responsible for the quality and governance of the information
updateFrequencyEnumHow often the information is updated
informationElementsArray[Object]Specific components or structures within the information asset

Enumerations:

  • informationType: database, dataset, report, document, knowledgeBase, apiData, realTimeStream, archive, model, dashboard
  • dataClassification: public, internal, confidential, restricted, topSecret

Element types: informationElement (requires title, description, purpose)

Primary Relationships: Information is passive: it receives relationships but never initiates them. Policy governs Information; Stakeholder responsibleFor Information; Capability consumes Information


Strategy​

Schema: strategy.schema.json · Identifier: strategyID · Domain page

AttributeTypeRequiredDescription
strategyIDString✓Unique identifier for the Strategy
titleString✓Name/title of strategy
descriptionString✓Detailed explanation
purposeString✓Intended function
ownerString✓Responsible individual/team
orgUnitTitleStringMost closely linked organizational units
orgUnitIDStringID of the organization unit (see orgUnitTitle)
strategyCategoryEnumBroad categorization of strategy type
strategyTypeEnumSpecific type of strategy
timeHorizonEnumStrategy time frame
marketPositionEnumDesired market position
parentStrategyIDStringID of the parent Strategy
relatedStrategyIDsArray[String]IDs of related Strategies
strategyObjectivesArray[Object]Specific objectives supporting the strategy

Enumerations:

  • timeHorizon: immediate, shortTerm, mediumTerm, longTerm, extended
  • marketPosition: marketLeader, marketChallenger, marketFollower, nichePlayer, disruptor, emergingPlayer, defensivePositioning

Element types: strategyObjective (identified by objectiveID; requires title, description, purpose, owner)

Primary Relationships: Strategy drives Initiatives; Strategy prioritizes Capabilities; Strategy informs Performance


Performance​

Schema: performance.schema.json · Identifier: performanceID · Domain page

AttributeTypeRequiredDescription
performanceIDString✓Unique identifier for the performance metric
titleString✓The name or title of the performance metric
descriptionString✓A detailed explanation of what the performance metric entails
purposeString✓The intended purpose or function of the performance metric within the Organization
ownerString✓The individual or team responsible for the performance metric
orgUnitTitleStringThe Organization unit(s) to which the performance metric is linked
orgUnitIDStringID of the organization unit (see orgUnitTitle)
performanceCategoryEnumBroad categorization of performance type
performanceTypeEnumSpecific type of performance metric
metricClassEnumClassification of metric characteristics
frequencyEnumHow often the performance metric is measured and reported
automationEnumLevel of automation in data collection and processing
performanceKPIsArray[Object]Key Performance Indicators

Enumerations:

  • frequency: continuous, realTime, hourly, daily, weekly, monthly, quarterly, semiAnnually, annually, eventDriven, onDemand, adHoc
  • automation: manual, semiAutomated, highlyAutomated, fullyAutomated, aiEnabled

Element types: performanceKPI (listed in performanceKPIs; requires title, description, purpose, owner)

Primary Relationships: Performance is passive: it receives relationships but never initiates them. Strategy informs Performance; Value Stream informs Performance; Finance reports Performance


Initiatives​

Schema: initiative.schema.json · Identifier: initiativeID · Domain page

AttributeTypeRequiredDescription
initiativeIDString✓Unique identifier for the Initiative
titleStringThe name or title of the Initiative
descriptionStringA detailed explanation of what the Initiative entails
purposeStringThe intended purpose or function of the Initiative within the Organization
scopeStringThe range or extent of the initiative
statusEnumCurrent progress state of the initiative
ownerStringThe individual or team responsible for the Initiative
orgUnitTitleStringThe Organization unit(s) to which the Initiative is linked
orgUnitIDStringID of the organization unit (see orgUnitTitle)
relatedStrategyIDsArray[String]IDs of the Strategies this Initiative aligns with
childProgramIDsArray[String]IDs of the Programs that are part of this Initiative

Enumerations:

  • status: proposed, planned, approved, inProgress, onHold, deferred, completed, cancelled

Element types: program (identified by programID, linked by parentInitiativeID) and project (identified by projectID, linked by parentProgramID)

Primary Relationships: Strategy drives Initiatives; Initiative transforms Capabilities; Finance funds Initiatives


Products​

Schema: product.schema.json · Identifier: productID · Domain page

AttributeTypeRequiredDescription
productIDString✓Unique identifier for the Product
titleString✓The name or title of the Product
descriptionString✓A detailed explanation of what the Product entails
purposeString✓The intended purpose or function of the Product within the Organization
ownerString✓The individual or team responsible for the Product
orgUnitTitleStringThe Organization unit(s) to which the Product is linked
orgUnitIDStringID of the organization unit (see orgUnitTitle)
productCategoryEnumBroad categorization of product type
productTypeEnumSpecific type of product
targetMarketEnumPrimary market or customer segment
lifecycleStageEnumCurrent stage in the product lifecycle
pricingStrategyEnumPricing approach
customerSegmentsArray[Enum]Types of customer the product targets
customerSegmentIDsArray[String]IDs of the customer segments the product targets (see the Customer domain)
productFeaturesArray[Object]Specific features of the product

Enumerations:

  • targetMarket: internal, external, b2b, b2c, b2g, b2e, partner, developer
  • lifecycleStage: 15 values, including ideation, planning, design, development, implementation, launch …

Element types: productFeature (listed in productFeatures; requires title, description, purpose)

Primary Relationships: Products are passive: they receive relationships but never initiate them. Capability enables Product; Market drives Product; Customer consumes Product


Services​

Schema: service.schema.json · Identifier: serviceID · Domain page

AttributeTypeRequiredDescription
serviceIDString✓Unique identifier for the Service
titleString✓The name or title of the Service
descriptionString✓A detailed explanation of what the Service entails
purposeString✓The intended purpose or benefit of the Service
ownerString✓The individual or team responsible for the Service
orgUnitTitleStringThe Organization unit the Service belongs to
orgUnitIDStringID of the organization unit (see orgUnitTitle)
serviceCategoryEnumBroad categorization of service type
serviceTypeEnumSpecific type of service
deliveryModelEnumHow the service is delivered
serviceLevelEnumService tier or quality level
channelsArray[Enum]The channels through which the Service is provided
automationLevelEnumDegree of automation in service delivery
parentServiceIDStringID of the parent Service this is derived from
serviceFeaturesArray[Object]Specific features or components of the Service

Enumerations:

  • deliveryModel: selfService, assistedService, automatedService, onDemand, scheduled, continuous, hybrid
  • serviceLevel: basic, standard, premium, enterprise, missionCritical
  • automationLevel: manual, semiAutomated, highlyAutomated, fullyAutomated, aiEnabled

Element types: serviceFeature (listed in serviceFeatures; requires title, description, purpose)

Primary Relationships: Services are passive: they receive relationships but never initiate them. Capability enables Service; Customer consumes Service; Channel enables Service


Policy​

Schema: policy.schema.json · Identifier: policyID · Domain page

AttributeTypeRequiredDescription
policyIDString✓Unique identifier for the Policy
titleStringThe name or title of the Policy
descriptionStringA detailed explanation of what the Policy entails
purposeStringThe intended purpose or function of the Policy within the Organization
scopeStringThe range or extent to which the policy applies
enforcedByStringParty responsible for enforcing the policy
ownerStringThe individual or team responsible for the Policy
orgUnitTitleStringThe Organization unit(s) to which the Policy is linked
orgUnitIDStringID of the organization unit (see orgUnitTitle)
requirementsStringSpecific conditions or criteria to be met under the Policy
complianceMetricsStringMeasures to ensure adherence to policies
reviewFrequencyStringHow often the Policy is reviewed and updated
relatedPolicyIDsArray[String]IDs of related Policies

Primary Relationships: Policy governs Information; Policy constrains Capabilities; Policy mitigates Risk


Extended Domains​

Customer​

Schema: customer.schema.json · Identifier: customerID · Domain page

AttributeTypeRequiredDescription
customerIDString✓Unique identifier for the customer element
titleString✓The name or title of the customer segment or persona
descriptionString✓A detailed explanation of the customer segment's characteristics
orgUnitTitleString✓The organization unit(s) responsible for this customer segment
orgUnitIDStringID of the organization unit (see orgUnitTitle)
customerSegmentTypeEnumClassification of segment (e.g., demographic, behavioral, value-based)
customerNeedsArray[String]Primary needs, wants, and pain points addressed
customerLifecycleStageEnumCurrent position in the customer journey
customerLifetimeValueObjectExpected or measured value of this customer type
crossDomainRelationshipsArray[Object]Directional relationships from this record to entities in other domains

Enumerations:

  • customerSegmentType: demographic, behavioral, valueBased, needsBased, lifecycle, industry, geographic, psychographic, technographic, other
  • customerLifecycleStage: awareness, consideration, purchase, onboarding, usage, growth, retention, advocacy, winBack, other

Element types: customerPersona (personaID), customerJourney (journeyID) and customerRelationship (relationshipID), each linked to the segment by customerSegmentID

Primary Relationships: Customer consumes Products; Customer consumes Services; Customer drives Value Stream


Market​

Schema: market.schema.json · Identifier: marketID · Domain page

AttributeTypeRequiredDescription
marketIDString✓Unique identifier for the market element
titleString✓Name or title of the market or competitive landscape
descriptionString✓Detailed explanation of the market environment
orgUnitTitleString✓Organization unit responsible for market intelligence
marketDefinitionStringDefinition of market boundaries and characteristics
orgUnitIDStringID of the organization unit (see orgUnitTitle)
marketSizeObjectCurrent and projected market dimensions
marketGrowthRateObjectRate of market expansion or contraction
marketTrendsArray[String]Emerging patterns and directional shifts (see the marketTrend element for detail)
competitiveIntensityObjectLevel of competition in the market
relatedMarketsArray[Object]Other markets with relationships to this one

Element types: competitivePosition (positionID), marketTrend (trendID) and industryAnalysis (industryID); competitive positions and trends reference a market by marketID

Primary Relationships: Market drives Strategy; Market drives Products; Market informs Customer


Finance​

Schema: finance.schema.json · Identifier: financeID · Domain page

AttributeTypeRequiredDescription
financeIDString✓Unique identifier for the finance element
titleString✓Name or title of the financial structure or element
descriptionString✓Detailed explanation of the financial element
orgUnitTitleString✓Organization unit responsible for financial management
financeDefinitionStringDefinition of financial boundaries and characteristics
orgUnitIDStringID of the organization unit (see orgUnitTitle)
totalValueObjectCurrent and projected financial dimensions
accountingTreatmentEnumHow the element is treated in accounting systems
fiscalPeriodObjectTime period for financial management
riskProfileObjectRisk characteristics of the financial element

Enumerations:

  • accountingTreatment: capital, operating, mixed, offBalanceSheet

Element types: financialResource (resourceID), budget (budgetID), investment (investmentID), revenueStream (streamID) and costStructure (costStructureID)

Primary Relationships: Finance funds Initiatives; Finance measures Capabilities; Finance reports Products


Risk Management​

Schema: risk-management.schema.json · Identifier: riskID · Domain page

AttributeTypeRequiredDescription
riskIDString✓Unique identifier for the risk element
titleString✓The name or title of the risk
descriptionString✓A detailed explanation of the risk
orgUnitTitleString✓The organization unit(s) responsible for managing this risk
riskCategoryEnumClassification of risk type
orgUnitIDStringID of the organization unit (see orgUnitTitle)
riskSourceEnumOrigin of the risk
riskOwnerStringIndividual or role responsible for risk management
riskProbabilityObjectLikelihood of risk occurrence
riskImpactObjectPotential effect if risk is realized
riskSeverityObjectCombined measure of probability and impact
riskStatusEnumCurrent status in management lifecycle
reviewFrequencyEnumHow often risk is reassessed
controlsArray[Object]Risk controls implemented

Enumerations:

  • riskCategory: 21 values, including strategic, operational, financial, market, economic, political …
  • riskSource: internal, external, hybrid
  • riskStatus: identified, assessed, accepted, mitigated, transferred, avoided, realized, closed

Primary Relationships: Policy mitigates Risk; Risk constrains Capabilities; Risk informs Strategy


Technology​

Schema: technology.schema.json · Identifier: technologyID · Domain page

AttributeTypeRequiredDescription
technologyIDString✓Unique identifier for the technology element
titleString✓The name or title of the technology component or service
descriptionString✓A detailed explanation of the technology element
orgUnitTitleString✓The IT or technology organization unit responsible for this component
technologyTypeEnumClassification of technology (e.g., application, infrastructure, service, standard)
orgUnitIDStringID of the organization unit (see orgUnitTitle)
technologyLayerEnumPosition in the technology stack
currentStateEnumStatus of the technology element
lifecycleEnumCurrent lifecycle stage
vendorsArray[String]External vendors/partners involved
securityClassificationEnumSecurity requirements rating
applicationComponentsArray[Object]Application components that are part of this technology

Enumerations:

  • technologyLayer: presentation, application, data, integration, infrastructure, security, management, crossCutting, other
  • lifecycle: emerging, growth, mature, declining, legacy, sunset
  • securityClassification: low, medium, high, critical

Element types: applicationComponent, technologyService, infrastructureElement, standardElement

Primary Relationships: Technology enables Capabilities; Technology enables Services; Technology maintains Information


Supply Chain​

Schema: supply-chain.schema.json · Identifier: supplyChainID · Domain page

AttributeTypeRequiredDescription
supplyChainIDString✓Unique identifier for the supply chain element
titleString✓The name or title of the supply chain element
descriptionString✓A detailed explanation of the supply chain element
supplyChainCategoryEnum✓Classification within supply network
orgUnitTitleString✓The organization unit(s) responsible for this supply chain element
orgUnitIDStringID of the organization unit (see orgUnitTitle)
supplyChainScopeEnumOrganizational scope covered by this supply chain element
leadTimeObjectTime required for fulfillment
flexibilityRatingObjectAdaptability to change
resilienceRatingObjectAbility to withstand disruption
riskProfileObjectSupply chain risk characteristics

Enumerations:

  • supplyChainCategory: manufacturing, distribution, retail, service, digital, project, spareParts, aftermarket, reverse, other
  • supplyChainScope: enterprise, businessUnit, productLine, facility, regional, global, project, other

Element types: supplierNetwork, supplyChainProcess, logisticsNetwork, inventoryManagement

Primary Relationships: Supply Chain enables Products; Supply Chain enables Manufacturing; Supply Chain informs Risk


People​

Schema: people.schema.json · Identifier: peopleID · Domain page

AttributeTypeRequiredDescription
peopleIDString✓Unique identifier for the people element
titleString✓The name or title of the people element
descriptionString✓A detailed explanation of what the people element entails
talentCategoryEnum✓Classification of people element type
orgUnitTitleString✓The organization unit responsible for this people element
orgUnitIDStringID of the organization unit (see orgUnitTitle)
workforceSizeObjectQuantitative metrics about the workforce
skillsProfileObjectSkills and competencies represented
culturalValuesArray[String]Core values represented
leadershipModelObjectLeadership approach
workforceElementsArray[Object]Workforce segments within this people domain
competencyFrameworksArray[Object]Competency frameworks within this people domain

Enumerations:

  • talentCategory: technical, leadership, administrative, operational, creative, analytical, customerFacing, crossFunctional

Element types: workforceElement (workforceID), cultureElement (cultureID), competencyFramework (frameworkID), knowledgeAsset (knowledgeID)

Primary Relationships: People enables Capabilities; People implements Initiatives; People delivers Services


Channel​

Schema: channel.schema.json · Identifier: channelID · Domain page

AttributeTypeRequiredDescription
channelIDString✓Unique identifier for the channel element
titleString✓The name or title of the channel
descriptionString✓A detailed explanation of the channel
channelTypeEnum✓Classification of channel approach
orgUnitTitleStringThe organization unit responsible for this channel
orgUnitIDStringID of the organization unit (see orgUnitTitle)
channelReachObjectGeographic and market coverage
customerSegmentsServedArray[String]Target customers for this channel
channelCostObjectCost structure of the channel
channelPerformanceObjectSuccess metrics for the channel
channelPartnersArray[Object]External partners involved in channel

Enumerations:

  • channelType: direct, indirect, digital, physical, hybrid, omnichannel

Primary Relationships: Channel enables Products; Channel enables Services; Channel delivers to Customer


Innovation​

Schema: innovation.schema.json · Identifier: innovationID · Domain page

AttributeTypeRequiredDescription
innovationIDString✓Unique identifier for the innovation element
titleString✓The name or title of the innovation
descriptionString✓A detailed explanation of what the innovation entails
innovationTypeEnum✓Classification of innovation approach
orgUnitTitleString✓The organization unit responsible for this innovation
innovationStageEnum✓Current development phase of the innovation
innovationOwnerString✓Individual or role responsible for the innovation
orgUnitIDStringID of the organization unit (see orgUnitTitle)
innovationScopeEnumOrganizational breadth of the innovation
investmentLevelObjectResources committed to the innovation
expectedOutcomesArray[Object]Anticipated results from the innovation
strategicHorizonEnumStrategic timeframe category
innovationBarriersArray[Object]Obstacles to innovation success
innovationEnablersArray[Object]Factors that support innovation success

Enumerations:

  • innovationType: product, service, process, businessModel, organizational, market, technology, customerExperience, supplyChain, financial, other
  • innovationStage: ideation, discovery, prototyping, validation, piloting, scaling, established, declining, discontinued
  • strategicHorizon: horizon1, horizon2, horizon3

Primary Relationships: Innovation evolves Capabilities; Innovation innovates Products; Technology enables Innovation


Sustainability​

Schema: sustainability.schema.json · Identifier: sustainabilityID · Domain page

AttributeTypeRequiredDescription
sustainabilityIDString✓Unique identifier for the sustainability element
titleString✓The name or title of the sustainability element
descriptionString✓A detailed explanation of the sustainability element
sustainabilityCategoryEnum✓Classification of sustainability type
orgUnitTitleString✓The organization unit responsible for this sustainability element
orgUnitIDStringID of the organization unit (see orgUnitTitle)
sustainabilityScopeEnumOrganizational scope covered by this sustainability element
currentPerformanceObjectPresent state of sustainability performance
targetPerformanceObjectDesired state of sustainability performance
reportingFrameworkObjectReporting methodology for sustainability
implementationStatusEnumCurrent status of implementation

Enumerations:

  • sustainabilityCategory: environmental, social, governance, integrated
  • sustainabilityScope: enterprise, businessUnit, productLine, project, location, function

Element types: environmentalImpact, socialResponsibility, governancePractice, sustainabilityStrategy

Primary Relationships: Sustainability aligns Strategy; Sustainability informs Performance; Policy governs Sustainability


Intelligence​

Schema: intelligence.schema.json · Identifier: intelligenceID · Domain page

AttributeTypeRequiredDescription
intelligenceIDString✓Unique identifier for the intelligence record
titleString✓Name of the intelligence product or activity
intelligenceTypeEnum✓Type of intelligence gathered
descriptionStringDetailed description of the intelligence
purposeStringPurpose of the intelligence activity
ownerStringPerson or team responsible for the intelligence
orgUnitTitleStringOrganizational unit responsible or consuming the intelligence
orgUnitIDStringID of the organization unit (see orgUnitTitle)
sourcesArray[Object]List of sources used for intelligence gathering
frequencyEnumFrequency of intelligence reporting or updates
confidentialityLevelEnumLevel of confidentiality applied to the intelligence output
applicationsArray[Object]Applications and outcomes linked to the intelligence activity

Enumerations:

  • intelligenceType: businessReporting, competitiveIntelligence, marketIntelligence, regulatorySurveillance, securityIntelligence, insiderThreatMonitoring, geopoliticalAnalysis, corporateEspionage, agencyIntelligenceFeed, socialMediaAndOsint, darkWebMonitoring
  • confidentialityLevel: public, internal, confidential, restricted, secret, topSecret

Element types: intelligenceSource (listed in sources) and intelligenceApplication (listed in applications)

Primary Relationships: Intelligence informs Strategy; Intelligence enriches Information; Intelligence consumes Information


Manufacturing​

Schema: manufacturing.schema.json · Identifier: manufacturingID · Domain page

AttributeTypeRequiredDescription
manufacturingIDString✓Unique identifier for the manufacturing entity
titleString✓Name/title of the manufacturing entity
descriptionString✓Detailed explanation of the manufacturing entity or process
purposeString✓Intended function or strategic goal of the manufacturing entity
ownerString✓Responsible individual or team (e.g., Head of Operations)
manufacturingCategoryEnum✓Broad categorization of the type of manufacturing process
manufacturingFocusEnum✓Primary focus area of the manufacturing strategy
timeHorizonEnum✓Strategy time frame
scopeLevelEnum✓Organizational or geographical scope
strategicAlignmentStringHow the manufacturing plan aligns with the broader business strategy
productionUnitsArray[Object]A list of production units within this manufacturing entity
workOrdersArray[Object]A list of active and completed work orders
billsOfMaterialsArray[Object]A collection of bills of materials for various products
inventoryArray[Object]Current inventory levels of raw materials, WIP, and finished goods

Enumerations:

  • manufacturingFocus: costReduction, qualityImprovement, leadTimeReduction, flexibility, innovation
  • timeHorizon: immediate, shortTerm, mediumTerm, longTerm, extended
  • scopeLevel: global, continental, regional, national, siteLevel, productionLine

Element types: productionUnit, workOrder (orderID), billOfMaterials (bomID), inventory, manufacturingObjective

Primary Relationships: Manufacturing delivers Products; Supply Chain enables Manufacturing; Technology optimizes Manufacturing


Social Change​

Schema: social-change.schema.json · Identifier: socialChangeID · Domain page

AttributeTypeRequiredDescription
socialChangeIDString✓Unique identifier for the social change activity
nameString✓Name/title of the social change action or campaign
descriptionString✓Short summary of the goal and focus
activityTypeEnum✓Type of activity or intervention
activityCategoryEnumPrimary category classification of the activity
systemicProblemStringSystemic problem or injustice being addressed
primaryAffectedGroupsArray[String]Primary groups impacted by the injustice
stakeholdersArray[Object]Structured list of involved or affected actors
tacticsArray[Object]Advocacy and action tactics used
changeScopeEnumLevel and breadth of change initiative
successMetricsArray[String]How success will be measured, e.g
relationshipsObjectRelationships to other domains in the Triodian Metamodel

Enumerations:

  • changeScope: departmentLevel, organizationWide, multiOrganizational, sectorWide, local, regional, national, international

Primary Relationships: Social Change aligns Strategy; Social Change delivers to Stakeholder; Social Change enables Sustainability

Quick Lookup by Attribute Type​

Common Attributes​

  • Identifier — Every record has a required identifier named after its entity (organizationID, capabilityID, valueStreamID, riskID …), never id. Element records have their own identifiers (orgUnitID, objectiveID, programID, stageID, personaID …).
  • Name and description — Most domains require title and description. Organization uses orgTitle, Social Change uses name, and Value Stream, Initiatives and Policy require only their identifier.
  • Purpose and owner — Capabilities, Information, Strategy, Performance, Products, Services and Manufacturing also require purpose and owner.
  • Organization unit — orgUnitTitle names the linked organization unit and orgUnitID carries its identifier. Customer, Market, Finance, Risk Management, Technology, Supply Chain, People, Innovation and Sustainability require orgUnitTitle.

Date Attributes​

DomainAttributeFormat
OrganizationincorporationDateISO 8601 date
Risk ManagementlastReviewDate, nextReviewDateISO 8601 date
TechnologylastUpdatedISO 8601 date
SustainabilitylastUpdatedISO 8601 date

Shared Value Lists​

Shared listValuesUsed by (examples)
maturityLevelinitial, repeatable, defined, managed, optimizingCapabilities, Value Stream, Information, Performance
riskLevel, criticalitylow, medium, high, criticalStakeholder requirements, Capabilities
timeHorizonimmediate, shortTerm, mediumTerm, longTerm, extendedStrategy, Manufacturing
frequencycontinuous, realTime, hourly, daily, weekly, monthly, quarterly, semiAnnually, annually, eventDriven, onDemand, adHocStakeholder, Information, Performance, Risk Management, Intelligence
automationLevelmanual, semiAutomated, highlyAutomated, fullyAutomated, aiEnabledPerformance, Services
workStatusproposed, planned, approved, inProgress, onHold, deferred, completed, cancelledInitiatives

Reference Attributes​

DomainAttributeTarget
CapabilitiesparentCapabilityID, childCapabilityIDs, relatedCapabilityIDsCapabilities
Organization unitparentOrgUnitID, subOrgUnitIDsOrganization units
StrategyparentStrategyID, relatedStrategyIDsStrategy
InitiativesrelatedStrategyIDsStrategy
InitiativeschildProgramIDsPrograms
ProductscustomerSegmentIDsCustomer
Value Stream StageparentValueStreamIDValue Stream
Value Stream StageenablingCapabilityIDCapabilities
Most domainsorgUnitIDOrganization units