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.
|Auto-generated and unique Id for the Machine
|User defined name for the Machine
|Machine Data Source
|The Data Source assigned to the machine, not editable after initial save.
|The Station where the machine is assigned.
|The Machine Type associated with the machine.
|Collection of mappings between a Data Source field and a Machine Attribute.
|A boolean that indicates whether the machine is active or deleted
|Machine Monitoring : 01 - Machine Editor
|Machine Monitoring : 03 - Event Editor
|Machine Monitoring : 09 - Deleting Machine/Machine Attributes
|Machine Monitoring : 04 - Machine Type
|Machine Monitoring : 07 - Machine Widgets
|Machine Monitoring : 08 - App Triggers For Machines
|Analytics - Machine Analytics
|Machine Monitoring : 05 - Machine Type Management
|Machine Monitoring : 10 - Used Machine Type Aspects can't be Deleted
|Provide a managed way to configure and maintain definitions of equipment models including creating, copying, editing, making obsolete, and deleting.
|Disallow deletion of equipment model definitions that have been used in execution of a work order or material processing
|Ability to send and receive data from legacy equipment or devices
|Ability to automatically capture data from process equipment in fermentation production
|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.