MTConnect

R
Standard
Part 2.0 – Devices Information Model
Version 1.6.0

Prepared for: MTConnect Institute

Prepared on: July 15, 2020

MTConnect R
is a registered trademark of AMT - The Association for Manufacturing Technology. Use of
MTConnect is limited to use as specified on http://www.mtconnect.org/.
 July 15, 2020

MTConnect Specification and Materials

The Association for Manufacturing Technology (AMT) owns the copyright in this MT-
Connect Specification or Material. AMT grants to you a non-exclusive, non-transferable,
revocable, non-sublicensable, fully-paid-up copyright license to reproduce, copy and re-
distribute this MTConnect Specification or Material, provided that you may only copy or
redistribute the MTConnect Specification or Material in the form in which you received
it, without modifications, and with all copyright notices and other notices and disclaimers
contained in the MTConnect Specification or Material.

If you intend to adopt or implement an MTConnect Specification or Material in a product,

whether hardware, software or firmware, which complies with an MTConnect Specifi-
cation, you shall agree to the MTConnect Specification Implementer License Agreement
(“Implementer License”) or to the MTConnect Intellectual Property Policy and Agreement
(“IP Policy”). The Implementer License and IP Policy each sets forth the license terms and
other terms of use for MTConnect Implementers to adopt or implement the MTConnect
Specifications, including certain license rights covering necessary patent claims for that
purpose. These materials can be found at www.MTConnect.org, or or by contacting
mailto:[email protected].

MTConnect Institute and AMT have no responsibility to identify patents, patent claims or
patent applications which may relate to or be required to implement a Specification, or to
determine the legal validity or scope of any such patent claims brought to their attention.
Each MTConnect Implementer is responsible for securing its own licenses or rights to any
patent or other intellectual property rights that may be necessary for such use, and neither
AMT nor MTConnect Institute have any obligation to secure any such rights.

This Material and all MTConnect Specifications and Materials are provided “as is” and
MTConnect Institute and AMT, and each of their respective members, officers, affiliates,
sponsors and agents, make no representation or warranty of any kind relating to these ma-
terials or to any implementation of the MTConnect Specifications or Materials in any prod-
uct, including, without limitation, any expressed or implied warranty of noninfringement,
merchantability, or fitness for particular purpose, or of the accuracy, reliability, or com-
pleteness of information contained herein. In no event shall MTConnect Institute or AMT
be liable to any user or implementer of MTConnect Specifications or Materials for the
cost of procuring substitute goods or services, lost profits, loss of use, loss of data or any
incidental, consequential, indirect, special or punitive damages or other direct damages,
whether under contract, tort, warranty or otherwise, arising in any way out of access, use
or inability to use the MTConnect Specification or other MTConnect Materials, whether
or not they had advance notice of the possibility of such damage.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 i

Table of Contents
1 Purpose of This Document 2

2 Terminology and Conventions 3

2.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 MTConnect References . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 Devices Information Model 12

4 Structural Elements for MTConnectDevices 14

4.1 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4 Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.1 XML Schema Structure for Component . . . . . . . . . . . . . . 19
4.4.2 Attribute for Component . . . . . . . . . . . . . . . . . . . . . . 21
4.4.3 Elements of Component . . . . . . . . . . . . . . . . . . . . . . 24
4.4.3.1 Description for Component . . . . . . . . . . . . . . . 24
4.4.3.2 Configuration for Component . . . . . . . . . . . . . . 26
4.4.3.3 DataItems for Component . . . . . . . . . . . . . . . . 27
4.4.3.4 Components within Component . . . . . . . . . . . . . 28
4.4.3.5 Compositions for Component . . . . . . . . . . . . . . 28
4.4.3.6 References for Component . . . . . . . . . . . . . . . . 28
4.5 Compositions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.6 Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.6.1 XML Schema Structure for Composition . . . . . . . . . . . . . . 30
4.6.2 Attributes for Composition . . . . . . . . . . . . . . . . . . . . . 31
4.6.3 Elements of Composition . . . . . . . . . . . . . . . . . . . . . . 32
4.6.3.1 Description for Composition . . . . . . . . . . . . . . . 33
4.7 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.8 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.8.1 ComponentRef . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.8.2 DataItemRef . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5 Component Structural Elements 39

5.1 Axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.1.1 Cartesian Coordinate Naming Conventions . . . . . . . . . . . . 41
5.1.1.1 Linear Motion . . . . . . . . . . . . . . . . . . . . . . 42
5.1.1.2 Rotary Motion . . . . . . . . . . . . . . . . . . . . . . 42
5.1.2 Articulated Machine Control Systems . . . . . . . . . . . . . . . 42
5.1.3 Articulated Machine Axis Names . . . . . . . . . . . . . . . . . 42

ii
 July 15, 2020

5.1.4 Rotary Component . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.1.5 Linear Component . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2.1 Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.3 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.3.1 Hydraulic System . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.3.2 Pneumatic System . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.3.3 Coolant System . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.3.4 Lubrication System . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3.5 Electric System . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3.6 Enclosure System . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3.7 Protective System . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3.8 ProcessPower System . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3.9 Feeder System . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.3.10 Dielectric System . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.3.11 EndEffector System . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.3.12 WorkEnvelope System . . . . . . . . . . . . . . . . . . . . . . . 46
5.4 Auxiliaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.4.1 Loader System . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.4.2 WasteDisposal System . . . . . . . . . . . . . . . . . . . . . . . 47
5.4.3 ToolingDelivery System . . . . . . . . . . . . . . . . . . . . . . 47
5.4.4 BarFeeder System . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.4.5 Environmental System . . . . . . . . . . . . . . . . . . . . . . . 47
5.4.6 Sensor System . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.4.7 Deposition System . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.5 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.5.1 Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.5.1.1 Stock . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.5.2 Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.6 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.7 Other Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.7.1 Actuator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.7.2 Door . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.7.3 Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6 Composition Type Structural Elements 51

7 Data Entities for Device 55

7.1 DataItems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.2 DataItem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.2.1 XML Schema Structure for DataItem . . . . . . . . . . . . . . . 56
7.2.2 Attributes for DataItem . . . . . . . . . . . . . . . . . . . . . . . 58

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 iii

 July 15, 2020

7.2.2.1 name Attribute for DataItem . . . . . . . . . . . . . . . 63

7.2.2.2 id Attribute for DataItem . . . . . . . . . . . . . . . . . 63
7.2.2.3 type and subType Attributes for DataItem . . . . . . . . 64
7.2.2.4 statistic Attribute for DataItem . . . . . . . . . . . . . . 64
7.2.2.5 units Attribute for DataItem . . . . . . . . . . . . . . . 66
7.2.2.6 nativeUnits Attribute for DataItem . . . . . . . . . . . . 68
7.2.2.7 nativeScale Attribute for DataItem . . . . . . . . . . . . 69
7.2.2.8 category Attribute for DataItem . . . . . . . . . . . . . 70
7.2.2.9 coordinateSystem Attribute for DataItem . . . . . . . . 71
7.2.2.10 compositionId Attribute for DataItem . . . . . . . . . . 71
7.2.2.11 sampleRate Attribute for DataItem . . . . . . . . . . . 72
7.2.2.12 representation Attribute for DataItem . . . . . . . . . . 72
7.2.2.13 significantDigits Attribute for DataItem . . . . . . . . . 74
7.2.2.14 discrete Attribute for DataItem . . . . . . . . . . . . . . 74
7.2.3 Elements for DataItem . . . . . . . . . . . . . . . . . . . . . . . 75
7.2.3.1 Source Element for DataItem . . . . . . . . . . . . . . 76
7.2.3.1.1 Attributes for Source . . . . . . . . . . . . . . 77
7.2.3.2 Constraints Element for DataItem . . . . . . . . . . . . 78
7.2.3.2.1 Schema for Constraints . . . . . . . . . . . . 78
7.2.3.3 Filters Element for DataItem . . . . . . . . . . . . . . . 81
7.2.3.3.1 Filter . . . . . . . . . . . . . . . . . . . . . . 82
7.2.3.4 InitialValue Element for DataItem . . . . . . . . . . . . 83
7.2.3.5 ResetTrigger Element for DataItem . . . . . . . . . . . 83
7.2.3.6 Definition Element for DataItem . . . . . . . . . . . . . 85
7.2.3.6.1 EntryDefinitions Element for Definition . . . . 87
7.2.3.6.2 EntryDefinition Element for Definition . . . . 87
7.2.3.6.3 CellDefinitions Element for Definition . . . . 88
7.2.3.6.4 CellDefinition Element for CellDefinitions . . 89

8 Listing of Data Items 90

8.1 Data Items in category SAMPLE . . . . . . . . . . . . . . . . . . . . . . 91
8.2 Data Items in category EVENT . . . . . . . . . . . . . . . . . . . . . . . 114
8.3 Data Items in category CONDITION . . . . . . . . . . . . . . . . . . . . 142

9 Configuration 144
9.1 Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
9.1.1 Sensor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
9.1.2 Sensor Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
9.1.3 Sensor Configuration . . . . . . . . . . . . . . . . . . . . . . . . 148
9.1.3.1 Elements for SensorConfiguration . . . . . . . . . . . . 151
9.1.3.1.1 Attributes for Channel . . . . . . . . . . . . . 152
9.1.3.1.2 Elements for Channel . . . . . . . . . . . . . 153

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 iv

 July 15, 2020

9.2 Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

9.2.1 Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
9.2.1.1 DeviceRelationship . . . . . . . . . . . . . . . . . . . . 158
9.2.1.2 ComponentRelationship . . . . . . . . . . . . . . . . . 163
9.3 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9.3.1 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
9.3.1.1 Attributes for Specification . . . . . . . . . . . . . . . . 167
9.3.1.2 Elements for Specification . . . . . . . . . . . . . . . . 168
9.4 CoordinateSystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
9.4.1 CoordinateSystem . . . . . . . . . . . . . . . . . . . . . . . . . . 169
9.4.1.1 Attributes for CoordinateSystem . . . . . . . . . . . . . 169
9.4.1.1.1 CoordinateSystem types . . . . . . . . . . . . 169
9.4.1.2 Elements for CoordinateSystem . . . . . . . . . . . . . 171
9.4.1.2.1 Elements for Transformation . . . . . . . . . 171

Appendices 172
A Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 v

 July 15, 2020

Table of Figures
Figure 1: Example Device Structural Elements . . . . . . . . . . . . . . . . . . 16
Figure 2: Example Composition Structural Elements . . . . . . . . . . . . . . 17
Figure 3: Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 4: Description of Component Diagram . . . . . . . . . . . . . . . . . . 25
Figure 5: Component Configuration Diagram . . . . . . . . . . . . . . . . . . 27
Figure 6: Composition Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 7: Description of Composition Diagram . . . . . . . . . . . . . . . . . . 33
Figure 8: Reference Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 9: ComponentRef Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 10:DataItemRef Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 11:Example Data Entities for Device (DataItem) . . . . . . . . . . . . . 55
Figure 12:DataItem Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 13:Source Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 14:Constraints Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 15:Filter Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 16:Definition Schema Diagram . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 17:Configuration Element . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 18:Sensor Data Associations . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 19:SensorConfiguration Diagram . . . . . . . . . . . . . . . . . . . . . . 150
Figure 20:Relationship Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 21:DeviceRelationship Diagram . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 22:ComponentRelationship Diagram . . . . . . . . . . . . . . . . . . . . 163
Figure 23:Specifications Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 24:CoordinateSystems Diagram . . . . . . . . . . . . . . . . . . . . . . 168

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 vi

List of Tables
Table 1: MTConnect Devices Element . . . . . . . . . . . . . . . . . . . . . . . 17
Table 2: MTConnect Components Element . . . . . . . . . . . . . . . . . . . . 18
Table 3: MTConnect Component Element . . . . . . . . . . . . . . . . . . . . 19
Table 4: Attributes for Component . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 5: Elements for Component . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 6: Attributes for Description for Component . . . . . . . . . . . . . . . 25
Table 7: MTConnect Configuration Element for Component . . . . . . . . . . 26
Table 8: MTConnect Compositions Element . . . . . . . . . . . . . . . . . . . 29
Table 9: MTConnect Composition Element . . . . . . . . . . . . . . . . . . . . 30
Table 10:Attributes for Composition . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 11:Elements for Composition . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 12:Attributes for Description for Composition . . . . . . . . . . . . . . . 34
Table 13:MTConnect References Element . . . . . . . . . . . . . . . . . . . . . 35
Table 14:Attributes for ComponentRef . . . . . . . . . . . . . . . . . . . . . . 37
Table 15:Attributes for DataItemRef . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 16:Top Level Component Elements . . . . . . . . . . . . . . . . . . . . . 39
Table 17:Composition type Elements . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 18:MTConnect DataItems Element . . . . . . . . . . . . . . . . . . . . . 56
Table 19:MTConnect DataItem Element . . . . . . . . . . . . . . . . . . . . . 56
Table 20:Attributes for DataItem . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 21:DataItem attribute statistic type . . . . . . . . . . . . . . . . . . . . . 65
Table 22:DataItem attribute units type . . . . . . . . . . . . . . . . . . . . . . 66
Table 23:DataItem attribute nativeunits type . . . . . . . . . . . . . . . . . . . 68
Table 24:DataItem attribute coordinateSystem type . . . . . . . . . . . . . . . 71
Table 25:DataItem attribute representation type . . . . . . . . . . . . . . . . . 72
Table 26:Elements for DataItem . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 27:Attributes for Source . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Table 28:Elements for Constraints . . . . . . . . . . . . . . . . . . . . . . . . . 80
Table 29:MTConnect Filters Element . . . . . . . . . . . . . . . . . . . . . . . 81
Table 30:DataItem Element Filter type . . . . . . . . . . . . . . . . . . . . . . 82
Table 31:MTConnect ResetTrigger Element . . . . . . . . . . . . . . . . . . . 84
Table 32:DataItem Element ResetTrigger type . . . . . . . . . . . . . . . . . . 84
Table 33:Elements for Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 34:Elements for EntryDefinitions . . . . . . . . . . . . . . . . . . . . . . 87
Table 35:Attributes for EntryDefinition . . . . . . . . . . . . . . . . . . . . . . 88
Table 36:Elements for EntryDefinition . . . . . . . . . . . . . . . . . . . . . . . 88
Table 37:Elements for CellDefinitions . . . . . . . . . . . . . . . . . . . . . . . 89
Table 38:Attributes for CellDefinition . . . . . . . . . . . . . . . . . . . . . . . 89
Table 39:Elements for CellDefinition . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 40:DataItem type subType for category SAMPLE . . . . . . . . . . . . . 91

vii
 July 15, 2020

Table 41:DataItem type subType for category EVENT . . . . . . . . . . . . . . 114

Table 42:DataItem type for category CONDITION . . . . . . . . . . . . . . . . 142
Table 43:Types of Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Table 44:MTConnect SensorConfiguration Element . . . . . . . . . . . . . . . 151
Table 45:Elements for SensorConfiguration . . . . . . . . . . . . . . . . . . . . 151
Table 46:Attributes for Channel . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Table 47:Elements for Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Table 48:MTConnect Relationships Element . . . . . . . . . . . . . . . . . . . 155
Table 49:Attributes for DeviceRelationship . . . . . . . . . . . . . . . . . . . . 160
Table 50:Attributes for ComponentRelationship . . . . . . . . . . . . . . . . . 164
Table 51:Attributes for Specification . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 52:Elements for Specification . . . . . . . . . . . . . . . . . . . . . . . . 168
Table 53:Attributes for CoordinateSystem . . . . . . . . . . . . . . . . . . . . 169
Table 54:CoordinateSystem types . . . . . . . . . . . . . . . . . . . . . . . . . 170
Table 55:Elements for CoordinateSystem . . . . . . . . . . . . . . . . . . . . . 171
Table 56:Elements for Transformation . . . . . . . . . . . . . . . . . . . . . . . 171

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 1

 July 15, 2020

1 1 Purpose of This Document

2 This document, MTConnect Standard: Part 2.0 - Devices Information Model of the MT-
3 Connect Standard, establishes the rules and terminology to be used by designers to de-
4 scribe the function and operation of a piece of equipment and to define the data that is
5 provided by an Agent from the equipment. The Devices Information Model also defines
6 the structure for the XML document that is returned from an Agent in response to a Probe
7 Request.

8 In the MTConnect Standard, equipment represents any tangible property that is used in the
9 operations of a manufacturing facility. Examples of equipment are machine tools, ovens,
10 sensor units, workstations, software applications, and bar feeders.

11 Note: See MTConnect Standard: Part 3.0 - Streams Information Model of the MT-
12 Connect Standard for details on the XML documents that are returned from an
13 Agent in response to a Sample Request or Current Request.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 2

 July 15, 2020

14 2 Terminology and Conventions

15 Refer to Section 3 of MTConnect Standard Part 1.0 - Overview and Fundamentals for a
16 dictionary of terms, reserved language, and document conventions used in the MTConnect
17 Standard.

18 2.1 Glossary

19 CDATA
20 General meaning:
21 An abbreviation for Character Data.
22 CDATA is used to describe a value (text or data) published as part of an XML ele-
23 ment.
24 For example, "This is some text" is the CDATA in the XML element:
25 <Message ...>This is some text</Message>
26 Appears in the documents in the following form: CDATA

27 HTTP
28 Hyper-Text Transport Protocol. The protocol used by all web browsers and web
29 applications.
30 Note: HTTP is an IETF standard and is defined in RFC 7230.
31 See https://tools.ietf.org/html/rfc7230 for more information.

32 NMTOKEN
33 The data type for XML identifiers.
34 Note: The identifier must start with a letter, an underscore "_" or a colon. The next
35 character must be a letter, a number, or one of the following ".", "-", "_", ":". The
36 identifier must not have any spaces or special characters.
37 Appears in the documents in the following form: NMTOKEN.

38 XML
39 Stands for eXtensible Markup Language.
40 XML defines a set of rules for encoding documents that both a human-readable and
41 machine-readable.
42 XML is the language used for all code examples in the MTConnect Standard.
43 Refer to http://www.w3.org/XML for more information about XML.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 3

 July 15, 2020

44 Agent
45 Refers to an MTConnect Agent.
46 Software that collects data published from one or more piece(s) of equipment, orga-
47 nizes that data in a structured manner, and responds to requests for data from client
48 software systems by providing a structured response in the form of a Response Doc-
49 ument that is constructed using the semantic data models defined in the Standard.
50 Appears in the documents in the following form: Agent.

51 Asset
52 General meaning:
53 Typically referred to as an MTConnect Asset.
54 An MTConnect Asset is something that is used in the manufacturing process, but is
55 not permanently associated with a single piece of equipment, can be removed from
56 the piece of equipment without compromising its function, and can be associated
57 with other pieces of equipment during its lifecycle.
58 Used to identify a storage area in an Agent:
59 See description of buffer.
60 Used as an Information Model:
61 Used to describe an Information Model that contains the rules and terminology that
62 describe information that may be included in electronic documents representing MT-
63 Connect Assets.
64 The Asset Information Models defines the structure for the Assets Response Docu-
65 ment.
66 Individual Information Models describe the structure of the Asset Documents rep-
67 resent each type of MTConnect Asset. Appears in the documents in the following
68 form: Asset Information Models or (asset type) Information Model.
69 Used when referring to an MTConnect Asset:
70 Refers to the information related to an MTConnect Asset or a group of MTConnect
71 Assets.
72 Appears in the documents in the following form: Asset or Assets.
73 Used as an XML container or element:

74 • When used as an XML container that consists of one or more types of Asset
75 XML elements.
76 Appears in the documents in the following form: Assets.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 4

 July 15, 2020

77 • When used as an abstract XML element. It is replaced in the XML document

78 by types of Asset elements representing individual Asset entities.
79 Appears in the documents in the following form: Asset.

80 Used to describe information stored in an Agent:

81 Identifies an electronic document published by a data source and stored in the assets
82 buffer of an Agent.
83 Appears in the documents in the following form: Asset Document.
84 Used as an XML representation of an MTConnect Response Document:
85 Identifies an electronic document encoded in XML and published by an Agent in
86 response to a Request for information from a client software application relating to
87 MTConnect Assets.
88 Appears in the documents in the following form: MTConnectAssets.
89 Used as an MTConnect Request:
90 Represents a specific type of communications request between a client software ap-
91 plication and an Agent regarding MTConnect Assets.
92 Appears in the documents in the following form: Asset Request.
93 Used as part of an HTTP Request:
94 Used in the path portion of an HTTP Request Line, by a client software applica-
95 tion, to initiate an Asset Request to an Agent to publish an MTConnectAssets
96 document.
97 Appears in the documents in the following form: asset.

98 Asset Document
99 An electronic document published by an Agent in response to a Request for infor-
100 mation from a client software application relating to Assets.

101 buffer
102 General meaning:
103 A section of an Agent that provides storage for information published from pieces
104 of equipment.
105 Used relative to Streaming Data:
106 A section of an Agent that provides storage for information relating to individual
107 pieces of Streaming Data.
108 Appears in the documents in the following form: buffer.
109 Used relative to MTConnect Assets:

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 5

 July 15, 2020

110 A section of an Agent that provides storage for Asset Documents.

111 Appears in the documents in the following form: assets buffer.

112 Child Element

113 A portion of a data modeling structure that illustrates the relationship between an
114 element and the higher-level Parent Element within which it is contained.
115 Appears in the documents in the following form: Child Element.

116 Controlled Vocabulary

117 A restricted set of values that may be published as the Valid Data Value for a Data
118 Entity.
119 Appears in the documents in the following form: Controlled Vocabulary.

120 Current Request

121 An HTTP request to the Agent for returning latest known values for the DataItem
122 as an MTConnectStreams XML document

123 Data Entity

124 A primary data modeling element that represents all elements that either describe
125 data items that may be reported by an Agent or the data items that contain the actual
126 data published by an Agent.
127 Appears in the documents in the following form: Data Entity.

128 Data Set

129 A set of key-value pairs where each entry is uniquely identified by the key.

130 Devices Information Model

131 A set of rules and terms that describes the physical and logical configuration for a
132 piece of equipment and the data that may be reported by that equipment.
133 Appears in the documents in the following form: Devices Information Model.

134 Document
135 General meaning:
136 A piece of written, printed, or electronic matter that provides information.
137 Used to represent an MTConnect Document:
138 Refers to printed or electronic document(s) that represent a Part(s) of the MTCon-
139 nect Standard.
140 Appears in the documents in the following form: MTConnect Document.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 6

 July 15, 2020

141 Used to represent a specific representation of an MTConnect Document:

142 Refers to electronic document(s) associated with an Agent that are encoded using
143 XML; Response Documents or Asset Documents.
144 Appears in the documents in the following form: MTConnect XML Document.
145 Used to describe types of information stored in an Agent:
146 In an implementation, the electronic documents that are published from a data source
147 and stored by an Agent.
148 Appears in the documents in the following form: Asset Document.
149 Used to describe information published by an Agent:
150 A document published by an Agent based upon one of the semantic data models
151 defined in the MTConnect Standard in response to a request from a client.
152 Appears in the documents in the following form: Response Document.

153 engineering units

154 A quantity, dimension, or magnitude used in engineering adopted as a standard in
155 terms of which the magnitude of other quantities of the same kind can be expressed
156 or calculated.
157 Equipment Metadata
158 See Metadata

159 HTTP Request

160 In the MTConnect Standard, a communications command issued by a client soft-
161 ware application to an Agent requesting information defined in the HTTP Request
162 Line.
163 Appears in the documents in the following form: HTTP Request.
164 HTTP Request Line
165 In the MTConnect Standard, the first line of an HTTP Request describing a specific
166 Response Document to be published by an Agent.
167 Appears in the documents in the following form: HTTP Request Line.

168 Information Model

169 The rules, relationships, and terminology that are used to define how information is
170 structured.
171 For example, an information model is used to define the structure for each MTCon-
172 nect Response Document; the definition of each piece of information within those
173 documents and the relationship between pieces of information.
174 Appears in the documents in the following form: Information Model.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 7

 July 15, 2020

175 Interaction Model

176 The definition of information exchanged to support the interactions between pieces
177 of equipment collaborating to complete a task.
178 Appears in the documents in the following form: Interaction Model.

179 Interface
180 General meaning:
181 The exchange of information between pieces of equipment and/or software systems.
182 Appears in the documents in the following form: interface.
183 Used as an Interaction Model:
184 An Interaction Model that describes a method for inter-operations between pieces
185 of equipment.
186 Appears in the documents in the following form: Interface.
187 Used as an XML container or element:
188 - When used as an XML container that consists of one or more types of Inter-
189 face XML elements.
190 Appears in the documents in the following form: Interfaces.
191 - When used as an abstract XML element. It is replaced in the XML document
192 by types of Interface elements.
193 Appears in the documents in the following form: Interface

