Asset Meter Readings Import

(This add-on cost has a one-time, perpetual license cost of $9,270 and an ongoing Upgrade & Support fee of $1,854.)

The solution is designed to import cumulative asset meter readings into your FASTER Web system. Any meter type supported by FASTER Web can be configured to import Miles, Hours, PTO, Engine Idle Hours, etc. (Please note not all vendors provide these meter types. Therefore, we recommend you confirm contractually that the vendor will provide you the meter data you need. For example, some telematic vendors do not provide cumulative engine idle time.)

These meters can be viewed for historical purposes in the Asset Module under the Meters, Warranties tab. The most recent valid meter reading will update the Meter’s Actual reading throughout the system.

(Using this solution would require that your vendor can provide the meter data you desire in an XML flat file that meets the below XML Export File Specifications. Please note that if your vendor has the ability to provide this data via APIs, see FASTER Web’s API options .)

Prerequisites

  • Supported FASTER Web versions include 6.4.79 and up.
  • View 6.4 System, Environment & Configuration Requirements
    • This documentation is accessible with FASTER Customer website credentials.
    • This is an SSIS integration and require you meet the Integrations Services (SSIS) Software Requirements listed in the above documentation.
  • The Vehicle Identification Number (VIN) will be the common data key between FASTER Web and the vendor’s system to identify data records belonging to an asset. For assets without a VIN, this integration requires a unique serial number as a shared key used by both systems.

 

XML Export File Specifications

Before you purchase the Asset Meter Readings Import, FASTER recommends you receive confirmation from your vendor that they can meet the XML Export File Specifications. These specifications provide the requirements for FASTER Web to import meter data.

File Upload and Transaction Frequency

It is our recommendation that meter updates be transmitted only once per day with only the latest recorded meter transaction per asset in the export.

For the Asset Meter Readings Import, filtering and grouping is recommended from your  vendor based on your requirements to ensure only the necessary data is included during each execution of the import. It is important for your  vendor to limit the volume of unnecessary or repetitive data in the export for the customer to gain the most value from the data.

For instance, if you are receiving a daily export of meter readings, it should include only the latest meter reading for an asset for that day. That way, you can easily recognize the daily usage of vehicles without being overwhelmed by extraneous meter readings over the course of a day that provide no additional value.

Too many meter transactions may cause frustration and will create difficulty troubleshooting an issue in any given execution of the integration. Even if the vendor’s system gathers transactions with a high frequency from a vehicle or device, it will not help to include every transaction in the given execution if there is a high repetition of the same data with only slightly differing time stamps.

By filtering or grouping data, the vendor will help ensure the integration will provide the most value to you while lessening the burden of maintenance.

Export File Location

In order for FASTER Web to import alert data from the vendor, the data file must be accessible to the FASTER Web application. This may be achieved in one of the following three methods:

Method 1Customer Hosted File Server: This method requires the vendor to transfer their export files to a file server hosted within your network, such as FTPS/SFTP or network share. Your IT can work with your vendor to determine the best solution for this transfer to occur. The files then have to be made available on a network share that is accessible by the FASTER Web application server.

Method 2SFTP Site: You or the vendor will host an SFTP site where the exported XML file(s) will be placed. SFTP credentials will need to be provided in the FASTER Web application for the import utility to retrieve the file.

      • FASTER Web 6.4.79 and above supports SFTP
      • Proper permissions will need to be granted for FASTER Web to access the file.

Method 3FASTER Web Cloud Customers (where the customer has contracted FASTER to provide hosting of FASTER Web) the following two options are available:

      1. The vendor can opt to transfer their export file to an FTPS location that FASTER provides.
      2. or FASTER can fetch the export file from the vendor’s SFTP location (see Method 2 above).

File Naming Convention

    • Each Export file will be prefixed: “Meter_” followed by date, time and UTC the export occurred. Date, time and UTC must be in the following format: YYYY-MM-DD_HHMMSS-0000. Example: “Meter_2015-08-19_010000-0500.xml”
    • Files should be placed in the “Meter_Import” folder (configurable by the customer).
    • All file extension must be “.XML”

Export File Data

