Technology
- damian.hickey
Overview
The Technology Domain represents the technical components and infrastructure that enable business operations. This domain focuses on applications, services, infrastructure elements, and technology standards that support organizational capabilities and business processes. It aligns with TOGAF's Technology Architecture while maintaining compatibility with the Orthogramic schema approach.
Purpose and Value
The Technology Domain enables organizations to:
Map technology components to business capabilities and strategic objectives
Document technical services and their relationships to business services
Analyze technology infrastructure to ensure it meets operational requirements
Establish and manage technology standards for consistency and interoperability
Support data-driven decision making about technology investments and priorities
Enable technology portfolio management and lifecycle planning
Provide a structured foundation for technology governance and risk management
Core Concepts
Application Component
A software application or system that provides specific functionality to support business operations. Application components are typically discrete software elements that can be deployed independently but may interact with other components.
Technology Service
A defined technical function or capability provided by technology components that can be consumed by other technology components, applications, or business processes. Technology services represent the operational capabilities provided by technology.
Technology Infrastructure
The foundational hardware, networks, platforms, and environments that support applications and services. Infrastructure elements represent the physical and virtual technology assets that enable all other technology operations.
Technology Standard
A formal specification, requirement, or approved approach for technology implementation, integration, or management. Standards ensure consistency, interoperability, and compliance across the technology landscape.
Conclusion
The Technology Domain extends the Orthogramic Metamodel with a comprehensive framework for modeling and managing the technical components that enable business operations. By providing structured schemas for applications, technology services, infrastructure, and standards, it enables organizations to systematically align their technology landscape with strategic objectives and operational requirements.
The integration with the Strategic Response Model ensures that technology insights drive strategic decision-making and organizational change. This domain complements other domains by focusing on the technical foundation that supports organizational activities, providing critical context for strategic planning and operational execution.
Organizations can use this domain to develop a more comprehensive understanding of their technology ecosystem, identify optimization opportunities, and ensure that technology investments are properly aligned with business needs and strategic priorities. The domain's alignment with TOGAF's Technology Architecture component enables organizations to leverage established enterprise architecture methods while maintaining compatibility with the Orthogramic schema approach.
Example Implementation
Example: 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-software",
"orgUnitTitle": "Enterprise Architecture & Integration",
"orgUnitRoles": [
"API Platform Manager",
"Integration Architect",
"Security Architect"
],
"technologyLayer": "integration",
"currentState": "operational",
"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",
"annualLicensing": "$750K",
"annualOperational": "$450K"
},
"risks": [
"API security vulnerabilities",
"Scalability limitations during peak loads",
"Developer adoption challenges"
],
"securityClassification": "high - gateway to critical business systems",
"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": [
{
"indicatorName": "API Platform Adoption",
"description": "Percentage of enterprise integrations using the API platform",
"currentValue": "72%",
"targetValue": "95%",
"trend": "increasing"
},
{
"indicatorName": "Developer Satisfaction",
"description": "Average rating from API consumers",
"currentValue": "4.1/5.0",
"targetValue": "4.5/5.0",
"trend": "stable"
},
{
"indicatorName": "API Response Time",
"description": "Average latency added by API gateway",
"currentValue": "85ms",
"targetValue": "<50ms",
"trend": "improving"
},
{
"indicatorName": "API Reuse Rate",
"description": "Average number of consumers per API",
"currentValue": "3.8",
"targetValue": "6.0",
"trend": "increasing"
}
],
"relationshipExamples": [
{
"relationshipType": "Technology-Capability",
"relatedEntityID": "CAP-INT-001",
"relationshipDescription": "Enables System Integration capability through standardized API management",
"relationshipStrength": 5
},
{
"relationshipType": "Technology-Service",
"relatedEntityID": "SRV-PARTNER-002",
"relationshipDescription": "Delivers secure partner integration services through managed APIs",
"relationshipStrength": 4
},
{
"relationshipType": "Technology-Initiative",
"relatedEntityID": "INIT-DIGITAL-005",
"relationshipDescription": "Core enabler for Digital Ecosystem Initiative",
"relationshipStrength": 5
}
]
}
Technology Domain schema
JSON Schema
See: https://github.com/Orthogramic/Orthogramic_Metamodel/blob/main/schemas/technology.schema.json
Domain Attributes
Attribute | Description | Example |
|---|---|---|
title | Name of the technology component or service | "Customer Relationship Management System" |
description | Detailed explanation of the technology element | "Enterprise CRM solution for managing customer interactions, sales pipelines, and service requests" |
technologyType | Classification of technology (e.g., application, infrastructure) | "Application" |
orgUnitTitle | The IT or technology organization unit responsible for this component | "Enterprise Applications Team" |
orgUnitRoles | Specific roles within the technology organization that manage this component | ["Application Owner", "System Administrator", "Business Analyst"] |
technologyLayer | Position in the technology stack | "Business Application Layer" |
currentState | Status of the technology element | "Production" |
targetState | Desired future state | "Enhance with AI-driven insights by Q4 2025" |
businessOwner | Business stakeholder responsible | "VP of Customer Experience" |
technicalOwner | Technical stakeholder responsible | "Enterprise Applications Director" |
supportModel | Support and maintenance approach | "24/7 service desk with tiered escalation to vendor" |
lifecycle | Current lifecycle stage | "Growth" |
vendors | External vendors/partners involved | ["Salesforce", "Implementation Partner Inc."] |
standards | Applicable technology standards | ["OAuth 2.0", "REST API", "Data Encryption Standard"] |
costs | Financial implications of this technology | {"acquisitionCost": "$1.2M", "annualOperatingCost": "$450K"} |
risks | Technical and business risks | ["Data migration complexities", "User adoption challenges"] |
securityClassification | Security requirements and rating | "High - Contains sensitive customer data" |
performanceRequirements | Required performance characteristics | "99.9% availability, <2 second response time" |
complianceRequirements | Regulatory compliance considerations | ["GDPR", "CCPA", "Industry data protection standards"] |
strategicAlignment | How this technology supports business strategy | "Enables personalized customer experience strategy and 360° customer view" |
Application Component Element
Sub-Element | Description | Example |
|---|---|---|
applicationName | Name of the application | "Enterprise CRM Platform" |
applicationDescription | Detailed description | "Cloud-based CRM solution that manages the complete customer lifecycle" |
applicationCategory | Classification within portfolio | "Customer Management" |
businessCapabilitiesSupported | Linked business capabilities | ["Customer Relationship Management", "Sales Pipeline Management", "Service Delivery"] |
functionalDescription | Key functions provided | "Contact management, opportunity tracking, service case management, marketing campaign integration" |
interfacesProvided | Interfaces exposed to other systems | ["Customer API", "Analytics Data Feed", "Integration Webhooks"] |
interfacesConsumed | External interfaces consumed | ["Identity Management System", "Product Catalog Service", "Email Gateway"] |
dataEntitiesManaged | Key data handled by the application | ["Customer profiles", "Interactions", "Opportunities", "Service cases"] |
technologyStack | Technical foundation | "Salesforce Lightning Platform, AWS infrastructure, React frontend" |
deploymentModel | How the application is deployed | "Multi-tenant SaaS with private database instances" |
scalability | Scaling capabilities and limitations | "Automatic scaling to 10,000 concurrent users, 200TB data capacity" |
availability | Availability requirements and measures | "99.9% availability SLA, active-active disaster recovery" |
developmentApproach | Development methodology used | "Agile with quarterly release cycles" |
lifecycleStage | Current stage in application lifecycle | "Growth - expanding capabilities and user base" |
Technology Service Element
Sub-Element | Description | Example |
|---|---|---|
serviceName | Name of the technology service | "Identity and Access Management Service" |
serviceDescription | Detailed description | "Centralized authentication and authorization service for enterprise applications" |
serviceType | Classification of service | "Security Service" |
serviceLevel | Performance and reliability parameters | "99.99% availability, <100ms response time, 24/7 support" |
serviceConsumers | Systems that use this service | ["CRM System", "HR System", "Customer Portal"] |
serviceProviders | Systems that deliver this service | ["Microsoft Azure AD", "On-premises AD infrastructure"] |
serviceProtocol | Technical protocols used | ["SAML 2.0", "OAuth 2.0", "OIDC"] |
serviceInterfaces | Interface specifications | ["REST API", "LDAP", "RADIUS"] |
securityControls | Security measures applied | "MFA, role-based access control, audit logging, encryption" |
serviceDependencies | Other services required | ["Directory Services", "Certificate Services"] |
serviceAvailability | Availability characteristics | "Multi-region deployment with automatic failover" |
serviceScalability | Scaling capabilities | "Supports up to 50,000 concurrent authentications" |
serviceCost | Cost structure for this service | "Per-user licensing plus infrastructure costs" |
serviceMonitoring | How service health is tracked | "Real-time monitoring dashboard with proactive alerting" |
Technology Infrastructure Element
Sub-Element | Description | Example |
|---|---|---|
infrastructureName | Name of the infrastructure component | "Primary Data Center" |
infrastructureType | Type of infrastructure | "Physical data center" |
infrastructureLocation | Physical or logical location | "Atlanta, GA" |
capacityMetrics | Key capacity parameters | "5MW power, 10,000 sq ft, 500 rack capacity" |
utilizationMetrics | Current utilization levels | "Power: 65%, Space: 72%, Cooling: 60%" |
environmentType | Production, development, test, etc. | "Production" |
infrastructureManager | Responsible management entity | "Data Center Operations Team" |
backupStrategy | Data protection approach | "Daily incremental, weekly full backups with offsite replication" |
disasterRecoveryCapability | Recovery capabilities | "Hot site with 4-hour RTO, 15-minute RPO" |
technicalSpecifications | Detailed specifications | "Tier 3 data center, redundant power and cooling, 10Gbps network" |
maintenanceSchedule | Maintenance approach | "Monthly maintenance window, Sunday 2AM-6AM" |
endOfLifeDate | Expected retirement date | "2028-12-31" |
replacementStrategy | Approach to replacement | "Phased migration to cloud infrastructure beginning 2026" |
infrastructureCost | Cost structure | "Annual operating cost of $3.5M" |
Technology Standard Element
Sub-Element | Description | Example |
|---|---|---|
standardName | Name of the technology standard | "Enterprise API Design Standard" |
standardType | Category of standard | "Integration" |
standardDescription | Detailed description | "Guidelines and requirements for designing and implementing APIs across the enterprise" |
standardVersion | Current version | "v2.3" |
standardStatus | Status (e.g., emerging, current, deprecated) | "Current" |
complianceRequirement | Mandatory or recommended | "Mandatory for all new API development" |
enforcementMechanism | How compliance is enforced | "Architecture review board approvals, automated compliance checks" |
waiverProcess | Process for exceptions | "Formal exception request with business justification and compensating controls" |
standardUsage | Where the standard applies | "All internal and external APIs developed by the organization" |
standardBenefits | Benefits of adoption | "Improved interoperability, reduced integration costs, consistent security implementation" |
alternativeStandards | Acceptable alternatives | "GraphQL for specific high-complexity data retrieval scenarios" |
governingBody | Entity managing the standard | "Enterprise Architecture Board" |
TOGAF Integration Points
This domain would include specific mappings to TOGAF concepts:
Alignment with TOGAF's Technology Architecture component
Support for TOGAF's Architecture Development Method (ADM)
Compatibility with TOGAF's content metamodel
Support for TOGAF's building blocks approach
The Orthogramic Metamodel license: Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0), ensuring it remains open, collaborative, and widely accessible.