With Policy Foundry, you can set policies to monitor conditions and define the actions triggered during condition excursions. Conditions that can be monitored include Smart Badge and Asset Tag 2 button clicks, device battery levels, when a device enters or exits a location, and Portal Beam measurements including room occupancy, temperature, humidity, and air quality.
When the condition set in a policy has been reached, the policy's action is automatically triggered. A policy's action can be set to send email or texts messages to notify staff or as an event to an AWS Kinesis or Azure Event Hub stream. When a condition returns to normal, the triggered action will end. All actions triggered by your policies can be viewed from the Policy Foundry activity log.
Policies and actions are the two components you'll set up to begin monitoring your Kontakt.io devices and events.
A Policy defines the monitored conditions and what action is taken when an excursion occurs.
As you prepare to add your policies, you'll need the following for each policy.
When the policy is active: always (24/7), specific days of the week, or during a specific date range.
What locations: your Smart Location campuses, buildings, floors, rooms.
What devices: all devices or specific devices.
What is the monitored condition: the event that triggers the policy action.
What action: how excursion notifications are sent. A policy is limited to one action.
You'll select from one of your configured actions - Streams, Emails, or Text messages.
Limit the quantity of action messages (limiters): during a condition excursion, set how many email/text notifications or stream events are sent during a specific duration of time (hours, minutes, seconds). For example, you may want to limit sending notifications to 5 or less per hour.
A policy can be set to monitor one of the following conditions.
Beacon Signals: button click including both the Default Button (blue) and Second Button (red), device battery level
Telemetry: Portal Beam environmental readings, including ambient air temperature, relative humidity readings, and air quality.
Positions: device location events.
Occupancy: Portal Beam room occupancy count.
Actions define how policy excursion notifications are sent. Available action types include Streams, Emails, and Text (SMS) messages. Although a policy is limited to one assigned action, an action can be assigned to one or multiple policies.
As you plan to set up your policy's actions, you'll need the following for each action type.
A stream action can be sent to an AWS Kinesis or Azure Event Hub Stream.
AWS Kinesis stream: endpoint URL, secret key, stream name, region, access key, and forced partition key (optional).
Azure Event Hub stream: endpoint, shared access key name, shared access key, and event hub name.
For email and text message actions, you can customize what's included in the notifications.
Email: notification recipients' email addresses, email subject, event data (parameters), and text included in the email body.
Text Messages: notification recipients mobile phone numbers, event data (parameters), and text included in the message.