Services Domain

The Services domain represents activities or functions provided to internal or external customers to deliver value. It captures service offerings, delivery models, service levels, and the operational components that ensure consistent, quality service delivery.

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

Overview

What is a Service?

A service represents an activity or function that an organization performs for customers, stakeholders, or other parts of the organization to deliver value. Unlike products (which are tangible or deliverable items), services are characterized by:

• Intangibility — Services are activities, not physical items
• Co-creation — Services often involve customer participation
• Variability — Service delivery can vary based on context
• Perishability — Services cannot be stored for later use

Purpose and Value

The Services domain enables architects and planners to:

• Catalog service offerings with consistent structure and metadata
• Define service levels through SLAs and performance commitments
• Map delivery channels by documenting how services reach customers
• Connect to capabilities by linking services to enabling capabilities
• Track performance through service-specific KPIs
• Support governance by linking services to compliance requirements

For Data Engineers

The Services domain maps directly to data platform concepts:

• Service → API, Pipeline, or Data Service
• Service Level → SLA tier or data freshness commitment
• Delivery Model → Batch vs. streaming, self-service vs. managed
• Channels → Consumption methods (API, UI, export)
• Performance Indicators → Service health metrics

Domain Attributes

Core Attributes

Attribute	Type	Description	Required
serviceID	String	Unique identifier for the Service, e.g. SVC-001	✓
title	String	Name or title of the Service	✓
description	String	Detailed explanation of the Service	✓
purpose	String	Intended purpose or benefit	✓
owner	String	Individual or team responsible	✓
orgUnitTitle	String	Organization unit the Service belongs to
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
serviceCategory	Enum	Broad categorization of service type
serviceType	Enum	Specific type of service
deliveryModel	Enum	How the service is delivered
serviceLevel	Enum	Service tier or quality level
serviceLevelAgreements	String	SLAs associated with the Service
channels	Array[Enum]	Channels through which Service is provided
customerFeedback	String	Methods for collecting customer feedback
processFlow	String	Sequence of activities in Service delivery
customerJourney	String	Touchpoints throughout Service delivery
dependencies	String	Other Services, systems, or resources required
stakeholderNetwork	String	Individuals/groups involved in or impacted by Service
performanceIndicators	String	Metrics for measuring Service effectiveness
continuousImprovement	String	Methods for gathering and implementing improvements
resourceManagement	String	Required resources for consistent delivery
riskManagement	String	Identified risks and mitigation strategies
strategicAlignment	String	How Service supports Organization objectives
qualityFramework	String	Standards and procedures for Service quality
valueStream	String	How value flows through Service delivery
complianceRequirements	Array[Enum]	Regulatory requirements affecting Service
targetAudience	Array[Enum]	Primary users or beneficiaries
availability	String	Service availability schedule
capacity	String	Service capacity limits and scaling
pricing	String	Pricing structure and cost model
competitiveAdvantage	String	What differentiates this service
integrations	String	Systems the service integrates with
automationLevel	Enum	Degree of automation in delivery (shared automation list)
scalability	String	Service scaling capabilities
lifecycle	Enum	Current stage in service lifecycle (shared lifecycle list)
innovationOpportunities	String	Areas for service innovation
sustainability	String	Environmental considerations
accessibility	String	Accessibility features
security	String	Security measures and protocols
businessModel	Enum	Revenue or value creation model
customerSegments	Array[Enum]	Target customer segments
valueProposition	String	Core value delivered
successMetrics	String	Key metrics defining service success
changeManagement	String	Approach to managing service changes
knowledgeManagement	String	How service knowledge is captured and shared
marketPosition	Enum	Desired market position in the service category: marketLeader, marketChallenger, marketFollower, nichePlayer, disruptor, emergingPlayer
investmentLevel	Enum	Required investment level for service delivery: highInvestment, mediumInvestment, lowInvestment, minimalInvestment
stakeholderImpact	String	Impact on key stakeholders
parentService	String	Parent service this is derived from
parentServiceID	String	ID of the parent service this is derived from
childServices	String	Child services derived from this
costs	String	Development, maintenance, and operational costs
revenueModel	String	How the service generates revenue or value
adoptionMetrics	String	Usage and adoption measurements
qualityMetrics	String	Quality assessment measures
userBase	String	Description of current user base
usage	String	How the service is typically used
relatedServices	String	Services that are related or linked
relatedServiceIDs	Array[String]	IDs of related services
technologyStack	String	Underlying technologies used
improvementOpportunities	String	Areas for enhancement or improvement
roadmap	String	Future development plans
localization	String	Multi-language and regional adaptations
serviceFeatures	Array[Object]	Specific features or components of the service (see Service Feature)

A service record may not carry fields other than those listed above.

Enumeration Values

Service Category (serviceCategory)

