Notification requests can follow a series of customer-defined rules, which can filter targets (users), sequences targets, serialize or parallelize transmissions, stagger / delay transmissions, await responses, etc. NOTIFeye includes a simple scripting language which allows customers to easily create rules, and even combine rules to create complex notification handling.

Each notification target (user) can have up to 255 attributes associated with them. Attributes can define roles, seniority, notification priority, geolocation, responsibilities, permitted receipt dates/times, and more. The customer can define the attributes and then use them in rules to make notification delivery and routing decisions. Attributes can reside in customer systems, or in NOTIFeye’s own database.

Templates capture all information necessary to perform a notification, and include a label for easy reference. A template can specify targets, rules, endpoints, and actions to take upon start, apply to each target, and actions to take upon completion.

Target groups can be statically or dynamically defined. Dynamically defined groups can require user opt-in, and manual opt-out or time and date based removal.

NOTIFeye can link to existing systems and databases to gather information on targets and endpoints (users, accounts, websites, etc.) so that customers don’t have to create and maintain duplicate databases. NOTIFeye also offers robust API’s allowing integration with user applications and devices so that users don’t have to carry additional devices or install additional software.

Notifications can be triggered manually by a user using the device of their choice. Notifications can also be triggered automatically, by systems or devices. Automatic notification triggers can include weather, a message, web page entries, state of physical devices (button, control panel), etc. Notifications can also be triggered by proximity (e.g. cell phone entering range of a sensor).

Alerts in text format can be automatically converted to speech as an audio recording, read to send to any suitable endpoint.  The audio can be transmitted over RF networks, delivered as speech when an endpoint answers their phone, left as a voicemail, etc.

NOTIFeye has the ability to use local computing and communications infrastructure in the event that backbone computing and communication services are unavailable at the time of a disaster. Integration with emergency service radio (RF) networks, local phone systems, peer-to-peer devices, etc. ensures unified communications continue in the face of a disaster.

NOTIFeye supports numerous trigger endpoints out of the box, including e-mail, SMS, phone, radio, peer-to-peer, e-signage, social media, and more. Designed from the ground up to be endpoint independent, it’s easy to add new and custom trigger endpoints for each deployment.

NOTIFeye works brilliantly with traditional push endpoint (e.g. SMS, voice messaging, signage), but also with pull endpoints (sometimes called “publish-subscribe”). Using NOTIFeye’s API, notifications can be stored for later retrieval (or expiry) with devices that support publish-subscribe; and devices that are out of range can also catch up on all missed alerts once back online.

Most alert endpoints support only one-way communications, either sending or receiving a message with returning a confirmation, or returning a custom response. NOTIFeye leverages the two-way messaging capabilities of endpoints, allowing for confirmation of receipt, confirmation of read, response from pre-defined options, etc.

Administrative and user access to NOTIFeye is protected by an security system with predefined roles and permissions. All API’s incorporate a challenge-response authentication and token mechanism, restricting access to features and data to authorized devices, systems, and users only.

All traffic (inbound and outbound) to NOTIFeye is logged, including confirmations of delivery or read, responses, etc. As well, where NOTIFeye has applied rules to determine timing, targets, etc. each rule’s execution (or exclusion) is logged. This allows for detailed audit of operations and actions following an incident.

NOTIFeye includes a variety of operations, performance, and audit reports which can be automatically generated on a schedule or created on-demand. Two-way notifications which allow targets to reply can feed reports to create up-to-date situational reports.  Reports are delivered in JSON format, allowing for viewing or printing in formats determined by the customer. This machine friendly format also allows for integration into customer systems for further analysis or archiving. Custom reports can be created by Telium to meet any customer need.

NOTIFeye can be deployed in the cloud, on-premise, or a hybrid of the two. Customer infrastructure and disaster survivability requirements influence the ideal deployment type . Customers whose needs are met with cloud based solutions have the option of purchasing NOTIFeye as a service (SaaS) or as an owned product.