Smart Data Models’ Candidates repository now includes a new candidate standard for the shop floor: mtconnect, with 6 candidate models translated from MTConnect 2.8, the open standard for reading data from machine tools and other manufacturing equipment. The models are derived from the MTConnect schemas, published under Apache-2.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.
About MTConnect
MTConnect is maintained by the MTConnect Institute and AMT, The Association For Manufacturing Technology. An MTConnect agent describes a machine as a Device made of Components (axes, controller, spindle, door, coolant…), each exposing DataItems of category SAMPLE, EVENT or CONDITION, and publishes their timestamped Observations. It also shares Assets such as cutting tools and files. The normative information model is a SysML model, documented at model.mtconnect.org and published as XML and JSON Schemas in github.com/mtconnect/schema.
The models
| Model | MTConnect class | Attributes | What it holds |
|---|---|---|---|
Device |
Device | 11 | A piece of equipment: name, uuid, description, configuration |
Component |
Component (119 types) | 12 | Linear and rotary axes, controller, path, spindle, door, coolant… |
DataItem |
DataItem | 23 | A data point: category, type (235 codes), subType, units, filters |
Observation |
Observation / Sample / Event / Condition | 28 | The latest value of a DataItem, with its timestamp and quality |
CuttingTool |
CuttingTool asset | 15 | Tool identity, life cycle, tool life and measurements |
File |
File asset | 26 | Part programs and documents, with location and destinations |
One consistent example machine
The public MTConnect demo agent states no licence for its data, so the examples are synthetic, and say so. They follow one fictitious 3-axis vertical machining centre: the device, its X axis, the X actual-position data item in millimetres, its latest observation, a 10 mm end mill in pot 12 with its tool life, and the part program it runs.
Translation notes
- MTConnect names, verbatim. Classes and attributes keep their MTConnect names, including element names such as
Description,ConfigurationandCuttingToolLifeCycle. Only names reserved in NGSI-LD were renamed:idtomtconnectId,typetodataItemType/observationType, and the observationvaluetoresult, its name in the SysML model. - From a tree to a graph. MTConnect nests components and data items inside the device. Here each is an entity that points to its parent with Relationships named after the SysML associations (
isComponentOf,isDataItemOf,madeForDataItem,isAssetOf). - One Component model. The 119 component types add no attributes of their own, so they are one model with a
componentTypecode list. - Extensible code lists. Codes keep MTConnect’s namespaced extension mechanism (
x:MY_CODE). Deprecated attributes and codes are left out. - Linked to the normative model. Each
@contextmaps every attribute to its anchor in the MTConnect model documentation. - Licence. The schema files are Apache-2.0. The specification documents themselves allow redistribution only without modification, so nothing is copied from them. A few gaps in the 2.8 JSON Schemas (missing File destinations, escaped unit codes) are fixed and documented in the metadata.
Try it, and tell us what’s missing
These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open questions are overlap with dataModel.ManufacturingMachine, dataModel.OPCUA (MachineTool) and dataModel.PredictiveMaintenance, and the generic type names Device and Observation, which already exist in other subjects. Natural next steps are the other MTConnect assets (raw material, fixtures, pallets, QIF documents) and the machine interfaces.
Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/mtconnect

