specs/models/M_MTYP
Machine Type
A Machine Type is rule set used to define the behavior of a Machine. Which includes a collection of Machine States, Attributes, Downtime Reasons, Activity Columns and Triggers. A Machine Type can be associated with zero, one or many Machines. This allows for the logic of a machine to be managed in a central location instead of for every machine independently. Assigning a Machine Type to a Machine will dictate the logic that is used to populate the Machine Activity for that Machine. A Machine Type cannot be deleted when used by a Machine. A Machine Type cannot be restored after it has been deleted.
Fields
| Name | Description |
|---|---|
| ID | Auto-generated and unique Id for the Type |
| Name | User defined name for the Type |
| Machine States | Collection of Machine States, user configurable |
| Machine Downtime Reasons | Collection of Downtime Reasons, user configurable |
| Machine Attributes | Collection of Attributes, user configurable |
| Machine Activity Fields | Collection of Machine Activity Fields, includes defaults that cannot be configured by the user and custom fields that are configurable by the user. |
| Machine Triggers | Collection of Machine Triggers, user configurable. Triggers can be enabled or disabled. |
Tests
| ID | Name |
|---|---|
| QA-T256 | Machine Monitoring : 04 - Machine Type |
| QA-T390 | Machine Monitoring : 05 - Machine Type Management |
| QA-T410 | Machine Monitoring : 10 - Used Machine Type Aspects can't be Deleted |
| QA-T588 | Machine Monitoring : 12 - Adding Machine Activity Fields to Machine Types |
| QA-T590 | Machine Monitoring : 14 - Creating Machine Downtime Reason |
Requirements
| ID | Requirement |
|---|---|
| PLAT-8821 (236) | Ability to capture time series data from (historize) manufacturing equipment |
| PLAT-8834 (239) | Ability to capture (historize) alarm and event information from equipment |
| PLAT-8910 (157) | Provide a managed way to configure and maintain definitions of equipment models including creating, copying, editing, making obsolete, and deleting. |
| PLAT-8917 (163) | The equipment model should have definition of capability, availability, status, and reservations. |
| PLAT-8918 (162) | The equipment model should have definition of equipment classes and equipment groups. |
| PLAT-8922 (160) | Support equipment model definition using hierarchies and equipment classes |
| PLAT-8945 (169) | Provide a managed way to configure and maintain a state model for an equipment, equipment group or equipment class with allowed transitions (eg. "running" and "not running" - running state; "clean", "in use", "not clean" - cleaning state) |