Well-Architected Frameworks

Well-Architected Frameworks provide structured approaches to evaluating and improving cloud and enterprise architectures. This page documents how Triodian domains map to well-architected concepts, enabling alignment between business architecture and technical architecture assessment, and describes the metamodel's extension schema for recording the TechnologyOne Well-Architected Framework as applied to a technology solution.

Schema: technology-one-well-architected-framework.schema.json
Specification: JSON Schema Draft-07
Frameworks covered: AWS, Azure, GCP, TechnologyOne

Overview

What are Well-Architected Frameworks?

Well-Architected Frameworks are assessment methodologies that evaluate architectures against best practices across key pillars:

Operational Excellence — Running and monitoring systems
Security — Protecting information and systems
Reliability — Recovering from failures, meeting demand
Performance Efficiency — Using resources efficiently
Cost Optimization — Avoiding unnecessary costs
Sustainability — Minimizing environmental impact (newer pillar)

Why Map to Well-Architected?

Benefit	Description
Business-technical alignment	Connect business capabilities to technical quality
Assessment consistency	Use common framework across organization
Cloud readiness	Evaluate readiness for cloud migration
Continuous improvement	Drive architecture improvements systematically

Framework Comparison

Pillar Alignment Across Frameworks

Pillar	AWS	Azure	GCP	Triodian Domain
Operational Excellence	✓	✓	✓	Capabilities, Value Stream
Security	✓	✓	✓	Policy, Risk Management
Reliability	✓	✓	✓	Technology, Capabilities
Performance	✓	✓	✓	Performance, Technology
Cost Optimization	✓	✓	✓	Finance, Technology
Sustainability	✓	✓	-	Sustainability

Domain Mappings by Pillar

Operational Excellence

Focus: Running and monitoring systems to deliver business value

Triodian Domain	Mapping	Relevance
Capabilities	Business capabilities require operational support	High
Value Stream	Value delivery depends on operational health	High
Performance	KPIs measure operational outcomes	High
Technology	Technical operations enable capabilities	Medium
People	Skills and culture support operations	Medium

Key Mappings:

Capability maturity → Operational readiness
Value stream performance → Operational metrics
SLAs/SLOs → Service-level expectations

Security

Focus: Protecting information, systems, and assets

Triodian Domain	Mapping	Relevance
Policy	Security policies govern behavior	High
Risk Management	Security risks require management	High
Information	Data classification and protection	High
Technology	Security controls implementation	High
Capabilities	Security capabilities required	Medium

Key Mappings:

Policy compliance → Security controls
Risk appetite → Security investment
Information classification → Data protection requirements

Reliability

Focus: Recovering from failures and meeting demand

Triodian Domain	Mapping	Relevance
Technology	Infrastructure reliability	High
Capabilities	Business continuity requirements	High
Risk Management	Availability risk management	High
Value Stream	Critical path identification	Medium
Supply Chain	Dependency management	Medium

Key Mappings:

Capability criticality → Recovery requirements (RTO/RPO)
Technology dependencies → Single points of failure
Value stream stages → Resilience requirements

Performance Efficiency

Focus: Using resources efficiently to meet requirements

Triodian Domain	Mapping	Relevance
Performance	Performance metrics and targets	High
Technology	Technical performance characteristics	High
Capabilities	Capability performance requirements	Medium
Value Stream	Process efficiency	Medium

Key Mappings:

Performance indicators → Technical metrics
Capability SLAs → Performance targets
Value stream throughput → System capacity

Cost Optimization

Focus: Avoiding unnecessary costs while delivering value

Triodian Domain	Mapping	Relevance
Finance	Cost management and optimization	High
Technology	Infrastructure cost efficiency	High
Capabilities	Capability cost-effectiveness	Medium
Value Stream	Value vs. cost analysis	Medium

Key Mappings:

Finance domain costs → Infrastructure spending
Capability ROI → Technology investment
Value stream value → Cost justification

Sustainability

Focus: Minimizing environmental impact

