ETA (Events-Triggers-Actions)

Every Event is an Opportunity for Automation

Sample interface of Media Sourcery Authorization Product

Media Sourcery's ETA product gives customers the capability to automate specific events based on customer configured rules, triggering customer configured actions. With the latest release ETA supports compond rules (i.e., if THIS and THIS then do this) providing more flexibility to automate whatever customers can imagine.

Automation Limited Only By Imagination

A few examples of what is possible

1

Healthcare. In healthcare, solutions like ETA are sometimes called "clinical decision support systems". The first version of ETA has been in use for several years monitoring diabetes meters. Events come from multiple types of meters. Rules (called "clinical protocols") are based on single readings or patterns of readings. These rules trigger a variety of actions - including notifying 7x24 hour nurse call centers who can dispatch 911 services for dangerous readings. This production solution has been a part of saving lives, something our team is very proud of and strives to improve with each new release.

2

Safety. At work sites such as oil fields, ports, medical centers and the like, safety is always a priority. IoT devices such as Romware from Media Sourcery partner Rombit provide hooks for easy integration into ETA to automate actions for certain events, or compound events. If social distance alerts (encounters) as an event from these types of devices are combined with events that indicate positive or negative COVID-19 test results, a company can put together a very effective work site or office contact tracing and alerting app in a matter of minutes.

3

Notification and Automation. Accelerating workflows means ensuring the current task is completed on time, and there is no wait time between that completion and the follow task in the process. With the task total elapsed time and the SLA (Service Level Agreement) for the task, an event can be monitored to trigger one action if the task is about to be late (maybe a reminder text or email), a different action if the task becomes late (programmatically move its visibility to the top) and another action if it passes another threshold (automatic escalation, notification to waiting interested parties). When the task is complete, that completion is another event, and a rule can be set to trigger the start and/or execution of the next task in the workflow. Acceleration through Automation.

Breaking It Down

Every Event in your process is an opportunity for Automation. An event could start the workflow; an event could generate a notification to a customer, an employee with a particular skill set, or both; an event could need another event to trigger a particular action. Or an event could just be an event - one that does not meet any configured rules, and is simply logged and recorded. Events can come from monitored devices (healthcare, IoT, others), from other programmatic endpoints or from workflows and processes.

When an event matches the criteria configured in your rule, an action is triggered. Rules can be simple (IF this), complex (IF this and that) or compound, combining two rules together (IF this rule is true and that rule is true). In this way, all permutations of an event can be covered if desired.

As with rules, Actions can be simple or complex. A notification Rule could trigger as an Action a text, an email, or a programmable voice message, notifying an interested part of the event, or of a task they need to do based on the event. A rRule could trigger a programmatic Action, which starts a more complex task. For example: a customer responds yes to a question, that event could trigger a rule that starts an action to complete an order, close the workflow and signal the shipping department to ship.

ETA (Events-Triggers-Actions)

Press Release