ARL Gateway Interfacing / message handling
The gateway/ message handler allows for a configurable set of rules to determine the action to be taken on certain data content received from the ARL gateway. The rules are flexible as different sites require different actions to be taken on the incoming messages. It is possible to configure which rules are active at any particular point in time and to disable or activate rules within the configuration. The system supports the following rules:
| Message | Description | Process |
|---|---|---|
| Driver log-in |
Check that the driver is registered on the system as a valid user (i.e. they use a valid warrant card or Dallas Key).
|
Using the driver id (either warrant card or Dallas key) check that the driver is a registered Police officer using the personnel table. If not, Alert Raised |
| Driver log-in | If Dallas keys are used. Check that the driver id used is a known ‘pool card’ identifier if not registered to an individual |
The system will hold details for a number of Dallas key identities against an employee of "POOL USER". If not, Alert Raised |
| Driver log-in | Is the driver authorised to drive this particular vehicle (either individually or based on vehicle type). |
The system will check the authorisation system to determine if the driver is authorised. If not, Alert Raised |
| Vehicle movement | Following a system defined period of time / movement, the system will check that a log-in has been performed |
The system will hold configuration values for minimum period of time / distance of movement before this check is made. If a vehicle moves as per the above conditions without a driver logging in then an alert is raised. |
| CAN bus Messages | Certain messages from the vehicle management systems (CAN bus) will need to be validated in real-time |
The system will hold configuration for the CAN bus messages to be processed and the appropriate alert action to be taken. For example: AIRBAG ACTIVATED is received by the system could generate an alert to Control operator and to the driver’s line manager / supervisor. |
| Accelerometer/ G-force Measurements | The system will detect accelerometer or g-force readings that fall outside of configurable threshold values. |
The system will hold configurable threshold values for each of the 3- axis accelerometers (x,y,z). Should a message be received that is outside of the threshold an immediate alert will be raised. |
| Auxiliary equipment activated | Auxiliary equipment – e.g. lights, sirens, gun box opened will be contained in specific message details |
The system will hold configurable details for the auxiliary equipment messages and the alert action to be taken. For example: Sirens on will potentially raise an alert, sirens off may not. |
| Geo-fences | Where geo-fences are defined in xc the alerts generated should be sent through the same mechanism as the DRM alerts | When a vehicle enters the Geo- fence an alert is sent to to the appropriate vehicle. |
| In-vehicle alert has been raised | The 3PAD device in the vehicle will be configured to request specific information from the system. There are 3 keys so 3 options. |
The system will define the configuration of the 3 keys and the action to be taken for each. There will be a defined set of actions that can be used against the 3 keys. For example: Officer Distress / emergency Request current information (geo- fence) is sent via email Acknowledge warning in vehicle |