Triodian Domain	Mapping	Relevance
Sustainability	Environmental objectives	High
Technology	Green technology choices	High
Supply Chain	Sustainable sourcing	Medium
Capabilities	Sustainable practices	Medium

Key Mappings:

Sustainability goals → Carbon reduction targets
Technology choices → Energy efficiency
Supply chain policies → Environmental requirements

Assessment Integration

Mapping Triodian to Well-Architected Review

Assessment Workflow

Identify scope — Which capabilities/value streams to assess?
Map to pillars — Connect business requirements to WA pillars
Conduct review — Use WA questions against mapped areas
Identify gaps — Where does architecture fall short?
Prioritize improvements — Use business value to prioritize
Track in SRM — Create strategic responses for improvements

Recording Assessment Findings

The metamodel has no separate record type for individual well-architected review results. Record each finding against the domain entity it concerns, and track the gaps it reveals through the Strategic Response Model (see Connecting to Strategic Response Model).

TechnologyOne Well-Architected Framework Extension

The extension schema records how the TechnologyOne Well-Architected Framework's principles, pillars, component types, methodology, governance and KPIs apply within a technology solution. All sections are optional.

Framework Record

Attribute	Type	Description
`frameworkOverview`	Object	General overview of the framework
`corePrinciples`	Array[Object]	Core guiding principles for architectural design
`architecturalPillars`	Array[Object]	The foundational pillars that ensure comprehensive architectural excellence (e.g. Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability)
`architecturalComponents`	Array[Object]	Abstracted types of components commonly found in TechnologyOne-based architectures
`implementationMethodology`	Object	Guidelines for implementing solutions following the framework
`governanceModel`	Object	Aspects of governance related to the architectural framework
`kpis`	Array[Object]	Key Performance Indicators relevant to solution architecture

Framework Overview (`frameworkOverview`)

Attribute	Type	Required	Description
`name`	String	✓	Name of the framework
`version`	String		Version of the framework referenced
`description`	String	✓	A high-level description of the framework's purpose

Core Principle (`corePrinciples`)

Attribute	Type	Required	Description
`principleName`	Enum	✓	Name of the core principle
`description`	String	✓	Description of the principle and its implications for solution architecture
`guidelines`	Array[String]		Specific guidelines or best practices associated with this principle

Principle Name (`principleName`)

Value	Description
`citizenCentricDesign`	Design services around the needs of citizens and other end users
`dataDrivenDecisionMaking`	Base architectural and business decisions on reliable data
`continuousEvolution`	Evolve the solution continuously rather than through large, infrequent changes
`other`	A principle not listed here

Architectural Pillar (`architecturalPillars`)

Attribute	Type	Required	Description
`pillarName`	String	✓	Name of the architectural pillar
`description`	String	✓	Description of what the pillar entails
`keyConsiderations`	Array[String]		Key considerations or areas of focus within this pillar
`bestPractices`	Array[String]		Recommended best practices for implementing this pillar

Architectural Component (`architecturalComponents`)

Attribute	Type	Required	Description
`componentType`	Enum	✓	Categorization of the architectural component
`genericDescription`	String	✓	A generic description of the component's function
`commonInteractions`	Array[String]		Common ways this component interacts with others (e.g. REST APIs, business events, data export, authenticated requests)

Component Type (`componentType`)

Value	Description
`coreErpModule`	Core ERP module, such as TechnologyOne Financials or HR
`integrationService`	Service that moves data or calls between systems
`apiGateway`	Gateway that exposes and secures APIs
`workflowEngine`	Engine that runs business workflows
`eventBus`	Bus that distributes business events
`dataWarehouse`	Store for reporting and analytical data
`reportingTool`	Reporting and analytics tool
`securityProxy`	Proxy that authenticates and authorizes requests
`externalSystemIntegration`	Integration with a system outside the platform
`webPortal`	Web portal for citizens, customers or staff
`other`	A component type not listed here

Implementation Methodology (`implementationMethodology`)

Attribute	Type	Required	Description
`phases`	Array[String]		Key phases of implementation (e.g. Design, Build, Test, Deploy, Operate)
`keyActivities`	Array[String]		Critical activities within the methodology