194 key
195 A unique identifier in a key-value pair association.

196 key-value pair

197 An association between an identifier referred to as the key and a value which taken
198 together create a key-value pair. When used in a set of key-value pairs each key is
199 unique and will only have one value associated with it at any point in time.

200 Lower Level

201 A nested element that is below a higher level element.

202 Metadata
203 Data that provides information about other data.
204 For example, Equipment Metadata defines both the Structural Elements that rep-
205 resent the physical and logical parts and sub-parts of each piece of equipment, the

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 8

 July 15, 2020

206 relationships between those parts and sub-parts, and the definitions of the Data En-
207 tities associated with that piece of equipment.
208 Appears in the documents in the following form: Metadata or Equipment Metadata.

209 MTConnect Document

210 See Document.

211 MTConnect Request

212 A communication request for information issued from a client software application
213 to an Agent.
214 Appears in the documents in the following form: MTConnect Request.

215 MTConnect XML Document

216 See Document.

217 observation
218 The observed value of a property at a point in time.

219 organize
220 The act of containing and owning one or more elements.

221 Parent Element

222 An XML element used to organize Lower Level child elements that share a common
223 relationship to the Parent Element.
224 Appears in the documents in the following form: Parent Element.

225 Request
226 A communications method where a client software application transmits a message
227 to an Agent. That message instructs the Agent to respond with specific information.
228 Appears in the documents in the following form: Request.

229 Response Document

230 See Document.

231 Sample Request

232 A request from the Agent for a stream of time series data.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 9

 July 15, 2020

233 semantic data model

234 A methodology for defining the structure and meaning for data in a specific logical
235 way.
236 It provides the rules for encoding electronic information such that it can be inter-
237 preted by a software system.
238 Appears in the documents in the following form: semantic data model.

239 Streaming Data

240 The values published by a piece of equipment for the Data Entities defined by the
241 Equipment Metadata.
242 Appears in the documents in the following form: Streaming Data.

243 Streams Information Model

244 The rules and terminology (semantic data model) that describes the Streaming Data
245 returned by an Agent from a piece of equipment in response to a Sample Request or
246 a Current Request.
247 Appears in the documents in the following form: Streams Information Model.

248 Structural Element

249 General meaning:
250 An XML element that organizes information that represents the physical and logical
251 parts and sub-parts of a piece of equipment.
252 Appears in the documents in the following form: Structural Element.
253 Used to indicate hierarchy of Components:
254 When used to describe a primary physical or logical construct within a piece of
255 equipment.
256 Appears in the documents in the following form: Top Level Structural Element.
257 When used to indicate a Child Element which provides additional detail describing
258 the physical or logical structure of a Top Level Structural Element.
259 Appears in the documents in the following form: Lower Level Structural Element.

260 Table
261 A two dimensional set of values given by a set of key-value pairs Table Entries.
262 Each Table Entry contains a set of key-value pairs of Table Cells. The Entry and
263 Cell elements comprise a tabular representation of the information.

264 Table Cell

265 A subdivision of a Table Entry representing a singular value.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 10

 July 15, 2020

266 Table Entry

267 A subdivision of a Table containing a set of key-value pairs representing Table Cells.

268 Top Level

269 Structural Elements that represent the most significant physical or logical functions
270 of a piece of equipment.

271 Valid Data Value

272 One or more acceptable values or constrained values that can be reported for a Data
273 Entity.
274 Appears in the documents in the following form: Valid Data Value(s).

275 XML Schema

276 In the MTConnect Standard, an instantiation of a schema defining a specific docu-
277 ment encoded in XML.

278 2.2 Acronyms

279 AMT
280 The Association for Manufacturing Technology

281 2.3 MTConnect References

282 [MTConnect Part 1.0] MTConnect Standard Part 1.0 - Overview and Fundamentals. Ver-
283 sion 1.5.0.
284 [MTConnect Part 2.0] MTConnect Standard: Part 2.0 - Devices Information Model. Ver-
285 sion 1.5.0.
286 [MTConnect Part 3.0] MTConnect Standard: Part 3.0 - Streams Information Model. Ver-
287 sion 1.5.0.
288 [MTConnect Part 4.0] MTConnect Standard: Part 4.0 - Assets Information Model. Ver-
289 sion 1.5.0.
290 [MTConnect Part 5.0] MTConnect Standard: Part 5.0 - Interfaces. Version 1.5.0.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 11

 July 15, 2020

291 3 Devices Information Model

292 The Devices Information Model provides a representation of the physical and logical con-
293 figuration for a piece of equipment used for a manufacturing process or for any other
294 purpose. It also provides the definition of data that may be reported by that equipment.

295 Using information defined in the Devices Information Model, a software application can
296 determine the configuration and reporting capabilities of a piece of equipment. To do this,
297 the software application issues a Probe Request (defined in MTConnect Standard Part 1.0
298 - Overview and Fundamentals Section 8.1.1) to an Agent associated with a piece of equip-
299 ment. An Agent responds to the Probe Request with an MTConnectDevices XML
300 document that contains information describing both the physical and logical structure of
301 the piece of equipment and a detailed description of each Data Entity that can be reported
302 by the Agent associated with the piece of equipment. This information allows the client
303 software application to interpret the document and to extract the data with the same mean-
304 ing, value, and context that it had at its original source.

305 The MTConnectDevices XML document is comprised of two sections: Header and
306 Devices.

307 The Header section contains protocol related information as defined in MTConnect Stan-
308 dard Part 1.0 - Overview and Fundamentals Section 6.5.1.

309 The Devices section of the MTConnectDevices document contains a Device XML
310 container for each piece of equipment described in the document. Each Device container
311 is comprised of two primary types of XML elements - Structural Elements and Data Enti-
312 ties.

313 Structural Elements are defined as XML elements that organize information that repre-
314 sents the physical and logical parts and sub-parts of a piece of equipment (See Section 4 -
315 Structural Elements for MTConnectDevices for more details).

316 Data Entities are defined as XML elements that describe data that can be reported by
317 a piece of equipment. In the Devices Information Model, Data Entities are defined as
318 DataItem elements (See Section 7 - Data Entities for Device and Section 8 - Listing of
319 Data Items).

320 The Structural Elements and Data Entities in the MTConnectDevices document pro-
321 vide information representing the physical and logical structure for a piece of equipment
322 and the types of data that the piece of equipment can report relative to that structure. The
323 MTConnectDevices document does not contain values for the data types reported by
324 the piece of equipment. The MTConnectStreams document defined in MTConnect

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 12

 July 15, 2020

325 Standard: Part 3.0 - Streams Information Model provides the data values that are reported
326 by the piece of equipment. As such, most Structural Elements and Data Entities in the
327 MTConnectDevices document do not contain CDATA. XML elements that provide
328 values or information in the CDATA will be specifically identified in Section 4 - Structural
329 Elements for MTConnectDevices, Section 7 - Data Entities for Device, and Section 9.1 -
330 Sensor.

331 Note: The MTConnect Standard also defines the information model for Assets. An
332 Asset is something that is used in the manufacturing process, but is not perma-
333 nently associated with a single piece of equipment, can be removed from the
334 piece of equipment without compromising its function, and can be associated
335 with other pieces of equipment during its lifecycle. See MTConnect Standard:
336 Part 4.0 - Assets Information Model for more details on Assets.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 13

 July 15, 2020

337 4 Structural Elements for MTConnectDevices

338 Structural Elements are XML elements that form the logical structure for the MTCon-
339 nectDevices XML document. These elements are used to organize information that
340 represents the physical and logical architecture of a piece of equipment. Refer to Figure 1
341 for an overview of the Structural Elements used in an MTConnectDevices document.

342 A variety of Structural Elements are defined to describe a piece of equipment. Some
343 of these elements MUST always appear in the MTConnectDevices XML document,
344 while others are optional and MAY be used, as required, to provide additional structure.

345 The first, or highest level, Structural Element in a MTConnectDevices XML document
346 is Devices. Devices is a container type XML element used to group one or more
347 pieces of equipment into a single XML document. Devices MUST always appear in the
348 MTConnectDevices document.

349 Device is the next Structural Element in the MTConnectDevices XML document.
350 Device is also a container type XML element. A separate Device container is used
351 to identify each piece of equipment represented in the MTConnectDevices document.
352 Each Device container provides information on the physical and logical structure of
353 the piece of equipment and the data associated with that equipment. Device can also
354 represent any logical grouping of pieces of equipment that function as a unit or any other
355 data source that provides data through an Agent.

356 One or more Device element(s) MUST always appear in an MTConnectDevices

357 document.

358 Components is the next Structural Element in the MTConnectDevices XML doc-
359 ument. Components is also a container type XML element. Components is used to
360 group information describing Lower Level physical parts or logical functions of a piece of
361 equipment.

362 If the Components container appears in the XML document, it MUST contain one or
363 more Component type XML elements.

364 Component is the next level of Structural Element in the MTConnectDevices XML
365 document. Component is both an abstract type XML element and a container type ele-
366 ment.

367 As an abstract type element, Component will never appear in the XML document de-
368 scribing a piece of equipment and will be replaced by a specific Component type defined
369 in Section 5 - Component Structural Elements. Each Component type is also a container
370 type element. As a container, the Component type element is used to organize infor-

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 14

 July 15, 2020

371 mation describing Lower Level Structural Elements or Data Entities associated with the
372 Component.

373 If Lower Level Structural Elements are described, these elements are by definition child
374 Component elements of a parent Component. At this next level, the Lower Level child
375 Component elements are grouped into an XML container called Components.

376 This Lower Level Components container is comprised of one or more child Compo-
377 nent XML elements representing the sub-parts of the parent Component. Just like the
378 parent Component element, the child Component element is an abstract type XML el-
379 ement and will never appear in the XML document – only the different Lower Level child
380 Component types will appear.

381 This parent-child relationship can continue to any depth required to fully define a piece of
382 equipment.

383 Example 1 illustrates the relationship between a parent Component and Lower Level
384 child components:
Example 1: Component Levels
385 1 <Devices>
386 2 <Device>
387 3 <Components>
388 4 <Axes> Parent Component
389 5 <Components>
390 6 <Rotary> Child component of Axes and Parent component of Lower Level compo-
391 nents
392 7 <Components>
393 8 <Chuck> Child Component of Rotary

394 Figure 1 demonstrates the various Structural Elements provided to describe a piece of
395 equipment and the relationship between these elements.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 15

 July 15, 2020

Figure 1: Example Device Structural Elements

396 Component type XML elements MAY be further decomposed into Composition type
397 XML elements. Composition elements describe the lowest level basic structural or
398 functional building blocks contained within a Component. Any number of Composi-
399 tion elements MAY be used. Data provided for a Component provides more specific
400 meaning when it is associated with one of the Composition elements of the Compo-
401 nent. The different Composition types that MAY appear in the XML document are
402 defined in Section 6 - Composition Type Structural Elements.

403 The Composition elements are organized into a Compositions container. The
404 Compositions container MAY appear in the XML document further describing a Com-
405 ponent. If one or more Composition element(s) is provided to describe a Compo-
406 nent, a Compositions container MUST be defined for the Component.

407 Example 2 represents an XML document structure that demonstrates the relationship be-
408 tween a parent Component and its Composition elements.
Example 2: Component levels with Composition
409 1 <Devices>
410 2 <Device>
411 3 <Components>
412 4 <Axes> (Component)
413 5 <Components>
414 6 <Linear> (Component)
415 7 <Compositions>
416 8 <Composition>
417 9 <Composition>
418 10 <Composition>

419 Figure 2 demonstrates this relationship between a Component and some of its potential
420 Composition elements.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 16

 July 15, 2020

Figure 2: Example Composition Structural Elements

421 4.1 Devices

422 Devices MUST organize one or more Device elements.

Table 1: MTConnect Devices Element

Element Description Occurrence

Devices The first, or highest level, Structural Element in a 1
MTConnectDevices document. Devices is a
container type XML element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 17

 July 15, 2020

423 4.2 Device

424 A Device is a Component that represents a piece of equipment that produces observa-
425 tions about itself. It organizes its parts as Components.

426 A Device MUST have a name and uuid attribute to identify itself.

427 A Device MUST have the following DataItems: AVAILABILITY, ASSET_CHANGED,

428 and ASSET_REMOVED.

429 See Section 4.4 - Component for details on the Device model.

430 4.3 Components

431 Components is an XML container used to group information describing physical parts
432 or logical functions of a piece of equipment. Components contains one or more Com-
433 ponent XML elements.
Table 2: MTConnect Components Element

Element Description Occurrence

Components An XML container that consists of one or more types 0..1
of Component XML elements.
If a Components XML element is provided, then
only one Components element MUST be defined
for a Device element.

434 4.4 Component

435 A Component XML element is a container type XML element used to organize informa-
436 tion describing a physical part or logical function of a piece of equipment. It also provides
437 structure for describing the Lower Level Structural Elements associated with the Compo-
438 nent. Component is an abstract type XML element and will never appear directly in
439 the MTConnect XML document. As an abstract type XML element, Component will be
440 replaced in the XML document by specific Component types. XML elements represent-
441 ing Component are described in Section 5 - Component Structural Elements and include
442 elements such as Axes, Controller, and Systems.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 18

 July 15, 2020

Table 3: MTConnect Component Element

Element Description Occurrence

Component An abstract XML element. Replaced in the XML 1..*
document by types of Component elements
representing physical parts and logical functions of a
piece of equipment.
There can be multiple types of Component XML
elements in the document.

443 4.4.1 XML Schema Structure for Component

444 Figure 3 represents the structure of a Component XML element showing the attributes
445 defined for Component and the elements that MAY be associated with Component.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 19

 July 15, 2020

Figure 3: Component Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 20

 July 15, 2020

446 4.4.2 Attribute for Component

447 Table 4 defines the attributes that may be used to provide additional information for a
448 Component type XML element.

Table 4: Attributes for Component

Attribute Description Occurrence

id The unique identifier for this element. 1
id is a required attribute.
An id MUST be unique across all the id
attributes in the document.
An XML ID-type.
nativeName The common name normally associated with a 0..1
specific physical or logical part of a piece of
equipment.
nativeName is an optional attribute.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 21

 July 15, 2020

Continuation of Table 4
Attribute Description Occurrence
sampleInterval An optional attribute that is an indication 0..1 ††
provided by a piece of equipment describing the
interval in milliseconds between the completion
of the reading of the data associated with the
Component element until the beginning of the
next sampling of that data. This indication is
reported as the number of milliseconds between
data captures.
This information may be used by client software
applications to understand how often
information from a piece of equipment for a
specific Component element is expected to be
refreshed.
The refresh rate for data from all Lower Level
Component elements will be the same as for
the parent Component element unless
specifically overridden by another
sampleInterval provided for the Lower
Level Component element.
If the value of sampleInterval is less than
one millisecond, the value will be represented as
a floating-point number. For example, an
interval of 100 microseconds would be 0.1.
sampleRate DEPRECATED in MTConnect Version 1.2. 0..1 †††
Replaced by sampleInterval.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 22

 July 15, 2020

Continuation of Table 4
Attribute Description Occurrence
uuid A unique identifier for this XML element. 0..1 †
uuid is an optional attribute.
The value provided for the uuid MUST be
unique amongst all uuid identifiers used in an
MTConnect installation.
For example, this may be a combination of the
manufacturer’s code and serial number. The
uuid SHOULD be alphanumeric and not
exceed 255 characters.
An NMTOKEN XML type.
name The name of the Component element. 0..1
name is an optional attribute.
However, if there are multiple Lower Level
components that have the same parent and are of
the same component type (example Linear),
then the name attribute MUST be provided for
all Lower Level components of the same
element type to differentiate between the similar
components.
When provided, name MUST be unique for all
Lower Level components of a parent
Component.
An NMTOKEN XML type.

449 Notes: † While uuid MUST be provided for the Device element, it is optional for
450 Component elements.
451 †† The sampleInterval is used to aid a client software application in in-

452 terpreting values provided by some Data Entities. This is the desired sample
453 interval and may vary depending on the capabilities of the piece of equipment.
454 ††† Remains in schema for backwards compatibility.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 23

 July 15, 2020

455 4.4.3 Elements of Component

456 Table 5 lists the elements defined to provide additional information for a Component
457 type XML element.

Table 5: Elements for Component

Element Description Occurrence

Description An element that can contain any descriptive 0..1
content.
Configuration An XML element that contains technical 0..1
information about a piece of equipment
describing its physical layout or functional
characteristics.
DataItems A container for the Data Entities (defined in 0..1 †
Section 8 - Listing of Data Items) associated with
this Component element.
Components A container for Lower Level Component XML 0..1 †
elements associated with this parent
Component.
Compositions A container for the Composition elements 0..1
(defined in Section 6 - Composition Type
Structural Elements) associated with this
Component element.
References A container for the Reference elements 0..1 †
associated with this Component element.

458 Note: † At least one of Components, DataItems, or References MUST be

459 provided.

460 4.4.3.1 Description for Component

461 Figure 4 illustrates the structure of the Description XML element showing the at-
462 tributes defined for Description. Description can contain any descriptive content
463 of this Component. This element is defined to contain mixed content and additional
464 XML elements (indicated by the any element) MAY be added to extend the schema for
465 Description.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 24

 July 15, 2020

Figure 4: Description of Component Diagram

466 Table 6 lists the attributes defined for the Description XML element.
Table 6: Attributes for Description for Component

Attribute Description Occurrence

manufacturer The name of the manufacturer of the physical or 0..1
logical part of a piece of equipment represented by
the Component element.
manufacturer is an optional attribute.
model The model description of the physical part or 0..1
logical function of a piece of equipment
represented by the Component element.
model is an optional attribute.
serialNumber The serial number associated with the physical 0..1
part or logical function of a piece of equipment
represented by the Component element.
serialNumber is an optional attribute.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 25

 July 15, 2020

Continuation of Table 6
Attribute Description Occurrence
station The station where the physical part or logical 0..1
function of a piece of equipment represented by
the Component element is located when it is part
of a manufacturing unit or cell with multiple
stations.
station is an optional attribute.

467 The content of Description MAY include any additional descriptive information the
468 implementer chooses to include regarding the Component element. This content SHOULD
469 be limited to information not included elsewhere in the MTConnectDevices XML doc-
470 ument.
Example 3: Example of Description
471 1 <Description manufacturer="Example Co"
472 2 serialNumber="EXCO-TT-099PP-XXXX"> Advanced Pulse
473 3 watt-hour transducer with pulse output
474 4 </Description>

475 4.4.3.2 Configuration for Component

476 The Configuration XML element contains technical information about a component.
477 Configuration MAY include any information describing the physical layout or func-
478 tional characteristics of a component, such as capabilities, testing, installation, operation,
479 calibration, or maintenance. Configuration MAY also include information represent-
480 ing the inter-relationships between components within a piece of equipment.

Table 7: MTConnect Configuration Element for Component

Element Description Occurrence

Configuration An XML element that contains technical 0..1
information about a component describing its
physical layout, functional characteristics, and
relationships with other components within a
piece of equipment.

481 Configuration data for Component is structured in the MTConnectDevices XML

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 26

 July 15, 2020

482 document as shown in Figure 5 . AbstractConfiguration is an abstract type XML

483 element. It will never appear in the XML document representing a piece of equipment.
484 When Configuration is provided for a component, that type of Configuration
485 will appear in the XML document.

486 See Section 9 - Configuration for details on the types of Configuration.

Figure 5: Component Configuration Diagram

487 4.4.3.3 DataItems for Component

488 DataItems is an XML container that provides structure for organizing the data reported
489 by a piece of equipment that is associated with the Component.

490 See Section 7 - Data Entities for Device for details on the DataItems XML element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 27

 July 15, 2020

491 4.4.3.4 Components within Component

492 The use of the XML container Components within a Component element provides
493 the ability to further break down the structure of a Component element into even Lower
494 Level physical and logical sub-parts. These Lower Level elements can add more clarity
495 and granularity to the physical or logical structure of a piece of equipment and the data
496 associated with that equipment.

497 This parent-child relationship can be extended down to any level necessary to fully de-
498 scribe a piece of equipment. These Lower Level Component elements use the same XML
499 structure as Component defined in Section 4.4.1 - XML Schema Structure for Component.
Example 4: Example of parent Component and Child Elements
500 1 <Devices>
501 2 <Device>
502 3 <Components>
503 4 <Axes> (Component)
504 5 <Components>
505 6 <Linear> (Component)
506 7 <Components>
507 8 <Etc. > (Component)

508 4.4.3.5 Compositions for Component

509 Compositions is an XML container used to organize the lowest level structural build-
510 ing blocks contained within a Component as defined below.

511 4.4.3.6 References for Component

512 References is an XML container used to organize Reference elements associated

513 with a Component element. See Section 4.7 - References for details on References.

514 4.5 Compositions

515 Compositions is an XML container that defines the lowest level structural building
516 blocks contained within a Component element.

517 Compositions contains one or more Composition XML elements.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 28

 July 15, 2020

Table 8: MTConnect Compositions Element

Element Description Occurrence

Compositions An XML container consisting of one or more 0..1
types of Composition XML elements. Only
one Compositions container MAY appear for a
Component element.

518 4.6 Composition

519 Composition XML elements are used to describe the lowest level physical building
520 blocks of a piece of equipment contained within a Component.

521 Composition provides the ability to organize information describing parts of its parent
522 Component. A Composition MUST NOT have child Components, Composi-
523 tions, or DataItems elements.

524 Composition elements are used to add more clarity and granularity to the data being
525 retrieved from a piece of equipment. The meaning of the data associated with a Com-
526 ponent may be enhanced by designating a specific Composition element associated
527 with that data.

528 An example of the additional detail provided when using Composition elements would
529 be:

530 A TEMPERATURE associated with a Linear type axis may be further clarified by ref-
531 erencing the MOTOR or AMPLIFIER type Composition element associated with that
532 axis, which differentiates the temperature of the motor from the temperature of the ampli-
533 fier.

534 Composition is a typed XML element and will always define a specific type of struc-
535 tural building block contained within a Component. XML elements representing the
536 types of Composition elements are described in Section 6 - Composition Type Struc-
537 tural Elements and include elements describing such basic building blocks as motors, am-
538 plifiers, filters, and pumps.
Example 5: Example of parent Component and child Composition elements
539 1 <Devices>
540 2 <Device>
541 3 <Components>
542 4 <Axes> (Component)
543 5 <Components>

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 29

 July 15, 2020

544 6 <Linear> (Component)

545 7 <Compositions>
546 8 <Composition>
547 9 <Composition>
548 10 <Composition>

Table 9: MTConnect Composition Element

Element Description Occurrence

Composition An XML element used to describe the lowest level 1..*
structural building blocks contained within a
Component element.
Composition is a typed XML element.
There can be multiple types of Composition
XML elements defined for a Component element.

549 4.6.1 XML Schema Structure for Composition

550 Figure 6 illustrates a Composition XML element showing the attributes defined for
551 Composition and the elements that may be associated with Composition type XML
552 elements.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 30

 July 15, 2020

Figure 6: Composition Diagram

553 4.6.2 Attributes for Composition

554 Table 10 defines the attributes that may be used to provide additional information for a
555 Composition type XML element.

Table 10: Attributes for Composition

Attribute Description Occurrence

id The unique identifier for this element. 1
id is a required attribute.
An id MUST be unique across all the id attributes in the
document.
An XML ID-type.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 31

 July 15, 2020

Continuation of Table 10
Attribute Description Occurrence
uuid A unique identifier for this XML element. 0..1
uuid is an optional attribute.
The uuid MUST be unique amongst all uuid identifiers
used in an MTConnect installation.
For example, this may be a combination of the
manufacturer’s code and serial number. The uuid
SHOULD be alphanumeric and not exceed 255
characters.
An NMTOKEN XML type.
name The name of the Composition element. 0..1
If more than one Composition elements have the same
type for the same Component, then the name attribute
MUST be provided. Otherwise, the name attribute is
optional.
If provided, name MUST be unique within a
Component element. name is an NMTOKEN XML
type
type The type of Composition element. 1
type is a required attribute.
Examples of types are MOTOR, FILTER, PUMP, and
AMPLIFIER.
Refer to Section 6 - Composition Type Structural
Elements for a list of currently defined types.

