With part 1 you can determine which information must be exchanged between the enterprise and the control system. After this information analysis, you can start to build the interface between both systems. The standard does not tell which technical solution you should choose (an example of a technical solution could be XML/B2MMl). But part 2 does offer a basis for this technical solution, because it determines the attributes of all the objects defined in part one. You can use these objects and attributes for the exchange of information, but they are also an excellent basis for developing relational databases.
Figure 1: part of the ISA-95 Material model
Part 2 has determined the attributes for the following object models:
With these objects and attributes you can build all the information flows defined by the functional model of part 1.
| Attribute name | Description | Examples |
|---|---|---|
| ID | A unique identification of a specific material sub lot, within the scope of the information exchanges (production capability, production schedule, production performance…). The ID shall be used in other parts of the model when the material sub lot needs to be identified, such as the production capability for this material sub lot, or a production response identifying the material sub lot used. | 1999-10-27-a67-B6653 |
| Description | Additional information about the material sub lot. | Pallet 2 of 6 |
| Status | Status of the current material sub lot. For example, released, approved, blocked, in process, in quality check. | Released |
| Storage Location | An identification of the storage location of the material sub lot. | “Warehouse 1 Rack 12 Slot 4” |
| Quantity | The quantity of the material sub lot. | 40 |
| Quantity Unit of Measure | The unit of measure of the associated quantity, if applicable. | Sheets |
The attributes are abstract; they do not define any specific data types. That’s why the standard can be used in all kinds of manufacturing facilities. For every different project, you have to determine how the information is going to be depicted. For example: an attribute could be shown as a string in one implementation, and it could have a numerical value in another implementation. A date or time value could be shown in the sequence Day-Month-Year, or Year-Month-Day. ISA-95.02 gives examples for every attribute. It will not always be necessary to use every attribute in every implementation. This depends on how many models you are using. It is allowed to leave out models that you don’t need. You can also add attributes by using properties. ISA-95.02 offers tables for properties. These can be used for information that is very specific for the company. This way the standard can be used in all kinds of industries.