The purpose of this module is to enable app builders to quickly add advanced production logging functionality to their applications. Tulip's built-in completion function is a simple and straight-forward way to log production data, but if you'd like to log information even if the user isn't pressing the complete button (for example, if the cell is down for a period of time) then this module may be a good solution for you.
How It Works
This module uses two tables - the *Stations table and the *Status History table. When you first enter the application, a record is created in the *Status History table, storing your station's status. There are a few critical parameters that we monitor in this application:
Any time that one of the above parameters is changed, a new record is created in the status history table. Every 30 seconds, the duration in incremented to account for the time spent in a given state. When either good or bad parts are logged, the status history record values are incremented.
This structure lets you very easily see what is happening at all of your stations using interactive dashboards and analytics, since all of your stations can write their information to the same table, using the same method. The only requirement is that the application be running at the station.
Copying the Module into your Application
You may decide that you like your current application but would like to add functionality from this module. Simple download the application from the library and copy the step from the application overview screen.
Next, navigate to your application and paste the step.
Then, view the production logging module step from within your application and add it wherever you would like. You may elect to copy and paste the "On step enter" trigger into the "On application start" trigger, for example. You also may decide to copy and paste the step timers to the master layout. Furthermore, you can connect this application to other modules or tables that you are currently using.