556 4.6.3 Elements of Composition

557 Table 11 lists the elements defined to provide additional information for a Composition
558 type XML element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 32

 July 15, 2020

Table 11: Elements for Composition

Element Description Occurrence

Description An element that can contain any descriptive content. 0..1

559 4.6.3.1 Description for Composition

560 Figure 7 represents the structure of the Description XML element showing the at-
561 tributes defined for Description. Description can contain any descriptive content
562 for this Composition element. This element is defined to contain mixed content and
563 additional XML elements (indicated by the any element) MAY be added to extend the
564 schema for Description.

Figure 7: Description of Composition Diagram

565 Table 12 lists the attributes defined for the Description XML element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 33

 July 15, 2020

Table 12: Attributes for Description for Composition

Attribute Description Occurrence

manufacturer The name of the manufacturer of the physical part 0..1
of a piece of equipment represented by the
Composition element.
manufacturer is an optional attribute.
model The model description of the physical part of a 0..1
piece of equipment represented by the
Composition element.
model is an optional attribute.
serialNumber The serial number associated with the physical 0..1
part of a piece of equipment represented by the
Composition element.
serialNumber is an optional attribute.
station The station where the physical part of a piece of 0..1
equipment represented by the Composition
element is located when it is part of a
manufacturing unit or cell with multiple stations.
station is an optional attribute.

566 The content of Description MAY include any additional descriptive information the
567 implementer chooses to include regarding the Composition element. This content
568 SHOULD be limited to information not included elsewhere in the MTConnectDevices
569 XML document.
Example 6: Example of Description
570 1 <Description manufacturer="Example Co"
571 2 serialNumber="A124FFF" station="2"> Spindle motor
572 3 associated with Path 2.
573 4 </Description>

574 4.7 References

575 References is an XML container that organizes pointers to information defined else-
576 where within the XML document for a piece of equipment.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 34

 July 15, 2020

577 References may be modeled as part of a Device, Component or Interface type

578 Structural Element.

579 References contains one or more Reference XML elements.

Table 13: MTConnect References Element

Element Description Occurrence

References An XML container consisting of one or more types 0..1
of Reference XML elements. Only one
References container MUST appear for a
Device, Component, or Interface element.

580 4.8 Reference

581 Reference is a pointer to information that is associated with another Structural Element
582 defined elsewhere in the XML document for a piece of equipment. That information may
583 be data from the other element or the entire structure of that element.

584 Reference is an efficient method to associate information with an element without du-
585 plicating any of the data or structure. For example, a Bar Feeder System may make a re-
586 quest for the BarFeederInterface and receive all the relevant data for the interface
587 and the associated spindle (Rotary element) that is referenced as part of the BarFeed-
588 erInterface.

589 Reference is an abstract type XML element and will never appear directly in the MT-
590 Connect XML document. As an abstract type XML element, Reference will be re-
591 placed in the XML document by a specific Reference type. The current supported
592 types of Reference are DataItemRef and ComponentRef XML elements.

593 Figure 8 represents the structure of the Reference XML element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 35

 July 15, 2020

Figure 8: Reference Diagram

594 4.8.1 ComponentRef

595 ComponentRef XML element is a pointer to all of the information associated with an-
596 other Structural Element defined elsewhere in the XML document for a piece of equip-
597 ment. ComponentRef allows all of the information (Lower Level Components and all
598 Data Entities) that is associated with the other Structural Element to be directly associated
599 with this XML element.

600 Figure 9 represents the structure of a ComponentRef XML element showing the at-
601 tributes defined for ComponentRef.

Figure 9: ComponentRef Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 36

 July 15, 2020

602 Table 14 lists the attributes defined for the ComponentRef element.
Table 14: Attributes for ComponentRef

Attribute Description Occurrence

idRef A pointer to the id attribute of the Component that 1
contains the information to be associated with this XML
element.
idRef is a required attribute.
name The optional name of the ComponentRef. Only 0..1
informative.
name is an NMTOKEN XML type.

603 4.8.2 DataItemRef

604 DataItemRef XML element is a pointer to a Data Entity associated with another Struc-
605 tural Element defined elsewhere in the XML document for a piece of equipment. DataItem-
606 Ref allows the data associated with a data item defined in another Structural Element to
607 be directly associated with this XML element.

608 Figure 10 represents the structure of a DataItemRef XML element showing the at-
609 tributes defined for DataItemRef.

Figure 10: DataItemRef Diagram

610 Table 15 lists the attributes defined for the DataItemRef element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 37

 July 15, 2020

Table 15: Attributes for DataItemRef

Attribute Description Occurrence

idRef A pointer to the id attribute of the DataItem that 1
contains the information to be associated with this XML
element.
idRef is a required attribute.
name The optional name of the DataItemRef. Only 0..1
informative.
name is an NMTOKEN XML type.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 38

 July 15, 2020

611 5 Component Structural Elements

612 Component Structural Elements are XML containers used to represent physical parts or
613 logical functions of a piece of equipment.

614 Component Structural Elements are defined into two major categories:

615 • Top Level Component elements are used to group the Structural Elements repre-
616 senting the most significant physical or logical functions of a piece of equipment.
617 The Top Level Component elements provided in an MTConnectDevices docu-
618 ment SHOULD be restricted to those defined in Table 16. However, these Top Level
619 Component elements MAY also be used as Lower Level Component elements;
620 as required.

621 • Lower Level Component elements are used to describe the sub-parts of the par-
622 ent Component to provide more clarity and granularity to the physical or logical
623 structure of the Top Level Component elements.

624 This section of the Devices Information Model provides guidance for the most common re-
625 lationships between Top Level Component elements and Lower Level child components.
626 However, all Component elements MAY be used in any configuration, as required, to
627 fully describe a piece of equipment.

628 As described in Section 4 - Structural Elements for MTConnectDevices, Component is

629 an abstract type Structural Element within the Devices Information Model and will never
630 appear directly in the MTConnectDevices XML document. As abstract type XML
631 elements, Component will be replaced in the XML document by a specific Component
632 type.

633 Table 16 defines the Top Level Component elements available to describe a piece of
634 equipment.

Table 16: Top Level Component Elements

Top Level Component Element †† Description

Axes An XML container used to organize the Structural
Elements of a piece of equipment that perform
linear or rotational motion.
Controller An XML container used to organize information
about an intelligent or computational function
within a piece of equipment.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 39

 July 15, 2020

Continuation of Table 16
Top Level Component Element †† Description
Systems An XML container used to organize information
for Lower Level elements representing the major
sub-systems that are permanently integrated into a
piece of equipment.
Auxiliaries An XML container used to organize information
for Lower Level elements representing functional
sub-systems that provide supplementary or
extended capabilities for a piece of equipment, but
they are not required for the basic operation of the
equipment.
Resources An XML container used to organize information
for Lower Level elements representing types of
items, materials, and personnel that support the
operation of a piece of equipment or work to be
performed at a location. Resources also
represents materials or other items consumed or
transformed by a piece of equipment for
production of parts or other types of goods.
Interfaces An XML container that organizes information
used to coordinate actions and activities between
pieces of equipment that communicate
information between each other.

635 Note: †† The following components have been relocated or redefined since they are
636 not classified as restricted Top Level components:
637 - Power was DEPRECATED in MTConnect Version 1.1 and was replaced
638 by the Data Entity called AVAILABILITY.
639 - Door has been redefined as a Lower Level component of a parent Compo-
640 nent element or as a Composition element.
641 - Actuator, due to its uniqueness, has been redefined as a piece of equip-
642 ment with the ability to be represented as a Lower Level component of a parent
643 Component element or as a Composition element.
644 - Sensor, due to its uniqueness, has been redefined as a piece of equipment
645 with the ability to be represented as a Lower Level component of a parent Com-
646 ponent element (See Section 9.1 - Sensor for further detail).
647 - Stock has been redefined as a Lower Level component of the Resources
648 Top Level Component element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 40

 July 15, 2020

649 The common relationship between the Top Level Component elements and the Lower
650 Level child Component elements are described below. It should be noted that as the MT-
651 Connect Standard evolves, more Component types will be added to organize information
652 for new types of equipment and/or new physical or logical sub-parts of equipment.

653 5.1 Axes

654 Axes is a top-level Component that organizes information representing linear or rota-
655 tional motion for a piece of equipment. The Linear axis Component represents linear
656 motion, and the Rotary axis Component represents rotational motion.

657 In robotics, the term Axis is synonymous with Joint. A Joint is the connection between
658 two parts of the structure that move in relation to each other.

659 Linear and Rotary components MUST have a name atribute that MUST follow the
660 conventions described below. Use the nativeName attribute for the manufacturer’s
661 name of the axis if it differs from the assigned name.

662 MTConnect has two high-level classes for automation equipment as follows: (1) Equip-
663 ment that controls cartesian coordinate axes and (2) Equipment that controls articulated
664 axes. There are ambiguous cases where some machines exhibit both characteristics; when
665 this occurs, the primary control system’s configuration determines the classification.

666 Examples of cartesian coordinate equipment are CNC Machine Tools, Coordinate mea-
667 surement machines, as specified in ISO 841, and 3D Printers. Examples of articulated
668 automation equipment are Robotic systems as specified in ISO 8373.

669 The following sections define the designation of names for the axes and additional guid-
670 ance when selecting the correct scheme to use for a given piece of equipment.

671 5.1.1 Cartesian Coordinate Naming Conventions

672 A Three-Dimensional Cartesian Coordinate control system organizes its axes orthogonally
673 relative to a machine coordinate system where the manufacturer of the equipment specifies
674 the origin.

675 Axes name SHOULD comply with ISO 841, if possible.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 41

 July 15, 2020

676 5.1.1.1 Linear Motion

677 A piece of equipment MUST represent prismatic motion using a Linear axis Compo-
678 nent and assign its name using the designations X, Y, and Z. A Linear axis name
679 MUST append a monotonically increasing suffix when there are more than one parallel
680 axes; for example, X2, X3, and X4.

681 5.1.1.2 Rotary Motion

682 MTConnect MUST assign the name to Rotary axes exhibiting rotary motion using A,
683 B, and C. A Rotary axis name MUST append a monotonically increasing suffix when
684 more than one Rotary axis rotates around the same Linear axis; for example, A2, A3,
685 and A4.

686 5.1.2 Articulated Machine Control Systems

687 An articulated control system’s axes represent the connecting linkages between two ad-
688 jacent rigid members of an assembly. The Linear axis represents prismatic motion,
689 and the Rotary axis represents the rotational motion of the two related members. The
690 control organizes the axes in a kinematic chain from the mounting surface (base) to the
691 end-effector or tooling.

692 5.1.3 Articulated Machine Axis Names

693 The axes of articulated machines represent forward kinematic relationships between me-
694 chanical linkages. Each axis is a connection between linkages, also referred to as joints,
695 and MUST be named using a J followed by a monotonically increasing number; for ex-
696 ample, J1, J2, J3. The numbering starts at the base axis connected or closest to the
697 mounting surface, J1, incrementing to the mechanical interface, Jn, where n is the num-
698 ber of the last axis. The chain forms a parent-child relationship with the parent being the
699 axis closest to the base.

700 A machine having an axis with more than one child MUST number each branch using its
701 numeric designation followed by a branch number and a monotonically increasing number.
702 For example, if J2 has two children, the first child branch MUST be named J2.1.1 and
703 the second child branch J2.2.1. A child of the first branch MUST be named J2.1.2,
704 incrementing to J2.1.n, where J2.1.n is the number of the last axis in that branch.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 42

 July 15, 2020

705 5.1.4 Rotary Component

706 A Rotary axis represents rotation about a fixed axis.

707 5.1.5 Linear Component

708 A Linear axis represents prismatic motion along a fixed axis.

709 5.2 Controller

710 Controller is a Top Level container that organizes information for an intelligent part
711 of a piece of equipment that monitors and calculates information to alter the operating
712 conditions of the equipment. Typical types of controllers for a piece of equipment include
713 CNC (Computer Numerical Control), PAC (Programmable Automation Control), IPC (In-
714 dustrialized Computer), or IC (Imbedded Computer).

715 Controller is a component that organizes and provides information regarding the exe-
716 cution of a control program(s), the mode of operation of the piece of equipment, and fault
717 information regarding the operation of the equipment.

718 Note: MTConnect Version 1.1.0 and later implementations SHOULD use a Lower
719 Level Component element called Path to represent an individual tool path or
720 other independent function within a Controller element. When the Con-
721 troller element is capable of executing more than one simultaneous and in-
722 dependent programs, the implementation MUST specify a Lower Level Path
723 element representing each of the independent functions of the Controller.

724 5.2.1 Path

725 Path is an XML container that represents the information for an independent operation
726 or function within a Controller. For many types of equipment, Path represents a set
727 of Axes, one or more Program elements, and the data associated with the motion of a
728 control point as it moves through space. However, it MAY also represent any independent
729 function within a Controller that has unique data associated with that function.

730 Path SHOULD provide an EXECUTION data item to define the operational state of the
731 Controller component of the piece of equipment.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 43

 July 15, 2020

732 If the Controller is capable of performing more than one independent operation or
733 function simultaneously, a separate Path component MUST be used to organize the data
734 associated with each independent operation or function.

735 5.3 Systems

736 Systems is a Top Level XML container that provides structure for the information de-
737 scribing one or more Lower Level functional systems that perform as discrete operating
738 modules of the equipment or provide utility type services to support the operation of the
739 equipment. These systems are required for the piece of equipment to perform its intended
740 function and are permanently integrated into the piece of equipment.

741 Since these systems operate as separate functional units, they are represented in the MT-
742 ConnectDevices XML document as individual Lower Level Component elements
743 of Systems based on the function or service provided.

744 5.3.1 Hydraulic System

745 Hydraulic is an XML container that represents the information for a system comprised
746 of all the parts involved in moving and distributing pressurized liquid throughout the piece
747 of equipment.

748 5.3.2 Pneumatic System

749 Pneumatic is an XML container that represents the information for a system comprised
750 of all the parts involved in moving and distributing pressurized gas throughout the piece
751 of equipment.

752 5.3.3 Coolant System

753 Coolant is an XML container that represents the information for a system comprised
754 of all the parts involved in distribution and management of fluids that remove heat from a
755 piece of equipment.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 44

 July 15, 2020

756 5.3.4 Lubrication System

757 Lubrication is an XML container that represents the information for a system com-
758 prised of all the parts involved in distribution and management of fluids used to lubricate
759 portions of the piece of equipment.

760 5.3.5 Electric System

761 Electric is an XML container that represents the information for the main power sup-
762 ply for device piece of equipment and the distribution of that power throughout the equip-
763 ment. The electric system will provide all the data with regard to electric current, voltage,
764 frequency, etc. that applies to the piece of equipment as a functional unit. Data regarding
765 electric power that is specific to a Component will be reported as Data Entities for that
766 specific Component.

767 5.3.6 Enclosure System

768 Enclosure is an XML container that represents the information for a structure used to
769 contain or isolate a piece of equipment or area. The Enclosure system may provide
770 information regarding access to the internal components of a piece of equipment or the
771 conditions within the enclosure. For example, Door may be defined as a Lower Level
772 Component or Composition element of the Enclosure system.

773 5.3.7 Protective System

774 Protective is an XML container that represents the information for those functions
775 that detect or prevent harm or damage to equipment or personnel. Protective does not
776 include the information relating to the Enclosure system.

777 5.3.8 ProcessPower System

778 ProcessPower is an XML container that represents the information for a power source
779 associated with a piece of equipment that supplies energy to the manufacturing process
780 separate from the Electric system. For example, this could be the power source for an
781 EDM machining process, an electroplating line, or a welding system.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 45

 July 15, 2020

782 5.3.9 Feeder System

783 Feeder is an XML container that represents the information for a system that manages
784 the delivery of materials within a piece of equipment. For example, this could describe
785 the wire delivery system for an EDM or welding process; conveying system or pump and
786 valve system distributing material to a blending station; or a fuel delivery system feeding
787 a furnace.

788 5.3.10 Dielectric System

789 Dielectric is an XML container that represents the information for a system that man-
790 ages a chemical mixture used in a manufacturing process being performed at that piece of
791 equipment. For example, this could describe the dielectric system for an EDM process or
792 the chemical bath used in a plating process.

793 5.3.11 EndEffector System

794 EndEffector is an XML container that represents the information for those functions
795 that form the last link segment of a piece of equipment. It is the part of a piece of equipment
796 that interacts with the manufacturing process.

797 5.3.12 WorkEnvelope System

798 WorkEnvelope organizes information about the physical process execution space within
799 a piece of equipment. The WorkEnvelope MAY provide information regarding the
800 physical workspace and the conditions within that workspace.

801 5.4 Auxiliaries

802 Auxiliaries is a Top Level XML container that provides structure for the information
803 describing one or more Lower Level functional systems that provide supplementary or
804 additional capabilities for the operation of a piece of equipment. These systems extend the
805 capabilities of a piece of equipment, but are not required for the equipment to function.

806 Since these systems operate as independent units or are only temporarily associated with a
807 piece of equipment, they are represented in the MTConnectDevices XML document as

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 46

 July 15, 2020

808 individual Lower Level Component elements of Auxiliaries based on the function
809 or service provided to the equipment.

810 5.4.1 Loader System

811 Loader is an XML container that represents the information for a unit comprised of all
812 the parts involved in moving and distributing materials, parts, tooling, and other items to
813 or from a piece of equipment.

814 5.4.2 WasteDisposal System

815 WasteDisposal is an XML container that represents the information for a unit com-
816 prised of all the parts involved in removing manufacturing byproducts from a piece of
817 equipment.

818 5.4.3 ToolingDelivery System

819 ToolingDelivery is an XML container that represents the information for a unit in-
820 volved in managing, positioning, storing, and delivering tooling within a piece of equip-
821 ment.

822 5.4.4 BarFeeder System

823 BarFeeder is an XML container that represents the information for a unit involved in
824 delivering bar stock to a piece of equipment.

825 5.4.5 Environmental System

826 Environmental is an XML container that represents the information for a unit or func-
827 tion involved in monitoring, managing, or conditioning the environment around or within
828 a piece of equipment.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 47

 July 15, 2020

829 5.4.6 Sensor System

830 Sensor is a XML container that represents the information for a piece of equipment that
831 responds to a physical stimulus and transmits a resulting impulse or value from a sensing
832 unit. When modeled as a component of Auxiliaries, sensor SHOULD represent an
833 integrated sensor unit system that provides signal processing, conversion, and communi-
834 cations. A sensor unit may have multiple sensing elements; each representing the data for
835 a variety of measured values. See Section 9.1.2 - Sensor Unit for more details on sensor
836 unit.

837 Note: If modeling an individual sensor, then sensor should be associated with the
838 component that the measured value is most closely associated. See Section 5.7.3
839 - Sensor.

840 5.4.7 Deposition System

841 Deposition is an XML container that represents the information for a system that man-
842 ages the addition of material or state change of material being performed in an additive
843 manufacturing process. For example, this could describe the portion of a piece of equip-
844 ment that manages a material extrusion process or a vat polymerization process.

845 5.5 Resources

846 Resources is a Top Level XML container that groups items that support the operation
847 of a piece of equipment. Resources also represents materials or other items consumed,
848 transformed, or used for production of parts, materials, or other types of goods by a piece
849 of equipment.

850 5.5.1 Materials

851 Materials is an XML container that provides information about materials or other items
852 consumed or used by the piece of equipment for production of parts, materials, or other
853 types of goods. Materials also represents parts or part stock that are present at a piece
854 of equipment or location to which work is applied to transform the part or stock material
855 into a more finished state.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 48

 July 15, 2020

856 5.5.1.1 Stock

857 Stock is an XML container that represents the information for the material that is used in
858 a manufacturing process and to which work is applied in a machine or piece of equipment
859 to produce parts.

860 Stock may be either a continuous piece of material from which multiple parts may be
861 produced or it may be a discrete piece of material that will be made into a part or a set of
862 parts.

863 5.5.2 Personnel

864 Personnel is an XML container that provides information about an individual or indi-
865 viduals who either control, support, or otherwise interface with a piece of equipment.

866 5.6 Interfaces

867 Interfaces is a Top Level XML Structural Element in the MTConnectDevices

868 XML document. Interfaces organizes the information provided by a piece of equip-
869 ment used to coordinate activities with other pieces of equipment. As such, Interfaces
870 represents the inter-device communication information between a piece of equipment and
871 other pieces of equipment.

872 See MTConnect Standard: Part 5.0 - Interfaces for detailed information on Inter-
873 faces.

874 5.7 Other Components

875 While most component elements SHOULD be modeled in a specific manner, there are
876 some types of component elements that are used ubiquitously in equipment and MAY be
877 associated with any number of different types of parent component elements.

878 These components MAY be modeled as Lower Level components of the Parent Element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 49

 July 15, 2020

879 5.7.1 Actuator

880 Actuator is an XML container that represents the information for an apparatus for mov-
881 ing or controlling a mechanism or system. It takes energy usually provided by air, electric
882 current, or liquid and converts the energy into some kind of motion.

883 5.7.2 Door

884 Door is an XML container that represents the information for a mechanical mechanism or
885 closure that can cover, for example, a physical access portal into a piece of equipment. The
886 closure can be opened or closed to allow or restrict access to other parts of the equipment.

887 When Door is represented as a Component, it MUST have a data item called DOOR_-
888 STATE to indicate if the door is OPEN, CLOSED, or UNLATCHED. A Component MAY
889 contain multiple Door components.

890 5.7.3 Sensor

891 Sensor is a XML container that represents the information for a piece of equipment that
892 responds to a physical stimulus and transmits a resulting impulse or value. If modeling
893 individual sensors, then sensor should be associated with the component that the measured
894 value is most closely associated.

895 See Section 9.1 - Sensor for more details on the use of Sensor.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 50

 July 15, 2020

896 6 Composition Type Structural Elements

897 Composition Structural Elements are used to describe the lowest level physical build-
898 ing blocks of a piece of equipment contained within a Component. By referencing a spe-
899 cific Composition element, further clarification and meaning to data associated with a
900 specific Component can be achieved.

901 Both Component and Composition elements are Lower Level child Component
902 XML elements representing the sub-parts of the parent Component. However, there are
903 distinct differences between Component and Composition type elements.

904 Component elements may be further defined with Lower Level Component elements
905 and may have associated Data Entities.

906 Composition elements represent the lowest level physical part of a piece of equipment.
907 They MUST NOT be further defined with Lower Level Component elements and they
908 MUST NOT have Data Entities directly associated with them. They do provide additional
909 information that can be used to enhance the specificity of Data Entities associated with the
910 parent Component.

911 Table 17 defines Composition type elements that are currently available to describe
912 sub-parts of a Component element.

Table 17: Composition type Elements

Element Type Description

ACTUATOR A mechanism for moving or controlling a
mechanical part of a piece of equipment.
It takes energy usually provided by air, electric
current, or liquid and converts the energy into
some kind of motion.
AMPLIFIER An electronic component or circuit for
amplifying power, electric current, or voltage.
BALLSCREW A mechanical structure for transforming rotary
motion into linear motion.
BELT An endless flexible band used to transmit
motion for a piece of equipment or to convey
materials and objects.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 51

 July 15, 2020

Continuation of Table 17
Element Type Description
BRAKE A mechanism for slowing or stopping a moving
object by the absorption or transfer of the
energy of momentum, usually by means of
friction, electrical force, or magnetic force.
CHAIN An interconnected series of objects that band
together and are used to transmit motion for a
piece of equipment or to convey materials and
objects.
CHOPPER A mechanism used to break material into
smaller pieces.
CHUCK A mechanism that holds a part, stock material,
or any other item in place.
CHUTE An inclined channel for conveying material.
CIRCUIT_BREAKER A mechanism for interrupting an electric circuit.
CLAMP A mechanism used to strengthen, support, or
fasten objects in place.
COMPRESSOR A pump or other mechanism for reducing
volume and increasing pressure of gases in
order to condense the gases to drive
pneumatically powered pieces of equipment.
DOOR A mechanical mechanism or closure that can
cover a physical access portal into a piece of
equipment allowing or restricting access to
other parts of the equipment.
DRAIN A mechanism that allows material to flow for
the purpose of drainage from, for example, a
vessel or tank.
ENCODER A mechanism to measure position.
EXPOSURE_UNIT A mechanism for emitting a type of radiation
EXTRUSION_UNIT A mechanism for dispensing liquid or powered
materials
FAN Any mechanism for producing a current of air.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 52

 July 15, 2020