The following table lists the parameters, data type, and a brief description about the parameters.

There are two options for identifying an asset. The export file must have data representing one of the below two options:

  • Asset Identification Option 1: VinSerial
  • Asset Identification Option 2: AssetNumber and AssetOrganization

 *Important Note: Vendor would need to confirm with Customer which option they have chosen in order to produce the export file.

ParameterRange/LengthDescription
VinSerialMax Length 25Asset Identification Option 1

The VIN or unique Serial Number for a non-vehicle asset.

Data Type: Alphanumeric

*Required if Customer is NOT using AssetNumber and AssetOrganization for mapping assets.
AssetNumberMax Length 20Asset Identification Option 2

An alphanumeric reference code used throughout FASTER Web to identify an asset.

Data Type: Alphanumeric

*Required if Customer is NOT using VinSerial for mapping assets.
AssetOrganizationMax Length 3Asset Identification Option 2

The code that represents the highest level of asset grouping available in FASTER. For example, it can represent an entire city,a private company, school district or government services (such as police and fire departments).

Data Type: Alphanumeric

*Required if Customer is NOT using VinSerial for mapping assets.
DateMax Length 25Date and time of meter transaction. (format: YYYY-MM-DD HH:MM:SS)

Data Type: Date

*Required
MeterTypeMax Length 60A Meter Type for example can be Miles, Kilometers, Hours, PTO, Engine Idle Hours, etc.

The MeterType in the export file must exactly match the Meter Description in FASTER Web. This value is customer-configurable so vendor should confirm the Meter Types and associated Meter Descriptions with the Customer.

Data Type: Alphanumeric

*Required
Reading1 to 2147483647
Meter reading value
All meter readings must be the actual reading.
(Ex: If the previous reading for the odometer was 4,000 and the new reading is 4,250, the reading passed in the import file should be 4,250.)

Data Type: Integer

*Required

XML Export File Format

FASTER has already created the middle-ware in order to import the export files in the defined XML schema below.

Example XML using Asset Identification Option 1: VinSerial

Example XML using Asset Identification Option 2: AssetNumber and AssetOrganization

Customer IT Notes
  • FASTER import components will reside on the same FASTER Web App Server and DB Server that are currently used and reside behind your firewall. No component of FASTER will be in the cloud or need to be exposed to the internet. We specifically share this to underscore that you will work with your telematics vendor to insure you receive any export files through whatever secure means you work out with your telematics vendor.
  • Related to export file storage and fetching: you will need to permit the FASTER Web App and DB server to access a shared file folder or SFTP site where you decide to locate your telematics vendor’s export files. And a second, separate, shared file folder or SFTP site will be needed to which the FASTER Import will move the export file after data is extracted. This will give your IT team the ability to manage (archive, delete, etc.) the historical export files.

Asset Meter Readings Import

(This add-on cost has a one-time, perpetual license cost of $9,270 and an ongoing Upgrade & Support fee of $1,854.)

The solution is designed to import cumulative asset meter readings into your FASTER Web system. Any meter type supported by FASTER Web can be configured to import Miles, Hours, PTO, Engine Idle Hours, etc. (Please note not all vendors provide these meter types. Therefore, we recommend you confirm contractually that the vendor will provide you the meter data you need. For example, some telematic vendors do not provide cumulative engine idle time.)

These meters can be viewed for historical purposes in the Asset Module under the Meters, Warranties tab. The most recent valid meter reading will update the Meter’s Actual reading throughout the system.

(Using this solution would require that your vendor can provide the meter data you desire in an XML flat file that meets the below XML Export File Specifications. Please note that if your vendor has the ability to provide this data via APIs, see FASTER Web’s API options .)

Prerequisites

  • Supported FASTER Web versions include 6.4.79 and up.
  • View 6.4 System, Environment & Configuration Requirements
    • This documentation is accessible with FASTER Customer website credentials.
    • This is an SSIS integration and require you meet the Integrations Services (SSIS) Software Requirements listed in the above documentation.
  • The Vehicle Identification Number (VIN) will be the common data key between FASTER Web and the vendor’s system to identify data records belonging to an asset. For assets without a VIN, this integration requires a unique serial number as a shared key used by both systems.

 