Governance Model (`governanceModel`)

Attribute	Type	Required	Description
`decisionMakingProcess`	String		Description of how architectural decisions are made
`reviewMechanisms`	String		How architectural adherence and quality are reviewed

KPI (`kpis`)

Attribute	Type	Required	Description
`kpiName`	String	✓	Name of the KPI
`description`	String		What the KPI measures
`measurementFrequency`	Enum		How often the KPI is measured

Measurement Frequency (`measurementFrequency`)

The shared frequency list.

Value	Description
`continuous`	Always running
`realTime`	Responds as events occur
`hourly`	Every hour
`daily`	Every day
`weekly`	Every week
`monthly`	Every month
`quarterly`	Every quarter
`semiAnnually`	Twice a year
`annually`	Once a year
`eventDriven`	Triggered by a defined event
`onDemand`	When requested
`adHoc`	Irregular, as needed

Example: Council Services Platform

{
  "frameworkOverview": {
    "name": "TechnologyOne Well-Architected Framework",
    "description": "Principles and practices for designing, operating and evolving solutions on the TechnologyOne platform"
  },
  "corePrinciples": [
    {
      "principleName": "citizenCentricDesign",
      "description": "Online services are designed around resident journeys rather than internal departments",
      "guidelines": ["Offer self-service for common requests", "Measure resident effort for each journey"]
    },
    {
      "principleName": "dataDrivenDecisionMaking",
      "description": "Service and investment decisions use shared, governed data from the data warehouse"
    }
  ],
  "architecturalPillars": [
    {
      "pillarName": "Reliability",
      "description": "Services recover quickly from failure and meet demand peaks such as rates notices",
      "keyConsiderations": ["Recovery time objectives for payment services", "Capacity for seasonal peaks"],
      "bestPractices": ["Automated backups with quarterly recovery testing"]
    },
    {
      "pillarName": "Security",
      "description": "Resident and financial data is protected in transit and at rest",
      "bestPractices": ["Encrypt all data at rest", "Route external requests through the security proxy"]
    }
  ],
  "architecturalComponents": [
    {
      "componentType": "coreErpModule",
      "genericDescription": "Financials and property and rating modules",
      "commonInteractions": ["REST APIs", "Business events"]
    },
    {
      "componentType": "apiGateway",
      "genericDescription": "Exposes platform services to the resident portal and partner systems",
      "commonInteractions": ["Authenticated requests"]
    },
    {
      "componentType": "webPortal",
      "genericDescription": "Resident self-service portal for requests, payments and bookings",
      "commonInteractions": ["REST APIs"]
    }
  ],
  "implementationMethodology": {
    "phases": ["Design", "Build", "Test", "Deploy", "Operate"],
    "keyActivities": ["Architecture review at each phase gate", "Recovery testing before go-live"]
  },
  "governanceModel": {
    "decisionMakingProcess": "Architecture Review Board approves designs that depart from the framework",
    "reviewMechanisms": "Annual well-architected review of each production solution"
  },
  "kpis": [
    {
      "kpiName": "Service availability",
      "description": "Share of time the resident portal is available",
      "measurementFrequency": "monthly"
    },
    {
      "kpiName": "Recovery test success rate",
      "description": "Share of recovery tests that meet the recovery time objective",
      "measurementFrequency": "quarterly"
    }
  ]
}

Usage Guidelines

When to Use WA Mappings

Cloud migration — Assess readiness before migration
Architecture review — Periodic health check
Incident response — Post-incident improvement
Investment justification — Link business value to technical improvements
Compliance — Meet security and reliability requirements

Best Practices

Start with critical capabilities — Focus WA reviews on business-critical areas
Use business context — Frame WA findings in business impact terms
Create SRM entries — Track improvements through Strategic Response Model
Regular cadence — Conduct WA reviews at least annually
Cross-pillar analysis — Look for improvements that address multiple pillars

Connecting to Strategic Response Model