Continuation of Table 17
Element Type Description
FILTER Any substance or structure through which
liquids or gases are passed to remove suspended
impurities or to recover solids.
GALVANOMOTOR An electromechanical actuator that produces
deflection of a beam of light or energy in
response to electric current through its coil in a
magnetic field.
GRIPPER A mechanism that holds a part, stock material,
or any other item in place.
HOPPER A chamber or bin in which materials are stored
temporarily, typically being filled through the
top and dispensed through the bottom.
LINEAR_POSITION_FEEDBACK A mechanism that measures linear motion or
position.
DEPRECATION WARNING : May be
deprecated in the future. Recommend using
ENCODER.
MOTOR A mechanism that converts electrical,
pneumatic, or hydraulic energy into mechanical
energy.
OIL A viscous liquid.
POWER_SUPPLY A unit that provides power to electric
mechanisms.
PULLEY A mechanism or wheel that turns in a frame or
block and serves to change the direction of or to
transmit force.
PUMP An apparatus raising, driving, exhausting, or
compressing fluids or gases by means of a
piston, plunger, or set of rotating vanes.
REEL A rotary storage unit for material
SENSING_ELEMENT A mechanism that provides a signal or
measured value.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 53

 July 15, 2020

Continuation of Table 17
Element Type Description
SPREADER A mechanism for flattening or spreading
materials
STORAGE_BATTERY A component consisting of one or more cells, in
which chemical energy is converted into
electricity and used as a source of power.
SWITCH A mechanism for turning on or off an electric
current or for making or breaking a circuit.
TABLE A surface for holding an object or material
TANK A receptacle or container for holding material.
TENSIONER A mechanism that provides or applies a stretch
or strain to another mechanism.
TRANSFORMER A mechanism that transforms electric energy
from a source to a secondary circuit.
VALVE Any mechanism for halting or controlling the
flow of a liquid, gas, or other material through a
passage, pipe, inlet, or outlet.
VAT A container for liquid or powdered materials
WATER A fluid.
WIRE A string like piece or filament of relatively rigid
or flexible material provided in a variety of
diameters.
WORKPIECE An object or material on which a form of work
is performed.

913 Note: As the MTConnect Standard evolves, more Composition types will be
914 added.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 54

 July 15, 2020

915 7 Data Entities for Device

916 In the MTConnectDevices XML document, Data Entities are XML elements that de-
917 scribe data that can be reported by a piece of equipment and are associated with Device
918 and Component Structural Elements. While the Data Entities describe the data that can
919 be reported by a piece of equipment in the MTConnectDevices document, the actual
920 data values are provided in the Streams Information Model. See MTConnect Standard:
921 Part 3.0 - Streams Information Model for detail on the reported values.

922 Each Data Entity SHOULD be modeled in the MTConnectDevices document such
923 that it is associated with the Structural Element that the reported data directly applies.

924 When Data Entities are associated with a Structural Element, they are organized in a
925 DataItems XML element. DataItems is a container type XML element. DataItems
926 provides the structure for organizing individual DataItem elements that represent each
927 Data Entity. The DataItems container is comprised of one or more DataItem type
928 XML element(s).

929 DataItem describes specific types of Data Entities that represent a numeric value, a
930 functioning state, or a health status reported by a piece of equipment. DataItem provides
931 a detailed description for each Data Entity that is reported; it defines the type of data being
932 reported and an array of optional attributes that further describe that data. The different
933 types of DataItem elements are defined in Section 8 - Listing of Data Items.

934 Figure 11 demonstrates the relationship between Data Entities (DataItem) and the var-
935 ious Structural Elements in the MTConnectDevices XML document.

Figure 11: Example Data Entities for Device (DataItem)

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 55

 July 15, 2020

936 7.1 DataItems

937 The DataItems XML element is the first, or highest, level container for the Data Entities
938 associated with a Device or Component XML element. DataItems MUST contain
939 only DataItem type elements. DataItems MUST contain at least one DataItem
940 type element, but MAY contain multiple DataItem type elements.

Table 18: MTConnect DataItems Element

Element Description Occurrence

DataItems An XML container consisting of one or more types of 0..1
DataItem XML elements.
Only one DataItems container MUST appear for
each Structural Element in the XML document.

941 7.2 DataItem

942 A DataItem XML element represents each Data Entity that MAY be reported by a piece
943 of equipment through an Agent. DataItem provides a detailed description for each Data
944 Entity that is reported and defines the type of data being reported along with an array of
945 optional attributes that further define that data. XML elements representing DataItem
946 will include elements such as TEMPERATURE, PRESSURE, and VELOCITY.
Table 19: MTConnect DataItem Element

Element Description Occurrence

DataItem Data Entity describing a piece of information reported 1..*
about a piece of equipment.

947 7.2.1 XML Schema Structure for DataItem

948 Figure 12 represents the structure of a DataItem XML element showing the attributes
949 defined for DataItem and the elements that may be associated with DataItem type
950 XML elements.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 56

 July 15, 2020

Figure 12: DataItem Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 57

 July 15, 2020

951 7.2.2 Attributes for DataItem

952 Table 20 lists the attributes defined to provide information for a DataItem type XML
953 element.

954 DataItem MUST specify the type of data being reported, the id of the DataItem, and
955 the category of the DataItem.
Table 20: Attributes for DataItem

Attribute Description Occurrence

name The name of the data item. 0..1
name is provided as an additional
human readable identifier for this data
item in addition to the id.
name is an optional attribute and will
be implementation dependent.
An NMTOKEN XML type.
id The unique identifier for this element. 1
id is a required attribute.
The id attribute MUST be unique
within the MTConnectDevices
document.
An XML ID-type.
type The type of data being measured. 1
type is a required attribute.
Examples of types are POSITION,
VELOCITY, ANGLE, BLOCK, and
ROTARY_VELOCITY.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 58

 July 15, 2020

Continuation of Table 20
Attribute Description Occurrence
subType A sub-categorization of the data item 0..1
type.
subType is an optional attribute.
For example, the subType of
POSITION can be ACTUAL or
COMMANDED.
Not all type attributes have a
subType.
statistic Describes the type of statistical 0..1
calculation performed on a series of
data samples to provide the reported
data value.
statistic is an optional attribute.
Examples of statistic are
AVERAGE, MINIMUM, MAXIMUM,
ROOT_MEAN_SQUARE, RANGE,
MEDIAN, MODE, and
STANDARD_DEVIATION.
units The unit of measurement for the 0..1
reported value of the data item.
units is an optional attribute.
Data items in the Sample category
MUST report the standard units for the
measured values.
See Section 7.2.2.5 - units Attribute for
DataItem for a list of available standard
units identified in the MTConnect
Standard.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 59

 July 15, 2020

Continuation of Table 20
Attribute Description Occurrence
nativeUnits The native units of measurement for the 0..1
reported value of the data item.
nativeUnits is an optional attribute.
See Section 7.2.2.6 - nativeUnits
Attribute for DataItem for a list of
available native units identified in the
MTConnect Standard.
nativeScale The nativeUnits may not be scaled 0..1
to directly represent the original
measured value. nativeScale MAY
be used to convert the reported value to
represent the original measured value.
nativeScale is an optional attribute.
As an example, the nativeUnits
may be reported as GALLON/MINUTE.
The measured value may actually be in
1000 GALLON/MINUTE. The value of
the reported data MAY be divided by
the nativeScale to convert the
reported value to its original measured
value and units.
If provided, the value MUST be
numeric.
category Specifies the kind of information 1
provided by a data item.
category is a required attribute.
The available options are Sample,
Event, or Condition.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 60

 July 15, 2020

Continuation of Table 20
Attribute Description Occurrence
coordinateSystem For measured values relative to a 0..1
coordinate system like POSITION, the
coordinate system being used may be
reported.
coordinateSystem is an optional
attribute.
The available values for
coordinateSystem are WORK and
MACHINE.
compositionId The identifier attribute of the 0..1
Composition element that the
reported data is most closely associated.
compositionId is an optional
attribute.
sampleRate The rate at which successive samples of 0..1
a data item are recorded by a piece of
equipment.
sampleRate is an optional attribute.
sampleRate is expressed in terms of
samples per second.
If the sampleRate is smaller than
one, the number can be represented as a
floating point number.
For example, a rate 1 per 10 seconds
would be 0.1

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 61

 July 15, 2020

Continuation of Table 20
Attribute Description Occurrence
representation Description of a means to interpret data 0..1
consisting of multiple data points or as
a single value.

representation is an optional
attribute.
representation defines the unique
format for each set of data.
representation for
TIME_SERIES, DISCRETE
(DEPRECATED in Version 1.5),
DATA_SET, TABLE, and VALUE are
defined in Section 7.2.2.12 -
representation Attribute for DataItem.
If representation is not specified,
it MUST be determined to be VALUE.
significantDigits The number of significant digits in the 0..1
reported value.
significantDigits is an optional
attribute.
This SHOULD be specified for all
numeric values.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 62

 July 15, 2020

Continuation of Table 20
Attribute Description Occurrence
discrete An indication signifying whether each 0..1
value reported for the Data Entity is
significant and whether duplicate values
are to be suppressed.
The value defined MUST be either
true or false - an XML boolean
type.
true indicates that each update to the
Data Entity’s value is significant and
duplicate values MUST NOT be
suppressed.
false indicates that duplicated values
MUST be suppressed.
If a value is not defined for discrete,
the default value MUST be false.
coordinateSystemIdRef The associated CoordinateSystem 0..1
context for the DataItem.

956 7.2.2.1 name Attribute for DataItem

957 The attribute name is provided as an additional human readable identifier for a data item.
958 It is not required and is implementation dependent.

959 7.2.2.2 id Attribute for DataItem

960 Each DataItem element MUST be identified with an id. The id attribute MUST be
961 unique across the entire MTConnectDevices document for a piece of equipment, in-
962 cluding the identifiers for all Structural Elements. This unique id provides the information
963 required by a client software application to uniquely identify each Data Entity.

964 For example, an XML document may provide three different Data Entities representing
965 the position of the axes on a machine (x axis position, y axis position, and z axis position).
966 All three may be modeled in the XML document as POSITION type data items for the
967 Axes components. The unique id allows the client software application to distinguish
968 the data for each of the axes.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 63

 July 15, 2020

969 7.2.2.3 type and subType Attributes for DataItem

970 The attribute type specifies the kind of data that is represented by the data item.

971 The attribute type MUST be specified for every data item.

972 A data item MAY further qualify the data being reported by specifying a subType.
973 subType is required for certain data item types. For example, POSITION has the
974 subType of ACTUAL and PROGRAMMED. Both data values can be represented in the
975 document as two separate and different DataItem XML elements – POSITION with
976 subType ACTUAL and POSITION with subType PROGRAMMED.

977 The type and subType SHOULD be used to further identify the meaning of the DataItem
978 associated with a Component element when a subType is applicable. There SHOULD
979 NOT be more than one DataItem with the same type, subType, and composi-
980 tionId within a Component element.

981 Section 8 - Listing of Data Items provides a detailed listing of the data item type and
982 subType elements defined for each category of data item available for a piece of
983 equipment: SAMPLE, EVENT, and CONDITION.

984 7.2.2.4 statistic Attribute for DataItem

985 A piece of equipment may further process some data types using a statistical calculation
986 like average, mean, or square root. In this case, the statistic attribute MAY be used
987 to indicate how the data was processed.

988 statistic may be defined for any SAMPLE type DataItem. All statistic data is re-
989 ported in the standard units of the DataItem.

990 statistic data is always the result of a calculation using data that has been measured
991 over a specified period of time.

992 The value of statistic may be periodically reset. When a piece of equipment reports
993 a DataItem with a value that is a statistic, the information provided in the XML
994 document for that Data Entity MUST include an additional attribute called duration.
995 The attribute duration defines the period of time over which the statistic has been
996 calculated. See MTConnect Standard: Part 3.0 - Streams Information Model for more
997 information about duration.

998 Table 21 shows the statistic calculations that can be defined for a DataItem.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 64

 July 15, 2020

Table 21: DataItem attribute statistic type

Statistic Description
AVERAGE Mathematical Average value calculated for the data item
during the calculation period.
KURTOSIS DEPRECATED in Version 1.6. A measure of the
"peakedness" of a probability distribution; i.e., the shape
of the distribution curve.
MAXIMUM Maximum or peak value recorded for the data item
during the calculation period.
MEDIAN The middle number of a series of numbers.
MINIMUM Minimum value recorded for the data item during the
calculation period.
MODE The number in a series of numbers that occurs most
often.
RANGE Difference between the maximum and minimum value of
a data item during the calculation period. Also represents
Peak-to-Peak measurement in a waveform.
ROOT_MEAN_SQUARE Mathematical Root Mean Square (RMS) value calculated
for the data item during the calculation period.
STANDARD_DEVIATION Statistical Standard Deviation value calculated for the
data item during the calculation period.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 65

 July 15, 2020

999 7.2.2.5 units Attribute for DataItem

1000 Table 22 lists the units that are defined as the standard unit of measure for each type of
1001 DataItem. All SAMPLE type data items MUST report data values in standard units.

Table 22: DataItem attribute units type

Units Description
AMPERE Amps
CELSIUS Degrees Celsius
COUNT A count of something.
CUBIC_MILLIMETER Geometric volume in millimeters
CUBIC_MILLIMETER/SECOND Change of geometric volume per second
CUBIC_MILLIMETER/SECOND2 Change in geometric volume per second
squared
DECIBEL Sound Level
DEGREE Angle in degrees
DEGREE/SECOND Angular degrees per second
DEGREE/SECOND2 Angular acceleration in degrees per second
squared
DEGREE_3D A space-delimited, floating-point
representation of the angular rotation in
degrees around the X, Y, and Z axes relative
to a cartesian coordinate system respectively
in order as A, B, and C. If any of the
rotations is not known, it MUST be zero (0).
GRAM/CUBIC_METER Gram per cubic meter.
HERTZ Frequency measured in cycles per second
JOULE A measurement of energy.
KILOGRAM Kilograms
LITER Measurement of volume of a fluid
LITER/SECOND Liters per second
MICRO_RADIAN Measurement of Tilt

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 66

 July 15, 2020

Continuation of Table 22
Units Description
MILLIGRAM Milligram
MILLIGRAM/CUBIC_MILLIMETER Milligram per cubic millimeter
MILLILITER Milliliter
MILLIMETER Millimeters
MILLIMETER/REVOLUTION Millimeters per revolution.
MILLIMETER/SECOND Millimeters per second
MILLIMETER/SECOND2 Acceleration in millimeters per second
squared
MILLIMETER_3D A point in space identified by X, Y, and Z
positions and represented by a
space-delimited set of numbers each
expressed in millimeters.
NEWTON Force in Newtons
NEWTON_METER Torque, a unit for force times distance.
OHM Measure of Electrical Resistance
PASCAL Pressure in Newtons per square meter
PASCAL_SECOND Measurement of Viscosity
PERCENT Percentage
PH A measure of the acidity or alkalinity of a
solution.
REVOLUTION/MINUTE Revolutions per minute
REVOLUTION/SECOND Revolutions per second.
REVOLUTION/SECOND2 Revolutions per second squared.
SECOND A measurement of time.
SIEMENS/METER A measurement of Electrical Conductivity
VOLT Volts
VOLT_AMPERE Volt-Ampere (VA)
VOLT_AMPERE_REACTIVE Volt-Ampere Reactive (VAR)
WATT Watts

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 67

 July 15, 2020

Continuation of Table 22
Units Description
WATT_SECOND Measurement of electrical energy, equal to
one Joule

1002 7.2.2.6 nativeUnits Attribute for DataItem

1003 The DataItem MAY specify the engineering units used by the information source using
1004 the optional attribute nativeUnits. The nativeUnits are inclusive of the engi-
1005 neering units for the units attribute (See Table 22). One MAY use a prefixed value,
1006 for example nativeUnits="x:MILE", to extend the Controlled Vocabulary with a
1007 namespace.

1008 MTConnect specifies the following Controlled Vocabulary for nativeUnits in Ta-
1009 ble 23:
Table 23: DataItem attribute nativeunits type

Native Units Description

CENTIPOISE A measure of Viscosity
DEGREE/MINUTE Rotational velocity in degrees per minute
FAHRENHEIT Temperature in Fahrenheit
FOOT Feet
FOOT/MINUTE Feet per minute
FOOT/SECOND Feet per second
FOOT/SECOND2 Acceleration in feet per second squared
FOOT_3D A point in space identified by X, Y, and Z positions and
represented by a space-delimited set of numbers each
expressed in feet.
GALLON/MINUTE Gallons per minute.
HOUR A measurement of time in hours
INCH Inches
INCH/MINUTE Inches per minute
INCH/SECOND Inches per second

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 68

 July 15, 2020

Continuation of Table 23
Native Units Description
INCH/SECOND2 Acceleration in inches per second squared
INCH_3D A point in space identified by X, Y, and Z positions and
represented by a space-delimited set of numbers each
expressed in inches.
INCH_POUND A measure of torque in inch pounds.
KELVIN A measurement of temperature
KILOWATT A measurement in kilowatt.
KILOWATT_HOUR Kilowatt hours which is 3.6 mega joules.
LITER Measurement of volume of a fluid
LITER/MINUTE Measurement of rate of flow of a fluid
MILLIMETER/MINUTE Velocity in millimeters per minute
MINUTE A measurement of time in minutes
OTHER Unsupported units
POUND US pounds
POUND/INCH2 Pressure in pounds per square inch (PSI).
RADIAN Angle in radians
RADIAN/MINUTE Velocity in radians per minute.
RADIAN/SECOND Rotational acceleration in radian per second squared
RADIAN/SECOND2 Rotational acceleration in radian per second squared
REVOLUTION/SECOND Rotational velocity in revolution per second

1010 7.2.2.7 nativeScale Attribute for DataItem

1011 The units of measure for some measured values may be different from the nativeUnits
1012 defined in Section 7.2.2.8 - category Attribute for DataItem. In the cases where the units
1013 of measure use a different weighting or range than is provided by nativeUnits, the
1014 nativeScale attribute can be used to define the original units of measure.

1015 As an example, a velocity measured in units of 100 ft/min can be represented as native-
1016 Units="FEET/MINUTE" and nativeScale="100".

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 69

 July 15, 2020

1017 7.2.2.8 category Attribute for DataItem

1018 Many DataItem types provide two forms of data, a value (reported as either a SAMPLE
1019 or EVENT category) and a health status (reported as a CONDITION category). Therefore,
1020 each occurrence of a DataItem in the XML document MUST report a category at-
1021 tribute. This category attribute provides the information required by a client software
1022 application to determine the specific meaning of the data provided.

1023 Each Data Entity provided by a piece of equipment MUST be identified with one of the
1024 following: SAMPLE, EVENT, CONDITION.

1025 A SAMPLE is the reading of the value of a continuously variable or analog data value. A
1026 continuous value can be measured at any point-in-time and will always produce a result.
1027 An example of a continuous data value is the position of a linear axis called X.

1028 The data provided for a SAMPLE category data item is always a floating point number
1029 or integers that have an infinite number of possible values. This is different from a state
1030 or discrete type data item that has a limited number of possible values. A data item of
1031 category SAMPLE MUST also provide the units attribute.

1032 An EVENT is a data item representing a discrete piece of information from the piece of
1033 equipment. EVENT does not have intermediate values that vary over time, as does SAM-
1034 PLE. An EVENT is information that, when provided at any specific point in time, repre-
1035 sents the current state of the piece of equipment.

1036 There are two types of EVENT: those representing state, with two or more discrete values,
1037 and those representing messages that contain plain text data.

1038 An example of a state type EVENT is the value of the data item DOOR_STATE, which
1039 can be OPEN, CLOSED, or UNLATCHED. (Note: No other values are valid to represent the
1040 value of DOOR_STATE.)

1041 An example of a message type EVENT is the value for a data item PROGRAM. The value
1042 representing PROGRAM can be any valid string of characters.

1043 A CONDITION is a data item that communicates information about the health of a piece
1044 of equipment and its ability to function. A valid value for a data item in the category
1045 CONDITION can be one of Normal, Warning, or Fault.

1046 A data item of category CONDITION MAY report multiple values (CONDITION) at one
1047 time whereas a data item of category SAMPLE or EVENT can only have a single value at
1048 any one point in time.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 70

 July 15, 2020

1049 7.2.2.9 coordinateSystem Attribute for DataItem

1050 The values reported by a piece of equipment for some types of data will be associated
1051 to a specific positioning measurement system used by the equipment. The coordi-
1052 nateSystem attribute MAY be used to specify the coordinate system used for the mea-
1053 sured value.

1054 The coordinateSystem attribute is used by a client software application to interpret

1055 the spatial relationship between values reported by a piece of equipment.

1056 If coordinateSystem is not provided, all values representing positional data for Axes
1057 MUST be interpreted using the MACHINE coordinate system and all values representing
1058 positional data for Path MUST be interpreted using the WORK coordinate system.

1059 Table 24 defines the types of coordinateSystem currently supported by the MTCon-
1060 nectDevices XML document:
Table 24: DataItem attribute coordinateSystem type

Coordinate System Description

MACHINE An unchangeable coordinate system that has machine zero as its
origin.
WORK The coordinate system that represents the working area for a
particular workpiece whose origin is shifted within the
MACHINE coordinate system. If the WORK coordinates are not
currently defined in the piece of equipment, the MACHINE
coordinates will be used.

1061 7.2.2.10 compositionId Attribute for DataItem

1062 compositionId attribute identifies the id of the Composition element where the
1063 reported data is most closely associated.

1064 An example would be a TEMPERATURE associated with a Linear type axis may be
1065 further clarified by referencing the MOTOR or AMPLIFIER type Composition element
1066 associated with that axis, which differentiates the temperature of the motor from the tem-
1067 perature of the amplifier.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 71

 July 15, 2020

1068 The compositionId attribute provides the information required by a client software
1069 application to interpret the data with a greater specificity and to disambiguate between
1070 multiple Data Entities of the same data type associated with a Component element.

1071 7.2.2.11 sampleRate Attribute for DataItem

1072 The value for some data types provided by a piece of equipment may be reported as a
1073 single set of data containing a series of values that have been recorded at a fixed sample
1074 rate. When such data is reported, the sampleRate defines the rate at which successive
1075 samples of data were recorded.

1076 The sampleRate attribute provides the information required by a client software appli-
1077 cation to interpret the data and the sampling time relationship between successive values
1078 contained in the set of data.

1079 sampleRate is expressed in terms of samples per second. If the sample rate is smaller
1080 than one, the number can be represented as a floating point number. For example, a rate 1
1081 per 10 seconds would be 0.1

1082 7.2.2.12 representation Attribute for DataItem

1083 Some data types provide data that may consist of a series of values or a file of data, not a
1084 single value. Other data types provide a series of data values that may require additional
1085 information so that the data may be correctly understood by a client software application.

1086 When such data is provided, the representation attribute MUST be used to define
1087 the format for the data provided.

1088 The types of representation defined are provided in Table 25.

1089 Note: See MTConnect Standard: Part 3.0 - Streams Information Model for more
1090 information on the structure and format of each representation.
Table 25: DataItem attribute representation type

Representation Description
DATA_SET The reported value(s) are represented as a set of
key-value pairs.
Each reported value in the Data Set MUST have a
unique key.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 72

 July 15, 2020

Continuation of Table 25
Representation Description
DISCRETE
DEPRECATED in Version 1.5 DEPRECATED as a representation in
MTConnect Version. 1.5. Replaced by the
discrete attribute for a Data Entity –
Section 7.2.2.14 - discrete Attribute for DataItem.
A Data Entity where each discrete occurrence of the
data may have the same value as the previous
occurrence of the data. There is no reported state
change between occurrences of the data.
In this case, duplicate occurrences of the same data
value SHOULD NOT be suppressed.
An example of a DISCRETE data type would be a
parts counter that reports the completion of each part
versus the accumulation of parts. Another example
would be a Message that does not typically have a
reset state and may re-occur each time a specific
message is triggered.
TIME_SERIES A series of sampled data.
The data is reported for a specified number of
samples and each sample is reported with a fixed
period.
VALUE The measured value of the sample data.
If no representation is specified for a data item, the
representation MUST be determined to be VALUE.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 73

 July 15, 2020

