Data Tag Templates
Last updated
Last updated
The Data Tag Template is how TilliT provides a no code solution for interpreting raw values and executing upon these values with a pre-configured behavior. For example, templates can help ingest live order counts, equipment availability or work order status.This will impact the asset metrics (performance, availability and quality) as well as order completion progress. Templates are defined on the Edge Data Tag of a Datasource and each asset/equipment can only have one of each template.
The templates starting with EQUIPMENT_STATUS_* are expecting a digital where 1/true is mapped to that status being active. Metrics like availability are calculated based on these statuses. When this template is selected, events(Equipment Stopped, Equipment Running, etc) are not automatically configured. You must create an edge trigger on the tag to cause the event to be triggered. You can see the affect of the template in the following image.
The COUNT_TOTAL template is expecting a counter that represents how many units (in the product's unit of measure) of the product is produced. Every minute TilliT will read that value, compare it with the previous value read and publish the difference to the cloud. The contents of the Order Progress table will display how many units were produced in the interval between Polling cycles.
Much like the COUNT_TOTAL, this is a counter that represents how many units of the product have been rejected. Every minute TilliT will read this value, compare it with the previous value read and publish the difference to the cloud. This count is used to display the number of reject units for an order, and calculates the quality metric of OEE.
Tag templates can be assigned to an edge data tag to tell TilliT how to interpret them. You can use the Order Number template to automatically complete a running order and start the new one. All you need to do is map TilliT to a source tag that contains the order number that is currently running. As soon as that tag changes, TilliT will complete the order the previous order and start running the one.
When you have an ORDER_NUMBER tag working, you can use this template to move an order between the READY, NEW, RUNNING, SUSPENDED and COMPLETED states.
Use this template for automatic qualification of your downtime reason. When this template is selected, the `Event Reason Option Group` field will appear. Here you can select the Option Group that will match the raw value read to a human readable reason. This downtime reason is attached to the equipment stopped event and any activities are pre-filled from this, allowing for an operator to confirm or change the reason.
As in the following image, the a Equipment Stopped event was triggered from the edge, at this same time, the DOWNTIME_REASON tag was populated with the value 3001. This was then recorded on the event with a full breakdown of that reason code of OPERATIONAL -> OPERATION -> Downstream Machine Issue -> 3001. The Enter stoppage reason activity is then created for an operator to confirm. If the operator re-qualifies the downtime, then the event will be updated with the correct stoppage reason.
