Data Interface Tag
Watch Connecting To Data Tutorial
Connect Data
Kanoa Ops supports a variety of data connectivity options, making an extensible system that can grow to collect data from additional systems as adoption increases and requirements evolve. Machine Performance and OEE data can be collected via PLCs and automation equipment through Ignition's built-in OPC server or Industry 4.0 protocols like MQTT. Web APIs allow Kanoa Ops to integrate with business systems like ERP to automatically download material specifications and production schedules. When automatic data collection is not an option, Kanoa Ops provides manual entry solutions so that every single asset can be accounted for.
Whenever an asset is 'OEE_Enabled', an instance of the assetOEE tag UDT is created in the [Kanoa] tag provider.
Inputs Folder
The Inputs folder is where the asset is connected to its source of data. At a minimum, infeed and outfeed counts and asset state should be connected. If not all counts are available, a single count i.e. infeed or outfeed can be connected and the missing counts will be automatically calculated. In order to determine OEE Quality, at least two counts are required. The Inputs tags are reference tags and will support mqtt backflushing in the event of a network drop.
If operations are started through the MES Application (Operator screen) or started by the schedule, that is all we really have to connect, however if the asset is operated from a different HMI or SCADA, then we can simply connect the Mode, Work Order and Product Code tags to the source, to fully capture production information within our MES.
| Tag | Description |
|---|---|
| Infeed Count | Connect this tag to your infeed count source, or leave blank if using the MQTTPath parameter |
| Machine ID | This tag allows you to set which cell on an asset caused the downtime event. So if you have an asset 'Packaging Line 1' with cells 'Filler', 'Capper' and 'Palletizer', you can set the Machine ID to the assetId for the Filler cell (7) and set the State to the stateCode linking the Filler to 'CIP' i.e. 127. |
| Mode | If the asset mode can be read from a tag source, connect this tag or leave blank if using the MQTTPath parameter |
| Outfeed Count | Connect this tag to your infeed count source, or leave blank if using the MQTTPath parameter |
| Part Required | This is currently only used in the Reliability KPIs analytics screen. That analysis screen breaks production hits into 'Loss Buckets', one of them being 'Breakdown' which was determined by a part needing to be replaced. |
| Outfeed Count | Connect this tag to your infeed count source, or leave blank if using the MQTTPath parameter |
| Product Code | If the product running on the asset can be read from a tag source, connect this tag or leave blank if using the MQTTPath parameter |
| State | If the state of the asset can be read from a tag source, connect this tag or leave blank if using the MQTTPath parameter |
| Tooling | This tag can be used to track the serial number or part number for a jig or mold used by an asset. That in turn can be used to track the number of counts against a tool, which can in turn notify when a tool needs to be replaced or sent for maintenance. We can also use it to trigger quality checks whenever the tooling is changed, and finally it can be used to track which tool was used to produce which lot of material. |
| Waste Count | Connect this tag to your infeed count source, or leave blank if using the MQTTPath parameter |
| Work Order | If the production order running on the asset can be read from a tag source, connect this tag or leave blank if using the MQTTPath parameter |