Continuation of Table 25
Representation Description
TABLE A Table is a two dimensional set of key-value pairs
where the Entry represents a row, and the value is
a set of key-value pair Cell elements. The Table
follows the same behavior as the Data Set for
change tracking, clearing, and history. When an
Entry changes, all Cell elements update as a
single unit following the behavior of a Data Set.
Note: It is best to use the VARIABLE DataItem
type if the Cell elements represent multiple
semantic types.
Each Entry in the Table MUST have a unique
key. Each Cell of each Entry in the Table
MUST have a unique key.
See Section 5.6.5 of MTConnect Standard: Part 3.0 -
Streams Information Model, for a description of
Entry and Cell elements.

1091 7.2.2.13 significantDigits Attribute for DataItem

1092 significantDigits is used to specify the level of precision (number of significant

1093 digits) for the value provided for a data item.

1094 significantDigits attribute is not required for a data item, but it is recommended
1095 and SHOULD be used for any data item reporting a numeric value.

1096 7.2.2.14 discrete Attribute for DataItem

1097 An indication signifying whether each value reported for the Data Entity is significant and
1098 whether duplicate values are to be suppressed.

1099 The value defined MUST be either true or false - an XML boolean type.

1100 true indicates that each update to the Data Entity’s value is significant and duplicate
1101 values MUST NOT be suppressed.

1102 false indicates that duplicated values MUST be suppressed.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 74

 July 15, 2020

1103 If a value is not defined for discrete, the default value MUST be false.

1104 7.2.3 Elements for DataItem

1105 Table 26 lists the elements defined to provide additional information for a DataItem
1106 type XML element.

Table 26: Elements for DataItem

Element Description Occurrence

Source Source is an optional XML element that 0..1
identifies the Component, DataItem, or
Composition representing the area of the piece
of equipment from which a measured value
originates.
Additionally, Source MAY provide information
relating to the identity of a measured value. This
information is reported as CDATA for Source.
(example, a PLC tag)
Constraints Constraints is an optional container that 0..1
provides a set of expected values that can be
reported for this DataItem. Constraints are
used by a software application to evaluate the
validity of the reported data.
Filters An optional container for the Filter elements 0..1
associated with this DataItem element.
InitialValue InitialValue is an optional XML element 0..1
that defines the starting value for a data item as
well as the value to be set for the data item after a
reset event.
Only one InitialValue element may be
defined for a data item. The value will be constant
and cannot change.
If no InitialValue element is defined for a
data item that is periodically reset, then the starting
value for the data item MUST be a value of 0.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 75

 July 15, 2020

Continuation of Table 26
Element Description Occurrence
ResetTrigger ResetTrigger is an optional XML element 0..1
that identifies the type of event that may cause a
reset to occur. It is additional information
regarding the meaning of the data that establishes
an understanding of the time frame that the data
represents so that the data may be correctly
understood by a client software application.
Definition The Definition defines the meaning of Entry 0..1
and Cell elements associated with the
DataItem when the representation is
either DATA_SET or TABLE.

1107 7.2.3.1 Source Element for DataItem

1108 Source is an optional XML element that may be used to identify the physical part of a
1109 piece of equipment where the data represented by DataItem originated and/or it may be
1110 used to identify a complex name or an alternate name used to identify the data where it
1111 originated (e.g. a PLC tag name).

1112 As an example, data related to a servo motor on an Axes component may actually origi-
1113 nate from a measurement made in the Controller element.

1114 In the case where the real name associated with a DataItem element is either complex
1115 or does not meet the format requirements of a NMTOKEN XML type, the real name of
1116 the element may not be able to be expressed in the name attribute. Additionally, a second
1117 or alternate name may be required to describe a piece of data. An example of this case
1118 would be the identity of the bit address in a PLC that represents this piece of data (PLC
1119 address I0015.4). When these cases occur, the alternate name can be provided as the value
1120 for the CDATA for Source.

1121 The XML schema in Figure 13 represents the structure of the Source XML element
1122 showing the attributes defined for Source.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 76

 July 15, 2020

Figure 13: Source Diagram

1123 7.2.3.1.1 Attributes for Source

1124 Table 27 identifies the attributes available to identify Source for a measured value:

Table 27: Attributes for Source

Attribute Description Occurrence

componentId The identifier attribute of the Component 0..1
element that represents the physical part of a
piece of equipment where the data represented by
the DataItem element originated.
A Valid Data Value reported for componentId
MUST be the value of the id attribute for the
Component element identified.
componentId is an optional attribute.
dataItemId The identifier attribute of the DataItem that 0..1
represents the originally measured value of the
data referenced by this data item.
A Valid Data Value reported for dataItemId
MUST be the value of the id attribute for the
DataItem element identified.
dataItemId is an optional attribute.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 77

 July 15, 2020

Continuation of Table 27
Attribute Description Occurrence
compositionId The identifier attribute of the Composition 0..1
element that represents the physical part of a
piece of equipment where the data represented by
the DataItem element originated.
A Valid Data Value reported for
compositionId MUST be the value of the
id attribute for the Composition element
identified.
compositionId is an optional attribute.

1125 Note: † One of componentID, componsitionId , or dataItemId MUST be provided.

1126 7.2.3.2 Constraints Element for DataItem

1127 For some types of DataItem elements, the expected value(s) for the data reported for the
1128 DataItem MAY be restricted to specific values or a range of values.

1129 Constraints is an optional XML element that provides a way to define the expected
1130 value(s) or the upper and lower limits for the range of values that are expected to be
1131 reported in response to a Current Request or Sample Request.

1132 Constraints are used by a software application to evaluate the validity of the data
1133 reported.

1134 The value associated with each Constraint element is reported in the CDATA for that
1135 element.

1136 7.2.3.2.1 Schema for Constraints

1137 The XML schema in Figure 14 represents the structure of the Constraints XML
1138 element and the elements defined for Constraints.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 78

 July 15, 2020

Figure 14: Constraints Diagram

1139 Table 28 identifies the elements available to identify Constraints for a measured value:

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 79

 July 15, 2020

Table 28: Elements for Constraints

Element Description Occurrence

Value Value represents a single data value that is expected to 0..*
be reported for a DataItem element.
The data value is provided in the CDATA for this
element and may be any numeric or text content.
When there are multiple data values that may be
expected to be reported for a DataItem element,
multiple Value elements may be defined.
In the case where only one Value element is defined,
the data returned in response to a Current Request or
Sample Request request MUST be the data value defined
for Value element.
Value MUST NOT be used in conjunction with any
other Constraint elements.
Maximum If the data reported for a data item is a range of numeric 0..1
values, the expected value reported MAY be described
with an upper limit defined by this constraint.
The data value is provided in the CDATA for this
element and MUST be a value using the same units as
the reported data.
Minimum If the data reported for a data item is a range of numeric 0..1
values, the expected value reported MAY be described
with a lower limit defined by this constraint.
The data value is provided in the CDATA for this
element and MUST be a value using the same units as
the reported data.
Nominal The target or expected value for this data item. 0..1
The data value is provided in the CDATA for this
element and MUST be a value using the same units as
the reported data.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 80

 July 15, 2020

Continuation of Table 28
Element Description Occurrence
Filter DEPRECATED in Version 1.4 – Moved to the 0..1 †
Filters element of a DataItem.
If the data reported for a DataItem is a numeric value, a
new value MUST NOT be reported if the change from
the last reported value is less than the delta given as the
CDATA of this element. Filter is an abstract type XML
element. As such, Filter will never appear in the XML
document, but will be replaced by a Filter type. The only
currently supported Filter type is MINIMUM_DELTA.
The CDATA MUST be an absolute value using the same
Units as the reported data. Additional filter types MAY
be supported in the future.

1140 Note: † Remains in schema for backwards compatibility.

1141 7.2.3.3 Filters Element for DataItem

1142 Filters is an optional XML container that organizes the Filter elements for DataItem.

1143 Filters contains one or more Filter XML elements.

Table 29: MTConnect Filters Element

Element Description Occurrence

Filters An XML container consisting of one or more types of 0..1
Filter XML elements. Only one Filters container
MAY appear for a DataItem element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 81

 July 15, 2020

1144 7.2.3.3.1 Filter

1145 Filter provides a means to control when an Agent records updated information for a
1146 data item. Currently, there are two types of Filter elements defined in the MTConnect
1147 Standard - MINIMUM_DELTA and PERIOD. More Filter types may be added in the
1148 future.

1149 The value associated with each Filter element is reported in the CDATA for that ele-
1150 ment.

1151 Figure 15 represents the structure for Filter XML element.

Figure 15: Filter Diagram

1152 Table 30 describes the types of Filter defined for a DataItem element and the ex-
1153 pected behavior of an Agent when a Filter is applied to DataItem element.

Table 30: DataItem Element Filter type

type Description Occurrence

MINIMUM_DELTA For a MINIMUM_DELTA type Filter, a new 0..1 †
value MUST NOT be reported for a data item
unless the measured value has changed from the
last reported value by at least the delta given as
the CDATA of this element.
The CDATA MUST be an absolute value using
the same units as the reported data.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 82

 July 15, 2020

Continuation of Table 30
type Description Occurrence
PERIOD For a PERIOD type Filter, the data reported 0..1 †
for a data item is provided on a periodic basis.
The PERIOD for reporting data is defined in the
CDATA for the Filter.
The CDATA MUST be an absolute value
reported in seconds representing the time
between reported samples of the value of the data
item.
If the PERIOD is smaller than one second, the
number can be represented as a floating point
number. For example, a PERIOD of 100
milliseconds would be 0.1.

1154 † Note: Either MINIMUM_DELTA or PERIOD can be defined, not both.

1155 7.2.3.4 InitialValue Element for DataItem

1156 InitialValue is an XML element that defines the value to be set for the data item after
1157 a reset event.

1158 The value associated with the InitialValue element is reported in the CDATA for this
1159 element and MUST be an absolute value using the same units as the reported data.

1160 7.2.3.5 ResetTrigger Element for DataItem

1161 The value of some data types is periodically reset to the value of the InitialValue ele-
1162 ment. These reset events may be based upon a specific elapsed time or may be triggered by
1163 a physical or logical reset action that causes the reset to occur. ResetTrigger provides
1164 additional information regarding the meaning of the data – establishing an understanding
1165 of the time frame that the data represents so that the data may be correctly understood by
1166 a client software application.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 83

 July 15, 2020

Table 31: MTConnect ResetTrigger Element

Element Description Occurrence

ResetTrigger ResetTrigger is an XML element that 0..1
describes the reset action that causes a reset to
occur.
It is additional information regarding the meaning
of the data that establishes an understanding of the
time frame that the data represents so that the data
may be correctly understood by a client software
application.

1167 The reset action that MAY cause a reset to occur is provided in the CDATA for this ele-
1168 ment.

1169 The reset actions that may cause a reset to occur are described in Table 32.

Table 32: DataItem Element ResetTrigger type

Reset Actions Description

ACTION_COMPLETE The value of the Data Entity that is measuring an action or
operation is to be reset upon completion of that action or
operation.
ANNUAL The value of the Data Entity is to be reset at the end of a
12-month period.
DAY The value of the Data Entity is to be reset at the end of a
24-hour period.
LIFE The value of the Data Entity is not reset and accumulates for
the entire life of the piece of equipment.
MAINTENANCE The value of the Data Entity is to be reset upon completion of
a maintenance event.
MONTH The value of the Data Entity is to be reset at the end of a
monthly period.
POWER_ON The value of the Data Entity is to be reset when power was
applied to the piece of equipment after a planned or
unplanned interruption of power has occurred.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 84

 July 15, 2020

Continuation of Table 32
Reset Actions Description
SHIFT The value of the Data Entity is to be reset at the end of a work
shift.
WEEK The value of the Data Entity is to be reset at the end of a
7-day period.

1170 7.2.3.6 Definition Element for DataItem

1171 Figure 16 represents the XML Schema structure for Definition element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 85

 July 15, 2020

Figure 16: Definition Schema Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 86

 July 15, 2020

1172 The Definition provides additional descriptive information for any DataItem rep-
1173 resentations. When the representation is either DATA_SET or TABLE, it gives the
1174 specific meaning of a key and MAY provide a Description, type, and units for
1175 semantic interpretation of data.

Table 33: Elements for Definition

Element Description Occurrence

Description The Description of the Definition. 0..1
See Component Description
EntryDefinitions The EntryDefinitions aggregates 0..1
EntryDefinition .
CellDefinitions The CellDefinitions aggregates 0..1
CellDefinition.

1176 7.2.3.6.1 EntryDefinitions Element for Definition

1177 The EntryDefinitions aggregates EntryDefinition for Definition.

1178 Elements for EntryDefinitions

Table 34: Elements for EntryDefinitions

Element Description Occurrence

EntryDefinition The semantic definition of an Entry 1..*

1179 7.2.3.6.2 EntryDefinition Element for Definition

1180 When the representation is DATA_SET, the EntryDefinition provides the

1181 Description, units, and type of each Entry identified by a unique key.

1182 When the representation is TABLE, the EntryDefinition provides a Descrip-

1183 tion and a set of CellDefinitions for an Entry identified by a unique key.

1184 The key for the EntryDefinion MUST be unique for a given DataItem Defini-
1185 tion.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 87

 July 15, 2020

1186 Attributes for EntryDefinition

Table 35: Attributes for EntryDefinition

Attribute Description Occurrence

key The unique identification of the Entry in the 1
Definition. The description applies to all Entry
observations having this key.
units Same as DataItem units. See Section 7.2.2.5 - units 0..1
Attribute for DataItem. Only valid for representation
of DATA_SET.
type Same as DataItem type. See Section 8 - Listing of Data 0..1
Items.
subType Same as DataItem subType. See Section 8 - Listing of 0..1
Data Items.

1187 Elements for EntryDefinition

Table 36: Elements for EntryDefinition

Element Description Occurrence

Description The Description of the 0..1
EntryDefinition. See Component
Description
CellDefinitions The CellDefinitions aggregates 0..1
CellDefinition if the representation is
TABLE.

1188 7.2.3.6.3 CellDefinitions Element for Definition

1189 The CellDefinitions aggregates CellDefinition declarations.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 88

 July 15, 2020

1190 Elements for CellDefinitions

Table 37: Elements for CellDefinitions

Element Description Occurrence

CellDefinition The semantic definition of a Cell. 1..*

1191 7.2.3.6.4 CellDefinition Element for CellDefinitions

1192 When the representation is TABLE, the CellDefinition provides the De-
1193 scription and the units associated each Cell by key.

1194 The key for the CellDefinion MUST be unique for a given Definition or En-
1195 tryDefinition.

1196 Attributes for CellDefinition

Table 38: Attributes for CellDefinition

Attribute Description Occurrence

key The unique identification of the Entry in the 1
Definition. The description applies to all Entry
observations having this key.
units Same as DataItem units. See Section 7.2.2.5 - units 0..1
Attribute for DataItem.
type Same as DataItem type. See Section 8 - Listing of Data 0..1
Items.
subType Same as DataItem subType. See Section 8 - Listing of 0..1
Data Items.

1197 Elements for CellDefinition

Table 39: Elements for CellDefinition

Element Description Occurrence

Description The Description of the CellDefinition. 0..1
See Component Description

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 89

 July 15, 2020

1198 8 Listing of Data Items

1199 In the MTConnect Standard, DataItem elements are defined and organized based upon
1200 the category and type attributes. The category attribute provides a high level
1201 grouping for DataItem elements based on the kind of information that is reported by
1202 the data item.

1203 These categories are:

1204 • SAMPLE
1205 A SAMPLE reports a continuously variable or analog data value.

1206 • EVENT
1207 An EVENT reports information representing a functional state, with two or more
1208 discrete values, associated with a component or it contains a message. The data
1209 provided may be a numeric value or text.

1210 • CONDITION
1211 A CONDITION reports information about the health of a piece of equipment and its
1212 ability to function.

1213 The type attribute specifies the specific kind of data that is reported. For some types of
1214 data items, a subType attribute may also be used to differentiate between multiple data
1215 items of the same type where the information reported by the data item has a different,
1216 but related, meaning.

1217 Many types of data items provide two forms of data: a value (reported as either a SAMPLE
1218 or EVENT) and a health status (reported as a CONDITION). These DataItem types MAY
1219 be defined in more than one category based on the data that they report.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 90

 July 15, 2020

1220 8.1 Data Items in category SAMPLE

1221 The types of DataItem elements in the SAMPLE category report data representing a
1222 continuously changing or analog data value. This data can be measured at any point-in-
1223 time and will always produce a result. The data provided may be a scalar floating point
1224 number or integers that have an infinite number of possible values. The units attribute
1225 MUST be defined and reported for each DataItem in this category.

1226 Table 40 defines the types and subtypes of DataItem elements defined for the SAMPLE
1227 category. The subtypes are indented below their associated types.

Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units