XML Export File Specifications

Before you purchase the Asset Meter Readings Import, FASTER recommends you receive confirmation from your vendor that they can meet the XML Export File Specifications. These specifications provide the requirements for FASTER Web to import meter data.

File Upload and Transaction Frequency

It is our recommendation that meter updates be transmitted only once per day with only the latest recorded meter transaction per asset in the export.

For the Asset Meter Readings Import, filtering and grouping is recommended from your  vendor based on your requirements to ensure only the necessary data is included during each execution of the import. It is important for your  vendor to limit the volume of unnecessary or repetitive data in the export for the customer to gain the most value from the data.

For instance, if you are receiving a daily export of meter readings, it should include only the latest meter reading for an asset for that day. That way, you can easily recognize the daily usage of vehicles without being overwhelmed by extraneous meter readings over the course of a day that provide no additional value.

Too many meter transactions may cause frustration and will create difficulty troubleshooting an issue in any given execution of the integration. Even if the vendor’s system gathers transactions with a high frequency from a vehicle or device, it will not help to include every transaction in the given execution if there is a high repetition of the same data with only slightly differing time stamps.

By filtering or grouping data, the vendor will help ensure the integration will provide the most value to you while lessening the burden of maintenance.

Export File Location

In order for FASTER Web to import alert data from the vendor, the data file must be accessible to the FASTER Web application. This may be achieved in one of the following three methods:

Method 1Customer Hosted File Server: This method requires the vendor to transfer their export files to a file server hosted within your network, such as FTPS/SFTP or network share. Your IT can work with your vendor to determine the best solution for this transfer to occur. The files then have to be made available on a network share that is accessible by the FASTER Web application server.

Method 2SFTP Site: You or the vendor will host an SFTP site where the exported XML file(s) will be placed. SFTP credentials will need to be provided in the FASTER Web application for the import utility to retrieve the file.

      • FASTER Web 6.4.79 and above supports SFTP
      • Proper permissions will need to be granted for FASTER Web to access the file.

Method 3FASTER Web Cloud Customers (where the customer has contracted FASTER to provide hosting of FASTER Web) the following two options are available:

      1. The vendor can opt to transfer their export file to an FTPS location that FASTER provides.
      2. or FASTER can fetch the export file from the vendor’s SFTP location (see Method 2 above).

File Naming Convention

    • Each Export file will be prefixed: “Meter_” followed by date, time and UTC the export occurred. Date, time and UTC must be in the following format: YYYY-MM-DD_HHMMSS-0000. Example: “Meter_2015-08-19_010000-0500.xml”
    • Files should be placed in the “Meter_Import” folder (configurable by the customer).
    • All file extension must be “.XML”

Export File Data

The following table lists the parameters, data type, and a brief description about the parameters.

There are two options for identifying an asset. The export file must have data representing one of the below two options:

  • Asset Identification Option 1: VinSerial
  • Asset Identification Option 2: AssetNumber and AssetOrganization

 *Important Note: Vendor would need to confirm with Customer which option they have chosen in order to produce the export file.

ParameterRange/LengthDescription
VinSerialMax Length 25Asset Identification Option 1

The VIN or unique Serial Number for a non-vehicle asset.

Data Type: Alphanumeric

*Required if Customer is NOT using AssetNumber and AssetOrganization for mapping assets.
AssetNumberMax Length 20Asset Identification Option 2

An alphanumeric reference code used throughout FASTER Web to identify an asset.

Data Type: Alphanumeric

*Required if Customer is NOT using VinSerial for mapping assets.
AssetOrganizationMax Length 3Asset Identification Option 2

The code that represents the highest level of asset grouping available in FASTER. For example, it can represent an entire city,a private company, school district or government services (such as police and fire departments).

Data Type: Alphanumeric

*Required if Customer is NOT using VinSerial for mapping assets.
DateMax Length 25Date and time of meter transaction. (format: YYYY-MM-DD HH:MM:SS)

Data Type: Date

*Required
MeterTypeMax Length 60A Meter Type for example can be Miles, Kilometers, Hours, PTO, Engine Idle Hours, etc.

