Objects are used extensively throughout the MES modules. Some are for the ISA-95 object model, while others are part of our platform. Collectively, we refer to all these objects as MES Objects. An object can represent material, equipment, an operation, production information, etc. Some properties, events and functions are common across all objects, while other objects add their own additional properties, events and functions. Today, the MES Objects are used by the Track & Trace and OEE 2.0 modules. In future releases, all other MES modules will also be based on the MES Objects.

Types Of MES Objects

The ISA-95 Objects are divided into two categories, Operations Configuration objects and Operations Information objects. Within these categories, the objects are further broken down into: 

  • Resource objects represent equipment, material or personnel items that are required for production tasks
  • Definition objects represent the definition of tasks that are carried out during production
  • Request objects represent scheduled production tasks
  • Response objects represent the actual production results

In addition to these type of objects, the MES 2.0 platform provides many other objects that provide a powerful and flexible way of accessing and modifying data and settings used by the MES modules. These objects are all derived from the AbstractMESObject, inheriting its methods and properties as well as adding their own.

MES Object Listing

The following MES objects are provided...

ISA-95 Object Model Inter-Relationships


Using MES Objects

Please note that the following characters are not allowed in MES Object Names: \ / % ^ ~ [ ] { } ` ? , " = + . ! # $ * |

There is a MES Object Link object. This is a light-weight object that acts like a reference to the full MES object, but only contains some general information. Consider using this when populating dropdowns or lists to reduce unneeded overhead.


Object Functions

ISA-95 does not define object functions but the MES modules extend these objects with functions to make common tasks easier. There are common functions that are available (inherited) on all MES objects and then each MES object type may have additional functions. The additional functions are appropriate for the type of MES object. An example of an object function that is common across all MES objects is addCustomProperty(). An example of a object function that is specific for one type of MES object is setMaterial() which is only appropriate for a Response Segment type of MES object.

The object model diagram in the Object Types section provides a quick view on which functions each object provides and which functions are inherited. Detailed information regarding the functions themselves can be found under the specific object in the Object Types section.

Object Properties

Properties are broken into three different categories.

  • Core Properties - The ISA-95 standard calls these attributes that each object should support. We call them core properties to keep with the ignition standard.
  • Custom Properties - The ISA-95 standards simply refers to these as properties. Again, the term is consistent with the term being used in Ignition.
  • Complex Properties - Complex properties are not defined explicitly in the ISA-95 standard, but are inferred when defining resources needed for an operation and other aggregate lists.


Object Events

MES Objects have events associated with them. click here for more information on MES Object Events.

  • No labels