Technology Domain

The Technology domain represents technical components, platforms, and infrastructure that enable business operations and capability delivery. It provides a structured approach for modeling applications, systems, platforms, and technical infrastructure within business architecture.

Schema: technology.schema.json
Specification: JSON Schema Draft-07

Overview

What is Technology?

Technology in business architecture represents the technical assets that enable and support organizational capabilities. The Technology domain covers:

• Applications — Software systems supporting business functions
• Infrastructure — Hardware, networks, and foundational services
• Platforms — Integrated technology environments
• Integration — Connections between systems and data flows
• Technical Services — Shared technology capabilities

The domain connects technical assets to business capabilities, helping organizations understand how technology enables value delivery.

Purpose and Value

The Technology domain enables architects and planners to:

• Map technology to capabilities — Understand how technical assets enable business functions
• Assess technology landscape — Identify redundancies, gaps, and modernization needs
• Plan technology investments — Align IT spending with business priorities
• Manage technical debt — Track and prioritize technology improvements
• Enable digital transformation — Connect business change to technology change

For Data Engineers

The Technology domain maps directly to your technical landscape:

• Application → Service /Application in your CMDB
• Infrastructure → Compute, storage, network resources
• Platform → Data platform, cloud platform
• Integration → Data pipelines, APIs, event streams
• Technical Service → Shared services (auth, monitoring, etc.)

Core Components

The Technology domain uses a layered structure:

1. Application Layer: Business and analytical applications
2. Platform Layer: Integrated technology environments
3. Infrastructure Layer: Foundational compute, storage, network

A record states its position in the stack with technologyLayer and its kind with technologyType (a platform is technologyType: platform). Inside a record, applicationComponents, technologyServices, infrastructureElements and standardElements describe its parts.

Domain Attributes

Core Attributes

Attribute	Type	Description	Required
technologyID	String	Unique identifier for the technology element	✓
title	String	Name or title of the technology component or service	✓
description	String	Detailed explanation of the technology element	✓
technologyType	Enum	Classification of technology (see below)
orgUnitTitle	String	IT or technology organization unit responsible for this component	✓
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
orgUnitRoles	Array[String]	Roles within the technology organization that manage this component
technologyLayer	Enum	Position in the technology stack (see below)
currentState	Enum	Status of the technology element (see below)
targetState	String	Desired future state
businessOwner	String	Business stakeholder responsible
technicalOwner	String	Technical stakeholder responsible
supportModel	String	Support and maintenance approach
lifecycle	Enum	Current lifecycle stage on the shared adoption curve (see below)
vendors	Array[String]	External vendors and partners involved
standards	Array[String]	Applicable technology standards
costs	Object	Financial implications: acquisitionCost, implementationCost, annualOperatingCost, totalCostOfOwnership (five-year), costTrends
risks	Array[String]	Technical and business risks
securityClassification	Enum	Security requirements rating: low, medium, high or critical. Give the reason in prose, e.g. "high: contains sensitive customer data"
performanceRequirements	String	Required performance characteristics
complianceRequirements	Array[String]	Regulatory compliance considerations
strategicAlignment	String	How this technology supports business strategy
performanceIndicators	Array[Object]	Metrics used to measure technology performance (see Performance Indicator)
dependencies	Array[Object]	Domains, processes or systems supporting or depending on this technology: dependencyType (critical, important, supportive, optional), domainType, entityID, description
relatedTechnologies	Array[Object]	Other technologies related to this one: technologyID, relationshipType, relationshipStrength (Integer 1–5), description
improvementOpportunities	Array[String]	Areas where the technology can be enhanced
applicationComponents	Array[Object]	Application components (see Application Component)
technologyServices	Array[Object]	Technology services provided (see Technology Service)
infrastructureElements	Array[Object]	Infrastructure elements (see Infrastructure Element)
standardElements	Array[Object]	Technology standards (see Standard Element)
governanceModel	Object	How the technology is governed: governanceStructure, decisionRights, reviewProcess, changeManagement
dataSecurity	Object	Security of data handling: dataClassification, securityControls, complianceStatus (shared compliance status list), securityAssessments
maturityLevel	Object	Maturity assessment: overallMaturity (initial, repeatable, defined, managed, optimizing), maturityAssessmentDate (Date), maturityRoadmap
lastUpdated	Date	Date when the record was last updated
crossDomainRelationships	Array[Object]	Directional relationships from this record to entities in other domains (see Cross-Domain Relationships)