When WA reviews identify gaps, record the finding as a trigger, the reason to act as a rationale, and the improvements as strategic responses:

{
  "triggers": [
    {
      "triggerID": "TRG-007",
      "label": "Well-Architected Review Finding",
      "description": "Security pillar assessment identified unencrypted data at rest in legacy systems",
      "primaryCategory": "performanceResponse",
      "origin": "internal",
      "affectedEntities": [
        {
          "domainType": "risk",
          "entityID": "RSK-DATA-BREACH-001"
        }
      ]
    }
  ],
  "rationales": [
    {
      "rationaleID": "RAT-004",
      "rationaleTitle": "Close encryption gap",
      "description": "Address security gap to reduce data breach risk",
      "triggerReference": "TRG-007",
      "rationaleType": "riskMitigation",
      "rationaleOrientation": "reactive"
    }
  ],
  "strategicResponses": [
    {
      "responseID": "SR-WA-001",
      "responseTitle": "Encrypt data at rest",
      "responseType": "securityRemediation",
      "responseDescription": "Implement encryption-at-rest for all storage",
      "triggerReferences": [
        "TRG-007"
      ],
      "rationaleReferences": [
        "RAT-004"
      ],
      "affectedDomains": [
        "technology"
      ],
      "status": "planned"
    },
    {
      "responseID": "SR-WA-002",
      "responseTitle": "Data encryption policy",
      "responseType": "policyChange",
      "responseDescription": "Create data encryption policy",
      "triggerReferences": [
        "TRG-007"
      ],
      "rationaleReferences": [
        "RAT-004"
      ],
      "affectedDomains": [
        "policy"
      ],
      "status": "planned"
    }
  ]
}

For Data Engineers

Well-Architected mappings can inform data platform architecture decisions. Use the reliability and security pillars to define requirements for data infrastructure, then track compliance through your data catalog's quality metrics.

Technology Domain — Technology architecture modeling
Risk Management Domain — Risk modeling
Sustainability Domain — Environmental objectives
Strategic Response Model — Tracking improvements

Overview​

What are Well-Architected Frameworks?​

Why Map to Well-Architected?​

Framework Comparison​

Pillar Alignment Across Frameworks​

Domain Mappings by Pillar​

Operational Excellence​

Security​

Reliability​

Performance Efficiency​

Cost Optimization​

Sustainability​

Assessment Integration​

Mapping Triodian to Well-Architected Review​

Assessment Workflow​

Recording Assessment Findings​

TechnologyOne Well-Architected Framework Extension​

Framework Record​

Framework Overview (frameworkOverview)​

Core Principle (corePrinciples)​

Principle Name (principleName)​

Architectural Pillar (architecturalPillars)​

Architectural Component (architecturalComponents)​

Component Type (componentType)​

Implementation Methodology (implementationMethodology)​

Governance Model (governanceModel)​

KPI (kpis)​

Measurement Frequency (measurementFrequency)​

Example: Council Services Platform​

Usage Guidelines​

When to Use WA Mappings​

Best Practices​

Connecting to Strategic Response Model​

Related Documentation​

Overview

What are Well-Architected Frameworks?

Why Map to Well-Architected?

Framework Comparison

Pillar Alignment Across Frameworks

Domain Mappings by Pillar

Operational Excellence

Security

Reliability

Performance Efficiency

Cost Optimization

Sustainability

Assessment Integration

Mapping Triodian to Well-Architected Review

Assessment Workflow

Recording Assessment Findings

TechnologyOne Well-Architected Framework Extension

Framework Record

Framework Overview (`frameworkOverview`)

Core Principle (`corePrinciples`)

Principle Name (`principleName`)

Architectural Pillar (`architecturalPillars`)

Architectural Component (`architecturalComponents`)

Component Type (`componentType`)

Implementation Methodology (`implementationMethodology`)

Governance Model (`governanceModel`)

KPI (`kpis`)

Measurement Frequency (`measurementFrequency`)

Example: Council Services Platform

Usage Guidelines

When to Use WA Mappings

Best Practices

Connecting to Strategic Response Model

Related Documentation