Value	Description	Example
customerService	Services directly interfacing with external customers	Customer support, sales assistance, account management
supportService	Internal or external support and assistance	Technical support, help desk, maintenance services
operationalService	Core operational and business process services	Manufacturing, logistics, quality control
administrativeService	Administrative and business management services	HR services, finance, procurement, legal
digitalService	Technology-enabled and digital services	Web applications, mobile apps, API services
professionalService	Expert knowledge and consulting services	Consulting, training, advisory, project management
infrastructureService	Foundational technology and facility services	IT infrastructure, facilities management, utilities

Service Type (serviceType)

Value	Description	Example
transportation	Movement and logistics services	Freight, passenger, delivery, shipping
consulting	Advisory and expertise services	Strategic consulting, technical advisory
maintenance	Upkeep and repair services	Equipment maintenance, facility maintenance
support	Assistance and help services	Customer support, technical support
platform	Platform-based services	Cloud platforms, SaaS
apiService	Application programming interface services	REST APIs, data services
analytics	Data analysis and intelligence services	Business intelligence, reporting
training	Education and training services	Workshops, courses, certification
monitoring	Monitoring and alerting services	System monitoring, performance tracking
integration	System integration services	Data integration, API integration

Delivery Model (deliveryModel)

Value	Description	Example
selfService	Customer performs service independently	Online portals, ATMs
assistedService	Service with staff assistance	Help desk, in-person support
automatedService	Fully automated service delivery	Chatbots, automated processing
onDemand	Service available when requested	API calls, streaming
scheduled	Service at scheduled times	Batch processing, appointments
continuous	Always-on service delivery	24/7 monitoring, real-time feeds
hybrid	Combination of delivery models	Self-service with escalation

Service Level (serviceLevel)

Value	Description	Example
basic	Entry-level service tier	Standard support, basic features
standard	Standard service tier	Business hours support, core features
premium	Enhanced service tier	Priority support, advanced features
enterprise	Enterprise-grade service	Dedicated support, custom SLAs
missionCritical	Highest availability requirements	99.99% uptime, immediate response

Service Channels (channels)

The channels through which the service is delivered.

Value	Description	Example
onlinePortal	Web-based service access	Customer portal, self-service website
mobileApp	Mobile application access	iOS/Android apps
phone	Telephone-based service	Call center, phone support
inPerson	Face-to-face service	Branch visits, on-site service
api	Programmatic access	REST API, webhook
email	Email-based service	Email support, notifications
chat	Real-time chat service	Live chat, messaging
socialMedia	Social media channels	Support via social platforms
partnerChannel	Delivered through partners	Reseller or partner-delivered service

Feature Channels (serviceFeature.channels)

A service feature has its own channels list, describing how that feature reaches its users.

Value	Description	Example
webPortal	Feature available in a web portal	Dashboard page
mobileApplication	Feature available in a mobile application	In-app feature
smsAlerts	Feature delivered as SMS alerts	Text notifications
emailNotifications	Feature delivered as email notifications	Alert emails
apiIntegration	Feature available through an API	Webhook, API endpoint
phone	Feature available by telephone	Phone booking line
chat	Feature available through chat	Chat assistant

Target Audience (targetAudience)

Value	Description
internalEmployees	Organization's internal staff
externalCustomers	External paying customers
partners	Business partners
vendors	Suppliers and vendors
government	Government agencies
public	General public

Automation Level (automationLevel)

automationLevel uses the shared automation level list from common.schema.json.

Value	Description	Example
manual	Fully manual service delivery	Hand-processed requests
semiAutomated	Partially automated	Workflow with manual steps
highlyAutomated	Mostly automated	Automated with exceptions handling
fullyAutomated	End-to-end automation	No human intervention
aiEnabled	Automation that uses AI to make or support decisions	AI triage of service requests

Lifecycle Stage (lifecycle)

lifecycle uses the shared lifecycle stage list from common.schema.json.

Value	Description	Example
ideation	Service idea being explored	Opportunity assessment
planning	Service being planned	Requirements gathering
design	Service being designed	Service blueprint
development	Service under development	Building and testing
implementation	Service being implemented	Rollout preparation
launch	Service being introduced	Go-live, pilot
operational	Service in active operation	Production
enhancement	Service being improved	Feature additions
optimization	Service being tuned for performance or cost	Efficiency improvements
retirement	Service being decommissioned	Sunset

Business Model (businessModel)

Value	Description	Example
feeForService	Charge per service instance	Consulting hours, transactions
subscription	Recurring subscription	Monthly SaaS fee
usageBased	Pay per usage	API calls, data volume
freemium	Free with paid upgrades	Basic free, premium paid
commission	Revenue share model	Marketplace fees
license	Licensing model	Software licensing
supportModel	Support-based revenue	Maintenance contracts

