specs/models/M_MACH
Machine
A Machine contains metadata about a machine and a collection of mappings between a Data Source field and a Machine Attribute. A Machine can be used to collect data independently of Apps or can be integrated into one or many Apps. Acts as a digital twin and enables data from physical equipment to be utilized and understood within Tulip. A machine will log data to the Activity History specific to that machine. A Machine cannot be restored after it has been deleted.
Fields
| Name | Description |
|---|---|
| ID | Auto-generated and unique Id for the Machine |
| Name | User defined name for the Machine |
| Machine Data Source | The Data Source assigned to the machine, not editable after initial save. |
| Station | The Station where the machine is assigned. |
| Type | The Machine Type associated with the machine. |
| Field Mappings | Collection of mappings between a Data Source field and a Machine Attribute. |
| Deletion Status | A boolean that indicates whether the machine is active or deleted |
Tests
| ID | Name |
|---|---|
| QA-T113 | Machine Monitoring : 01 - Machine Editor |
| QA-T115 | Machine Monitoring : 03 - Event Editor |
| QA-T117 | Machine Monitoring : 09 - Deleting Machine/Machine Attributes |
| QA-T256 | Machine Monitoring : 04 - Machine Type |
| QA-T257 | Machine Monitoring : 07 - Machine Widgets |
| QA-T258 | Machine Monitoring : 08 - App Triggers For Machines |
| QA-T259 | Analytics - Machine Analytics |
| QA-T390 | Machine Monitoring : 05 - Machine Type Management |
| QA-T410 | Machine Monitoring : 10 - Used Machine Type Aspects can't be Deleted |
| QA-T723 | Machine Monitoring : 01 / Failing to Create and Edit Machines |
Requirements
| ID | Requirement |
|---|---|
| 157 | Provide a managed way to configure and maintain definitions of equipment models including creating, copying, editing, making obsolete, and deleting. |
| 158 | Disallow deletion of equipment model definitions that have been used in execution of a work order or material processing |
| 234 | Ability to send and receive data from legacy equipment or devices |
| 342 | Ability to automatically capture data from process equipment in fermentation production |
| 346 | Provide a managed way to capture equipment events during production processing. All events will be logged with cause and timestamp. These events may be - Stop causes, Downtime events, Breakdowns, Repair, Etc. |