css
type: Ontology
version IRI: http://www.w3id.org/hsu-aut/css/1.0.1
comment: An ontology for the Capability, Skill and Service reference model defined by Plattform Industrie 4.0. See https://www.plattform-i40.de/IP/Redaktion/DE/Downloads/Publikation/CapabilitiesSkillsServices.html for a description of the abstract reference model.

Capability
type: Class
disjoint with: Resource
disjoint with: ServiceOffer
disjoint with: ServiceProvider
disjoint with: ServiceRequester
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
comment: Implementation-independent specification of a function in industrial production to achieve an effect in the physical or virtual world. Notes: - A capability can be restricted by constraints. - A capability can be specified by capability properties. - A capability can be realized by skills

CapabilityConstraint
type: Class
disjoint with: Resource
disjoint with: Service
disjoint with: ServiceOffer
disjoint with: ServiceProvider
disjoint with: ServiceRequester
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
comment: Condition imposed on a capability that further details its applicability. Notes: - A capability constraint can be formulated as one of the following three constraint types: ▪ A precondition, i.e., a condition that must hold before a function can be executed. ▪ A postcondition, i.e., a condition that must hold after a function has been executed. ▪ An invariant, i.e., a condition that must hold during the execution of a function. - A capability constraint restricts the values of the properties associated with the respective capability. - A capability constraint can involve one or more properties

Process
type: Class
disjoint with: Resource
disjoint with: Service
disjoint with: ServiceOffer
disjoint with: ServiceProvider
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
comment: Production-relevant activity at any level of granularity that might affect materials and is performed by resources. Notes: - In general, a process can be decomposed into sub-processes or single activities. - A process can require capabilities to express that any suitable resource used for performing this process needs to provide compatible capabilities. - A process step relates to materials that constitute either input or output for the processing in this step

Product
type: Class
disjoint with: Service
disjoint with: ServiceOffer
disjoint with: ServiceProvider
disjoint with: ServiceRequester
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
comment: Physical object being used as an input or created as an output of a production process. Notes: - The term Product may be used for objects in various states of manufacturing and may be seen as a generic term for raw materials, work in process and finished goods. Consumable supplies such as fuel, lubricants or cleaning agents may also be regarded as products. Furthermore, both purchased parts as well as parts manufactured in-house may be regarded as products. - Besides the actual product, there can be additional artifacts related to that product that are created and used in different life cycle phases to specify the product. ▪ 3D/CAD models ▪ specifications ▪ BOM - A Service Requester may use these additional artifacts to formulate requirements against products.

Property
type: Class
disjoint with: Resource
disjoint with: Service
disjoint with: ServiceOffer
disjoint with: ServiceProvider
disjoint with: ServiceRequester
disjoint with: Skill
disjoint with: SkillInterface
comment: Quality or characteristic inherent in or ascribed to any CSS model element Notes: - Properties may be used to describe and differentiate all kinds of PPR entities (i.e., products, process steps, resources) - Capabilities, services and offers are specified by properties in order to detail their description with regard to certain entities (e.g. products, process steps, resources)

Resource
type: Class
disjoint with: Service
disjoint with: ServiceOffer
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
disjoint with: StateMachine
comment: Entity capable of performing functions specified as Capabilities and potentially implemented as Skills. Notes - A production resource may consist of hardware, software or both - A production resource may only provide capabilities (i.e. when engineering a resource, for planning purposes) and may additionally provide skills for automatic execution of the specified function. - A human becomes a Production Resource, if that person is able to perform a function specified as a capability.

Service
type: Class
disjoint with: ServiceOffer
disjoint with: ServiceProvider
disjoint with: ServiceRequester
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
disjoint with: StateMachine
comment: Description of the commercial aspects and means of provision of offered capabilities. Notes: - The term “service” should be understood in the sense of economics and shall not be confused with e.g., web services. - The capabilities and means of provisions are specified by properties - A service is demanded by service requesters and provided by a service provider - A service is an input for an offer proposed by

ServiceOffer
type: Class
disjoint with: ServiceProvider
disjoint with: ServiceRequester
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
disjoint with: StateMachine
comment: Proposal for a binding contract from the Service Provider to execute one or more particular services that a ServiceRequester can receive and accept. Notes: - A ServiceOffer should determine the commercial aspects of the service provision and may remain valid for a certain period of time. - An Offer may consist of partial offers proposed by different service providers

ServiceProvider
type: Class
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
disjoint with: StateMachine
comment: Provides Services and can propose ServiceOffers to ServiceRequesters.

ServiceRequester
type: Class
disjoint with: Skill
disjoint with: SkillInterface
disjoint with: SkillParameter
disjoint with: StateMachine
comment: Demands Services under particular commercial aspects by providing either a specification of services or a specification of product requirements.

Skill
type: Class
disjoint with: SkillParameter
comment: Executable implementation of an encapsulated (automation) function specified by a Capability. Notes: - A skill must have a skill interface. - One capability can be realized by more than one skill. - A skill may have any number of SkillParameters. - A skill’s behavior conforms to a state machine. - A skill controls a process step

SkillInterface
type: Class
disjoint with: SkillParameter
disjoint with: StateMachine
comment: Access point to configure, control and monitor a skill. Notes: - A skill interface exposes interaction points to be used by other external systems (e.g. MES, other skills). - A skill interface exposes the state machine of a skill so that skill states can be monitored and transitions triggered. - A skill interface exposes the parameters of a skill so that they can be written and read.

SkillParameter
type: Class
disjoint with: StateMachine
comment: Data unit to configure, control and monitor the execution of a skill. Notes: - Skill parameters might be used as in- /output parameters - Skill parameters might be used as results - Skill parameters might have a relation or be equivalent to capability properties