devices with devices from a third party telematics provider. Although this solved the problem of having multiple data providers requiring unique integration methods, this was by far the most expensive option. In addition to the expense, many third-party devices available for construction equipment are unable to access data directly from the machine's electronic control modules (ECMs), or computers, and are more limited than the device installed by the OEM (Cat, Volvo, Deere, Komatsu, etc.) in the data they are able to provide. In some cases, these devices are limited to location and engine runtime, although they are increasingly able to accommodate a number of add-on sensors to provide additional data. The AEMP Telematics Data Standard provides a fourth option. By concentrating on the key data elements that drive the majority of fleet management reports (hours, miles, location, fuel consumption), making those data elements available in a standardized xml format, and standardizing the means by which the document is retrieved, the standard enables the end user to use one API to retrieve data from any participating telematics provider (as opposed to the unique API for each provider that was required previously), greatly reducing integration development costs. The current draft version of the AEMP Telematics Data Standard is now called the AEM/AEMP Draft Telematics API Standard, which expands the original standard Version 1.2 to include 19 data fields (with fault code capability). This new draft standard is a collaborative effort of AEMP and the Association of Equipment Manufacturers (AEM), working on behalf of their members and the industry. This Draft API replaces the current version 1.2 and does not currently cover some types of equipment, e.g., agriculture equipment, cranes, mobile elevating work platforms, air compressors, and other niche products. In addition to the new data fields, the AEM/AEMP Draft Telematics API Standard changes how data is accessed in an effort to make it easier to consume and integrate with other systems and processes. It includes standardized communication protocols for the ability to transfer telematics information in mixed-equipment fleets to end user business enterprise systems, enabling the end user to employ their own business software to collect and then analyze asset data from mixed-equipment fleets without the need to work across multiple telematics provider applications. To achieve a globally recognized standard for conformity worldwide, the AEM/AEMP Draft Telematics API Standard will be submitted for acceptance by the International Organization for Standardization (ISO). Final