While creating training material for our internal staff on telematics, we found the below site that gives a very good introduction to novices on the basics of telematics -
http://www.equipmentworld.com/tag/telematics-101/
I had covered the business benefits of telematics in this blog post. One of the fundamental challenge for the wide spread adoption of telematics has been the lack of standards around aggregating data from multiple TCU (Telematics Control Unit) vendors.
But now, the Association of Equipment Managers (AEM) and Association of Equipment Management Professionals (AEMP) have created a ISO standard to help systems
from different manufacturers all speak the same language - http://www.aemp.org/?page=AEMPTelematicsAPI
The AEMP 1.0 standard defined a XML data format that is available here.
An example of the AEMP REST API by John Deere is available here (in both XML and JSON formats) - https://developer.deere.com/content/documentation/aemptwo/fleet.htm#
The newer version (v 2.0) of the AEMP telematics standard is now an ISO standard (ISO 15143-3).
An example of ISO 15143-3 telematics API (with XML data format) is here.
As part of this standard, equipment makers would report the following data points and 42 fault codes using a standard protocol that will allow mixed equipment fleets to be managed from a single application.
Data Elements
http://www.equipmentworld.com/tag/telematics-101/
I had covered the business benefits of telematics in this blog post. One of the fundamental challenge for the wide spread adoption of telematics has been the lack of standards around aggregating data from multiple TCU (Telematics Control Unit) vendors.
But now, the Association of Equipment Managers (AEM) and Association of Equipment Management Professionals (AEMP) have created a ISO standard to help systems
from different manufacturers all speak the same language - http://www.aemp.org/?page=AEMPTelematicsAPI
The AEMP 1.0 standard defined a XML data format that is available here.
An example of the AEMP REST API by John Deere is available here (in both XML and JSON formats) - https://developer.deere.com/content/documentation/aemptwo/fleet.htm#
The newer version (v 2.0) of the AEMP telematics standard is now an ISO standard (ISO 15143-3).
An example of ISO 15143-3 telematics API (with XML data format) is here.
As part of this standard, equipment makers would report the following data points and 42 fault codes using a standard protocol that will allow mixed equipment fleets to be managed from a single application.
Data Elements
- Serial Number
- Asset ID
- Hours
- Location
- GPS Distance Traveled
- Machine Odometer
- Fault Codes
- Idle Time
- Fuel Consumption
- Fuel Level
- Engine Running Status (on/off)
- Switch Input Events
- PTO Hours
- Average Load Factor
- Max Speed
- Ambient Air Temp
- Load Counts
- Payload Totals
- Active Regen Hours
Fault Codes
- Engine coolant temperature
- Engine oil pressure
- Coolant level
- Engine oil temperature
- Hydraulic oil temperature
- Transmission oil temperature
- Engine overspeed
- Transmission oil pressure
- Water in fuel indicator
- Transmission oil filter, blocked
- Air cleaner
- Fuel supply pressure
- Air filter pressure drop
- Coolant system thermostat
- Crankcase pressure
- Cool water temp, outlet cooler
- Rail pressure system
- ECU temperature
- Axle oil temp, front
- Axle oil temp, rear
- Intake manifold temperature
- Secondary steering pressure
- After-treatment reagent internal filter heater
- Crankcase ventilation
- Boost pressure
- Outgoing brake pressure status
- Brake pressure, output
- Brake pressure, output
- All wheel drive hydraulic filter, blocked
- All wheel drive hydraulic filter, blocked
- Brake pressure acc status
- Injection control pressure
- Brake circuit differential pressure
- Brake pressure acc charging
- Brake pressure actuator
- Reserve steering control pressure
- HVAC water temperature
- Rotor pump temperature
- Refrigerant temperature
- Alert and alarms help power down machines quickly
- Multiple pressure indicators
- Switching gear events
No comments:
Post a Comment