PhyDiT Ontology

IRI:
http://www.w3id.org/PhyDiT
Date :
04/12/2023
Current version :
1.1
Other visualisation :
Ontology source - WebVowl

Abstract

An ontology to enable creation of physics-inflused description of a digital twin.

Table of Content

  1. Introduction
  2. Classes
  3. Object Properties
  4. Data Properties
  5. Annotation Properties
  6. Namespace Declarations

Introduction

PhyDiT provides the bare-essential classes and relationships which bridge to ontologies for control program description (like CTRLOnt, CDL etc.), system design description (like BRICK, SOSA, etc.), and physical process models (like OntoCAPE, Tubes, Flow etc.)

Classes

actuatorc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Actuator

A device that changes the characterstics of a mechanical form or electrical parameters such that stuff that flows through the conduit or conducting media is influenced in at least one physical variable. Examples include valve actuator which changes the opening in the flow path (thereby changing the pressure drop) and variable frequency drive of a motor which changes the characterstics of the AC waveform.
has super-classes
peripheral componentc
is in domain of
affectsop, at componentop, manipulatesop
is in range of
intended forop

componentc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Component

An electro-mechanical device that from a given abstraction of the system design manages a physical mechanism.
has super-classes
system design conceptc
has sub-classes
peripheral componentc
is in domain of
has portop, managesop
is in range of
at componentop, has partop

control programc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#ControlProgram

A software program that contains the control logic for operating the technical system
has super-classes
control program conceptc
is in domain of
has inputop, has outputop, has parameterop, has program interfaceop, intended forop

control program conceptc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#ControlProgramConcept

A concept related to describing a control program.
has sub-classes
control programc, program interfacec

design specificationc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#DesignSpecification

Specification of nominal, minimum, or maximum value of some physical process variable or sizing or characterstic of the technical system. Examples: minimum air flow rate, maximum current, tank capacity, etc.
has super-classes
system design conceptc
is in domain of
has maximum valueop, has minimum valueop, has nominal valueop, has value specificationop, specifies variableop
is in range of
refers toop, specified byop

inputc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Input

The interface through which a program obtains the state of the controlled process. The state could be a measured physical variable or a signal which could be potentially interesting to the program.
has super-classes
program interfacec
is in domain of
intended forop
is in range of
has inputop

outputc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Output

The interface through with a program acts on the physical process. This is usually done by signaling an actuator.
has super-classes
program interfacec
is in domain of
intended forop
is in range of
has outputop

parameterc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Parameter

A value that is used or produced by the program for or by some intermediate computation.
has super-classes
program interfacec
is in domain of
intended forop, refers toop, specified byop
is in range of
has parameterop

peripheral componentc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#PeripheralComponent

A component that does not play a direct role in the physical process but either observes a process variable it or actuates another component.
has super-classes
componentc
has sub-classes
actuatorc, sensorc

physical mechanismc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#PhysicalMechanism

PhySys (Pim Borst et al) defines this as "a specification of a generic physical principal or law". It covers "source, storage, dissipation, conversion, and distribution (of stuff in a process)". A practical take on this is for the automation application is that a mechanism is enaged in a distinct transformation of the state of a stuff (substance or energy). For example, in pump, the fluids static pressure is increased by transferring kinetic energy from the impeller. Examples include pressurization, combusion, heat transfer, throttling, etc.
has super-classes
physical process conceptc
is in domain of
has dependent variableop, has independent variableop, has variableop
is in range of
has mechanismop, managesop

physical processc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#PhysicalProcess

A physical process formed by a composition of mechanisms. The simplest process may have just one mechanism. A process is formed with an objective of tranforming one or more stuff by passing it through a chain of mechanisms. For example, dehumidification as a process may include first cooling the air below its dew point temperature and then reheating it.
has super-classes
physical process conceptc
is in domain of
has mechanismop
is in range of
managesop

physical process conceptc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#PhysicalProcessConcept

A concept that is used for describing the physical process and its physical mechanisms.
has sub-classes
physical mechanismc, physical processc, physical stuffc, process positionc, process variablec, quantity kindc, unitc, valuec

physical stuffc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#PhysicalStuff

Substance (matter) or energy which is involved in the physical process or mechanism. Examples include, air, water, heat, electrical current, etc.
has super-classes
physical process conceptc
is in range of
deals with stuffop

portc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Port

The physical connection point on a component through which stuff flows in or out.
has super-classes
system design conceptc
is in range of
has portop

process positionc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#ProcessPosition

The position relative to a mechanism when we describe a process variable. This can be namely inlet or outlet. For example, we can say water temperature at inlet of the heat-exchange mechanism.
has super-classes
physical process conceptc
is in range of
has process positionop, positionop

process variablec back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#ProcessVariable

The pyhsical variable that describes the state (quantity) of a stuff. The description of a variable therefore includes the stuff, quantity kind, and measurement units.
has super-classes
physical process conceptc
is in domain of
at componentop, deals with stuffop, has current valueop, has measurement unitop, has process positionop, has quantity kindop, has valueop, positionop, related to portop
is in range of
affectsop, has dependent variableop, has independent variableop, has variableop, manipulatesop, observesop, specifies variableop

program interfacec back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#ProgramInterface

The (software) interface of a control program
has super-classes
control program conceptc
has sub-classes
inputc, outputc, parameterc
is in domain of
is optionaldp
is in range of
has program interfaceop

quantity kindc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#QuantityKind

The state or measurement of a (quantifiable) stuff.
has super-classes
physical process conceptc
is in range of
has quantity kindop

sensorc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Sensor

