Difference between revisions of "V2/Concepts/Automation"
From Senfi Docs
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | <h1 class="main-heading">Expression, Event | + | <h1 class="main-heading">Expression, Event, Alarm</h1> |
| − | + | The modern building is alive with activities. Not just human activities, but activities of the systems that exists within, and those that interacts with it from the outside. These activities are mostly unseen and untapped – we typically only make use of a fraction of the data being generated. | |
| − | + | Building data can be ingested by Senfi to facilitate automation and improve building operations. To do so, Senfi provides an event-driven autonomous workflow engine. Similar to other event-driven architectures, users may define events in Senfi and specify actions to be carried out when an event occurs. Senfi provides a flexible way to define the conditions for triggering events in the form of an expression. Events may also optionally raise alarms, if it is intended to be handled by a human operator. | |
| − | === | + | === Implementing autonomous workflow in Senfi === |
| − | + | Users may implement autonomous workflows by configuring the following in the CMS: | |
* [[V2/Concepts/Expression|Expression Editor]] | * [[V2/Concepts/Expression|Expression Editor]] | ||
* [[V2/Concepts/Event|Event]] | * [[V2/Concepts/Event|Event]] | ||
| Line 13: | Line 13: | ||
[[File:Concepts_Automation_Engine_Overview.png|800px|center|link=]] | [[File:Concepts_Automation_Engine_Overview.png|800px|center|link=]] | ||
| + | <!-- | ||
First, User has to design an Expression specifying conditions that Senfi has to check for, in order to detect the event or situation that the User wishes to be notified of. So when data is being pumped into Senfi, relevant data will go through the Expression for autonomous checking, and if the set of conditions evaluates to true, an Event can be triggered. | First, User has to design an Expression specifying conditions that Senfi has to check for, in order to detect the event or situation that the User wishes to be notified of. So when data is being pumped into Senfi, relevant data will go through the Expression for autonomous checking, and if the set of conditions evaluates to true, an Event can be triggered. | ||
| Line 18: | Line 19: | ||
In the case where an Event is a notable situation and requires attention, User can set the Event to trigger an Alarm in the Digital Twin. In this way, all Users monitoring the Digital Twin will be alerted. | In the case where an Event is a notable situation and requires attention, User can set the Event to trigger an Alarm in the Digital Twin. In this way, all Users monitoring the Digital Twin will be alerted. | ||
| + | --> | ||
==== What's Next ==== | ==== What's Next ==== | ||
Latest revision as of 22:04, 4 July 2021
Expression, Event, Alarm
The modern building is alive with activities. Not just human activities, but activities of the systems that exists within, and those that interacts with it from the outside. These activities are mostly unseen and untapped – we typically only make use of a fraction of the data being generated.
Building data can be ingested by Senfi to facilitate automation and improve building operations. To do so, Senfi provides an event-driven autonomous workflow engine. Similar to other event-driven architectures, users may define events in Senfi and specify actions to be carried out when an event occurs. Senfi provides a flexible way to define the conditions for triggering events in the form of an expression. Events may also optionally raise alarms, if it is intended to be handled by a human operator.
Implementing autonomous workflow in Senfi
Users may implement autonomous workflows by configuring the following in the CMS:
What's Next
- Learn about Expression
- Learn about Event
- Learn about Alarm