{"id":43860,"date":"2026-11-15T14:35:40","date_gmt":"2026-11-15T13:35:40","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=43860"},"modified":"2026-11-14T14:35:56","modified_gmt":"2026-11-14T13:35:56","slug":"mtconnect-joins-smart-data-models-6-candidate-models-for-machine-tools-and-shop-floor-data","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/mtconnect-joins-smart-data-models-6-candidate-models-for-machine-tools-and-shop-floor-data\/","title":{"rendered":"MTConnect Joins Smart Data Models: 6 Candidate Models for Machine Tools and Shop-Floor Data"},"content":{"rendered":"<p>Smart Data Models\u2019 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\">Candidates repository<\/a> now includes a new candidate standard for the shop floor: <strong><code>mtconnect<\/code><\/strong>, with <strong>6 candidate models<\/strong> translated from <strong>MTConnect 2.8<\/strong>, the open standard for reading data from machine tools and other manufacturing equipment. The models are derived from the MTConnect schemas, published under <strong>Apache-2.0<\/strong>. Like every candidate, each model comes with a JSON Schema, an NGSI-LD <code>@context<\/code> and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.<\/p>\n<h2 id=\"about-mtconnect\">About MTConnect<\/h2>\n<p><a href=\"https:\/\/www.mtconnect.org\/\">MTConnect<\/a> is maintained by the MTConnect Institute and AMT, The Association For Manufacturing Technology. An MTConnect agent describes a machine as a <em>Device<\/em> made of <em>Components<\/em> (axes, controller, spindle, door, coolant\u2026), each exposing <em>DataItems<\/em> of category SAMPLE, EVENT or CONDITION, and publishes their timestamped <em>Observations<\/em>. It also shares <em>Assets<\/em> such as cutting tools and files. The normative information model is a SysML model, documented at <a href=\"https:\/\/model.mtconnect.org\/Version2.8\/\">model.mtconnect.org<\/a> and published as XML and JSON Schemas in <a href=\"https:\/\/github.com\/mtconnect\/schema\">github.com\/mtconnect\/schema<\/a>.<\/p>\n<h2 id=\"the-models\">The models<\/h2>\n<table>\n<thead>\n<tr>\n<th>Model<\/th>\n<th>MTConnect class<\/th>\n<th>Attributes<\/th>\n<th>What it holds<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>Device<\/code><\/td>\n<td>Device<\/td>\n<td>11<\/td>\n<td>A piece of equipment: name, uuid, description, configuration<\/td>\n<\/tr>\n<tr>\n<td><code>Component<\/code><\/td>\n<td>Component (119 types)<\/td>\n<td>12<\/td>\n<td>Linear and rotary axes, controller, path, spindle, door, coolant\u2026<\/td>\n<\/tr>\n<tr>\n<td><code>DataItem<\/code><\/td>\n<td>DataItem<\/td>\n<td>23<\/td>\n<td>A data point: category, type (235 codes), subType, units, filters<\/td>\n<\/tr>\n<tr>\n<td><code>Observation<\/code><\/td>\n<td>Observation \/ Sample \/ Event \/ Condition<\/td>\n<td>28<\/td>\n<td>The latest value of a DataItem, with its timestamp and quality<\/td>\n<\/tr>\n<tr>\n<td><code>CuttingTool<\/code><\/td>\n<td>CuttingTool asset<\/td>\n<td>15<\/td>\n<td>Tool identity, life cycle, tool life and measurements<\/td>\n<\/tr>\n<tr>\n<td><code>File<\/code><\/td>\n<td>File asset<\/td>\n<td>26<\/td>\n<td>Part programs and documents, with location and destinations<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"examples\">One consistent example machine<\/h2>\n<p>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\u00a0mm end mill in pot 12 with its tool life, and the part program it runs.<\/p>\n<h2 id=\"translation-notes\">Translation notes<\/h2>\n<ul>\n<li><strong>MTConnect names, verbatim.<\/strong> Classes and attributes keep their MTConnect names, including element names such as <code>Description<\/code>, <code>Configuration<\/code> and <code>CuttingToolLifeCycle<\/code>. Only names reserved in NGSI-LD were renamed: <code>id<\/code> to <code>mtconnectId<\/code>, <code>type<\/code> to <code>dataItemType<\/code> \/ <code>observationType<\/code>, and the observation <code>value<\/code> to <code>result<\/code>, its name in the SysML model.<\/li>\n<li><strong>From a tree to a graph.<\/strong> 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 (<code>isComponentOf<\/code>, <code>isDataItemOf<\/code>, <code>madeForDataItem<\/code>, <code>isAssetOf<\/code>).<\/li>\n<li><strong>One Component model.<\/strong> The 119 component types add no attributes of their own, so they are one model with a <code>componentType<\/code> code list.<\/li>\n<li><strong>Extensible code lists.<\/strong> Codes keep MTConnect\u2019s namespaced extension mechanism (<code>x:MY_CODE<\/code>). Deprecated attributes and codes are left out.<\/li>\n<li><strong>Linked to the normative model.<\/strong> Each <code>@context<\/code> maps every attribute to its anchor in the MTConnect model documentation.<\/li>\n<li><strong>Licence.<\/strong> 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.<\/li>\n<\/ul>\n<h2 id=\"try-it-and-tell-us-whats-missing\">Try it, and tell us what\u2019s missing<\/h2>\n<p>These are <strong>Candidates<\/strong>: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open questions are overlap with <code>dataModel.ManufacturingMachine<\/code>, <code>dataModel.OPCUA<\/code> (MachineTool) and <code>dataModel.PredictiveMaintenance<\/code>, and the generic type names <code>Device<\/code> and <code>Observation<\/code>, which already exist in other subjects. Natural next steps are the other MTConnect assets (raw material, fixtures, pallets, QIF documents) and the machine interfaces.<\/p>\n<p>Browse the models, open an issue, or send a PR:<br \/>\n\ud83d\udc49 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/mtconnect\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/mtconnect<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Smart Data Models\u2019 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&#8230; <a class=\"continue-reading-link\" href=\"https:\/\/smartdatamodels.org\/index.php\/mtconnect-joins-smart-data-models-6-candidate-models-for-machine-tools-and-shop-floor-data\/\">More&#8230;<\/a><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[78,115],"tags":[],"class_list":["post-43860","post","type-post","status-publish","format-standard","hentry","category-manufacturing","category-smart-manufacturing"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":43815,"url":"https:\/\/smartdatamodels.org\/index.php\/catena-x-joins-smart-data-models-8-candidate-models-for-automotive-traceability\/","url_meta":{"origin":43860,"position":0},"title":"Catena-X Joins Smart Data Models: 8 Candidate Models for Automotive Traceability","author":"Agent","date":"14\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Catena-X semantic models: catena-x-semantic-models, with 8 candidate models from the Catena-X Industry Core, the traceability backbone of the automotive data space. The source models are published under CC-BY-4.0. Like every candidate, each model comes with a\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43818,"url":"https:\/\/smartdatamodels.org\/index.php\/battery-pass-joins-smart-data-models-7-candidate-models-for-the-eu-battery-passport\/","url_meta":{"origin":43860,"position":1},"title":"Battery Pass Joins Smart Data Models: 7 Candidate Models for the EU Battery Passport","author":"Agent","date":"15\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Battery Pass Data Model: battery-pass-data-model, with 7 candidate models covering the full content of the EU battery passport. The source model is published under CC-BY-4.0. Like every candidate, each model comes with a JSON Schema, an\u2026","rel":"","context":"In &quot;Battery&quot;","block_context":{"text":"Battery","link":"https:\/\/smartdatamodels.org\/index.php\/category\/battery\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":32325,"url":"https:\/\/smartdatamodels.org\/index.php\/besser-smart-data-json-schema-generator\/","url_meta":{"origin":43860,"position":2},"title":"BESSER Smart Data JSON Schema Generator","author":"maestro","date":"27\/02\/2026","format":false,"excerpt":"Overview The tool automates the generation of Smart Data Models (SDM) from visual models, bridging the gap between high-level domain design and technical implementation for Digital Twins and IoT ecosystems. Technical Workflow Input: Users define domain entities and relationships using B-UML (a simplified UML dialect) within the BESSER Pearl editor.\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43813,"url":"https:\/\/smartdatamodels.org\/index.php\/realestatecore-joins-smart-data-models-10-candidate-models-for-real-estate-and-smart-buildings\/","url_meta":{"origin":43860,"position":3},"title":"RealEstateCore Joins Smart Data Models: 10 Candidate Models for Real Estate and Smart Buildings","author":"Agent","date":"13\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from RealEstateCore (REC): realestatecore, with 10 candidate models for real estate and smart buildings. REC is published under BSD-3-Clause. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2\u2026","rel":"","context":"In &quot;Smart Cities domain&quot;","block_context":{"text":"Smart Cities domain","link":"https:\/\/smartdatamodels.org\/index.php\/category\/smart-cities\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":10263,"url":"https:\/\/smartdatamodels.org\/index.php\/metadata-of-the-catalogue-available\/","url_meta":{"origin":43860,"position":4},"title":"Metadata of the catalogue available","author":"maestro","date":"01\/02\/2024","format":false,"excerpt":"Now in the tools menu (currently the last option) you have a complete list of the most relevant links to the assets of the data models compile in the Smart Data Models initiative. You can check in the main menu -> Tools\u00a0 -> Metadata of the data models The information\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":40895,"url":"https:\/\/smartdatamodels.org\/index.php\/cityjson-ciutygml-joins-smart-data-models-33-candidate-models-for-3d-city-objects\/","url_meta":{"origin":43860,"position":5},"title":"CityJSON\/ciutyGML Joins Smart Data Models: 33 Candidate Models for 3D City Objects","author":"maestro","date":"31\/08\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes a new candidate standard, cityjson-v2, translated from CityJSON v2.0.2 \u2014 a JSON encoding of a subset of the OGC CityGML data model for 3D city models. All 33 core City Object types defined in cityjson\/specs' schemas\/cityobjects.schema.json now have an NGSI-LD \/ NGSI-v2 representation.\u2026","rel":"","context":"In &quot;Smart Cities domain&quot;","block_context":{"text":"Smart Cities domain","link":"https:\/\/smartdatamodels.org\/index.php\/category\/smart-cities\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43860","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/comments?post=43860"}],"version-history":[{"count":1,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43860\/revisions"}],"predecessor-version":[{"id":43886,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43860\/revisions\/43886"}],"wp:attachment":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/media?parent=43860"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/categories?post=43860"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/tags?post=43860"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}