A device that uses a physical mechanism to measure a quantity and consequently produces a signal that is in a standard form to be an input to a controller hardware. The mechanism is implemented by a sensing element in the sensor. Additional electro-mechanical apparatus (more often electronics) interface with the sensing element to produce a standard signal form (e.g. 0-10V DC, 4-20mA, potential-free contact, etc.)
has super-classes
peripheral componentc
is in domain of
at componentop, observesop
is in range of
intended forop

systemc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#System

A composition of components with a coherent set of process goals.
has super-classes
system design conceptc
is in domain of
has partop, managesop
is in range of
has partop, intended forop

system design conceptc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#SystemDesignConcept

A concept related to describing the structural design of a technical system.
has sub-classes
componentc, design specificationc, portc, systemc

unitc back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Unit

The unit of measurement for a quantity kind.
has super-classes
physical process conceptc
is in range of
has measurement unitop

valuec back to ToC or Class ToC

IRI: http://www.w3id.org/PhyDiT#Value

The measured value (or quantity)
has super-classes
physical process conceptc
is in range of
has current valueop, has maximum valueop, has minimum valueop, has nominal valueop, has valueop, has value specificationop

Object Properties

affectsop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#affects

Represents the physical influence of an actuator on a process variable which could be anywhere in the chain of process mechanisms. For example, when a valve actuator changes the opening in the flow path it influences the flow rate (immediat manipulation), but the influence of the changed flow rate may cause downstream or upstream effect - like changing the outlet temperature at a heat exchanger.
has sub-properties
manipulatesop
has domain
actuatorc
has range
process variablec

at componentop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#atComponent

The relationship between a process variable (and therefore of sensors and actuators that may be observing or manipulating) and a component which manages the process mechanism (to which the process variable is related)

deals with stuffop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#dealsWithStuff

Refers to the physical stuff that process variable is specified for. For example, a variable "air flow rate" deals with "air" as the stuff.
has domain
process variablec
has range
physical stuffc

has current valueop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasCurrentValue

has super-properties
has valueop
has domain
process variablec
has range
valuec

has dependent variableop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasDependentVariable

has super-properties
has variableop
has domain
physical mechanismc
has range
process variablec

has independent variableop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasIndependentVariable

has super-properties
has variableop
has domain
physical mechanismc
has range
process variablec

has inputop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasInput

has super-properties
has program interfaceop
has domain
control programc
has range
inputc

has maximum valueop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasMaximumValue

has super-properties
has value specificationop
has domain
design specificationc
has range
valuec

has measurement unitop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasMeasurementUnit

The engineering units used for measurement.
has domain
process variablec
has range
unitc

has mechanismop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasMechanism

This relation is used to model the situation that a PhysicalProcess is composed of one or more PhysicalMechanism.

has minimum valueop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasMinimumValue

has super-properties
has value specificationop
has domain
design specificationc
has range
valuec

has nominal valueop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasNominalValue

has super-properties
has value specificationop
has domain
design specificationc
has range
valuec

has outputop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasOutput

has super-properties
has program interfaceop
has domain
control programc
has range
outputc

has parameterop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasParameter

has super-properties
has program interfaceop
has domain
control programc
has range
parameterc

has partop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasPart

In this structural specification of a system, this relationship is used for specifying compositions (and aggregations).
has domain
systemc
has range
componentc
systemc

has portop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasPort

A Component may have one or more Ports through with stuff flows in or out.
has domain
componentc
has range
portc

has process positionop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasProcessPosition

Used for indicating "where" a process variable can be observed or manipulated. The position is enumeration off well-known locations like inlet, outlet, bypass, etc.
has equivalent properties
positionop
has domain
process variablec
has range
process positionc

has program interfaceop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasProgramInterface

A control program has one or more interfaces to the outer world.
has sub-properties
has inputop, has outputop, has parameterop
has domain
control programc
has range
program interfacec

has quantity kindop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasQuantityKind

has domain
process variablec
has range
quantity kindc

has valueop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasValue

has sub-properties
has current valueop
has domain
process variablec
has range
valuec

has value specificationop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasValueSpecification

has super-properties
top object property
has sub-properties
has maximum valueop, has minimum valueop, has nominal valueop
has domain
design specificationc
has range
valuec

has variableop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#hasVariable

intended forop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#intendedFor

managesop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#manages

manipulatesop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#manipulates

Represents the immediate physical influence of an actuator on a process variable.
has super-properties
affectsop
has domain
actuatorc
has range
process variablec

observesop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#observes

has domain
sensorc
has range
process variablec

positionop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#position

has equivalent properties
has process positionop
has domain
process variablec
has range
process positionc

refers toop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#refersTo

has equivalent properties
specified byop
has domain
parameterc
has range
design specificationc

related to portop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#relatedToPort

has domain
process variablec

specified byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#specifiedBy

A parameter (Parameter) of a control program can specify its source in the form of a DesignSpecification. For example, a control program might have a parameter which needs to be configured with the maximum input current of a component.
has equivalent properties
refers toop
has domain
parameterc
has range
design specificationc

specifies variableop back to ToC or Object Property ToC

IRI: http://www.w3id.org/PhyDiT#specifiesVariable

A design specification (DesignSpecification) refers to a process variable. For example, the specification for "Maximum current drawn" refers to the electrical current (say, in Amperes) at the inlet terminal of a component. The specification also states the value (see hasMinValue, hasMaxValue, and hasNominalValue)

Data Properties

is optionaldp back to ToC or Data Property ToC

IRI: http://www.w3id.org/PhyDiT#isOptional

Annotation Properties

dateap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/date

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/description

rightsap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/rights

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/title

Namespace Declarations back to ToC

default namespace
http://www.w3id.org/PhyDiT
dc
http://purl.org/dc/elements/1.1/
owl
http://www.w3.org/2002/07/owl#
phydit
http://www.w3id.org/PhyDiT#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
www-w3id-org
http://www.w3id.org/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni .