The Security Center Vehicle Monitoring plugin, also known as the GPS plugin, integrates your GPS tracking systems and other sensors in Security Center.
Architecture diagram for Vehicle Monitoring integration
Components of Vehicle Monitoring integration
- Vehicle Monitoring plugin
- The Vehicle Monitoring plugin is
installed in-vehicle and on a Security Center server and runs as a plugin
role. GPS data from a vehicle can be collected by one of the following methods:
- An on-board GPS router sends NMEA or TAIP data to the GPS plugin
- An on-board GPS hardware is physically connected to a Security Center server, and a GPS unit configured with serial communication parameters reads the data
- A custom integrated data source (such as a web service) pushes the data to the plugin
- Third party software uses the GPS SDK to push the data
- Third party software uses a UDP socket or MQTT topic pushes the data
- The plugin pulls the data from a GTFS realtime feed
- In-vehicle
-
- Hosts the Omnicast Transit Base
- Hosts Config Tool and Security Desk
- Hosts the Vehicle Monitoring plugin
- Communicates with the headend using Federation™
- Forwards notifications, events, and alarms from the onboard Security Center system to the Enterprise Federation™ headend.
- At the Federation™ headend
-
- Hosts Security Center Enterprise
- Hosts Plan Manager Advanced
- Hosts the Vehicle Monitoring plugin
- Provides the user interface and reports for the plugins in Security Center
- Config Tool
- The Vehicle Monitoring plugin is also installed on a Config Tool workstation. The Security Center administrator uses Config Tool to create and configure the plugin role.
- Security Desk
- The Vehicle Monitoring plugin is installed on all Security Desk workstations. Security Desk operators can monitor integrated vehicle systems and generate reports on offloads and metadata.