Automated production runs using tag data collection

The AVEVA Insight Production Run Data Collection feature allows you to trigger production runs using tags.

Configuring Production Run Tags

Production run tags are configured in the equipment efficiency model using the Production Run Tag card. To configure automated data collection, production run tags are assigned to each piece of equipment and uploaded using CSV files to the associated efficiency model. Efficiency model production run tag upload files are arranged similar to the following:

Namespace,Name,TriggerProductionRun,PlannedQuantity,PlannedDurationInMillisec,RateQuantity,RateUOM,RateTime

Austin,Capper,Austin.Capper.ProdRunTrigger,Austin.Capper.ProdRunQuantity,Austin.Capper.ProdRunDuration,Austin.Capper.ProdRunTargetRate,Austin.Capper.ProdRunUOM,Austin.Capper.ProdRunTime

The production run trigger tag is used by the system to detect tag value changes for indicating when to start or stop a production run. When starting a production run, the additional production run tags are used to set the production run quantity, duration, and target rate. For detailed information on managing configuration files within the efficiency model, and detailed production run tag configuration requirements, see Manage the efficiency model and Production run tag columns.

RunTime Behavior

When the production run trigger tag transitions to True, the values of all of the production run tag values that define production run settings are retrieved, and the production run starts. If the planned quantity tag is not defined or invalid, no production run will be started. If the planned duration tag is not defined or invalid, the duration will be set to zero. If any of the ideal rate tags are not defined or invalid, the default values configured in the OEE calculation definition for the equipment will be used. When the production run trigger tag transitions to False, the production run completes.

When the runtime tag values change, production run updates are displayed on the Production Events tab of the Equipment Efficiency page. Production runs should not be edited when automated production triggers are used. Avoid manually starting or stopping production runs from the Production Event tab if you are managing production runs using tags.

Support for Store-and-Forward Scenarios

While data should typically be processed in chronological order from published live data sources, it is possible that old data will be added. In this event, store-and-forward scenarios are supported for automated production runs including manual imports of csv files. If old data (that is, store-and-forward data) is added, received, the system will process the data in the background and correct historical records. If old data is received, existing production runs may be modified to change their start and complete times, new production runs may be created, and all related KPIs will be updated. Depending on the number of updates to be made and recalculations required, this process will take time to complete and the corresponding data in the Equipment Efficiency and OEE Analysis pages will change once the process is completed.

Note: Tags older than 30 days will be ignored.