Services
Outline the platform services that run under the hood.
Core Services
Perspio extends its modular design into the core platform. These services are not exposed to platform consumers and exist within the shared processing environment. This overview provides context to the operation of the data and operational interfaces. Various aspects of how these services behave for a particular customer can be managed through the available interfaces; however, note that these are shared platform services.
Interfaces
The Data Interfaces and Operational Interfaces will be more important to understand in detail as they will provide the points of interaction for any implementation.
Core Services Summary
Capability Block | Interface | Function |
---|---|---|
PerspioCore | System | The platform engine enables aggregation, transformation, abstraction, data processing and analytics. These are deployed across several modular microservices that can be toggled to run based on the desired feature set of the customer. |
PerspioHistory | System | An integrated approach to historical data storage (telemetry and enterprise) that provides an evolving balance between performance, security, cost and retention. |
PerspioMgmt | System | Collection of services to manage, monitor and update an instance of Perspio™ |
PerspioSecure | System | Collection of services to provide complete security coverage that can be heavily configured to meet the needs of any customer. |
Microservices
Service | Description | Input | Output |
---|---|---|---|
Geofencing | Responsible for generating Entry and Exit events for conanalysesassets. The service analyzes a change feed of location data and contains logic to handle geofencing accurately, even from devices with poor GPS coverage. | Asset History Query | Entry Event, Exit Event |
Trip/Activity | Responsible for creating new trip records bound by a specific events. The default trip is bound by the Ignition ON and Ignition OFF event. | Asset Change Feed | Trip Records |
Custom Counter | Responsible for incrementing up to 3 counters for each configured asset. Counters will increment based on a configured condition. | Asset Change Feed | Update Asset Meter Property (Custom Counter 1/2/3) |
Proximity | Responsible for creating a Proximity event when two assets are less than a specified distance apart. Distance thresholds and relationships can be handled independently. | Asset Change Feed | Proximity Event |
Speeding | Respasset'se for creating Speeding events when an assets speed is +5% of the posted road speed. This service shoud be limited to on-road assets with a high fidelity device. (Limited to Australia and New Zealand) | Asset Change Feed | Speeding Event |
Toll Charging | Responsible for creating Toll Charge events. Analyzes the Toll Pass events in completed trip records distance-basedoll charges and contains logic to handle distance based and time-of-day charges. (Limited to Australia and New Zealand) | Trip Record Feed | Toll Charge Events |
Updated almost 2 years ago
What’s Next
Continue to check out other platform overview pages