The Orsus Situator system collects, correlates and analyzes data from sensors and video cameras that interface with the system. This information can trigger situation responses, including recommendations and automated task assignments based on pre-defined rules and protocols.
The Situator Situation Management System includes the following:
- Monitoring Engine
A “watchdog” module, responsible for permanent observation of the “well being” of the product components, such as services of Situator or 3rd party. The module provides independent error reporting mechanism. It comes with a monitoring application for administrators.
- Reporting Engine
A module responsible for generations of the reports of different kind in the system, and there distribution to the recipients – according to manual requests or rather predefined set of rules.
- Sensor Server
Sensor Server is the module responsible for all the communication between the gateways (from one side) and general-purpose core components like Operational Server (from the other side). Sensor Server is a generic component, while gateways provide the “normalization” (translation) between the gateway “protocol” and Situator core “generic model” of sensors.
- Flood Protection
A mechanism designed to protect the stability of the overall system, upon an unexpected volume of events coming from one of the gateways (systems). The mechanism ignores the “nosy” signal at very initial stage, protecting the key system components.
- Discovery
A mechanism to import dynamically the information on sensors, users, groups and permissions from the systems (gateways) – into Situator. Discovery supports both initial import and further updates. Sensor discovery is especially useful to speed up the system setup, and avoid manual work.
- Business Process Management
BPM is a component supporting design and execution of the “business processes” within Situator, implemented via the “workflow” model. BPM provides support for mapping the business rules into a set of workflows, supporting the business logic and providing automatic response.
- Situator Server
The Situator Server manages the internal communication, routing and processing of all information handled by the Situator system, including edge device alerts and commands, notifications, escalation requests, incident logic and event triggers.
- Notification & Mobile Engines
The Situator Notification Server facilitates and coordinates on-demand and automated communication. Notifications, which can include task assignments and attachments, can be sent by rules triggered by device alarms and escalation policy events, by Situator Control Room operators and by responders using wireless mobile devices equipped with the Situator Mobile Client Application. The Situator Notification Engine supports radio, telephone, public address systems, fax, email, SMS and multimedia messaging using a secured network, standard telephone interface, GPRS and other mobile protocols. For mobile notification, to ensure that tasks, attachments and other messages are delivered, Orsus Situator promises Guaranteed Message Delivery. Unlike commercial mobile messaging services which acknowledge message delivery only, Situator sends acknowledgement when tasks and messages are actually received by the intended recipient, and can activate escalation rules.
- GIS Server
The GIS Server collects real-time data from devices such as GPS, RFID and other location tracking products whose status and position change frequently and provides up-to-date information for monitoring those devices in the GIS map display.
- Escalation Engine
Tasks, notifications and incidents that are not handled within pre-defined time thresholds are tagged and reassigned by the Situator Escalation Engine. Escalation events prompt the Notification Engine to send notification to relevant Situator operators and can trigger procedures or alternate tasks, including device control commands to be activated.
- Scheduler
Any task that can be initiated on-demand, such as routine diagnostics or communication and sensor activation/deactivation, can also be scheduled and managed by the Scheduler Server. For example, Situator can schedule night and day modes for access control sensor activation and deactivation in selected locations.
- Situator Database
The Microsoft SQL database stores situation response rules and procedures, data and video from edge devices as well as security and administration event logs. Database services, such as data collection, simulations and off-line analysis run independent of – and so do not interfere with – processor-intensive operations which require optimal availability for efficient situation response.
