Components Package
This section provides semantic information for the Component entity. Figure Components shows the Component model.
Note: See Section Components Schema Diagrams for XML schema.
Components Model
MTConnectDevices provides the physical and logical architecture of a piece of equipment. Figure Device Entity Hierarchy Example provides an overview of the entities used in an example of an MTConnectDevices entity.
Note 1 to entry: See device-entity-hierarchy-example for the XML representation of the same example.
Note 2 to entry: Example above only shows the
ComponentandCompositionlevel hierarchy. For a complete semantics on each kind seeComponentsandCompositions.
A variety of entities are defined to describe a piece of equipment. Some of these entities MUST always be defined for an MTConnectDevices entity, while others are optional and MAY be used, as required, to provide additional structure.
The first, or highest level, entity defined for an MTConnectDevices entity is Devices. Devices is used to group one or more pieces of equipment into a single document. Devices MUST always be defined for an MTConnectDevices entity.
Device is the next entity defined for the MTConnectDevices entity. A separate Device entity is used to identify each piece of equipment for an MTConnectDevices entity. Each Device provides information on the physical and logical structure of the piece of equipment and the data associated with that equipment. Device can also represent any logical grouping of pieces of equipment that function as a unit or any other data source that provides data through an agentsoftware that collects data published from one or more piece(s) of equipment, organizes that data in a structured manner, and responds to requests for data from client software systems by providing a structured response in the form of a response document that is constructed using the semantic data model of a Standard. .
One or more Device entities MUST always be defined for an MTConnectDevices entity.
Components is the next entity defined for the MTConnectDevices entity. Components is used to group information describing lower level physical parts or logical functions of a piece of equipment.
Component is the next level of entity defined for the MTConnectDevices entity. Component is both an abstract type entity and an organizerentity that organizes one or more elements. type entity.
As an abstract entity, Component will always be realized by a specific Component type defined in Component Types. Each Component can also be used to organize information describing lower levelnested element that is below a higher level element. entities or DataItemsobservable observed by a Component that may make Observations associated with the Component.
If lower levelnested element that is below a higher level element. entities are described, these entities are by definition child Component entities of a parent Component. At this next level, the lower levelnested element that is below a higher level element. child Component entities are grouped by Components.
A Component MAY be further decomposed into Composition entities that are grouped by Compositions. These describe the lowest level basic structural or functional building blocks contained within a Component. Data provided for a Component provides more specific meaning when it is associated with one of the Composition entities of the Component. The different Composition types that MAY be defined for the MTConnectDevices entity are defined in Compositions.
This parent-child relationship can continue to any depth required to fully define a piece of equipment.
Note: See Figure Device Entity Hierarchy Example for an example.