The MeterType in the export file must exactly match the Meter Description in FASTER Web. This value is customer-configurable so vendor should confirm the Meter Types and associated Meter Descriptions with the Customer.

Data Type: Alphanumeric

*Required
Reading1 to 2147483647
Meter reading value
All meter readings must be the actual reading.
(Ex: If the previous reading for the odometer was 4,000 and the new reading is 4,250, the reading passed in the import file should be 4,250.)

Data Type: Integer

*Required

XML Export File Format

FASTER has already created the middle-ware in order to import the export files in the defined XML schema below.

Example XML using Asset Identification Option 1: VinSerial

Example XML using Asset Identification Option 2: AssetNumber and AssetOrganization

Customer IT Notes
  • FASTER import components will reside on the same FASTER Web App Server and DB Server that are currently used and reside behind your firewall. No component of FASTER will be in the cloud or need to be exposed to the internet. We specifically share this to underscore that you will work with your telematics vendor to insure you receive any export files through whatever secure means you work out with your telematics vendor.
  • Related to export file storage and fetching: you will need to permit the FASTER Web App and DB server to access a shared file folder or SFTP site where you decide to locate your telematics vendor’s export files. And a second, separate, shared file folder or SFTP site will be needed to which the FASTER Import will move the export file after data is extracted. This will give your IT team the ability to manage (archive, delete, etc.) the historical export files.

Asset Meter Readings Import

(This add-on cost has a one-time, perpetual license cost of $9,270 and an ongoing Upgrade & Support fee of $1,854.)

The solution is designed to import cumulative asset meter readings into your FASTER Web system. Any meter type supported by FASTER Web can be configured to import Miles, Hours, PTO, Engine Idle Hours, etc. (Please note not all vendors provide these meter types. Therefore, we recommend you confirm contractually that the vendor will provide you the meter data you need. For example, some telematic vendors do not provide cumulative engine idle time.)

These meters can be viewed for historical purposes in the Asset Module under the Meters, Warranties tab. The most recent valid meter reading will update the Meter’s Actual reading throughout the system.

(Using this solution would require that your vendor can provide the meter data you desire in an XML flat file that meets the below XML Export File Specifications. Please note that if your vendor has the ability to provide this data via APIs, see FASTER Web’s API options.)

Prerequisites

  • Supported FASTER Web versions include 6.4.79 and up.
  • View 6.4 System, Environment & Configuration Requirements
    • This documentation is accessible with FASTER Customer website credentials.
    • This is an SSIS integration and require you meet the Integrations Services (SSIS) Software Requirements listed in the above documentation.
  • The Vehicle Identification Number (VIN) will be the common data key between FASTER Web and the vendor’s system to identify data records belonging to an asset. For assets without a VIN, this integration requires a unique serial number as a shared key used by both systems.

XML Export File Specifications

Before you purchase the Asset Meter Readings Import, FASTER recommends you receive confirmation from your vendor that they can meet the XML Export File Specifications. These specifications provide the requirements for FASTER Web to import meter data.

File Upload and Transaction Frequency

It is our recommendation that meter updates be transmitted only once per day with only the latest recorded meter transaction per asset in the export.

For the Asset Meter Readings Import, filtering and grouping is recommended from your  vendor based on your requirements to ensure only the necessary data is included during each execution of the import. It is important for your  vendor to limit the volume of unnecessary or repetitive data in the export for the customer to gain the most value from the data.

For instance, if you are receiving a daily export of meter readings, it should include only the latest meter reading for an asset for that day. That way, you can easily recognize the daily usage of vehicles without being overwhelmed by extraneous meter readings over the course of a day that provide no additional value.

Too many meter transactions may cause frustration and will create difficulty troubleshooting an issue in any given execution of the integration. Even if the vendor’s system gathers transactions with a high frequency from a vehicle or device, it will not help to include every transaction in the given execution if there is a high repetition of the same data with only slightly differing time stamps.

By filtering or grouping data, the vendor will help ensure the integration will provide the most value to you while lessening the burden of maintenance.

Export File Location

In order for FASTER Web to import alert data from the vendor, the data file must be accessible to the FASTER Web application. This may be achieved in one of the following three methods:

Method 1Customer Hosted File Server: This method requires the vendor to transfer their export files to a file server hosted within your network, such as FTPS/SFTP or network share. Your IT can work with your vendor to determine the best solution for this transfer to occur. The files then have to be made available on a network share that is accessible by the FASTER Web application server.

Method 2SFTP Site: You or the vendor will host an SFTP site where the exported XML file(s) will be placed. SFTP credentials will need to be provided in the FASTER Web application for the import utility to retrieve the file.

      • FASTER Web 6.4.79 and above supports SFTP
      • Proper permissions will need to be granted for FASTER Web to access the file.

Method 3FASTER Web Cloud Customers (where the customer has contracted FASTER to provide hosting of FASTER Web) the following two options are available:

      1. The vendor can opt to transfer their export file to an FTPS location that FASTER provides.
      2. or FASTER can fetch the export file from the vendor’s SFTP location (see Method 2 above).

File Naming Convention

    • Each Export file will be prefixed: “Meter_” followed by date, time and UTC the export occurred. Date, time and UTC must be in the following format: YYYY-MM-DD_HHMMSS-0000. Example: “Meter_2015-08-19_010000-0500.xml”
    • Files should be placed in the “Meter_Import” folder (configurable by the customer).
    • All file extension must be “.XML”

Export File Data

The following table lists the parameters, data type, and a brief description about the parameters.

There are two options for identifying an asset. The export file must have data representing one of the below two options:

  • Asset Identification Option 1: VinSerial
  • Asset Identification Option 2: AssetNumber and AssetOrganization

 *Important Note: Vendor would need to confirm with Customer which option they have chosen in order to produce the export file.

ParameterRange/LengthDescription
VinSerialMax Length 25Asset Identification Option 1

The VIN or unique Serial Number for a non-vehicle asset.

Data Type: Alphanumeric

*Required if Customer is NOT using AssetNumber and AssetOrganization for mapping assets.
AssetNumberMax Length 20Asset Identification Option 2

An alphanumeric reference code used throughout FASTER Web to identify an asset.

Data Type: Alphanumeric

*Required if Customer is NOT using VinSerial for mapping assets.
AssetOrganizationMax Length 3Asset Identification Option 2

The code that represents the highest level of asset grouping available in FASTER. For example, it can represent an entire city,a private company, school district or government services (such as police and fire departments).

Data Type: Alphanumeric

*Required if Customer is NOT using VinSerial for mapping assets.
DateMax Length 25Date and time of meter transaction. (format: YYYY-MM-DD HH:MM:SS)

Data Type: Date

*Required
MeterTypeMax Length 60A Meter Type for example can be Miles, Kilometers, Hours, PTO, Engine Idle Hours, etc.

The MeterType in the export file must exactly match the Meter Description in FASTER Web. This value is customer-configurable so vendor should confirm the Meter Types and associated Meter Descriptions with the Customer.

Data Type: Alphanumeric

*Required
Reading1 to 2147483647
Meter reading value
All meter readings must be the actual reading.
(Ex: If the previous reading for the odometer was 4,000 and the new reading is 4,250, the reading passed in the import file should be 4,250.)

Data Type: Integer

*Required

XML Export File Format

FASTER has already created the middle-ware in order to import the export files in the defined XML schema below.

Example XML using Asset Identification Option 1: VinSerial

Example XML using Asset Identification Option 2: AssetNumber and AssetOrganization

Customer IT Notes
  • FASTER import components will reside on the same FASTER Web App Server and DB Server that are currently used and reside behind your firewall. No component of FASTER will be in the cloud or need to be exposed to the internet. We specifically share this to underscore that you will work with your telematics vendor to insure you receive any export files through whatever secure means you work out with your telematics vendor.
  • Related to export file storage and fetching: you will need to permit the FASTER Web App and DB server to access a shared file folder or SFTP site where you decide to locate your telematics vendor’s export files. And a second, separate, shared file folder or SFTP site will be needed to which the FASTER Import will move the export file after data is extracted. This will give your IT team the ability to manage (archive, delete, etc.) the historical export files.