Performance Indicator

Technology performance indicators use the shared performance indicator definition in common.schema.json.

Field	Type	Description	Required
metricName	String	Name of the metric	✓
metricDescription	String	What the metric measures
currentValue	String	Current value
targetValue	String	Target value
unit	String	Unit of measurement
trend	Enum	Direction against the goal: improving, stable, declining, fluctuating, notTracked

Enumeration Values

Technology Type (technologyType)

Value	Description	Example
application	Business, analytical or custom software	SAP, Salesforce, custom web apps
infrastructure	Foundational technical resources	Servers, VMs, storage, API gateway clusters
service	Shared technology service	Authentication, monitoring
platform	Integrated technology environment	Data platform, cloud platform, Kubernetes
database	Data storage system	PostgreSQL, Oracle, Snowflake
integration	Integration middleware and data flow technology	MuleSoft, ETL tools, event streams
security	Security technology	IAM, encryption, SIEM
endUser	End-user computing	Laptops, productivity suites
network	Network infrastructure	Routers, firewalls, load balancers
standard	A technology standard	OpenAPI 3.0
other	Any other technology	—

Technology Layer (technologyLayer)

Value	Description
presentation	User interfaces and channels
application	Business and analytical applications
data	Data storage, management and analytics
integration	APIs, messaging and data movement
infrastructure	Compute, storage and network
security	Security controls and services
management	Operations, monitoring and management tooling
crossCutting	Concerns spanning several layers
other	Any other layer

Current State (currentState)

Value	Description	Example
proposed	Under evaluation or planning	New technology assessment
underDevelopment	Being developed or configured	Implementation project
pilot	In pilot or testing	Limited deployment
production	Actively in production	Live systems
beingReplaced	Being replaced by another technology	Migration under way
deprecated	Still running but no longer recommended	Legacy systems
retired	No longer in use	Decommissioned

Lifecycle Stage (lifecycle)

lifecycle uses the shared adoption stage list: where the technology sits on its adoption curve, as distinct from its operational currentState.

Value	Description	Example
emerging	New technology, early adoption	Generative AI tooling
growth	Adoption expanding	Expanding API platform
mature	Established and stable	Core ERP
declining	Use decreasing	Older middleware
legacy	Kept running but not invested in	Mainframe applications
sunset	Planned for retirement	Systems scheduled for decommissioning

Relationship Type (relationshipType)

Used in relatedTechnologies.

Value	Description
dependsOn	This technology depends on the related one
supports	This technology supports the related one
integratesWith	The technologies exchange data or calls
replaces	This technology replaces the related one
isReplacedBy	This technology is replaced by the related one
extends	This technology extends the related one
complement	The technologies complement each other
alternative	The technologies are alternatives
other	Any other relationship

Standard Status (standardStatus)

Value	Description
emerging	Being trialled or introduced
current	The current standard
stable	Established, not expected to change
declining	Being phased out
deprecated	No longer recommended
retired	No longer in force

Compliance Requirement (complianceRequirement)

Value	Description
mandatory	Must be followed
recommended	Should be followed
optional	May be followed
referenceOnly	For reference only

Technology Component Elements

Application Component (applicationComponent)

Attribute	Type	Description	Required
applicationName	String	Name of the application	✓
applicationDescription	String	Detailed description	✓
applicationCategory	String	Classification within the portfolio
businessCapabilitiesSupported	Array[String]	Linked business capabilities
functionalDescription	String	Key functions provided
interfacesProvided	Array[String]	Interfaces exposed to other systems
interfacesConsumed	Array[String]	External interfaces consumed
dataEntitiesManaged	Array[String]	Key data handled by the application
technologyStack	String	Technical foundation
deploymentModel	String	How the application is deployed (e.g. public cloud, on-premises, SaaS)
scalability	String	Scaling capabilities and limitations
availability	String	Availability requirements and measures
developmentApproach	String	Development methodology used
lifecycleStage	String	Current stage in the application lifecycle

Technology Service (technologyService)

Attribute	Type	Description	Required
serviceName	String	Name of the technology service	✓
serviceDescription	String	Detailed description	✓
serviceType	String	Classification of service
serviceLevel	String	Performance and reliability parameters
serviceConsumers	Array[String]	Systems that use this service
serviceProviders	Array[String]	Systems that deliver this service
serviceProtocol	Array[String]	Technical protocols used
serviceInterfaces	Array[String]	Interface specifications
securityControls	String	Security measures applied
serviceDependencies	Array[String]	Other services required
serviceAvailability	String	Availability characteristics
serviceScalability	String	Scaling capabilities
serviceCost	String	Cost structure for this service
serviceMonitoring	String	How service health is tracked