ACCELERATION Rate of change of velocity. MILLIMETER/SECOND2
ACCUMULATED_TIME The measurement of SECOND
accumulated time for an
activity or event.
DEPRECATION
WARNING : May be
deprecated in the future.
Recommend using
PROCESS_TIMER and
EQUIPMENT_TIMER.
AMPERAGE DEPRECATED in Version AMPERE
1.6. Replaced by
AMPERAGE_AC and
AMPERAGE_DC.
ACTUAL The measured amperage AMPERE
being delivered from a
power source.
ALTERNATING The measurement of AMPERE
alternating current. If not
specified further in
statistic, defaults to
RMS voltage.
DIRECT The measurement of DC AMPERE
current.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 91

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
TARGET The desired or preset AMPERE
amperage to be delivered
from a power source.
AMPERAGE_AC The measurement of an AMPERE
electrical current that
reverses direction at regular
short intervals.
A subType MUST
always be specified.
If not specified further in
statistic, defaults to
RMS amperage.
ACTUAL The measured amperage AMPERE
within an electrical circuit.
COMMANDED The value for a current as AMPERE
specified by a component.
The COMMANDED current
is a calculated value that
includes adjustments and
overrides.
PROGRAMMED The value for a current as AMPERE
specified by a logic or
motion program or set by a
switch.
AMPERAGE_DC The measurement of an AMPERE
electric current flowing in
one direction only.
A subType MUST
always be specified.
ACTUAL The measured amperage AMPERE
within an electrical circuit.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 92

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
COMMANDED The value for a current as AMPERE
specified by a component.
The COMMANDED current
is a calculated value that
includes adjustments and
overrides.
PROGRAMMED The value for a current as AMPERE
specified by a logic or
motion program or set by a
switch.
ANGLE The measurement of DEGREE
angular position.
ACTUAL The actual angular position DEGREE
as read from the physical
component.
COMMANDED A calculated value for DEGREE
angular position computed
by the Controller type
component.
ANGULAR_- Rate of change of angular DEGREE/SECOND2
ACCELERATION velocity.
ANGULAR_VELOCITY Rate of change of angular DEGREE/SECOND
position.
AXIS_FEEDRATE The feedrate of a linear MILLIMETER/SECOND
axis.
ACTUAL The measured value of the MILLIMETER/SECOND
feedrate of a linear axis.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 93

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
COMMANDED The feedrate of a linear axis MILLIMETER/SECOND
as specified by the
Controller type
component.
The COMMANDED feedrate
is a calculated value that
includes adjustments and
overrides.
JOG The feedrate specified by a MILLIMETER/SECOND
logic or motion program,
by a pre-set value, or set by
a switch as the feedrate for
a linear axis when
operating in a manual state
or method (jogging).
OVERRIDE The operator’s overridden PERCENT
value. Percent of
commanded.
DEPRECATED in Version
1.3. See EVENT category
data items.
PROGRAMMED The feedrate specified by a MILLIMETER/SECOND
logic or motion program or
set by a switch for a linear
axis.
RAPID The feedrate specified by a MILLIMETER/SECOND
logic or motion program,
by a pre-set value, or set by
a switch as the feedrate for
a linear axis when
operating in a rapid
positioning mode.
CAPACITY_FLUID The fluid capacity of an MILLILITER
object or container.
CAPACITY_SPATIAL The geometric capacity of CUBIC_MILLIMETER
an object or container.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 94

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
CLOCK_TIME The value provided by a yyyy-mm-
timing device at a specific ddthh:mm:ss.ffff
point in time.
CLOCK_TIME MUST be
reported in W3C ISO 8601
format.
CONCENTRATION Percentage of one PERCENT
component within a
mixture of components.
CONDUCTIVITY The ability of a material to SIEMENS/METER
conduct electricity.
CUTTING_SPEED The speed difference MILLIMETER/SECOND
(relative velocity) between
the cutting mechanism and
the surface of the
workpiece it is operating
on.
ACTUAL The measured value MILLIMETER/SECOND
between the cutting
mechanism and the surface
of the workpiece it is
operating on.
COMMANDED The commanded value MILLIMETER/SECOND
between the cutting
mechanism and the surface
of the workpiece it is
operating on.
PROGRAMMED The programmed value MILLIMETER/SECOND
between the cutting
mechanism and the surface
of the workpiece it is
operating on.
DENSITY The volumetric mass of a MILLIGRAM/CUBIC_-
material per unit volume of MILLIMETER
that material.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 95

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
DEPOSITION_- The rate of change in CUBIC_-
ACCELERATION_- spatial volume of material MILLIMETER/SECOND2
VOLUMETRIC deposited in an additive
manufacturing process.
ACTUAL The measured rate of CUBIC_-
change in spatial volume of MILLIMETER/SECOND2
material deposited in an
additive manufacturing
process.
COMMANDED The commanded rate of CUBIC_-
change in spatial volume of MILLIMETER/SECOND2
material to be deposited in
an additive manufacturing
process.
DEPOSITION_DENSITY The density of the material MILLIGRAM/CUBIC_-
deposited in an additive MILLIMETER
manufacturing process per
unit of volume.
ACTUAL The measured density of MILLIGRAM/CUBIC_-
the material deposited in an MILLIMETER
additive manufacturing
process.
COMMANDED The commanded density of MILLIGRAM/CUBIC_-
material to be deposited in MILLIMETER
an additive manufacturing
process.
DEPOSITION_MASS The mass of the material MILLIGRAM
deposited in an additive
manufacturing process.
ACTUAL The measured mass of the MILLIGRAM
material deposited in an
additive manufacturing
process.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 96

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
COMMANDED The commanded mass of MILLIGRAM
the material to be deposited
in an additive
manufacturing process.
DEPOSITION_RATE_- The rate at which a spatial CUBIC_-
VOLUMETRIC volume of material is MILLIMETER/SECOND
deposited in an additive
manufacturing process.
ACTUAL The measured rate at which CUBIC_-
a spatial volume of material MILLIMETER/SECOND
is deposited in an additive
manufacturing process.
COMMANDED The programmed rate at CUBIC_-
which a spatial volume of MILLIMETER/SECOND
material is to be deposited
in an additive
manufacturing process.
DEPOSITION_VOLUME The spatial volume of CUBIC_MILLIMETER
material to be deposited in
an additive manufacturing
process.
ACTUAL The measured spatial CUBIC_MILLIMETER
volume of material
deposited.
COMMANDED The target spatial volume CUBIC_MILLIMETER
of material to be deposited.
DIAMETER The measured dimension of MILLIMETER
a diameter.
DISPLACEMENT The change in position of MILLIMETER
an object.
ELECTRICAL_ENERGY The measurement of WATT_SECOND
electrical energy
consumption by a
component.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 97

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
EQUIPMENT_TIMER The measurement of the SECOND
amount of time a piece of
equipment or a sub-part of
a piece of equipment has
performed specific
activities. Often used to
determine when
maintenance may be
required for the equipment.
Multiple subTypes of
EQUIPMENT_TIMER
MAY be defined.
A subType MUST
always be specified.
DELAY Measurement of the time SECOND
that a piece of equipment is
waiting for an event or an
action to occur.
LOADED Measurement of the time SECOND
that the sub-parts of a piece
of equipment are under
load.
Example: For traditional
machine tools, this is a
measurement of the time
that the cutting tool is
assumed to be engaged
with the part.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 98

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
OPERATING Measurement of the time SECOND
that the major sub-parts of
a piece of equipment are
powered or performing any
activity whether producing
a part or product or not.
Example: For traditional
machine tools, this includes
WORKING, plus idle time.
POWERED The measurement of time SECOND
that primary power is
applied to the piece of
equipment and, as a
minimum, the controller or
logic portion of the piece of
equipment is powered and
functioning or components
that are required to remain
on are powered.
Example: Heaters for an
extrusion machine that are
required to be powered
even when the equipment is
turned off
WORKING Measurement of the time SECOND
that a piece of equipment is
performing any activity the
equipment is active and
performing a function
under load or not.
Example: For traditional
machine tools, this includes
LOADED, plus rapid moves,
tool changes, etc.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 99

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
FILL_LEVEL The measurement of the PERCENT
amount of a substance
remaining compared to the
planned maximum amount
of that substance.
FLOW The rate of flow of a fluid. LITER/SECOND
FREQUENCY The measurement of the HERTZ
number of occurrences of a
repeating event per unit
time.
GLOBAL_POSITION DEPRECATED in Version None
1.1
HUMIDITY_ABSOLUTE The amount of water vapor GRAM/CUBIC_METER
expressed in grams per
cubic meter.
ACTUAL The measured value. GRAM/CUBIC_METER
COMMANDED The commanded value. GRAM/CUBIC_METER
HUMIDITY_RELATIVE The amount of water vapor PERCENT
present expressed as a
percent to reach saturation
at the same temperature.
ACTUAL The measured value. PERCENT
COMMANDED The commanded value. PERCENT
HUMIDITY_SPECIFIC The ratio of the water vapor PERCENT
present over the total
weight of the water vapor
and air present expressed as
a percent.
ACTUAL The measured value. PERCENT
COMMANDED The commanded value. PERCENT
LENGTH The length of an object. MILLIMETER
REMAINING The remaining total length MILLIMETER
of an object.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 100

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
STANDARD The standard or original MILLIMETER
length of an object.
USEABLE The remaining useable MILLIMETER
length of an object.
LEVEL DEPRECATED in Version None
1.2. See FILL_LEVEL
LINEAR_FORCE The measurement of the NEWTON
push or pull introduced by
an actuator or exerted on an
object.
LOAD The measurement of the PERCENT
actual versus the standard
rating of a piece of
equipment.
MASS The measurement of the KILOGRAM
mass of an object(s) or an
amount of material.
ORIENTATION A measured or calculated DEGREE_3D
orientation of a plane or
vector relative to a cartesian
coordinate system.
ORIENTATION SHOULD
have a coordi-
nateSytemIdRef or a
coordinateSystem
attribute, otherwise the
coordinateSystem
attribute MUST default to
WORK coordinates.
ACTUAL The measured value. DEGREE_3D
COMMANDED The commanded value. DEGREE_3D
PATH_FEEDRATE The feedrate for the axes, MILLIMETER/SECOND
or a single axis, associated
with a Path component– a
vector.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 101

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
ACTUAL The measured value of the MILLIMETER/SECOND
feedrate of the axes, or a
single axis, associated with
a path component.
COMMANDED The feedrate as specified by MILLIMETER/SECOND
the Controller type
component for the axes, or
a single axis, associated
with a Path component.
The COMMANDED feedrate
is a calculated value that
includes adjustments and
overrides.
JOG The feedrate specified by a MILLIMETER/SECOND
logic or motion program,
by a pre-set value, or set by
a switch as the feedrate for
the axes, or a single axis,
associated with a Path
when operating in a manual
state or method (jogging).
OVERRIDE The operator’s overridden PERCENT
value. Percent of
commanded.
DEPRECATED in Version
1.3. See EVENT category
data items.
PROGRAMMED The feedrate specified by a MILLIMETER/SECOND
logic or motion program or
set by a switch as the
feedrate for the axes, or a
single axis, associated with
a Path.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 102

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
RAPID The feedrate specified by a MILLIMETER/SECOND
logic or motion program,
by a pre-set value, or set by
a switch as the feedrate for
the axes, or a single axis,
associated with a Path
when operating in a rapid
positioning mode.
PATH_FEEDRATE_- The feedrate for the axes, MILLIMETER/REVO-
PER_REVOLUTION or a single axis. LUTION
ACTUAL The measured value of the MILLIMETER/REVO-
feedrate of the axes, or a LUTION
single axis.
COMMANDED The feedrate as specified by MILLIMETER/REVO-
the Controller for the LUTION
axes, or a single axis. The
COMMANDED feedrate is a
calculated value that
includes adjustments and
overrides.
PROGRAMMED The feedrate specified by a MILLIMETER/REVO-
logic or motion program or LUTION
set by a switch as the
feedrate for the axes, or a
single axis.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 103

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
PATH_POSITION A measured or calculated MILLIMETER_3D
position of a control point
associated with a piece of
equipment. The control
point MUST be reported as
a set of space-delimited
floating-point numbers
representing a point in 3-D
space. The position of the
control point MUST be
reported in units of
MILLIMETER and listed in
order of X, Y, and Z
referenced to the
coordinate system of the
piece of equipment. Any
control point representing a
position in 1-D or 2-D
space MAY be represented
in terms of 3-D space by
setting any undefined
coordinate to zero (0).
PATH_POSITION
SHOULD be further
defined with a
coordinateSystem
attribute. If a
coordinateSystem
attribute is not specified,
the position of the control
point MUST be reported in
WORK coordinates.
ACTUAL The measured position of MILLIMETER_3D
the current program control
point as reported by the
piece of equipment.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 104

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
PROGRAMMED The position of the control MILLIMETER_3D
point specified by a logic or
motion program.
COMMANDED The position computed by MILLIMETER_3D
the Controller type
component.
PROBE The position provided by a MILLIMETER_3D
measurement probe.
TARGET The desired end position MILLIMETER_3D
for a movement or a series
of movements. Multiple
discrete movements may
need to be completed to
achieve the final TARGET
position.
PH The measurement of the PH
acidity or alkalinity.
POSITION A measured or calculated MILLIMETER
position of a Component
element as reported by a
piece of equipment.
POSITION SHOULD be
further defined with a
coordinateSytem attribute.
If a
coordinateSystem
attribute is not specified,
the position of the control
point MUST be reported in
MACHINE coordinates.
ACTUAL The physical measured MILLIMETER
position of the control point
for a Component.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 105

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
COMMANDED A position calculated by MILLIMETER
the Controller type
component for a discrete
movement.
PROGRAMMED The position of the control MILLIMETER
point for a Component
specified by a logic or
motion program.
TARGET The desired end position of MILLIMETER
the control point for a
Component resulting
from a movement or a
series of movements.
Multiple discrete
movements may need to be
completed to achieve the
final TARGET position.
POWER_FACTOR The measurement of the PERCENT
ratio of real power flowing
to a load to the apparent
power in that AC circuit.
PRESSURE The force per unit area PASCAL
exerted by a gas or liquid.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 106

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
PROCESS_TIMER The measurement of the SECOND
amount of time a piece of
equipment has performed
different types of activities
associated with the process
being performed at that
piece of equipment.
Multiple subtypes of
PROCESS_TIMER may be
defined.
Typically,
PROCESS_TIMER
SHOULD be modeled as a
data item for the Device
element, but MAY be
modeled for either a
Controller or Path
Structural Element in the
XML document.
A subType MUST
always be specified.
DELAY Measurement of the time SECOND
that a process is waiting
and unable to perform its
intended function.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 107

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
PROCESS The measurement of the SECOND
time from the beginning of
production of a part or
product on a piece of
equipment until the time
that production is complete
for that part or product on
that piece of equipment.
This includes the time that
the piece of equipment is
running, producing parts or
products, or in the process
of producing parts.
RESISTANCE The degree to which a OHM
substance opposes the
passage of an electric
current.
ROTARY_VELOCITY The rotational speed of a REVOLUTION/MINUTE
rotary axis.
ACTUAL The measured value of REVOLUTION/MINUTE
rotational speed that the
rotary axis is spinning.
COMMANDED The rotational speed as REVOLUTION/MINUTE
specified by the
Controller type
component.
The COMMANDED velocity
is a calculated value that
includes adjustments and
overrides.
OVERRIDE The operator’s overridden PERCENT
value. Percent of
commanded.
DEPRECATED in Version
1.3. See EVENT category
data items.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 108

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
PROGRAMMED The rotational velocity REVOLUTION/MINUTE
specified by a logic or
motion program or set by a
switch.
SOUND_LEVEL The measurement of a DECIBEL
sound level or sound
pressure level relative to
atmospheric pressure.
A_SCALE A Scale weighting factor. DECIBEL
This is the default
weighting factor if no
factor is specified
B_SCALE B Scale weighting factor DECIBEL
C_SCALE C Scale weighting factor DECIBEL
D_SCALE D Scale weighting factor DECIBEL
NO_SCALE No weighting factor on the DECIBEL
frequency scale
SPINDLE_SPEED DEPRECATED in Version REVOLUTION/MINUTE
1.2. Replaced by
ROTARY_VELOCITY
ACTUAL The rotational speed of a REVOLUTION/MINUTE
rotary axis.
ROTARY_MODE MUST
be SPINDLE.
COMMANDED The rotational speed the as REVOLUTION/MINUTE
specified by the
Controller type
Component.
OVERRIDE The operator’s overridden PERCENT
value. Percent of
commanded.
STRAIN The amount of deformation PERCENT
per unit length of an object
when a load is applied.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 109

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
TEMPERATURE The measurement of CELSIUS
temperature.
ACTUAL The measured value. CELSIUS
COMMANDED The commanded value. CELSIUS
TENSION The measurement of a NEWTON
force that stretches or
elongates an object.
TILT The measurement of MICRO_RADIAN
angular displacement.
TORQUE The turning force exerted NEWTON_METER
on an object or by an
object.
VELOCITY The rate of change of MILLIMETER/SECOND
position.
VISCOSITY The measurement of a PASCAL_SECOND
fluids resistance to flow.
VOLTAGE DEPRECATED in Version VOLT
1.6. Replaced by
VOLTAGE_AC and
VOLTAGE_DC.
ACTUAL The measured voltage VOLT
being delivered from a
power source.
ALTERNATING The measurement of VOLT
alternating voltage. If not
specified further in statistic,
defaults to RMS voltage.
DIRECT The measurement of DC VOLT
voltage.
TARGET The desired or preset VOLT
voltage to be delivered
from a power source.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 110

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
VOLTAGE_AC The measurement of the VOLT
electrical potential between
two points in an electrical
circuit in which the current
periodically reverses
direction.
A subType MUST be
specified.
If not specified further in
statistic, defaults to
RMS voltage.
ACTUAL The measured voltage VOLT
within an electrical circuit.
COMMANDED The value for a voltage as VOLT
specified by a
Controller component.
The COMMANDED voltage
is a calculated value that
includes adjustments and
overrides.
PROGRAMMED The value for a voltage as VOLT
specified by a logic or
motion program or set by a
switch.
VOLTAGE_DC The measurement of the VOLT
electrical potential between
two points in an electrical
circuit in which the current
is unidirectional.
A subType MUST be
specified.
ACTUAL The measured voltage VOLT
within an electrical circuit.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 111

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
COMMANDED The value for a voltage as VOLT
specified by a
Controller component.
The COMMANDED voltage
is a calculated value that
includes adjustments and
overrides.
PROGRAMMED The value for a voltage as VOLT
specified by a logic or
motion program or set by a
switch.
VOLT_AMPERE The measurement of the VOLT_AMPERE
apparent power in an
electrical circuit, equal to
the product of
root-mean-square (RMS)
voltage and RMS current
(commonly referred to as
VA).
VOLT_AMPERE_- The measurement of VOLT_AMPERE_-
REACTIVE reactive power in an AC REACTIVE
electrical circuit
(commonly referred to as
VAR).
VOLUME_FLUID The fluid volume of an MILLILITER
object or container.
ACTUAL The amount of fluid MILLILITER
currently present in an
object or container.
CONSUMED The amount of fluid MILLILITER
material consumed from an
object or container during a
manufacturing process.
VOLUME_SPATIAL The geometric volume of CUBIC_MILLIMETER
an object or container.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 112

 July 15, 2020

Continuation of Table 40: DataItem type subType for category SAMPLE

DataItem type/subType Description Units
ACTUAL The amount of bulk CUBIC_MILLIMETER
material currently present
in an object or container.
CONSUMED The amount of bulk CUBIC_MILLIMETER
material consumed from an
object or container during a
manufacturing process.
WATTAGE The measurement of power WATT
flowing through or
dissipated by an electrical
circuit or piece of
equipment.
ACTUAL The measured wattage WATT
being delivered from a
power source.
TARGET The desired or preset WATT
wattage to be delivered
from a power source.
X_DIMENSION Measured dimension of an MILLIMETER
entity relative to the X
direction of the referenced
coordinate system.
Y_DIMENSION Measured dimension of an MILLIMETER
entity relative to the Y
direction of the referenced
coordinate system.
Z_DIMENSION Measured dimension of an MILLIMETER
entity relative to the Z
direction of the referenced
coordinate system.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 113

 July 15, 2020

1228 8.2 Data Items in category EVENT

1229 DataItem types in the EVENT category represent a discrete piece of information from a
1230 piece of equipment. EVENT does not have intermediate values that vary over time.

1231 An EVENT is information that, when provided at any specific point in time, represents the
1232 current state of the piece of equipment.

1233 There are two types of EVENT: those representing state, with two or more discrete values,
1234 and those representing messages that contain plain text data.

1235 Table 41 defines the DataItem types and subtypes defined for the EVENT category. The
1236 subtypes are indented below their associated types.

Table 41: DataItem type subType for category EVENT

DataItem type subType Description

