Trigger

Trigger is used to make software events happen in response to signals from your process.

There are a range of tasks that you might want to automate based on signals from your various ARDI data sources. Just a few options are…

• Calculate totals for individual operations/loads,
• Produce immediate KPIs at the end of shifts or batches,
• Capture product runs and issues,
• Record or notify when unscheduled down-time is detected,
• Produce end-of-batch, cycle or product run reporting,
• Log key process events to local, remote or cloud databases.

Although trigger is quite simple, there are several advantages to using it to power your event-driven applications, such as…

• Trigger takes care of subscribing to live data, dealing with connection loss and scheduling your custom scripts to run.
• A single trigger service can handle many different, individually-triggered applications, meaning that you only use a single concurrent user license instead of several.
• The trigger system allows for back-filling across times that might have been missed when equipment or services were offline or unavailable.
• Trigger allows you to deploy event-driven software solutions across multiple sites, even when their backends are radically different.