Infrastructure Element (infrastructureElement)

Attribute	Type	Description	Required
infrastructureName	String	Name of the infrastructure component	✓
infrastructureType	String	Type of infrastructure	✓
infrastructureLocation	String	Physical or logical location (e.g. primary data center, AWS region)
capacityMetrics	String	Key capacity parameters
utilizationMetrics	String	Current utilization levels
environmentType	String	Production, development, test, etc.
infrastructureManager	String	Responsible management entity
backupStrategy	String	Data protection approach
disasterRecoveryCapability	String	Recovery capabilities
technicalSpecifications	String	Detailed specifications
maintenanceSchedule	String	Maintenance approach
endOfLifeDate	String	Expected retirement date
replacementStrategy	String	Approach to replacement
infrastructureCost	String	Cost structure

Standard Element (standardElement)

Attribute	Type	Description	Required
standardName	String	Name of the technology standard	✓
standardType	String	Category of standard
standardDescription	String	Detailed description	✓
standardVersion	String	Current version
standardStatus	Enum	Status of the standard (see above)
complianceRequirement	Enum	Whether compliance is mandatory, recommended, optional or for reference (see above)
enforcementMechanism	String	How compliance is enforced
waiverProcess	String	Process for exceptions
standardUsage	String	Where the standard applies
standardBenefits	String	Benefits of adoption
alternativeStandards	String	Acceptable alternatives
governingBody	String	Entity managing the standard

Domain Relationships

The Technology domain integrates with other metamodel domains:

Target Domain	Relationship Type	Description
Capabilities	Enablement	Technology enables capability delivery
Information	Management	Technology manages information assets
Services	Delivery	Technology delivers service capabilities
Products	Support	Technology supports product delivery
Organization	Ownership	Organization units own technology assets
Performance	Measurement	Technology tracked through performance metrics
Policy	Compliance	Technology complies with policies
Initiatives	Implementation	Initiatives implement technology changes
Value Stream	Automation	Technology automates value stream activities
Stakeholder	Usage	Stakeholders use technology systems

A technology record lists its own relationships in crossDomainRelationships, with itself as the source (see Example 3).

Examples

Example 1: Enterprise Data Platform

{
  "technologyID": "TECH-DATA-001",
  "title": "Enterprise Data Platform",
  "description": "Cloud-native data platform providing unified data management, analytics, and AI/ML capabilities for the enterprise, enabling data-driven decision making through centralized, governed data access",
  "technologyType": "platform",
  "orgUnitTitle": "Data and Analytics Division",
  "orgUnitID": "OU-DATA-001",
  "technologyLayer": "data",
  "currentState": "production",
  "businessOwner": "Chief Data Officer",
  "technicalOwner": "Head of Data Platform",
  "supportModel": "Vendor support with internal platform team; serves 500 analysts, 50 data scientists and 100 dashboard users",
  "lifecycle": "mature",
  "vendors": ["Snowflake", "AWS"],
  "costs": {
    "annualOperatingCost": "$1.2M (compute: $800K, storage: $400K)"
  },
  "risks": ["Cloud provider dependency", "Data security", "Cost management"],
  "securityClassification": "high",
  "performanceRequirements": "99.9% SLA, multi-AZ deployment, auto-scaling compute with separate storage scaling",
  "complianceRequirements": ["SOC2", "GDPR", "Internal data policies"],
  "strategicAlignment": "Core enabler for digital transformation and data-driven culture initiatives",
  "performanceIndicators": [
    {
      "metricName": "Query Response Time",
      "metricDescription": "95th percentile query response time",
      "targetValue": "<5s"
    },
    {
      "metricName": "Data Freshness",
      "metricDescription": "Delay between source update and availability in the platform",
      "targetValue": "<4 hours"
    }
  ],
  "dependencies": [
    {
      "dependencyType": "critical",
      "domainType": "technology",
      "entityID": "TECH-AWS-001",
      "description": "AWS infrastructure"
    },
    {
      "dependencyType": "critical",
      "domainType": "technology",
      "entityID": "TECH-IDP-001",
      "description": "Corporate identity provider for SSO"
    }
  ],
  "applicationComponents": [
    {
      "applicationName": "Data Ingestion Layer",
      "applicationDescription": "Manages data ingestion from 50+ source systems",
      "interfacesConsumed": [
        "SAP ERP (daily batch ETL)",
        "Salesforce CRM (CDC streaming, near real-time)"
      ],
      "deploymentModel": "Public cloud"
    },
    {
      "applicationName": "Analytics Data Mart",
      "applicationDescription": "Curated data models for business analytics",
      "interfacesProvided": ["Tableau direct query"],
      "dataEntitiesManaged": [
        "Customer Master Data",
        "Transaction History",
        "Financial Data",
        "Operational Metrics"
      ]
    }
  ],
  "dataSecurity": {
    "dataClassification": "Confidential",
    "securityControls": ["SSO integration", "Column-level security", "Data masking", "Audit logging"],
    "complianceStatus": "compliant"
  },
  "crossDomainRelationships": [
    {
      "targetDomain": "capability",
      "targetEntityID": "CAP-DATA-001",
      "relationshipType": "enables",
      "description": "Enables the Data Integration, Data Warehousing, Business Intelligence and Advanced Analytics capabilities"
    }
  ]
}

