support such a standard, the AEMP formed a standards development subcommittee chaired by Pat Crail CEM to develop the standard. 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. The result, the AEMP Telematics Data Standard V1.1, 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. The AEMP's telematics data standard was developed to allow end users to integrate key telematics data (operating hours, location, 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. 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. A third option for mixed-fleet integration was to replace the various factory-installed telematics