ACTIVE_AXES The set of axes currently associated with a
Path or Controller Structural Element.
If this DataItem is not provided, it will be
assumed that all axes are currently associated
with the Controller Structural Element and
with an individual Path.
The Valid Data Value for ACTIVE_AXES
SHOULD be a space-delimited set of axes
reported as the value of the name attribute for
each axis. If name is not available, the piece of
equipment MUST report the value of the
nativeName attribute for each axis.
ACTUATOR_STATE Represents the operational state of an apparatus
for moving or controlling a mechanism or
system.
The Valid Data Value MUST be ACTIVE or
INACTIVE.
ALARM DEPRECATED in Version 1.1. Replaced with
CONDITION category.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 114

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
APPLICATION The application on a component.
The Valid Data Value MUST be a text string.
A subType MUST always be specified.
LICENSE The license code to validate or activate the
hardware or software.
VERSION The version of the hardware or software.
RELEASE_DATE The date the hardware or software was released
for general use.
INSTALL_DATE The date the hardware or software was installed.
MANUFACTURER The corporate identity for the maker of the
hardware or software.
AVAILABILITY Represents the Agent’s ability to communicate
with the data source.
This MUST be provided for a Device
Element and MAY be provided for any other
Structural Element. The Valid Data Value
MUST be AVAILABLE or UNAVAILABLE.
AXIS_COUPLING Describes the way the axes will be associated to
each other.
This is used in conjunction with
COUPLED_AXES to indicate the way they are
interacting.
The Valid Data Value MUST be TANDEM,
SYNCHRONOUS, MASTER, and SLAVE.
The coupling MUST be viewed from the
perspective of a specific axis. Therefore, a
MASTER coupling indicates that this axis is the
master for the COUPLED_AXES.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 115

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
AXIS_FEEDRATE_OVERRIDE The value of a signal or calculation issued to
adjust the feedrate of an individual linear type
axis.
The value provided for
AXIS_FEEDRATE_OVERRIDE is expressed
as a percentage of the designated feedrate for
the axis.
When AXIS_FEEDRATE_OVERRIDE is
applied, the resulting commanded feedrate for
the axis is limited to the value of the original
feedrate multiplied by the value of the
AXIS_FEEDRATE_OVERRIDE.
There MAY be different subtypes of
AXIS_FEEDRATE_OVERRIDE; each
representing an override value for a designated
subtype of feedrate depending on the state of
operation of the axis. The subtypes of operation
of an axis are currently defined as
PROGRAMMED, JOG, and RAPID.
JOG The value of a signal or calculation issued to
adjust the feedrate of an individual linear type
axis when that axis is being operated in a
manual state or method (jogging).
When the JOG subtype of
AXIS_FEEDRATE_OVERRIDE is applied, the
resulting commanded feedrate for the axis is
limited to the value of the original JOG subtype
of the AXIS_FEEDRATE multiplied by the
value of the JOG subtype of
AXIS_FEEDRATE_OVERRIDE.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 116

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
PROGRAMMED The value of a signal or calculation issued to
adjust the feedrate of an individual linear type
axis that has been specified by a logic or motion
program or set by a switch.
When the PROGRAMMED subtype of
AXIS_FEEDRATE_OVERRIDE is applied, the
resulting commanded feedrate for the axis is
limited to the value of the original
PROGRAMMED subtype of the
AXIS_FEEDRATE multiplied by the value of
the PROGRAMMED subtype of
AXIS_FEEDRATE_OVERRIDE.
RAPID The value of a signal or calculation issued to
adjust the feedrate of an individual linear type
axis that is operating in a rapid positioning
mode.
When the RAPID subtype of
AXIS_FEEDRATE_OVERRIDE is applied, the
resulting commanded feedrate for the axis is
limited to the value of the original RAPID
subtype of the AXIS_FEEDRATE multiplied by
the value of the RAPID subtype of
AXIS_FEEDRATE_OVERRIDE.
AXIS_INTERLOCK An indicator of the state of the axis lockout
function when power has been removed and the
axis is allowed to move freely.
The Valid Data Value MUST be ACTIVE or
INACTIVE.
AXIS_STATE An indicator of the controlled state of a
Linear or Rotary component representing
an axis.
The Valid Data Value MUST be HOME,
TRAVEL, PARKED, or STOPPED.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 117

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
BLOCK The line of code or command being executed by
a Controller Structural Element.
The value reported for Block MUST include
the entire expression for a line of program code,
including all parameters.
BLOCK_COUNT The total count of the number of blocks of
program code that have been executed since
execution started.
BLOCK_COUNT counts blocks of program code
executed regardless of program structure (e.g.,
looping or branching within the program).
The starting value for BLOCK_COUNT MAY be
established by an initial value provided in the
Constraint element defined for the data item.
CHUCK_INTERLOCK An indication of the state of an interlock
function or control logic state intended to
prevent the associated CHUCK component from
being operated.
The Valid Data Value MUST be ACTIVE or
INACTIVE.
MANUAL_UNCLAMP An indication of the state of an operator
controlled interlock that can inhibit the ability
to initiate an unclamp action of an electronically
controlled chuck.
The Valid Data Value MUST be ACTIVE or
INACTIVE.
When MANUAL_UNCLAMP is ACTIVE, it is
expected that a chuck cannot be unclamped
until MANUAL_UNCLAMP is set to INACTIVE.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 118

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
CHUCK_STATE An indication of the operating state of a
mechanism that holds a part or stock material
during a manufacturing process. It may also
represent a mechanism that holds any other
mechanism in place within a piece of
equipment.
The Valid Data Value MUST be OPEN,
CLOSED, or UNLATCHED.
CODE DEPRECATED in Version 1.1.
COMPOSITION_STATE An indication of the operating condition of a
mechanism represented by a Composition
type element.
A subType MUST always be specified.
A compositionId MUST always be
specified.
ACTION An indication of the operating state of a
mechanism represented by a Composition
type component.
The operating state indicates whether the
Composition element is activated or
disabled.
The Valid Data Value MUST be ACTIVE or
INACTIVE.
LATERAL An indication of the position of a mechanism
that may move in a lateral direction. The
mechanism is represented by a Composition
type component.
The position information indicates whether the
Composition element is positioned to the
right, to the left, or is in transition.
The Valid Data Value MUST be RIGHT, LEFT,
or TRANSITIONING.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 119

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
MOTION An indication of the open or closed state of a
mechanism. The mechanism is represented by a
Composition type component.
The operating state indicates whether the state
of the Composition element is open, closed,
or unlatched.
The Valid Data Value MUST be OPEN,
UNLATCHED, or CLOSED.
SWITCHED An indication of the activation state of a
mechanism represented by a Composition
type component.
The activation state indicates whether the
Composition element is activated or not.
The Valid Data Value MUST be ON or OFF.
VERTICAL An indication of the position of a mechanism
that may move in a vertical direction. The
mechanism is represented by a Composition
type component.
The position information indicates whether the
Composition element is positioned to the
top, to the bottom, or is in transition.
The Valid Data Value MUST be UP, DOWN, or
TRANSITIONING.
CONTROLLER_MODE The current mode of the Controller
component. The Valid Data Value MUST be
AUTOMATIC, MANUAL,
MANUAL_DATA_INPUT,
SEMI_AUTOMATIC, or EDIT.
CONTROLLER_MODE_OVERRIDE A setting or operator selection that changes the
behavior of a piece of equipment.
A subType MUST always be specified.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 120

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
DRY_RUN A setting or operator selection used to execute a
test mode to confirm the execution of machine
functions.
The Valid Data Value MUST be ON or OFF.
When DRY_RUN is ON, the equipment performs
all of its normal functions, except no part or
product is produced. If the equipment has a
spindle, spindle operation is suspended.
MACHINE_AXIS_LOCK A setting or operator selection that changes the
behavior of the controller on a piece of
equipment.
The Valid Data Value MUST be ON or OFF.
When MACHINE_AXIS_LOCK is ON, program
execution continues normally, but no equipment
motion occurs
OPTIONAL_STOP A setting or operator selection that changes the
behavior of the controller on a piece of
equipment.
The Valid Data Value MUST be ON or OFF.
The program execution is stopped after a
specific program block is executed when
OPTIONAL_STOP is ON.
In the case of a G-Code program, a program
BLOCK containing a M01 code designates the
command for an OPTIONAL_STOP.
EXECUTION MUST change to
OPTIONAL_STOP after a program block
specifying an optional stop is executed and the
OPTIONAL_STOP selection is ON.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 121

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
SINGLE_BLOCK A setting or operator selection that changes the
behavior of the controller on a piece of
equipment.
The Valid Data Value MUST be ON or OFF.
Program execution is paused after each BLOCK
of code is executed when SINGLE_BLOCK is
ON.
When SINGLE_BLOCK is ON, EXECUTION
MUST change to INTERRUPTED after
completion of each BLOCK of code.
TOOL_CHANGE_STOP A setting or operator selection that changes the
behavior of the controller on a piece of
equipment.
The Valid Data Value MUST be ON or OFF.
Program execution is paused when a command
is executed requesting a cutting tool to be
changed.
EXECUTION MUST change to
INTERRUPTED after completion of the
command requesting a cutting tool to be
changed and TOOL_CHANGE_STOP is ON.
COUPLED_AXES Refers to the set of associated axes.
The Valid Data Value for COUPLED_AXES
SHOULD be a space-delimited set of axes
reported as the value of the name attribute for
each axis. If name is not available, the piece of
equipment MUST report the value of the
nativeName attribute for each axis.
DATE_CODE The time and date code associated with a
material or other physical item.
DATE_CODE MUST be reported in ISO 8601
format.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 122

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
MANUFACTURE The time and date code relating to the
production of a material or other physical item.
EXPIRATION The time and date code relating to the
expiration or end of useful life for a material or
other physical item.
FIRST_USE The time and date code relating the first use of a
material or other physical item.
DEVICE_UUID The identifier of another piece of equipment
that is temporarily associated with a component
of this piece of equipment to perform a
particular function.
The Valid Data Value MUST be a NMTOKEN
XML type.
DIRECTION The direction of motion.
A subType MUST always be specified
LINEAR The direction of linear motion.
The Valid Data Value MUST be POSTIVE,
NEGATIVE, or NONE.
ROTARY The direction of rotary motion using the
right-hand rule convention.
The Valid Data Value MUST be CLOCKWISE,
COUNTER_CLOCKWISE, or NONE.
DOOR_STATE The operational state of a DOOR type
component or composition element.
The Valid Data Value MUST be OPEN,
UNLATCHED, or CLOSED.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 123

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
EMERGENCY_STOP The current state of the emergency stop signal
for a piece of equipment, controller path, or any
other component or subsystem of a piece of
equipment.
The Valid Data Value MUST be ARMED (the
circuit is complete and the device is allowed to
operate) or TRIGGERED (the circuit is open
and the device must cease operation).
END_OF_BAR An indication of whether the end of a piece of
bar stock being feed by a bar feeder has been
reached.
The Valid Data Value MUST be expressed as a
Boolean expression of YES or NO.
AUXILIARY When multiple locations on a piece of bar stock
are referenced as the indication for the
END_OF_BAR, the additional location(s)
MUST be designated as AUXILIARY
indication(s) for the END_OF_BAR.
PRIMARY Specific applications MAY reference one or
more locations on a piece of bar stock as the
indication for the END_OF_BAR. The main or
most important location MUST be designated
as the PRIMARY indication for the
END_OF_BAR.
If no subType is specified, PRIMARY MUST
be the default END_OF_BAR indication.
EQUIPMENT_MODE An indication that a piece of equipment, or a
sub-part of a piece of equipment, is performing
specific types of activities.
EQUIPMENT_MODE MAY have more than one
subtype defined.
A subType MUST always be specified.
DELAY An indication that a piece of equipment is
waiting for an event or an action to occur.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 124

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
LOADED An indication that the sub-parts of a piece of
equipment are under load.
Example: For traditional machine tools, this is
an indication that the cutting tool is assumed to
be engaged with the part.
The Valid Data Value MUST be ON or OFF.
OPERATING An indication that the major sub-parts of a piece
of equipment are powered or performing any
activity whether producing a part or product or
not.
Example: For traditional machine tools, this
includes when the piece of equipment is
WORKING or it is idle.
The Valid Data Value MUST be ON or OFF.
POWERED An indication that primary power is applied to
the piece of equipment and, as a minimum, the
controller or logic portion of the piece of
equipment is powered and functioning or
components that are required to remain on are
powered.
Example: Heaters for an extrusion machine that
required to be powered even when the
equipment is turned off.
The Valid Data Value MUST be ON or OFF.
WORKING An indication that a piece of equipment is
performing any activity the equipment is active
and performing a function under load or not.
Example: For traditional machine tools, this
includes when the piece of equipment is
LOADED, making rapid moves, executing a tool
change, etc.
The Valid Data Value MUST be ON or OFF.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 125

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
EXECUTION The execution status of the component.
The Valid Data Value MUST be READY,
ACTIVE, INTERRUPTED, WAIT,
FEED_HOLD, STOPPED, OPTIONAL_STOP,
PROGRAM_STOPPED, or
PROGRAM_COMPLETED.
FIRMWARE The embedded software of a component.
The Valid Data Value MUST be a text string.
A subType MUST always be specified.
LICENSE The license code to validate or activate the
hardware or software.
VERSION The version of the hardware or software.
RELEASE_DATE The date the hardware or software was released
for general use.
INSTALL_DATE The date the hardware or software was installed.
MANUFACTURER The corporate identity for the maker of the
hardware or software.
FUNCTIONAL_MODE The current intended production status of the
device or component.
Typically, the FUNCTIONAL_MODE SHOULD
be modeled as a data item for the Device
element, but MAY be modeled for any
Structural Element in the XML document.
The Valid Data Value MUST be PRODUCTION,
SETUP, TEARDOWN, MAINTENANCE, or
PROCESS_DEVELOPMENT.
HARDNESS The measurement of the hardness of a material.
The measurement does not provide a unit.
A subType MUST always be specified to
designate the hardness scale associated with the
measurement.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 126

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
BRINELL A scale to measure the resistance to
deformation of a surface.
LEEB A scale to measure the elasticity of a surface.
MOHS A scale to measure the resistance to scratching
of a surface.
ROCKWELL A scale to measure the resistance to
deformation of a surface.
SHORE A scale to measure the resistance to
deformation of a surface.
VICKERS A scale to measure the resistance to
deformation of a surface.
HARDWARE The hardware of a component.
The Valid Data Value MUST be a text string.
A subType MUST always be specified.
LICENSE The license code to validate or activate the
hardware or software.
VERSION The version of the hardware or software.
RELEASE_DATE The date the hardware or software was released
for general use.
INSTALL_DATE The date the hardware or software was installed.
MANUFACTURER The corporate identity for the maker of the
hardware or software.
INTERFACE_STATE The current functional or operational state of an
Interface type element indicating whether
the interface is active or is not currently
functioning.
The Valid Data Value MUST be ENABLED or
DISABLED.
LIBRARY The software library on a component.
The Valid Data Value MUST be a text string.
A subType MUST always be specified.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 127

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
LICENSE The license code to validate or activate the
hardware or software.
VERSION The version of the hardware or software.
RELEASE_DATE The date the hardware or software was released
for general use.
INSTALL_DATE The date the hardware or software was installed.
MANUFACTURER The corporate identity for the maker of the
hardware or software.
LINE The current line of code being executed.
The data will be an alpha numeric value
representing the line number of the current line
of code being executed.
DEPRECATED in Version 1.4.0.
MAXIMUM The maximum line number of the code being
executed.
MINIMUM The minimum line number of the code being
executed.
LINE_LABEL An optional identifier for a BLOCK of code in a
PROGRAM.
LINE_NUMBER A reference to the position of a block of
program code within a control program. The
line number MAY represent either an absolute
position starting with the first line of the
program or an incremental position relative to
the occurrence of the last LINE_LABEL.
LINE_NUMBER does not change subject to any
looping or branching in a control program.
A subType MUST be defined.
ABSOLUTE The position of a block of program code relative
to the beginning of the control program.
INCREMENTAL The position of a block of program code relative
to the occurrence of the last LINE_LABEL
encountered in the control program.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 128

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
MATERIAL The identifier of a material used or consumed in
the manufacturing process.
The Valid Data Value MUST be a text string.
MATERIAL_LAYER Identifies the layers of material applied to a part
or product as part of an additive manufacturing
process.
The Valid Data Value MUST be an integer.
ACTUAL The current number of layers of material
applied to a part or product during an additive
manufacturing process.
TARGET The target or planned number layers of material
applied to a part or product during an additive
manufacturing process.
MESSAGE Any text string of information to be transferred
from a piece of equipment to a client software
application.
NETWORK Network details of a component.
The Valid Data Value MUST be a text string.
A subType MUST always be specified.
If the subType is WIRELESS, the Valid Data
Value MUST be YES or NO.
IPV4_ADDRESS The IPV4 network address of the component.
IPV6_ADDRESS The IPV6 network address of the component.
GATEWAY The Gateway for the component network.
SUBNET_MASK The SubNet mask for the component network.
VLAN_ID The layer2 Virtual Local Network (VLAN) ID
for the component network.
MAC_ADDRESS Media Access Control Address. The unique
physical address of the network hardware.
WIRELESS Identifies whether the connection type is
wireless.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 129

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
OPERATING_SYSTEM The Operating System of a component.
The Valid Data Value MUST be a text string.
A subType MUST always be specified.
LICENSE The license code to validate or activate the
hardware or software.
VERSION The version of the hardware or software.
RELEASE_DATE The date the hardware or software was released
for general use.
INSTALL_DATE The date the hardware or software was installed.
MANUFACTURER The corporate identity for the maker of the
hardware or software.
OPERATOR_ID The identifier of the person currently
responsible for operating the piece of
equipment.
DEPRECATION WARNING : May be
deprecated in the future. See USER below.
PALLET_ID The identifier for a pallet.
The Valid Data Value MUST be a text string.
PART_COUNT The aggregate count of parts.
Use the discrete attribute with value true
to report non-aggregate part count.
See Section 7.2.3.5 - ResetTrigger Element for
DataItem to reset the count.
The Valid Data Value MUST be numeric.
ALL The number of parts produced. ALL is the
default subType.
BAD The number of parts produced that do not
conform to specification.
GOOD The number of parts produced that conform to
specification.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 130

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
REMAINING The number of remaining or in-stock parts to be
produced.
TARGET The number of projected or planned parts to be
produced.
PART_DETECT An indication designating whether a part or
work piece has been detected or is present.
The Valid Data Value MUST be PRESENT or
NOT_PRESENT.
PART_ID An identifier of a part in a manufacturing
operation.
The Valid Data Value MUST be a text string.
PART_NUMBER An identifier of a part or product moving
through the manufacturing process.
The Valid Data Value MUST be a text string.
DEPRECATION WARNING : May be
deprecated in the future.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 131

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
PATH_FEEDRATE_OVERRIDE The value of a signal or calculation issued to
adjust the feedrate for the axes associated with a
Path component that may represent a single
axis or the coordinated movement of multiple
axes.
The value provided for
PATH_FEEDRATE_OVERRIDE is expressed
as a percentage of the designated feedrate for
the path.
When PATH_FEEDRATE_OVERRIDE is
applied, the resulting commanded feedrate for
the path is limited to the value of the original
feedrate multiplied by the value of the
PATH_FEEDRATE_OVERRIDE.
There MAY be different subtypes of
PATH_FEEDRATE_OVERRIDE; each
representing an override value for a designated
subtype of feedrate depending on the state of
operation of the path. The states of operation of
a path are currently defined as PROGRAMMED,
JOG, and RAPID.
JOG The value of a signal or calculation issued to
adjust the feedrate of the axes associated with a
Path component when the axes, or a single
axis, are being operated in a manual mode or
method (jogging).
When the JOG subtype of
PATH_FEEDRATE_OVERRIDE is applied, the
resulting commanded feedrate for the axes, or a
single axis, associated with the path are limited
to the value of the original JOG subtype of the
PATH_FEEDRATE multiplied by the value of
the JOG subtype of
PATH_FEEDRATE_OVERRIDE.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 132

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
PROGRAMMED The value of a signal or calculation issued to
adjust the feedrate of the axes associated with a
Path component when the axes, or a single
axis, are operating as specified by a logic or
motion program or set by a switch.
When the PROGRAMMED subtype of
PATH_FEEDRATE_OVERRIDE is applied, the
resulting commanded feedrate for the axes, or a
single axis, associated with the path are limited
to the value of the original PROGRAMMED
subtype of the PATH_FEEDRATE multiplied by
the value of the PROGRAMMED subtype of
PATH_FEEDRATE_OVERRIDE.
RAPID The value of a signal or calculation issued to
adjust the feedrate of the axes associated with a
Path component when the axes, or a single
axis, are being operated in a rapid positioning
mode or method (rapid).
When the RAPID subtype of
PATH_FEEDRATE_OVERRIDE is applied, the
resulting commanded feedrate for the axes, or a
single axis, associated with the path are limited
to the value of the original RAPID subtype of
the PATH_FEEDRATE multiplied by the value
of the RAPID subtype of
PATH_FEEDRATE_OVERRIDE.
PATH_MODE Describes the operational relationship between
a Path Structural Element and another Path
Structural Element for pieces of equipment
comprised of multiple logical groupings of
controlled axes or other logical operations.
The Valid Data Value MUST be
INDEPENDENT, MASTER, SYNCHRONOUS, or
MIRROR.
The default value MUST be INDEPENDENT if
PATH_MODE is not specified.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 133

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
POWER_STATE The indication of the status of the source of
energy for a Structural Element to allow it to
perform its intended function or the state of an
enabling signal providing permission for the
Structural Element to perform its functions.
The Valid Data Value MUST be ON or OFF.
DEPRECATION WARNING : May be
deprecated in the future.
CONTROL The state of the enabling signal or control logic
that enables or disables the function or
operation of the Structural Element.
LINE The state of the power source for the Structural
Element.
POWER_STATUS DEPRECATED in Version 1.1.0.
PROCESS_TIME The time and date associated with an activity or
event.
PROCESS_TIME MUST be reported in ISO
8601 format.
START The time and date associated with the beginning
of an activity or event.
COMPLETE The time and date associated with the
completion of an activity or event.
TARGET_COMPLETION The projected time and date associated with the
end or completion of an activity or event.
PROGRAM The identity of the logic or motion program
being executed by the piece of equipment.
The Valid Data Value MUST be a text string.
SCHEDULE The identity of a control program that is used to
specify the order of execution of other
programs.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 134

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
MAIN The identity of the primary logic or motion
program currently being executed. It is the
starting nest level in a call structure and may
contain calls to sub programs.
ACTIVE The identity of the logic or motion program
currently executing.
PROGRAM_COMMENT A comment or non-executable statement in the
control program.
The Valid Data Value MUST be a text string.
SCHEDULE The identity of a control program that is used to
specify the order of execution of other
programs.
MAIN The identity of the primary logic or motion
program currently being executed. It is the
starting nest level in a call structure and may
contain calls to sub programs.
ACTIVE The identity of the logic or motion program
currently executing.
PROGRAM_EDIT An indication of the status of the Controller
components program editing mode.
On many controls, a program can be edited
while another program is currently being
executed.
The Valid Data Value MUST be:
ACTIVE: The controller is in the program edit
mode.
READY: The controller is capable of entering
the program edit mode and no function is
inhibiting a change of mode.
NOT_READY: A function is inhibiting the
controller from entering the program edit mode.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 135

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
PROGRAM_EDIT_NAME The name of the program being edited.
This is used in conjunction with
PROGRAM_EDIT when in ACTIVE state.
The Valid Data Value MUST be a text string.
PROGRAM_HEADER The non-executable header section of the
control program.
If not specified, the default subType is MAIN.
The Valid Data Value MUST be a text string.
SCHEDULE The identity of a control program that is used to
specify the order of execution of other
programs.
MAIN The identity of the primary logic or motion
program currently being executed. It is the
starting nest level in a call structure and may
contain calls to sub programs.
ACTIVE The identity of the logic or motion program
currently executing.
PROGRAM_LOCATION The Uniform Resource Identifier (URI) for the
source file associated with PROGRAM.
SCHEDULE An identity of a control program that is used to
specify the order of execution of other
programs.
MAIN The identity of the primary logic or motion
program currently being executed. It is the
starting nest level in a call structure and may
contain calls to sub programs.
ACTIVE The identity of the logic or motion program
currently executing.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 136

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
PROGRAM_LOCATION_TYPE Defines whether the logic or motion program
defined by PROGRAM is being executed from
the local memory of the controller or from an
outside source.
The Valid Data Value MUST be LOCAL or
EXTERNAL.
SCHEDULE An identity of a control program that is used to
specify the order of execution of other
programs.
MAIN The identity of the primary logic or motion
program currently being executed. It is the
starting nest level in a call structure and may
contain calls to sub programs.
ACTIVE The identity of the logic or motion program
currently executing.
PROGRAM_NEST_LEVEL An indication of the nesting level within a
control program that is associated with the code
or instructions that is currently being executed.
If an initial value is not defined, the nesting level
associated with the highest or initial nesting
level of the program MUST default to zero (0).
The value reported for
PROGRAM_NEST_LEVEL MUST be an
integer.
ROTARY_MODE The current operating mode for a Rotary type
axis.
The Valid Data Value MUST be SPINDLE,
INDEX, or CONTOUR.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 137

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
ROTARY_VELOCITY_OVERRIDE The value of a command issued to adjust the
programmed velocity for a Rotary type axis.
This command represents a percentage change
to the velocity calculated by a logic or motion
program or set by a switch for a Rotary type
axis.
ROTARY_VELOCITY_OVERRIDE is
expressed as a percentage of the programmed
ROTARY_VELOCITY.
ROTATION A three space angular rotation relative to a
coordinate system.
When the DataItem has a
coordinateSystemIdRef attribute and the
CoordinateSystem does not specify a
Rotation, the value of the observation is the
rotation of the the referenced
CoordinateSystem.
The units MUST be DEGREE_3D
SERIAL_NUMBER The serial number associated with a
Component, Asset, or Device. The Valid
Data Value MUST be a text string.
SPINDLE_INTERLOCK An indication of the status of the spindle for a
piece of equipment when power has been
removed and it is free to rotate.
The Valid Data Value MUST be:
ACTIVE if power has been removed and the
spindle cannot be operated.
INACTIVE if power to the spindle has not been
deactivated.
TOOL_ASSET_ID The identifier of an individual tool asset.The
Valid Data Value MUST be a text string.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 138

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
TOOL_GROUP An identifier for the tool group associated with
a specific tool. Commonly used to designate
spare tools.
TOOL_ID DEPRECATED in Version 1.2.0. See
TOOL_ASSET_ID. The identifier of the tool
currently in use for a given Path.
TOOL_NUMBER The identifier assigned by the Controller
component to a cutting tool when in use by a
piece of equipment.
The Valid Data Value MUST be a text string.
TOOL_OFFSET A reference to the tool offset variables applied
to the active cutting tool.
The Valid Data Value MUST be a text string.
The reported value returned for TOOL_OFFSET
identifies the location in a table or list where the
actual tool offset values are stored.
DEPRECATED in V1.5 A subType MUST
always be specified.
LENGTH A reference to a length type tool offset.
RADIAL A reference to a radial type tool offset.
TRANSLATION A three space linear translation relative to a
coordinate system.
When the DataItem has a
coordinateSystemIdRef attribute and the
CoordinateSystem does not specify a
Translation, the value of the observation is
the translation of the referenced
CoordinateSystem.
The units MUST be MILLIMETER_3D

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 139

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
USER The identifier of the person currently
responsible for operating the piece of
equipment.
A subType MUST always be specified.
MAINTENANCE The identifier of the person currently
responsible for performing maintenance on the
piece of equipment.
OPERATOR The identifier of the person currently
responsible for operating the piece of
equipment.
SET_UP The identifier of the person currently
responsible for preparing a piece of equipment
for production or restoring the piece of
equipment to a neutral state after production.
VARIABLE A data value whose meaning may change over
time due to changes in the operation of a piece
of equipment or the process being executed on
that piece of equipment.
WAIT_STATE An indication of the reason that EXECUTION is
reporting a value of WAIT.
The Valid Data Value MUST be
POWERING_UP, POWERING_DOWN,
PART_LOAD, PART_UNLOAD, TOOL_LOAD,
TOOL_UNLOAD, MATERIAL_LOAD,
MATERIAL_UNLOAD,
SECONDARY_PROCESS, PAUSING, or
RESUMING.
WIRE The identifier for the type of wire used as the
cutting mechanism in Electrical Discharge
Machining or similar processes.
The Valid Data Value MUST be a text string.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 140

 July 15, 2020

Continuation of Table 41: DataItem type subType for category EVENT

DataItem type subType Description
WORKHOLDING_ID The identifier for the current workholding or
part clamp in use by a piece of equipment.
The Valid Data Value MUST be a text string.
WORK_OFFSET A reference to the offset variables for a work
piece or part associated with a Path in a
Controller type component.
The Valid Data Value MUST be a text string.
The reported value returned for WORK_OFFSET
identifies the location in a table or list where the
actual work offset values are stored.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 141

 July 15, 2020

1237 8.3 Data Items in category CONDITION

1238 CONDITION category data items report data representing a Structural Element’s status
1239 regarding its ability to operate or it provides an indication whether the data reported for
1240 the Structural Element is within an expected range.

1241 CONDITION is reported differently than SAMPLE or EVENT. CONDITION MUST be

1242 reported as Normal, Warning, or Fault.

1243 All DataItem types in the SAMPLE category MAY have associated CONDITION states.
1244 CONDITION states indicate whether the value for the data is within an expected range and
1245 MUST be reported as Normal, or the value is unexpected or out of tolerance for the data
1246 and a Warning or Fault MUST be provided.

1247 Some DataItem types in the EVENT category MAY have associated CONDITION states.

1248 Additional CONDITION types are provided to represent the health and fault status of
1249 Structural Elements. Table 42 defines these additional DataItem types.

1250 CONDITION type data items are unlike other data item types since they MAY have mul-
1251 tiple concurrently active values at any point in time.

Table 42: DataItem type for category CONDITION

DataItem type Description

ACTUATOR An indication of a fault associated with an actuator.
CHUCK_INTERLOCK An indication of the operational condition of the interlock
function for an electronically controller chuck.
COMMUNICATIONS An indication that the piece of equipment has experienced a
communications failure.
DATA_RANGE An indication that the value of the data associated with a
measured value or a calculation is outside of an expected
range.
DIRECTION An indication of a fault associated with the direction of
motion of a Structural Element.
END_OF_BAR An indication that the end of a piece of bar stock has been
reached.
HARDWARE An indication of a fault associated with the hardware
subsystem of the Structural Element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 142

 July 15, 2020

Continuation of Table 42
DataItem type Description
INTERFACE_STATE An indication of the operation condition of an Interface
component.
LOGIC_PROGRAM An indication that an error occurred in the logic program or
programmable logic controller (PLC) associated with a piece
of equipment.
MOTION_PROGRAM An indication that an error occurred in the motion program
associated with a piece of equipment.
SYSTEM An indication of a fault associated with a piece of equipment
or component that cannot be classified as a specific type.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 143

 July 15, 2020

1252 9 Configuration

1253 Configuration contains technical information about a component describing its phys-
1254 ical layout, functional characteristics, and relationships with other components within a
1255 piece of equipment.

Figure 17: Configuration Element

1256 Table 43 lists the types of Configuration defined for a Component.

Table 43: Types of Configuration

type Description
CoordinateSystems CoordinateSystems organizes
CoordinateSystem elements for a Component
and its children.
Relationships Relationships organizes Relationship
elements for a Component.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 144

 July 15, 2020

Continuation of Table 43
type Description
SensorConfiguration SensorConfiguration contains configuration
information about a Sensor.
Specifications Specifications organizes Specification
elements for a Component.

1257 9.1 Sensor

1258 Sensor is a unique type of a piece of equipment. A Sensor is typically comprised of

1259 two major components: a sensor unit that provides signal processing, conversion, and
1260 communications and the sensing elements that provides a signal or measured value.

1261 The sensor unit is modeled as a Lower Level Component called Sensor. The sensing
1262 element may be modeled as a Composition element of a Sensor element and the mea-
1263 sured value would be modeled as a DataItem (See Section 8 - Listing of Data Items for
1264 more information on DataItem elements). Each sensor unit may have multiple sensing
1265 elements; each representing the data for a variety of measured values.

1266 Example: A pressure transducer could be modeled as a Sensor (Component) with a

1267 name = Pressure Transducer B and its measured value could be modeled as a PRESSURE
1268 type DataItem.

1269 While a Sensor may be modeled in the XML document in different ways, it will always be
1270 modeled to associate the information measured by each sensor element with the Structural
1271 Element to which the measured value is most closely associated.

1272 9.1.1 Sensor Data

1273 The most basic implementation of a sensor occurs when the sensing element itself is not
1274 identified in the data model, but the data that is measured by the sensing element is pro-
1275 vided as a data item associated with a Component. An example would be the measured
1276 value of the temperature of a spindle motor. This would be represented as a DataItem
1277 called TEMPERATURE that is associated with the Rotary type axis element called "C"
1278 as shown in Example 7:

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 145

 July 15, 2020

Example 7: Example of Sensing Element provided as data item associated with a Com-
ponent
1279 1 <Components>
1280 2 <Axes
1281 3 <Components>
1282 4 <Rotary id="c" name="C">
1283 5 <DataItems>
1284 6 <DataItem type="TEMPERATURE"
1285 7 id="ctemp" category="SAMPLE"
1286 8 name="Stemp" units="DEGREE"/>
1287 9 </DataItems>
1288 10 </Rotary>
1289 11 </Components>
1290 12 </Axes>
1291 13 </Components>

1292 A sensor may measure values associated with any Component or Device element.
1293 Some examples of how sensor data may be modeled are represented in Figure 18 :

Figure 18: Sensor Data Associations

1294 9.1.2 Sensor Unit

1295 A sensor unit is an intelligent piece of equipment that manages the functions of one or
1296 more sensing elements.

1297 Typical functions of the sensor unit include:

1298 • convert low level signals from the sensing elements into data that can be used by
1299 other pieces of equipment. (Example: Convert a non-linear millivolt signal from a
1300 temperature sensor into a scaled temperature value that can be transmitted to another
1301 piece of equipment.)

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 146

 July 15, 2020

1302 • process sensing element data into calculated values. (Example: temperature sensor
1303 data is converted into calculated values of average temperature, maximum tempera-
1304 ture, minimum temperature, etc.)

1305 • provide calibration and configuration information associated with each sensing ele-
1306 ment