Example 2: Track Monitoring System

{
  "technologyID": "TECH-TRACK-002",
  "title": "Track Condition Monitoring System",
  "description": "IoT-based system for real-time monitoring of track conditions using sensors and predictive analytics, enabling predictive maintenance and improved safety",
  "technologyType": "application",
  "orgUnitTitle": "Technology Innovation Division",
  "technologyLayer": "application",
  "currentState": "production",
  "technicalOwner": "Director of Track Technology",
  "supportModel": "Internal support (internally developed, version 3.2.1)",
  "lifecycle": "growth",
  "costs": {
    "acquisitionCost": "$2M sensor network (capital)",
    "annualOperatingCost": "$450K"
  },
  "risks": ["Sensor reliability", "Connectivity in remote areas", "Model accuracy"],
  "securityClassification": "high",
  "performanceRequirements": "99.5% uptime, fault-tolerant architecture",
  "complianceRequirements": ["Federal regulations", "Safety standards"],
  "strategicAlignment": "Directly supports safety excellence and infrastructure reliability goals",
  "performanceIndicators": [
    {
      "metricName": "Sensor Data Latency",
      "targetValue": "<1 second"
    },
    {
      "metricName": "Prediction Accuracy",
      "currentValue": "94%"
    }
  ],
  "technologyServices": [
    {
      "serviceName": "Sensor Data Collection",
      "serviceDescription": "Real-time collection of track sensor data over MQTT",
      "serviceProtocol": ["MQTT"],
      "securityControls": "End-to-end encryption, device authentication"
    },
    {
      "serviceName": "Work Order Generation",
      "serviceDescription": "Event-driven creation of maintenance work orders",
      "serviceConsumers": ["Maintenance Management System"],
      "serviceProtocol": ["REST API"]
    }
  ],
  "infrastructureElements": [
    {
      "infrastructureName": "Track Sensor Hosting",
      "infrastructureType": "Hybrid cloud",
      "infrastructureLocation": "Azure and edge gateways"
    }
  ],
  "crossDomainRelationships": [
    {
      "targetDomain": "capability",
      "targetEntityID": "CAP-TRACK-INSPECT-001",
      "relationshipType": "enables",
      "description": "Enables track inspection, predictive maintenance and safety monitoring"
    }
  ]
}

Example 3: Enterprise API Management Platform