Service Feature Elements

Service Feature (serviceFeature)

Attribute	Type	Description	Required
title	String	The name or title of the Service feature	✓
description	String	A detailed explanation of what the Service feature entails	✓
purpose	String	The intended purpose or benefit of the Service feature	✓
owner	String	The individual or team responsible for the Service feature
orgUnitTitle	String	The Organization unit(s) involved in the Service feature
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
featureType	Enum	Type of service feature (see below)
priority	Enum	Business and development priority (shared priority list: low, medium, high, critical)
complexity	Enum	Implementation and operational complexity (shared list: simple, moderate, complex, highlyComplex)
serviceLevelAgreements	String	The SLAs associated with the Service feature
channels	Array[Enum]	Channels through which the feature is provided (see Service Channels)
customerFeedback	String	Methods for collecting feedback on this feature
userExperience	String	Description of user interaction and experience
performanceMetrics	String	Metrics specific to this feature
dependencies	String	Technical or business dependencies for this feature
integrationRequirements	String	Integration needs with other systems or services
securityRequirements	String	Security specifications for the feature
accessibilityFeatures	String	Accessibility accommodations
businessValue	String	Business impact and value delivered
implementationTimeline	String	Development and rollout timeline
maintenanceRequirements	String	Ongoing maintenance and support needs
scalabilityConsiderations	String	Scaling capabilities and constraints
complianceAspects	String	Regulatory and compliance considerations
innovationOpportunities	String	Future enhancement possibilities
rolloutStrategy	Enum	Feature rollout approach: bigBang, phased, canary, beta, geographic, segment
targetAudience	String	Specific users or groups for the feature
successMetrics	String	Metrics to measure feature success
feedback	String	User feedback and feature reception
costs	String	Development and operational costs for the feature
riskFactors	String	Key risks to feature success

A service feature must have title, description and purpose, and may not carry other fields.

Feature Type (featureType)

Value	Description
coreFeature	Included in every tier of the service
premiumFeature	Available in higher service tiers
addOn	Optional extra, enabled separately
integration	Connects the service to other systems
automation	Automates part of the service
enhancement	Improves existing functionality

Domain Relationships

The Services domain integrates with other metamodel domains:

Target Domain	Relationship Type	Description
Capabilities	Realization	Capabilities are realized through services
Products	Delivery	Products may be delivered as services
Customer	Consumption	Customers consume services
Organization	Provision	Organization units provide services
Value Stream	Contribution	Services contribute to value streams
Information	Exchange	Services exchange information
Technology	Enablement	Technology enables service delivery
Performance	Measurement	Performance metrics measure service effectiveness
Policy	Governance	Policies govern service delivery
Stakeholder	Engagement	Stakeholders engage with services

Examples

Example 1: Freight Transportation Service

{
  "serviceID": "SVC-001",
  "title": "Rail Freight Transportation Service",
  "description": "Comprehensive freight transportation service via the national rail network",
  "purpose": "To provide reliable, cost-effective freight transportation solutions",
  "owner": "James Wilson, Director of Freight Operations",
  "orgUnitTitle": "Freight Operations Division",
  "serviceCategory": "operationalService",
  "serviceType": "transportation",
  "deliveryModel": "scheduled",
  "serviceLevel": "premium",
  "serviceLevelAgreements": "98% on-time delivery, maximum delay of 2 hours for priority shipments",
  "channels": [
    "onlinePortal",
    "phone",
    "api",
    "email"
  ],
  "customerFeedback": "Post-delivery satisfaction surveys, annual customer interviews",
  "processFlow": "Booking request → Cargo inspection → Loading → Transport → Tracking → Delivery",
  "customerJourney": "Inquiry → Quote → Contract → Scheduling → Tracking → Delivery → Invoice",
  "dependencies": "Track maintenance services, locomotive fleet management",
  "stakeholderNetwork": "Shippers, receivers, rail network operations team",
  "performanceIndicators": "On-time delivery percentage, customer satisfaction score",
  "continuousImprovement": "Quarterly performance reviews, customer feedback integration",
  "resourceManagement": "Locomotive allocation system, crew scheduling software",
  "riskManagement": "Weather contingency plans, security protocols for high-value cargo",
  "strategicAlignment": "Supports national freight mobility goals, carbon reduction initiatives",
  "qualityFramework": "ISO 9001 certified operations, monthly safety inspections",
  "valueStream": "Initial customer inquiry → Contract → Service delivery → Invoice",
  "complianceRequirements": [
    "federalRegulations",
    "safetyRequirements",
    "environmentalStandards"
  ],
  "targetAudience": [
    "externalCustomers",
    "partners"
  ],
  "availability": "24/7 tracking, business hours customer support, emergency on-call",
  "capacity": "Maximum 500 concurrent shipments, auto-scaling for peak seasons",
  "pricing": "Per-mile rates, volume discounts, premium service surcharges",
  "competitiveAdvantage": "Real-time tracking with 99.5% accuracy, carbon-neutral options",
  "integrations": "ERP systems, warehouse management, GPS tracking platforms",
  "automationLevel": "semiAutomated",
  "scalability": "Horizontally scalable with cloud infrastructure, seasonal capacity planning",
  "lifecycle": "operational",
  "innovationOpportunities": "AI-powered route optimization, blockchain-based tracking",
  "sustainability": "Carbon offset programs, electric vehicle integration",
  "accessibility": "Multi-language support, disability-friendly interfaces",
  "security": "End-to-end encryption, role-based access control",
  "businessModel": "feeForService",
  "customerSegments": [
    "enterprise",
    "smb",
    "government"
  ],
  "valueProposition": "Reduce transportation costs by 25% while improving delivery reliability",
  "successMetrics": "Customer retention rate, Net Promoter Score, first-call resolution",
  "changeManagement": "Phased rollouts, customer communication, training programs",
  "knowledgeManagement": "Service documentation, best practices database, training materials"
}

