Editing Telematics (section)

=== Telematics standards ===
{{update|section|date=February 2018}}
The Association of Equipment Management Professionals (AEMP)<ref name="Association of Equipment Management Professionals 2017">{{cite web | title=Association of Equipment Management Professionals | website=Association of Equipment Management Professionals | date=2017-10-20 | url=http://www.aemp.org/ | access-date=2018-02-28}}</ref> developed the industry's first telematics standard.{{Citation needed|date=September 2017}}

In 2008, AEMP brought together the major construction equipment manufacturers and telematics providers in the heavy equipment industry to discuss the development of the industry's first telematics standard.<ref>{{cite web|url=http://www.constructionequipment.com/aemp-releases-updated-version-telematics-standard|title=AEMP Releases Updated Version of Telematics Standard - Construction Equipment|website=www.constructionequipment.com}}</ref> Following agreement from [[Caterpillar Inc.|Caterpillar]], [[Volvo]] CE, [[Komatsu Limited|Komatsu]], and [[John Deere]] Construction & Forestry to support such a standard, the AEMP formed a standards development subcommittee chaired by Pat Crail CEM to develop the standard.<ref>{{cite web |url=https://netforum.avectra.com/eWeb/DynamicPage.aspx?Site=AEMP&Webcode=LeadershipDetail&cmt_key=19a31e1d-e426-4931-bb58-1153bc98ce87 |title=NetFORUM Team/Pro |access-date=2010-11-06 |url-status=dead |archive-url=https://web.archive.org/web/20131004232617/https://netforum.avectra.com/eWeb/DynamicPage.aspx?Site=AEMP&Webcode=LeadershipDetail&cmt_key=19a31e1d-e426-4931-bb58-1153bc98ce87 |archive-date=2013-10-04 }}</ref> This committee consisted of developers provided by the Caterpillar/Trimble joint venture known as Virtual Site Solutions, Volvo CE, and John Deere. This group worked from February 2009 through September 2010 to develop the industry's first standard for the delivery of telematics data.<ref name="telematicstandard">{{Cite web|title=ISO/TS 15143-3:2020|url=https://www.iso.org/cms/render/live/en/sites/isoorg/contents/data/standard/07/63/76394.html|access-date=2020-07-28|website=ISO|language=en}}</ref>

The result, the AEMP Telematics Data Standard V1.1,<ref name="telematicstandard"/> was released in 2010 and officially went live on October 1, 2010. As of November 1, 2010, Caterpillar, Volvo CE, John Deere Construction & Forestry, OEM Data Delivery, and [[Navman]] Wireless are able to support customers with delivery of basic telematics data in a standard xml format. Komatsu, [[Topcon]], and others are finishing beta testing and have indicated their ability to support customers in the near future.<ref name="telematicstandard"/>

The AEMP's telematics data standard was developed to allow end users to integrate key telematics data (operating hours, location, [[fuel consumption|fuel consumed]], and [[odometer]] reading where applicable) into their existing fleet management reporting systems. As such, the standard was primarily intended to facilitate importation of these data elements into [[enterprise software]] systems such as those used by many medium-to-large construction contractors. Prior to the standard, end users had few options for integrating this data into their reporting systems in a mixed-fleet environment consisting of multiple brands of machines and a mix of telematics-equipped machines and legacy machines (those without telematics devices where operating data is still reported manually via pen and paper). One option available to machine owners was to visit multiple websites to manually retrieve data from each manufacturer's telematics interface and then manually enter it into their fleet management program's database. This option was cumbersome and labor-intensive.<ref name="constructionequipment.com">{{cite web|url=http://www.constructionequipment.com/article/telematics-turns-corner|title=Telematics Turns the Corner - Construction Equipment|website=www.constructionequipment.com|date=27 October 2010}}</ref>

A second option was for the end user to develop an API ([[Application Programming Interface]]), or program, to integrate the data from each telematics provider into their database. This option was quite costly as each telematics provider had different procedures for accessing and retrieving the data and the data format varied from provider to provider. This option automated the process, but because each provider required a unique, custom API to retrieve and parse the data, it was an expensive option. In addition, another API had to be developed any time another brand of machine or telematics device was added to the fleet.<ref name="constructionequipment.com"/>

A third option for mixed-fleet integration was to replace the various factory-installed telematics 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 module]]s (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.<ref name="constructionequipment.com"/>

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.<ref name="telematicstandard"/>

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 language is dependent upon completion of the ISO acceptance process.