{
  "technologyID": "TECH-API-001",
  "title": "Enterprise API Management Platform",
  "description": "Centralized platform for designing, implementing, publishing, and monitoring APIs across the organization, enabling secure integration between internal and external systems.",
  "technologyType": "infrastructure",
  "orgUnitTitle": "Enterprise Architecture & Integration",
  "orgUnitRoles": [
    "API Platform Manager",
    "Integration Architect",
    "Security Architect"
  ],
  "technologyLayer": "integration",
  "currentState": "production",
  "targetState": "enhance with AI-driven API analytics and automated documentation generation",
  "businessOwner": "Chief Digital Officer",
  "technicalOwner": "VP of Enterprise Architecture",
  "supportModel": "24/7 operational support with specialized integration team and vendor escalation path",
  "lifecycle": "growth",
  "vendors": [
    "MuleSoft",
    "Apigee"
  ],
  "standards": [
    "REST API Design Standards",
    "OAuth 2.0",
    "OpenAPI 3.0"
  ],
  "costs": {
    "implementationCost": "$1.8M",
    "annualOperatingCost": "$1.2M ($750K licensing, $450K operations)"
  },
  "risks": [
    "API security vulnerabilities",
    "Scalability limitations during peak loads",
    "Developer adoption challenges"
  ],
  "securityClassification": "high",
  "performanceRequirements": "99.99% gateway availability, <100ms latency overhead, 5000 TPS capacity",
  "complianceRequirements": [
    "SOC2 compliance",
    "Data residency requirements",
    "Regulatory audit trails"
  ],
  "strategicAlignment": "Enabler for digital ecosystem strategy, partner integration, and legacy modernization initiatives",
  "applicationComponents": [
    {
      "applicationName": "API Developer Portal",
      "applicationDescription": "Self-service platform for API discovery, documentation, and developer onboarding",
      "applicationCategory": "development-tool",
      "businessCapabilitiesSupported": [
        "Partner Ecosystem Management",
        "Digital Channel Development",
        "Integration"
      ],
      "functionalDescription": "API catalog, interactive documentation, API key management, analytics dashboard, community forums",
      "interfacesProvided": [
        "Developer Registration API",
        "API Metrics API",
        "Documentation Rendering Service"
      ],
      "interfacesConsumed": [
        "API Gateway Metrics",
        "API Repository",
        "Identity Service"
      ],
      "dataEntitiesManaged": [
        "API definitions",
        "Developer accounts",
        "Application registrations",
        "Usage analytics"
      ],
      "technologyStack": "Node.js, React, MongoDB, Docker, Kubernetes",
      "deploymentModel": "Containerized microservices in private cloud",
      "scalability": "Horizontally scalable to support 10,000 registered developers",
      "availability": "99.9% availability with automated failover",
      "developmentApproach": "Agile with CI/CD pipeline",
      "lifecycleStage": "growth - expanding capabilities for external developer communities"
    }
  ],
  "technologyServices": [
    {
      "serviceName": "API Gateway Service",
      "serviceDescription": "Core service managing API routing, security, throttling, and monitoring",
      "serviceType": "integration-service",
      "serviceLevel": "99.99% availability, <100ms latency, 24/7 support",
      "serviceConsumers": [
        "Mobile Applications",
        "Web Applications",
        "Partner Systems",
        "Internal Microservices"
      ],
      "serviceProviders": [
        "API Gateway Clusters",
        "Load Balancers"
      ],
      "serviceProtocol": [
        "HTTPS",
        "WebSockets",
        "gRPC"
      ],
      "serviceInterfaces": [
        "Management REST API",
        "Metrics API",
        "Configuration API"
      ],
      "securityControls": "OAuth 2.0 enforcement, API key validation, JWT validation, rate limiting, IP filtering",
      "serviceDependencies": [
        "Identity and Access Management Service",
        "Monitoring and Alerting Platform"
      ],
      "serviceAvailability": "Active-active deployment across multiple availability zones",
      "serviceScalability": "Auto-scaling based on traffic patterns up to 5000 TPS",
      "serviceCost": "$85 per million API calls with volume discounts",
      "serviceMonitoring": "Real-time dashboards, synthetic testing, anomaly detection, business impact alerts"
    }
  ],
  "infrastructureElements": [
    {
      "infrastructureName": "API Gateway Cluster",
      "infrastructureType": "application-infrastructure",
      "infrastructureLocation": "Multi-region cloud deployment",
      "capacityMetrics": "5000 transactions per second, 2TB configuration storage",
      "utilizationMetrics": "Average 45% CPU utilization, 65% peak periods",
      "environmentType": "production",
      "infrastructureManager": "Integration Operations Team",
      "backupStrategy": "Configuration snapshots every 6 hours, geo-redundant storage",
      "disasterRecoveryCapability": "Multi-region active-active with automated failover",
      "technicalSpecifications": "Container-based deployment on Kubernetes, with dedicated nodes for high-performance processing",
      "maintenanceSchedule": "Monthly patch window, rolling updates without downtime",
      "endOfLifeDate": "Platform refresh planned for 2028",
      "replacementStrategy": "Continuous evolution with major version upgrades annually",
      "infrastructureCost": "Annual operational cost of $650K including cloud resources"
    }
  ],
  "standardElements": [
    {
      "standardName": "Enterprise API Design Standard",
      "standardType": "integration",
      "standardDescription": "Comprehensive guidelines for designing, documenting, and implementing APIs across the enterprise",
      "standardVersion": "3.2",
      "standardStatus": "current",
      "complianceRequirement": "mandatory",
      "enforcementMechanism": "Automated validation in CI/CD pipeline, architectural review for exceptions",
      "waiverProcess": "Formal exception request to API Governance Board with business justification",
      "standardUsage": "All internal and external APIs developed by the organization",
      "standardBenefits": "Consistent developer experience, improved reusability, streamlined integration, reduced support costs",
      "alternativeStandards": "GraphQL standard available for complex data retrieval scenarios",
      "governingBody": "API Governance Board chaired by Enterprise Architecture"
    }
  ],
  "performanceIndicators": [
    {
      "metricName": "API Platform Adoption",
      "metricDescription": "Percentage of enterprise integrations using the API platform",
      "currentValue": "72%",
      "targetValue": "95%",
      "trend": "improving"
    },
    {
      "metricName": "Developer Satisfaction",
      "metricDescription": "Average rating from API consumers",
      "currentValue": "4.1/5.0",
      "targetValue": "4.5/5.0",
      "trend": "stable"
    },
    {
      "metricName": "API Response Time",
      "metricDescription": "Average latency added by API gateway",
      "currentValue": "85ms",
      "targetValue": "<50ms",
      "trend": "improving"
    },
    {
      "metricName": "API Reuse Rate",
      "metricDescription": "Average number of consumers per API",
      "currentValue": "3.8",
      "targetValue": "6.0",
      "trend": "improving"
    }
  ],
  "crossDomainRelationships": [
    {
      "targetDomain": "capability",
      "targetEntityID": "CAP-INT-001",
      "relationshipType": "enables",
      "description": "Enables System Integration capability through standardized API management",
      "metadata": {
        "strength": 5
      }
    },
    {
      "targetDomain": "service",
      "targetEntityID": "SRV-PARTNER-002",
      "relationshipType": "delivers",
      "description": "Delivers secure partner integration services through managed APIs",
      "metadata": {
        "strength": 4
      }
    },
    {
      "targetDomain": "initiative",
      "targetEntityID": "INIT-DIGITAL-005",
      "relationshipType": "enables",
      "description": "Core enabler for Digital Ecosystem Initiative",
      "metadata": {
        "strength": 5
      }
    }
  ]
}

