Protected Website Forms
HTTPS, antiforgery validation, input limits, and reCAPTCHA protect public form submissions. Review the safeguards.
What Is the MTConnect Information Model?
The MTConnect information model is the standardized manufacturing vocabulary and set of relationships used to describe equipment, the information it can provide, and the observations an Agent reports.
Four concepts that should not be conflated
| Concept | Its job | What it is not |
|---|---|---|
| Information model | Defines equipment entities, vocabulary, properties, and relationships. | It is not a machine API, Adapter executable, database, or dashboard. |
| MTConnect Adapter | Translates controller, PLC, sensor, or vendor-interface data into observations for an Agent. | It does not define the Standard and does not by itself serve the complete MTConnect response documents. |
| MTConnect Agent | Applies the device model, manages observations, and responds to client requests with MTConnect documents and streams. | It does not guarantee that every desired value exists at the machine source. |
| Protocol and representation | Defines how a client requests and receives MTConnect response documents under the applicable Standard version. | Transport alone does not supply the domain meaning of each observation. |
Device, Component, Composition, DataItem, Asset, and Observation
- DeviceThe modeled piece of equipment
- Components and CompositionsLogical functions and relevant physical parts within the Device
- DataItemsDefinitions of information associated with the applicable Device or Component
- ObservationsReported values, states, or conditions for those DataItems
- AssetsLifecycle information for associated entities such as tools, files, fixtures, or processes
A DataItem belongs at the model entity the information directly describes. Observations reference the DataItem definition so a consumer can interpret both the value and its equipment context. Assets can be associated with equipment while retaining their own lifecycle identity.
Practical CNC example
A CNC machine can be modeled as a Device containing a Controller, a Path, linear axes, and a rotary spindle. The Path may define DataItems for EXECUTION, PROGRAM, and PATH_FEEDRATE; the spindle may define ROTARY_VELOCITY; an axis may define actual POSITION.
When the machine is running, the Agent reports Observations for those definitions with sequence and time context. A cutting-tool Asset can be associated separately. The exact Component hierarchy and DataItem coverage must match the controller interface, machine configuration, and agreed MTConnect version.
Version and source context
MTConnect evolves. Confirm terms, multiplicities, required properties, and representation rules in the version used by the implementation.
Browse the official MTConnect model Open official MTConnect documentationInformation model terms
- Information model
- The structured vocabulary, entities, properties, and relationships used to describe manufacturing equipment and its information.
- Device
- The top-level equipment entity described by an MTConnect device model.
- Component
- A logical or physical part of a Device that can contain Components, Compositions, and DataItems.
- Composition
- A physical part associated with a Component when the additional physical detail is relevant to the model.
- DataItem
- The model definition for a type of information that can be observed for a Device or Component.Explore DataItem terms.
- Observation
- A value, state, or condition reported for a DataItem at a sequence and timestamp in an MTConnect stream.
- Asset
- Information about a mobile or associated entity used in manufacturing, such as a cutting tool, file, fixture, or process definition, identified across its lifecycle.
- Relationship
- A model element that expresses an association between equipment-model entities.
MTConnect information model FAQ
Is the MTConnect information model a transport protocol?
No. The information model defines manufacturing semantics and relationships. An MTConnect Agent serves response documents over the protocol and representation supported by the applicable Standard version.
Is a DataItem the same as an observed value?
No. A DataItem defines what can be observed, including its type and association in the equipment model. An Observation is a reported value, state, or condition for that DataItem.
What is the difference between an Adapter and an Agent?
An Adapter maps machine-specific source data into observations for an Agent. The Agent applies the MTConnect device model and serves MTConnect response documents and streams to consumers.
Do all machine integrations expose the same DataItems?
No. Coverage depends on the equipment, controller interface, configuration, agreed model, and Standard version. A consistent vocabulary does not create data that the source cannot provide.