1307 • monitor the health and integrity of the sensing elements and the sensor unit. (Exam-
1308 ple: The sensor unit may provide diagnostics on each sensing element (e.g., open
1309 wire detection) and itself (e.g., measure internal temperature of the sensor unit).

1310 Depending on how the sensor unit is used, it may be considered as either an independent
1311 piece of equipment and modeled in the XML document as a Device, or it may be mod-
1312 eled as a Top Level Component called Sensor if it is integral to a piece of equipment.

1313 A Sensor MAY have its own uuid so it can be tracked throughout its lifetime.

1314 The following examples demonstrate how a Sensor may be modeled in the XML document
1315 differently based on how the Sensor functions within the overall piece of equipment

1316 Example#1: If the Sensor provides vibration measurement data for the spindle on a
1317 piece of equipment, it could be modeled as a Sensor for rotary axis named C.

Example 8: Example of Sensor for rotary axis

1318 1 <Components>
1319 2 <Axes
1320 3 <Components>
1321 4 <Rotary id="c" name="C">
1322 5 <Components>
1323 6 <Sensor id="spdlm" name="Spindlemonitor">
1324 7 <DataItems>
1325 8 <DataItem type="DISPLACEMENT" id="cvib"
1326 9 category="SAMPLE" name="Svib"
1327 10 units="MILLIMETER"/>
1328 11 </DataItems>
1329 12 </Sensor >
1330 13 <Components>
1331 14 </Rotary>
1332 15 </Components>
1333 16 </Axes>
1334 17 </Components>

1335 Example#2: If a Sensor provides measurement data for multiple Component elements
1336 within a piece of equipment and is not associated with any particular Component ele-
1337 ment, it MAY be modeled in the XML document as an independent Lower Level Com-

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 147

 July 15, 2020

1338 ponent and the data associated with measurements are associated with their associated
1339 Component elements.

1340 This example represents a sensor unit with two sensing elements, one measures spindle
1341 vibration and the other measures the temperature for the X axis. The sensor unit also has
1342 a sensing element measuring the internal temperature of the sensor unit.
Example 9: Example of Sensor Unit with Sensing Element
1343 1 <Device id="d1" uuid="HM1" name="HMC_3Axis">
1344 2 <Description>3 Axis Mill</Description>
1345 3 <Components>
1346 4 <Axes
1347 5 <Components>
1348 6 <Sensor id="sens1" name="Sensorunit">
1349 7 <DataItems>
1350 8 <DataItem type="TEMPERATURE" id="sentemp"
1351 9 category="SAMPLE" name="Sensortemp"
1352 10 units="DEGREE"/>
1353 11 </DataItems>
1354 12 </Sensor >
1355 13 <Rotary id="c" name="C">
1356 14 <DataItems>
1357 15 <DataItem type="DISPLACEMENT" id="cvib"
1358 16 %category="SAMPLE" name="Svib"
1359 17 units="MILLIMETER">
1360 18 <Source componentId="sens1"/>
1361 19 <DataItem/>
1362 20 </DataItems>
1363 21 </Rotary>
1364 22 <Linear id="x" name="X">
1365 23 <DataItems>
1366 24 <DataItem type="TEMPERATURE" id="xt"
1367 25 category="SAMPLE" name="Xtemp"
1368 26 units="DEGREE">
1369 27 <Source componentId="sens1"/>
1370 28 <DataItem/>
1371 29 </DataItems>
1372 30 </Linear>
1373 31 <Components>
1374 32 </Axes>
1375 33 </Components>
1376 34 </Device>

1377 9.1.3 Sensor Configuration

1378 When a Sensor unit is modeled in the XML document as a Component or as a separate
1379 piece of equipment, it may provide additional configuration information for the sensor

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 148

 July 15, 2020

1380 elements and the sensor unit itself.

1381 Configuration data provides information required for maintenance and support of the
1382 sensor.

1383 Configuration data is only available when the Sensor unit is modeled as a Com-
1384 ponent or a separate piece of equipment. For details on the modeling of configuration
1385 data in the XML document, see Section 4.4.3.2 - Configuration for Component.

1386 When Sensor represents the sensor unit for multiple sensing element(s), each sensing
1387 element is represented by a Channel. The sensor unit itself and each Channel repre-
1388 senting one sensing element MAY have its own configuration data.

1389 SensorConfiguration can contain any descriptive content for a sensor unit. This
1390 element is defined to contain mixed content and additional XML elements (indicated by
1391 the any element in Figure 19 ) MAY be added to extend the schema for SensorCon-
1392 figuration.

1393 Figure 19 represents the structure of the SensorConfiguration XML element show-
1394 ing the attributes defined for SensorConfiguration.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 149

 July 15, 2020

Figure 19: SensorConfiguration Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 150

 July 15, 2020

Table 44: MTConnect SensorConfiguration Element

Element Description Occurrence

SensorConfiguration An element that can contain descriptive 0..1
content defining the configuration
information for Sensor.
For Sensor, the valid configuration is
SensorConfiguration which
provides data from a subset of items
commonly found in a transducer
electronic data sheet for sensors and
actuators called TEDS.
TEDS formats are defined in IEEE 1451.0
and 1451.4 transducer interface standards
(ref 15 and 16, respectively).
MTConnect does not support all of the
data represented in the TEDS data, nor
does it duplicate the function of the TEDS
data sheets.

1395 9.1.3.1 Elements for SensorConfiguration

1396 Table 45 defines the configuration elements available for SensorConfiguration:

Table 45: Elements for SensorConfiguration

Element Description Occurrence

FirmwareVersion Version number for the sensor unit as 1
specified by the manufacturer.
FirmwareVersion is a required
element if SensorConfiguration is
used.
The data value for FirmwareVersion
is provided in the CDATA for this element
and MAY be any numeric or text content.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 151

 July 15, 2020

Continuation of Table 45
Element Description Occurrence
CalibrationDate Date upon which the sensor unit was last 0..1
calibrated.
The data value for CalibrationDate
is provided in the CDATA for this element
and MUST be represented in the W3C
ISO 8601 format.
NextCalibrationDate Date upon which the sensor unit is next 0..1
scheduled to be calibrated.
The data value for
NextCalibrationDate is provided
in the CDATA for this element and MUST
be represented in the W3C ISO 8601
format.
CalibrationInitials The initials of the person verifying the 0..1
validity of the calibration data.
The data value for
CalibrationInitials is provided
in the CDATA for this element and MAY
be any numeric or text content.
Channels When Sensor represents multiple 0..1
sensing elements, each sensing element is
represented by a Channel for the
Sensor.
Channels is an XML container used to
organize information for the sensing
elements.

1397 9.1.3.1.1 Attributes for Channel

1398 Channel represents each sensing element connected to a sensor unit. Table 46 defines
1399 the attributes for Channel:

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 152

 July 15, 2020

Table 46: Attributes for Channel

Attribute Description Occurrence

number A unique identifier that will only refer to a specific 1
sensing element.
number is a required attribute.
For example, this can be the manufacturer code and the
serial number.
number SHOULD be alphanumeric and not exceeding
255 characters.
An NMTOKEN XML type.
name The name of the sensing element. 0..1
name is an optional attribute.
name SHOULD be unique within the sensor unit to
allow for easier data integration.
An NMTOKEN XML type.

1400 9.1.3.1.2 Elements for Channel

1401 Table 47 describes the elements provided for Channel.

Table 47: Elements for Channel

Element Description Occurrence

Description An XML element that can contain any 0..1
descriptive content.
The CDATA of Description MAY
include any additional descriptive
information the implementer chooses to
include regarding a sensor element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 153

 July 15, 2020

Continuation of Table 47
Element Description Occurrence
CalibrationDate Date upon which the sensor unit was last 0..1
calibrated to the sensor element.
The data value for CalibrationDate
is provided in the CDATA for this element
and MUST be represented in the W3C
ISO 8601 format.
NextCalibrationDate Date upon which the sensor element is 0..1
next scheduled to be calibrated with the
sensor unit.
The data value for
NextCalibrationDate is provided
in the CDATA for this element and MUST
be represented in the W3C ISO 8601
format.
CalibrationInitials The initials of the person verifying the 0..1
validity of the calibration data.
The data value for
CalibrationInitials is provided
in the CDATA for this element and MAY
be any numeric or text content.

1402 Example 10 is an example of the configuration data for Sensor that is modeled as a Com-
1403 ponent. It has Configuration data for the sensor unit, one Channel named A/D:1,
1404 and two DataItems – Voltage (as a SAMPLE) and Voltage (as a CONDITION or
1405 alarm).

Example 10: Example of configuration data for Sensor

1406 1 <Sensor id="sensor" name="sensor">
1407 2 <Configuration>
1408 3 <SensorConfiguration>
1409 4 <FirmwareVersion>2.02</FirmwareVersion>
1410 5 <CalibrationDate>2010-05-16</CalibrationDate>
1411 6 <NextCalibrationDate>2010-05-16</NextCalibrationDate>
1412 7 <CalibrationInitials>WS</CalibrationInitials>
1413 8 <Channels>
1414 9 <Channel number="1" name="A/D:1">
1415 10 <Description>A/D With Thermister</Description>
1416 11 </Channel>

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 154

 July 15, 2020

1417 12 </Channels>
1418 13 </SensorConfiguration>
1419 14 </Configuration>
1420 15 <DataItems>
1421 16 <DataItem category="CONDITION" id="senvc"
1422 17 type="VOLTAGE" />
1423 18 <DataItem category="SAMPLE" id="senv"
1424 19 type="VOLTAGE" units="VOLT" subType="DIRECT" />
1425 20 </DataItems>
1426 21 </Sensor>

1427 9.2 Relationships

1428 Relationships is an XML container that organizes information defining the associ-
1429 ation between pieces of equipment that function independently but together perform a
1430 manufacturing operation. Relationships may also define the association between
1431 components within a piece of equipment.

1432 Relationships may be modeled as part of a Device or a Component Structural

1433 Element.

1434 Relationships contains one or more Relationship XML elements.

Table 48: MTConnect Relationships Element

Element Description Occurrence

Relationships XML container consisting of one or more 0..1
Relationship XML elements.
Only one Relationships container MUST
appear for a Device or a Component element.

1435 9.2.1 Relationship

1436 Relationship is an XML element that describes the association between two pieces
1437 of equipment that function independently but together perform a manufacturing operation.
1438 Relationship may also be used to define the association between two components
1439 within a piece of equipment.

1440 Relationship is an abstract type XML element, Relationship will be replaced in

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 155

 July 15, 2020

1441 the XML document by specific Relationship types. XML elements representing Re-
1442 lationship are described in Section 9.2.1.1 - DeviceRelationship and Section 9.2.1.2 -
1443 ComponentRelationship.

1444 A separate Relationship type element MAY be defined to describe each pair of as-
1445 sociations with a piece of equipment or between Component elements within a piece of
1446 equipment.

1447 Pieces of equipment may only be associated with other pieces of equipment and Compo-
1448 nent elements may only be associated with other Component elements within a specific
1449 piece of equipment.

1450 The XML schema diagram in Figure 20 represents the structure of the Relationship
1451 XML element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 156

 July 15, 2020

Figure 20: Relationship Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 157

 July 15, 2020

1452 9.2.1.1 DeviceRelationship

1453 DeviceRelationship describes the association between two pieces of equipment that
1454 function independently but together perform a manufacturing operation.

1455 The XML schema diagram in Figure 21 represents the structure of a DeviceRela-
1456 tionship XML element showing the attributes defined for DeviceRelationship.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 158

 July 15, 2020

Figure 21: DeviceRelationship Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 159

 July 15, 2020

1457 The Table 49 lists the attributes defined for the DeviceRelationship element.
Table 49: Attributes for DeviceRelationship

Attribute Description Occurrence

id The unique identifier for this 1
DeviceRelationship.
id is a required attribute.
The id attribute MUST be unique within the
MTConnectDevices document.
An XML ID-type.
name The name associated with this 0..1
DeviceRelationship.
name is provided as an additional human readable
identifier for this DeviceRelationship.
name is an optional attribute.
An NMTOKEN XML type.
type Defines the authority that this piece of equipment 1
has relative to the associated piece of equipment.
type is a required attribute.
The value provided for type MUST be one of the
following values:
PARENT: This piece of equipment functions as
a parent in the relationship with the associated
piece of equipment.
CHILD: This piece of equipment functions as a
child in the relationship with the associated piece
of equipment.
PEER: This piece of equipment functions as a
peer which provides equal functionality and
capabilities in the relationship with the associated
piece of equipment.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 160

 July 15, 2020

Continuation of Table 49
Attribute Description Occurrence
criticality Defines whether the services or functions provided 0..1
by the associated piece of equipment is required
for the operation of this piece of equipment.
criticality is an optional attribute.
The value provided for criticality MUST be
one of the following values:
CRITICAL: The services or functions provided
by the associated piece of equipment is required
for the operation of this piece of equipment.
NONCRITICAL: The services or functions
provided by the associated piece of equipment is
not required for the operation of this piece of
equipment.
deviceUuidRef A reference to the associated piece of equipment. 1
The value provided for deviceUuidRef MUST
be the value provided for the uuid attribute of the
Device element of the associated piece of
equipment.
deviceUuidRef is a required attribute.
An NMTOKEN XML type.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 161

 July 15, 2020

Continuation of Table 49
Attribute Description Occurrence
role Defines the services or capabilities that the 0..1
referenced piece of equipment provides relative to
this piece of equipment.
role is an optional attribute.
The value provided for role MUST be one of the
following values:
SYSTEM: The associated piece of equipment
performs the functions of a System for this piece
of equipment. In MTConnect, System provides
utility type services to support the operation of a
piece of equipment and these services are required
for the operation of a piece of equipment.
AUXILIARY: The associated piece of
equipment performs the functions as an
Auxiliary for this piece of equipment. In
MTConnect, Auxiliary extends the capabilities
of a piece of equipment, but is not required for the
equipment to function.
href A URI identifying the Agent that is publishing 0..1
information for the associated piece of equipment.
href MUST also include the UUID for that
specific piece of equipment.
href is of type xlink:href from the W3C
XLink specification:
(https://www.w3.org/TR/xlink11/).
href is an optional attribute.
xlink:type The XLink type attribute MUST have a fixed 0..1
value of locator as defined in W3C XLink 1.1
https://www.w3.org/TR/xlink11/ section 5.4
Locator Attribute (href).
If the href attribute is provided, it MUST
conform to the URI syntactic rules as defined in
IETF RFC 3986 for Uniform Resource Identifiers.
(https://www.ietf.org/rfc/rfc3986.txt)

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 162

 July 15, 2020

1458 9.2.1.2 ComponentRelationship

1459 ComponentRelationship describes the association between two components within

1460 a piece of equipment that function independently but together perform a capability or
1461 service within a piece of equipment.

1462 The XML schema in Figure 22 represents the structure of a ComponentRelation-

1463 ship XML element showing the attributes defined for ComponentRelationship.

Figure 22: ComponentRelationship Diagram

1464 The Table 50 lists the attributes defined for the ComponentRelationship element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 163

 July 15, 2020

Table 50: Attributes for ComponentRelationship

Attribute Description Occurrence

id The unique identifier for this 1
ComponentRelationship.
id is a required attribute.
The id attribute MUST be unique within the
MTConnectDevices document.
An XML ID-type.
name The name associated with this 0..1
ComponentRelationship.
name is provided as an additional human readable
identifier for this ComponentRelationship.
name is an optional attribute.
An NMTOKEN XML type.
type Defines the authority that this component element has 1
relative to the associated component element.
type is a required attribute.
The value provided for type MUST be one of the
following values:
PARENT: This component functions as a parent in
the relationship with the associated component
element.
CHILD: This component functions as a child in
the relationship with the associated component
element.
PEER: This component functions as a peer which
provides equal functionality and capabilities in the
relationship with the associated component element.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 164

 July 15, 2020

Continuation of Table 50
Attribute Description Occurrence
criticality Defines whether the services or functions provided by 0..1
the associated component element is required for the
operation of this piece of equipment.
criticality is an optional attribute.
The value provided for criticality MUST be
one of the following values:
CRITICAL: The services or functions provided
by the associated component element is required for
the operation of this piece of equipment.
NONCRITICAL: The services or functions
provided by the associated component element is not
required for the operation of this piece of equipment.
idRef A reference to the associated component element. 1
The value provided for idRef MUST be the value
provided for the id attribute of the associated
Component element.
idRef is a required attribute.
An NMTOKEN XML type.

1465 9.3 Specifications

1466 Specifications is an XML container in the Configuration of a Component

1467 that contains one or more Specification elements describing the design characteris-
1468 tics for a piece of equipment.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 165

 July 15, 2020

Figure 23: Specifications Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 166

 July 15, 2020

1469 9.3.1 Specification

1470 Specification elements define information describing the design characteristics for
1471 a piece of equipment.

1472 9.3.1.1 Attributes for Specification

1473 Table 51 lists the attributes defined to provide information for a Specification ele-
1474 ment.
Table 51: Attributes for Specification

Attribute Description Occurrence

type Same as DataItem type. See 1
Section 8 - Listing of Data Items.
subType Same as DataItem subtypes. See 0..1
Section 8 - Listing of Data Items.
dataItemIdRef A reference to the id attribute of the 0..1
DataItem associated with this
element.
units Same as DataItem units. See 0..1
Section 7.2.2.5 - units Attribute for
DataItem.
compositionIdRef A reference to the id attribute of the 0..1
Composition associated with this
element.
name The name provides additional 0..1
meaning and differentiates between
Specifications.
A name MUST exist when two
Specifications have the same
type and subType within a
Component.
coordinateSystemIdRef References the 0..1
CoordinateSystem for geometric
Specification elements.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 167

 July 15, 2020

1475 9.3.1.2 Elements for Specification

1476 Table 52 lists the elements defined to provide information for a Specification ele-
1477 ment.
Table 52: Elements for Specification

Element Description Occurrence

Maximum A numeric upper limit constraint. 0..1
Minimum A numeric lower limit constraint. 0..1
Nominal The numeric target or expected value. 0..1

1478 9.4 CoordinateSystems

1479 CoordinateSystems aggregates CoordinateSystem configurations for a Com-

1480 ponent.

Figure 24: CoordinateSystems Diagram

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 168

 July 15, 2020

1481 9.4.1 CoordinateSystem

1482 A CoordinateSystem is a reference system that associates a unique set of n parame-

1483 ters with each point in an n-dimensional space. Ref: ISO 10303-218:2004

1484 9.4.1.1 Attributes for CoordinateSystem

1485 Table 53 lists the attributes defined to provide information for a CoordinateSystem
1486 element.
Table 53: Attributes for CoordinateSystem

Attribute Description Occurrence

id The unique identifier for this element. 1
name The name of the coordinate system. 0..1
If more than one CoordinateSystem elements
have the same type for the same Component, then
the name attribute MUST be provided. Otherwise,
the name attribute is optional.
name provides as an additional human-readable
identifier in addition to the id.
nativeName The manufacturer’s name or users name for the 0..1
coordinate system.
parentIdRef A pointer to the id attribute of the parent 0..1
CoordinateSystem.
type The type of coordinate system. 1

1487 9.4.1.1.1 CoordinateSystem types

1488 Table 54 defines the various types of coordinate systems.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 169

 July 15, 2020

Table 54: CoordinateSystem types

type Description
WORLD stationary coordinate system referenced to earth,
which is independent of the robot motion. Ref:ISO
9787:2013
For non-robotic devices, stationary coordinate system
referenced to earth, which is independent of the
motion of a piece of equipment.
BASE coordinate system referenced to the base mounting
surface. Ref:ISO 9787:2013
A base mounting surface is a connection surface
between the arm and its supporting structure.Ref:ISO
9787:2013
For non-robotic devices, it is the connection surface
between the device and its supporting structure.
OBJECT coordinate system referenced to the object. Ref:ISO
9787:2013
TASK coordinate system referenced to the site of the task.
Ref:ISO 9787:2013
MECHANICAL_INTERFACE coordinate system referenced to the mechanical
interface. Ref:ISO 9787:2013
TOOL coordinate system referenced to the tool or to the end
effector attached to the mechanical interface. Ref:ISO
9787:2013
MOBILE_PLATFORM coordinate system referenced to one of the
components of a mobile platform. Ref:ISO 8373:2012
MACHINE coordinate system referenced to the home position
and orientation of the primary axes of a piece of
equipment.
CAMERA coordinate system referenced to the sensor which
monitors the site of the task. Ref:ISO 9787:2013

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 170

 July 15, 2020

1489 9.4.1.2 Elements for CoordinateSystem

1490 Table 55 lists the elements defined to provide information for a CoordinateSystem
1491 element.
Table 55: Elements for CoordinateSystem

Element Description Occurrence

Origin The coordinates of the origin position of a 0..1
coordinate system. The coordinate MUST be in
MILLIMETER_3D.
Transformation The process of transforming to the origin 0..1
position of the coordinate system from a parent
coordinate system using Translation and
Rotation.

1492 Notes: Only one of Location or Transformation can be defined for a Coor-
1493 dinateSystem.

1494 9.4.1.2.1 Elements for Transformation

1495 Table 56 lists the elements defined to provide information for a Transformation ele-
1496 ment.
Table 56: Elements for Transformation

Element Description Occurrence

TRANSLATION Translations along X, Y, and Z axes are expressed as 0..1
x,y, and z respectively within a 3-dimensional vector.
The values MUST be given in MILLIMETER_3D.
ROTATION Rotations about X, Y, and Z axes are expressed in A, 0..1
B, and C respectively within a 3-dimensional vector.
The values MUST be given in DEGREE_3D.
Positive A, B, and C are in the directions to advance
right-hand screws in the positive X, Y, and Z
directions, respectively. Ref:ISO 9787:2013

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 171

 July 15, 2020

1497 Appendices

1498 A Bibliography

1499 Engineering Industries Association. EIA Standard - EIA-274-D, Interchangeable Variable,

1500 Block Data Format for Positioning, Contouring, and Contouring/Positioning Numerically
1501 Controlled Machines. Washington, D.C. 1979.

1502 ISO TC 184/SC4/WG3 N1089. ISO/DIS 10303-238: Industrial automation systems and
1503 integration Product data representation and exchange Part 238: Application Protocols: Ap-
1504 plication interpreted model for computerized numerical controllers. Geneva, Switzerland,
1505 2004.

1506 International Organization for Standardization. ISO 14649: Industrial automation sys-
1507 tems and integration – Physical device control – Data model for computerized numerical
1508 controllers – Part 10: General process data. Geneva, Switzerland, 2004.

1509 International Organization for Standardization. ISO 14649: Industrial automation sys-
1510 tems and integration – Physical device control – Data model for computerized numerical
1511 controllers – Part 11: Process data for milling. Geneva, Switzerland, 2000.

1512 International Organization for Standardization. ISO 6983/1 – Numerical Control of ma-
1513 chines – Program format and definition of address words – Part 1: Data format for posi-
1514 tioning, line and contouring control systems. Geneva, Switzerland, 1982.

1515 Electronic Industries Association. ANSI/EIA-494-B-1992, 32 Bit Binary CL (BCL) and

1516 7 Bit ASCII CL (ACL) Exchange Input Format for Numerically Controlled Machines.
1517 Washington, D.C. 1992.

1518 National Aerospace Standard. Uniform Cutting Tests - NAS Series: Metal Cutting Equip-
1519 ment Specifications. Washington, D.C. 1969.

1520 International Organization for Standardization. ISO 10303-11: 1994, Industrial automa-
1521 tion systems and integration Product data representation and exchange Part 11: Descrip-
1522 tion methods: The EXPRESS language reference manual. Geneva, Switzerland, 1994.

1523 International Organization for Standardization. ISO 10303-21: 1996, Industrial automa-
1524 tion systems and integration – Product data representation and exchange – Part 21: Imple-
1525 mentation methods: Clear text encoding of the exchange structure. Geneva, Switzerland,
1526 1996.

1527 H.L. Horton, F.D. Jones, and E. Oberg. Machinery’s Handbook. Industrial Press, Inc.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 172

 July 15, 2020

1528 New York, 1984.

1529 International Organization for Standardization. ISO 841-2001: Industrial automation sys-
1530 tems and integration - Numerical control of machines - Coordinate systems and motion
1531 nomenclature. Geneva, Switzerland, 2001.

1532 ASME B5.57: Methods for Performance Evaluation of Computer Numerically Controlled
1533 Lathes and Turning Centers, 1998.

1534 ASME/ANSI B5.54: Methods for Performance Evaluation of Computer Numerically Con-
1535 trolled Machining Centers. 2005.

1536 OPC Foundation. OPC Unified Architecture Specification, Part 1: Concepts Version 1.00.
1537 July 28, 2006.

1538 IEEE STD 1451.0-2007, Standard for a Smart Transducer Interface for Sensors and Ac-
1539 tuators – Common Functions, Communication Protocols, and Transducer Electronic Data
1540 Sheet (TEDS) Formats, IEEE Instrumentation and Measurement Society, TC-9, The In-
1541 stitute of Electrical and Electronics Engineers, Inc., New York, N.Y. 10016, SH99684,
1542 October 5, 2007.

1543 IEEE STD 1451.4-1994, Standard for a Smart Transducer Interface for Sensors and Ac-
1544 tuators – Mixed-Mode Communication Protocols and Transducer Electronic Data Sheet
1545 (TEDS) Formats, IEEE Instrumentation and Measurement Society, TC-9, The Institute of
1546 Electrical and Electronics Engineers, Inc., New York, N.Y. 10016, SH95225, December
1547 15, 2004.

MTConnect Part 2.0: Devices Information Model - Version 1.6.0 173