Implementation Guidelines

Technology Management Best Practices

1. Align to capabilities — Map every technology asset to business capabilities
2. Manage lifecycle — Track lifecycle stage and plan transitions
3. Control technical debt — Document and prioritize debt remediation
4. Standardize platforms — Consolidate to strategic platforms
5. Plan for change — Maintain technology roadmaps aligned to strategy

Technology Landscape Assessment

OpenMetadata Integration

For Data Platform Teams

When integrating with OpenMetadata, map Technology entities as follows:

Triodian Element	OpenMetadata Entity	Notes
application	Service	Application as a service
database	Database	Database assets
platform (data platform)	Database Service	Platform connection
integration	Pipeline	Integration flows
Technology service (API)	API Service	API endpoints

# Example: Map Technology to OpenMetadata Service
def create_service(technology):
    """
    Map Triodian Technology to OpenMetadata Service entity
    """
    service_type_map = {
        "database": "databaseService",
        "platform": "databaseService",
        "integration": "pipelineService",
        "infrastructure": "storageService"
    }

    return {
        "name": technology["title"].lower().replace(" ", "_"),
        "displayName": technology["title"],
        "description": technology["description"],
        "serviceType": service_type_map.get(
            technology.get("technologyType"), "customService"
        ),
        "owner": {"name": technology.get("technicalOwner", technology["orgUnitTitle"]), "type": "user"},
        "tags": [
            {"tagFQN": f"TechnologyLayer.{technology.get('technologyLayer', 'other')}"},
            {"tagFQN": f"Lifecycle.{technology.get('lifecycle', 'mature')}"},
            {"tagFQN": f"CurrentState.{technology.get('currentState', 'production')}"}
        ],
        "extension": {"triodianTechnologyID": technology["technologyID"]}
    }

Schema Reference

• Repository: Triodian/Triodian_Metamodel
• Schema: technology.schema.json
• Specification: JSON Schema Draft-07
• License: Apache License 2.0

---

Previous: Value Stream Domain | Next: People Domain