Comparison of USM with Other Architectural Approaches
Overview
The Unified Service Management (USM) method defines a management architecture for service organizations.
While many frameworks describe enterprise structures, governance models, or best practices, few provide a formal, domain-independent architecture for the management system itself.
This article compares USM with other architectural or quasi-architectural approaches, showing how USM provides the missing systemic layer that connects enterprise strategy, operations, and governance through a single, coherent model.
Comparative Overview
| # | Framework / Approach | Primary Scope | Architectural Nature | Relation to Service Management | Relationship to USM |
|---|---|---|---|---|---|
| 1 | USM (Unified Service Management) | Service management across all domains | Management architecture defining the structure of the management system itself | Core: provides the universal architecture of service delivery | — |
| 2 | TOGAF | Enterprise architecture (business, data, application, technology) | Descriptive enterprise architecture | Describes enterprise structure, not management operation | USM forms the management layer within TOGAF’s Business Architecture |
| 3 | IT4IT | IT value-chain management | Information architecture | Defines information flows for IT management | Fits under USM as an IT-domain information model |
| 4 | ISO Management System Standards (9001, 27001, 20001) | Quality, security, service management, etc. | Normative control architecture | Specify what a management system must contain or comply with | USM provides the structure to implement them coherently |
| 5 | NORA | Dutch public-sector enterprise architecture | Reference architecture public sector | Describes how government services interoperate | USM supplies the internal management backbone; bcDV applies it |
| 6 | bcDV | Basisconcept Dienstverlening (NL), in layer 2 of the NORA model | Applied public sector service architecture | Defines the architecture of public service delivery | Direct domain-specific implementation of USM logic |
| 7 | Zachman Framework | Enterprise modeling taxonomy | Meta-framework | Classifies architecture artifacts, not operations | USM populates the How and Who dimensions for governance |
| 8 | Viable System Model (VSM) | Systemic viability of organizations | Cybernetic system model | Explains recursive management and control | USM operationalizes VSM principles for service delivery |
| 9 | Service Design / Lean Service Creation | Service innovation and customer experience | Design methodology | Focuses on creating or improving services | USM ensures manageability of those designed services |
| 10 | COBIT | IT governance and control | Governance framework | Aligns IT with business objectives | USM provides the operational management layer below COBIT |
1. USM – Unified Service Management
USM defines the service management architecture that governs how any organization can design, deliver, and improve services using only five processes and eight workflows. It provides a closed, non-redundant system of control, independent of domain or technology.
Where most frameworks describe what to manage, USM defines how management itself is structured.
2. TOGAF – The Open Group Architecture Framework
TOGAF structures enterprise architecture into four layers (Business, Data, Application, Technology).
It describes what the enterprise looks like, but assumes management as an internal capability.
USM can be positioned within TOGAF’s Business Architecture as the operational management system that executes enterprise goals.
3. IT4IT – The IT Value-Chain Reference Architecture
IT4IT defines value streams and data objects that support IT management functions such as Plan, Build, Deliver, and Run.
It provides a coherent information architecture for IT operations but not a management architecture.
Within the USM model, IT4IT represents the information view of the IT service domain.
4. ISO Management System Standards
ISO 9001 (quality), 27001 (information security), and 20001 (service management) define requirements for management systems but not their internal structure.
They specify what must exist — policy, planning, control, improvement — yet leave open how to design them as a single integrated system.
USM provides this meta-structure, enabling compliance through one shared architecture.
5. NORA – Nederlandse Overheid Referentie Architectuur
NORA defines the architectural framework for the Dutch public sector.
It describes principles and structures for interoperable digital services among government bodies.
However, it didn't define the internal management system of those organizations until it adopted USM for this purpose in 2022.
USM filled the gap: it provides the internal management architecture on which public service interoperability can rely.
6. bcDV – Basisconcept Dienstverlening
The bcDV model (Basic Concept for Service Delivery) is the Dutch government’s conceptual architecture for services in the NORA.
It directly reflects the USM architecture, adapted to public-sector terminology.
bcDV demonstrates how the same service management logic can be applied to multi-agency collaboration and citizen-facing services.
7. Zachman Framework
Zachman’s framework offers a taxonomy for organizing enterprise architecture artifacts according to six interrogatives (What, How, Where, Who, When, Why) and six perspectives (planner to worker).
It is not a management model but a classification grid.
USM provides the content for the How (process) and Who (roles) cells, linking design and operation.
8. Viable System Model (VSM)
Stafford Beer’s Viable System Model explains how organizations remain viable through recursive control systems (Systems 1–5).
It is a cybernetic reference for management and adaptation.
USM operationalizes these principles in concrete service-management structures: its five processes correspond to the essential feedback and control functions described by VSM. Check this video on how USM supports variety reduction in the VSM (2021).
9. Service Design and Lean Service Creation
Service Design and Lean Service Creation methods help organizations co-create and test new services with users.
They are creative and exploratory frameworks, not management architectures.
USM provides the stable operational structure into which such designed services can be embedded and managed sustainably.
10. COBIT – Control Objectives for Information and Related Technologies
COBIT defines governance and control objectives to align IT with business strategy.
It specifies what should be governed, not how the management system is architected.
USM functions beneath COBIT as the execution architecture that delivers the controlled outcomes COBIT governs.
Synthesis
Across these approaches, a clear pattern emerges:
Enterprise frameworks (TOGAF, NORA, Zachman) describe the organization as a system.
Information and governance frameworks (IT4IT, ISO, COBIT) define what must be controlled or exchanged.
Design frameworks (Service Design, Lean) focus on what should be created.
USM uniquely defines how the system of management itself is constructed — the Service Management Architecture (SMA).
USM thereby acts as the vertical spine that connects strategic intent (governance) to operational execution (workflows), providing an architectural foundation on which all other frameworks can align.