IT Service Management Ontology (ITSMO)
type: Ontology
version IRI: itsmo
abstract: IT Service Management Ontology (ITSMO) provides a semantic framework for IT Service Providing businesses. ITSMO aligns with ITIL best practices, ISO 20000 standards, and W3C architecture. It is free and easy to extend. **Please see the [ITSMO User Guide](https://purl.org/itsmo) for more info.**
bibliographic citation: IT Service Management Ontology 2 (ITSMO). https://w3id.org/itsmo
creator: Enrico Fagnoni
license: http://creativecommons.org/licenses/by/4.0/
publisher: LinkedData.Center
subject: ITSM, ITIL, IT Service Management
status: accepted
preferred namespace prefix: itsmo
extends: prov#
extends: schema.org
comment: ITSMO encapsulates a typical ITIL service management model: Services and Software are tracked as configuration items, they have defined relationships to providers and customers, and they go through building and deployment processes that rely on underlying infrastructure (as a service). The structure highlights both accountability (who is responsible and who is the customer/provider) and the dependencies among CIs in a CMDB-like environment. ITSMO works best with the [PROV](https://www.w3.org/TR/prov-o) and https://schema.org/ontologies. This vocabulary is the second edition of ITSMO that replaces the deprecated http://ontology.it/itsmo/v1 version
label: ITSMO
incompatible with: v1
prior version: v1
version info: 2.0.0
generated at time: 2025-02-02T05:03:00
funded by: LinkedData.Center
code repository: https://gitlab.com/linkeddatacenter/itsmo
introduction: IT Service Management Ontology (ITSMO) is a formal [vocabulary](http://www.w3.org/standards/semanticweb/ontology) (also known as "schema," "data dictionary," or "ontology") for describing resources related to IT Service Management best practices. The ITSMO namespace is `https://w3id.org/itsmo#` and its usual prefix is `itsmo`. **The goals of ITSMO:** 1. Supporting IT Service Providers and product developers with a formal and shared vocabulary consistent with ITIL and ISO 20000 glossaries. 2. Describing and publishing knowledge about IT managed assets. 3. Being methodology agnostic. 4. Being independent from tools and vendors, allowing flexibility in asset control. 5. Enabling semantic web technologies to [infer](http://www.w3.org/standards/semanticweb/inference) useful insights about configuration items. 6. Serving as a foundation for applications supporting automatic impact analysis and risk management.
type: NamedIndividual
type: ObjectRepository

builtFrom
type: ObjectProperty
sub property of: topObjectProperty
type: FunctionalProperty
domain: Artifact
range: Packaging
comment: A software baseline that contributes to the construction of an artifact.

dependsOn
type: ObjectProperty
domain: ConfigurationItem
range: ConfigurationItem
comment: Indicates a directed dependency between entities.

deployedFrom
type: ObjectProperty
sub property of: topObjectProperty
type: FunctionalProperty
domain: Service
range: Deployment
comment: States baseline that contains the instructions to deploy a specific version of a service in a specific environment.

hasCriticality
type: ObjectProperty
sub property of: topObjectProperty
type: FunctionalProperty
domain: Service
range: Criticality
comment: Represents the relative criticality of an entity.

hasEndpoint
type: ObjectProperty
sub property of: versionOf
type: FunctionalProperty
type: InverseFunctionalProperty
domain: ITService
comment: an URL where the service responds, it is an inverse functional property
editorial note: for WebService this is usually the same of the service URI.

hasOwner
type: ObjectProperty
domain: ObjectRepository
range: Agent
comment: Denotes the legal owner of an asset
editorial note: think it as the owner of a git repository

hasPriority
type: ObjectProperty
sub property of: topObjectProperty
type: FunctionalProperty
domain: Service
range: Priority
comment: A priority qualitative value.

hasResponsible
type: ObjectProperty
domain: ConfigurationItem
range: Agent
comment: Those who do the work to achieve a Process. There is typically one role with a participation type of Responsible, although others can be delegated to assist in the work required.
editorial note: think it as the Git repository maintainer

hasScope
type: ObjectProperty
type: FunctionalProperty
domain: Service
range: ServiceScope
comment: This attribute states the service scope

informedBy
type: ObjectProperty
sub property of: topObjectProperty
domain: Service
range: Service
comment: Indicates a source or entity providing relevant information.

links
type: ObjectProperty
sub property of: topObjectProperty
domain: ConfigurationItem
range: ConfigurationItem
comment: Indicates a connection or relationship between two entities, such as systems, services, or processes.

partOf
type: ObjectProperty
sub property of: dependsOn
type: FunctionalProperty
domain: ConfigurationItem
range: ConfigurationItem
comment: a direct hierarchical dependency

promises
type: ObjectProperty
sub property of: links
domain: ProductSheet
range: FeatureSheet
comment: Represents a formal commitment or assurance provided by a service provider to meet certain standards or deliver specific outcomes.

serviceStatus
type: ObjectProperty
sub property of: topObjectProperty
type: FunctionalProperty
domain: Service
range: ServiceLifeCycleStage
comment: the referenced resource is a stage in the life cycle of the described resource.

versionOf
type: ObjectProperty
sub property of: topObjectProperty
sub property of: specializationOf
type: FunctionalProperty
domain: ConfigurationItem
range: Thing
comment: the referring ConfigurationItem is a total or partial snapshot of a resource state

path
type: DatatypeProperty
type: FunctionalProperty
domain: ConfigurationBaseline
range: string
comment: an optional reference inside the repository structure.
editorial note: in GittLab or GithHub repository can be assigned on a path of a file or directory in a commit or tag tree or

versionTag
type: DatatypeProperty
type: FunctionalProperty
domain: ConfigurationItem
range: string
comment: A label or identifier assigned to a specific reference version of a component, application, or document for tracking and management.
editorial note: in GitLab/GitHub can be a tag or the commit id.

Agent
type: Class
equivalent class: Class
  union of: Agent
  union of: Organization
  union of: Person
comment: An autonomous entity capable of performing actions in a system.

Agreement
type: Class
subclass of: Documentation
comment: A document that describes a formal understanding between two or more parties. An agreement is not legally binding, unless it forms part of a contract.

Artifact
type: Class
subclass of: ConfigurationBaseline
comment: A tangible output from a process, such as a document, container, or a library.

ArtifactRegistry
type: Class
subclass of: ObjectRepository
comment: A repository where software artifacts such as code, configurations, and dependencies are stored, managed, and versioned.

BinaryDistribution
type: Class
subclass of: SoftwarePackage
comment: a software package distributed in compiled form

BuildingConfiguration
type: Class
subclass of: Documentation
comment: Documentation of Any human-made structure used or intended for supporting or sheltering any use or continuous occupancy.

Catalogue
type: Class
subclass of: Documentation
comment: A complete list of items, typically one in alphabetical or other systematic order.

ConfigurationBaseline
type: Class
subclass of: CreativeWork
subclass of: ConfigurationItem
subclass of: Restriction
  on property: versionOf
  qualified cardinality: 1
  on class: ObjectRepository
disjoint with: Service
comment: A Configuration Item and a schema:CreativeWork that represents a portion of a snapshot of an ObjectRepository.
editorial note: think it as a commit tree in a git repository

ConfigurationItem
type: Class
equivalent class: Restriction
  on property: versionOf
  cardinality: 1
comment: Any component or other service asset whose state needs to be managed in order to deliver an IT service. Information about each configuration item is recorded in a record within the configuration management system and is maintained throughout its lifecycle by service asset and configuration management. Configuration items are under the control of change management. They typically include IT services, hardware, software, buildings, and formal documentation such as process documentation and service level agreements.
editorial note: represents an immutable records that identifies a specific state of an object

Container
type: Class
subclass of: Artifact
comment: A structure or system designed to hold or encapsulate elements.

Criticality
type: Class
subclass of: QualitativeValue
comment: A process criticality.

CustomerAgreementPortfolio
type: Class
subclass of: Catalogue
comment: A database or structured document used to manage service contracts or agreements between an IT service provider and its customers. Each IT service delivered to a customer should have a contract or other agreement that is listed in the customer agreement portfolio.

CustomerPortfolio
type: Class
subclass of: Catalogue
comment: A database or structured document used to record all customers of the IT service provider. The customer portfolio is the business relationship manager’s view of the customers who receive services from the IT service provider.

Dataset
type: Class
subclass of: Artifact
comment: A structured collection of data, typically used for analysis or reference.

Deployment
type: Class
subclass of: Plan
subclass of: ProcessDescription
subclass of: Software
comment: a document that describes how to crate an instance of a service or change its status.

Documentation
type: Class
subclass of: ConfigurationBaseline
comment: Information in readable form. A document may be paper or electronic – for example, a policy statement, service level agreement, incident record or diagram of a computer room layout. Dublin Core vocabulary appy to objetc of thes class.
comment: Information in readable form. A document may be paper or electronic – for example, a policy statement, service level agreement, incident record or diagram of a computer room layout. Dublin Core vocabulary applies to objects of this class.

FeatureSheet
type: Class
subclass of: Utility
comment: A document summarizing the key features and functionalities of a service, system, or product for stakeholders or users.

GitHubProject
type: Class
subclass of: ObjectRepository
comment: A project hosted on GitHub, typically containing source code and version control.

GitLabProject
type: Class
subclass of: ObjectRepository
comment: A project hosted on GitLab, typically containing code and version control.

Hardware
type: Class
subclass of: Documentation
comment: The documentation of the physical part of a computer.

ITService
type: Class
subclass of: Service
comment: An IT service is made up of a combination of information technology. It is deployed from a deployment baseline.
editorial note: An IT service is a runtime object that must be linkked with a Deployment software that stores the service configuration and tthe process descriptio (or pipelines) used to deploy it.

Library
type: Class
subclass of: Software
comment: A structured collection of documents, assets, or components that support knowledge sharing, versioning, and reuse within the ITIL framework.

ManagementProcess
type: Class
subclass of: ProcessDescription
comment: Is a process of planning and controlling one or more of activities. Here are some examples: - **Configuration Management**: the process responsible for ensuring that the assets required to deliver services are properly controlled, and that accurate and reliable information about those assets is available when and where it is needed. This information includes details of how the assets have been configured and the relationships betweens [ITIL glossary]. - **Project Management**: the discipline of planning, organizing, securing, and managing resources to achieve specific goals. A project is a temporary endeavor with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables), undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value [Wikipedia]. - **Change Management**: the process responsible for controlling the lifecycle of all changes, enabling beneficial changes to be made with minimum disruption to IT services. [ITIL glossary]

ObjectRepository
type: Class
comment: an service management entity with a state that can be versioned and managed in a repository
editorial note: think it as a git repository

Packaging
type: Class
subclass of: Plan
subclass of: ProcessDescription
subclass of: Software
comment: A document that describes how to create an artifact.

Plan
type: Class
subclass of: Documentation
comment: A structured document or set of instructions outlining objectives, strategies, and actions for achieving specific IT or business goals.

Policy
type: Class
subclass of: Documentation
comment: Formally documented management expectations and intentions. Policies are used to direct decisions, and to ensure consistent and appropriate development and implementation of processes, standards, roles, activities, IT infrastructure etc.

Priority
type: Class
subclass of: QualitativeValue
comment: A process priority

ProcessDescription
type: Class
subclass of: Documentation
comment: A documenthat describes a structured set of activities designed to accomplish a specific objective. A process takes one or more defined inputs and turns them into defined outputs. It may include any of the roles, responsibilities, tools and management controls required to reliably deliver the outputs. A process may define policies, standards, guidelines, activities and work instructions if they are needed.

ProductSheet
type: Class
subclass of: Utility
comment: A document that provides an overview of a product, including its features, capabilities, and benefits, aimed at potential users or stakeholders.

Service
type: Class
subclass of: Service
subclass of: ConfigurationItem
subclass of: Restriction
  on property: deployedFrom
  qualified cardinality: 1
  on class: Deployment
subclass of: Restriction
  on property: hasCriticality
  qualified cardinality: 1
  on class: Criticality
subclass of: Restriction
  on property: hasPriority
  qualified cardinality: 1
  on class: Priority
subclass of: Restriction
  on property: serviceStatus
  qualified cardinality: 1
  on class: ServiceLifeCycleStage
comment: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks.

ServiceCatalogue
type: Class
subclass of: ServicePortfolio
comment: A database or structured document with information about all live IT services, including those available for deployment. The service catalogue is part of the service portfolio and contains information about two types of IT service: customer-facing services that are visible to the business; and supporting services required by the service provider to deliver customer-facing services.

ServiceLifeCycleStage
type: Class
subclass of: Enumeration
comment: A stage in the life of a configuration item. The lifecycle defines the categories for status and the status transitions that are permitted. For example: - The lifecycle of an application includes requirements, design, build, deploy, operate, optimize. - The expanded incident lifecycle includes detection, diagnosis, repair, recovery, and restoration. - The lifecycle of a server may include: ordered, received, in test, live, disposed, etc.

ServiceOption
type: Class
subclass of: Utility
comment: A choice of utility and warranty offered to customers by a core service or service package.

ServicePortfolio
type: Class
subclass of: Catalogue
comment: The complete set of services that is managed by a service provider. The service portfolio is used to manage the entire lifecycle of all services, and includes three categories: service pipeline (proposed or in development), service catalogue (live or available for deployment), and retired services.

ServiceScope
type: Class
subclass of: Enumeration
comment: The service scope (business or infrastructure).

Software
type: Class
subclass of: SoftwareSourceCode
subclass of: ConfigurationBaseline
comment: Software code

SoftwarePackage
type: Class
subclass of: Artifact
comment: An artifact that realizes a software release or a software feature set. For example: "VirtueMart 1.1.x", "Linux LTS 10.04" , "Windows 7 service pack 2", "Apache 2" . Sometime referenced only with "software".

SourceDistribution
type: Class
subclass of: SoftwarePackage
comment: A software package distributed with source code

SystemComponent
type: Class
subclass of: Software
comment: A fundamental building block or element of an IT system, such as hardware, software, or a network component.

Template
type: Class
subclass of: Documentation
comment: A skeleton document or a document to be used as reference for editing another document.

Utility
type: Class
subclass of: Documentation
comment: The functionality offered by a product or service to meet a particular need. Utility can be summarized as ‘what the service does’, and can be used to determine whether a service is able to meet its required outcomes, or is ‘fit for purpose’. The business value of an IT service is created by the combination of utility and warranty.

Warranty
type: Class
subclass of: Documentation
comment: Assurance that a product or service will meet agreed requirements. This may be a formal agreement such as a service level agreement or contract, or it may be a marketing message or brand image. Warranty refers to the ability of a service to be available when needed, to provide the required capacity, and to provide the required reliability in terms of continuity and security. Warranty can be summarized as ‘how the service is delivered’, and can be used to determine whether a service is ‘fit for use’. The business value of an IT service is created by the combination of utility and warranty.

WebService
type: Class
subclass of: WebAPI
subclass of: ITService
comment: A service that communicates over a network using web-based protocols.

Enrico Fagnoni
type: NamedIndividual

LinkedData.Center
type: NamedIndividual

ITSMO User Guide
type: NamedIndividual

BuildProcessDescription
type: NamedIndividual
type: Role
comment: An entity that defines the process for constructing or assembling something.

BusinessService
type: NamedIndividual
type: ServiceScope
conforms to: English 2011 Glossary
comment: An IT service that is visible to the customer. These are normally services that support the customer’s business processes and facilitate one or more outcomes desired by the customer. All live customer-facing services, including those available for deployment, are recorded in the service catalogue along with customer-visible information about deliverables, prices, contact points, ordering and request processes. Other information such as relationships to supporting services and other CIs will also be recorded for internal use by the IT service provider. ITIL 2011 calls this "customer-facing service" while use Business Service as a more general term ( ITIL Business Service could be also a non IT ).

IT Components Taxonomy
type: NamedIndividual
type: ConceptScheme

DeployProcessDescription
type: NamedIndividual
type: Role
comment: An entity responsible for deploying and managing a system or application.

Design
type: NamedIndividual
type: ServiceLifeCycleStage
comment: A plan or specification for constructing an object, system, or service.

HighCriticality
type: NamedIndividual
type: Criticality
comment: an high criticality value

HighPriority
type: NamedIndividual
type: Priority
comment: an high priority

InfrastructureService
type: NamedIndividual
type: ServiceScope
conforms to: English 2011 Glossary
comment: An IT service that is not directly used by the business, but is required by the IT service provider to deliver IT Business Services (for example, a directory service or a backup service). Supporting services may also include IT services only used by the IT service provider. All live supporting services, including those available for deployment, are recorded in the service catalogue along with information about their relationships to Business Services and other CIs. ITIL 2011 call ths also "Supporting Service"

LowCriticality
type: NamedIndividual
type: Criticality
comment: a low criticality value

LowPriority
type: NamedIndividual
type: Priority
comment: a low priority

MediumCriticality
type: NamedIndividual
type: Criticality
comment: A medium criticality value.

MediumPriority
type: NamedIndividual
type: Priority
comment: A medium priority.

Operation
type: NamedIndividual
type: ServiceLifeCycleStage
comment: A specific action or series of actions performed as part of a process.

OperationLevelAgreement
type: NamedIndividual
type: WarranyScope
comment: An agreement outlining operational expectations and responsibilities.

Owner
type: NamedIndividual
type: Role
comment: An entity or individual possessing rights or control over an object or resource.

Responsible
type: NamedIndividual
type: Role
comment: An entity or individual accountable for a particular task or decision.

Retire
type: NamedIndividual
type: ServiceLifeCycleStage
comment: Permanent removal of a configuration item, from the live environment. Being retired is a stage in the lifecycle of many configuration items.

ServiceLevelAgreement
type: NamedIndividual
type: WarranyScope
comment: A formal agreement defining the expected service performance and commitments.

Strategy
type: NamedIndividual
type: ServiceLifeCycleStage
comment: A high-level plan or approach designed to achieve specific long-term objectives, often related to business or IT goals.

SupportService
type: NamedIndividual
type: ServiceScope
comment: A service that provides assistance or maintenance.

Transition
type: NamedIndividual
type: ServiceLifeCycleStage
comment: The phase or process in ITIL that focuses on ensuring that changes, updates, or new services are transitioned smoothly from development to production.

RESTfull APIs
type: NamedIndividual
type: ComponentInterface
broader: Web Resource
definition: Generic HTTP based application program interface compliant with the RESTful architecture.
in scheme: IT Components Taxonomy
notation: API
interface implementation status: optional

External Interface
type: NamedIndividual
type: ComponentInterface
definition: Custom interface used to access data from a legacy system or external data providers through unspecified protocols and formats. (Not a Web Resource)
in scheme: IT Components Taxonomy
notation: EI
interface implementation status: optional

Config Interface
type: NamedIndividual
type: ComponentInterface
definition: Service configuration options passed through environment variables and/or startup options.
in scheme: IT Components Taxonomy
notation: ENV
interface implementation status: mandatory

File System Interface
type: NamedIndividual
type: ComponentInterface
definition: A POSIX compliant sharable file system interface (can be read-only).
in scheme: IT Components Taxonomy
notation: FS
interface implementation status: optional

Linked Data Resource
type: NamedIndividual
type: ComponentInterface
broader: RESTfull APIs
definition: A RESTFul API interface providing Linked Data Resources.
in scheme: IT Components Taxonomy
notation: LDR
interface implementation status: optional

Local Interface
type: NamedIndividual
type: ComponentInterface
broader: Operator Console
definition: A generic user interface on a local client.
in scheme: IT Components Taxonomy
notation: LI
interface implementation status: optional

Log Interface
type: NamedIndividual
type: ComponentInterface
definition: A logging feature compatible with the Docker Log commands.
in scheme: IT Components Taxonomy
notation: LOG
interface implementation status: mandatory

Mongo DB
type: NamedIndividual
type: ComponentInterface
broader: RESTfull APIs
definition: A DB exposing Mongo DB interface.
in scheme: IT Components Taxonomy
notation: MDB
interface implementation status: optional

Mopso Operator Console
type: NamedIndividual
type: ComponentInterface
broader: Local Interface
definition: An Operator Console supporting Mopso SDaaS commands.
in scheme: IT Components Taxonomy
notation: MOC
interface implementation status: optional

Message queue interface
type: NamedIndividual
type: ComponentInterface
broader: RESTfull APIs
definition: Queues exposing RabbitMQ interface.
in scheme: IT Components Taxonomy
notation: MQ
interface implementation status: optional

Operator Console
type: NamedIndividual
type: ComponentInterface
definition: A basic compatible bash shell through ssh protocol providing STDIN and STDOUT.
in scheme: IT Components Taxonomy
notation: OC
interface implementation status: mandatory

Protocol Interface
type: NamedIndividual
type: ComponentInterface
definition: A protocol‐based interface representing endpoints following specific communication protocols.
in scheme: IT Components Taxonomy
notation: PI
interface implementation status: optional

OBS S3 interface
type: NamedIndividual
type: ComponentInterface
broader: RESTfull APIs
definition: Object Block Storage exposing AWS S3 interface.
in scheme: IT Components Taxonomy
notation: S3
interface implementation status: optional

SPARQL QUERY
type: NamedIndividual
type: ComponentInterface
broader: Protocol Interface
definition: An endpoint compliant with the SPARQL 1.1 protocol specification providing the sd:SPARQL11Query and sd:UnionDefaultGraph features.
in scheme: IT Components Taxonomy
notation: SQ
interface implementation status: optional

SPARQL UPDATE
type: NamedIndividual
type: ComponentInterface
broader: RESTfull APIs
definition: An endpoint compliant with the SPARQL 1.1 protocol specification providing the sd:SPARQL11Update and sd:UnionDefaultGraph features, plus support for the SPARQL 1.1 Graph Store HTTP Protocol.
in scheme: IT Components Taxonomy
notation: SU
interface implementation status: optional

Semantic Workbench
type: NamedIndividual
type: ComponentInterface
broader: Web App Interface
definition: A web application providing browsable user access to a knowledge graph.
in scheme: IT Components Taxonomy
notation: SWB
interface implementation status: optional

Web App Interface
type: NamedIndividual
type: ComponentInterface
definition: A web application providing browsable user access.
in scheme: IT Components Taxonomy
notation: WAPP
interface implementation status: optional

Web Resource
type: NamedIndividual
type: ComponentInterface
definition: A generic web resource in the definition of the W3C Web Architecture.
in scheme: IT Components Taxonomy
notation: WR
interface implementation status: optional

ITSMO User Guide

OperationLevelAgreement