Example 2: API Data Service

{
  "serviceID": "SVC-006",
  "title": "Track Condition Data API",
  "description": "RESTful API providing real-time and historical track condition data",
  "purpose": "Enable third-party applications and internal systems to access track condition information",
  "owner": "API Platform Team",
  "orgUnitTitle": "Digital Services Division",
  "serviceCategory": "digitalService",
  "serviceType": "apiService",
  "deliveryModel": "onDemand",
  "serviceLevel": "enterprise",
  "serviceLevelAgreements": "99.9% uptime, <100ms response time, 1000 requests/minute rate limit",
  "channels": [
    "api"
  ],
  "targetAudience": [
    "externalCustomers",
    "partners",
    "internalEmployees"
  ],
  "availability": "24/7 with scheduled maintenance windows",
  "automationLevel": "fullyAutomated",
  "security": "OAuth 2.0 authentication, TLS 1.3 encryption, API key rotation",
  "businessModel": "usageBased",
  "valueProposition": "Real-time track data integration with <100ms latency",
  "serviceFeatures": [
    {
      "title": "Real-time Track Conditions",
      "description": "Live feed of track condition measurements",
      "purpose": "Enable real-time operational decisions",
      "featureType": "coreFeature",
      "targetAudience": "All service tiers"
    },
    {
      "title": "Historical Data Query",
      "description": "Query historical track condition data up to 5 years",
      "purpose": "Support trend analysis and planning",
      "featureType": "premiumFeature",
      "targetAudience": "Premium and Enterprise tiers"
    },
    {
      "title": "Webhook Notifications",
      "description": "Push notifications for track condition alerts",
      "purpose": "Proactive alerting for critical conditions",
      "featureType": "addOn",
      "channels": [
        "apiIntegration"
      ],
      "targetAudience": "Customers who enable the add-on"
    }
  ]
}

Implementation Guidelines

Service Design Best Practices

1. Start with customer needs — Design services around customer journeys and outcomes
2. Define clear SLAs — Establish measurable service level commitments
3. Map dependencies — Document all service dependencies explicitly
4. Plan for scale — Include capacity and scalability considerations
5. Enable feedback — Build in mechanisms for continuous improvement

Service Blueprint Pattern

OpenMetadata Integration

For Data Platform Teams

When integrating with OpenMetadata, map Service entities as follows:

Triodian Element	OpenMetadata Entity	Notes
Digital Service	Messaging Service /API	For API services
Data Service	Pipeline /Dashboard	For data delivery services
Service Level	SLA Custom Property	Track SLA commitments
Channels	Service Connection	How service is consumed
Performance Indicators	Metrics	Service health metrics

# Example: Map Service to OpenMetadata Messaging Service
def create_om_service(service):
    """
    Map Triodian Service to OpenMetadata Service entity
    """
    if service.get("serviceType") == "apiService":
        return {
            "serviceType": "messagingServices",
            "name": service["serviceID"],
            "displayName": service["title"],
            "description": service["description"],
            "connection": {
                "config": {
                    "type": "CustomMessaging",
                    "sourcePlatform": "Triodian"
                }
            },
            "tags": [
                {"tagFQN": f"ServiceCategory.{service['serviceCategory']}"},
                {"tagFQN": f"ServiceLevel.{service['serviceLevel']}"}
            ],
            "extension": {
                "sla": service.get("serviceLevelAgreements"),
                "deliveryModel": service.get("deliveryModel"),
                "automationLevel": service.get("automationLevel")
            }
        }

Schema Reference

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

---

Previous: Products Domain | Next: Information Domain