The PreCise MRM feed type in ArcGIS Velocity sends HTTPS requests to a specific PreCise MRM API URL with the relevant parameters. The request returns the last known locations for permitted vehicles.
Example
The following are example use cases for the feed:
- A company that rents heavy-duty earth-moving equipment to customers wants to monitor the location and use of rented equipment. The company uses the real-time locations of rented equipment to efficiently dispatch service technicians to equipment locations when repairs are needed and to receive notifications when the equipment is used outside of a project area.
- A utility company uses real-time locations of their fleet vehicles and information on engine hours, on-board equipment, and odometer readings to efficiently dispatch vehicles while maximizing vehicle longevity.
Usage notes
Keep the following in mind when working with the feed:
- Set the Username, API Key, and Your PreCise MRM company ID parameter values to your PreCise MRM credentials for authentication.
- The PreCise MRM feed sends requests to the specified PreCise MRM API URL at the rate defined by the Feed Polling Interval step of the configuration wizard. The minimum feed polling interval is 10 seconds.
- The feed should not be configured to run more frequently than the PreCise MRM API can return features.
- You can flatten arrays and provide specific array flattening exemptions.
- Velocity automatically handles paginated responses from the PreCise MRM API to process all features.
- This feed supports removing unwanted fields and adjusting field names. The assetID field is automatically configured as TRACK_ID, and the gpsTime field is automatically configured as START_TIME. Adding new fields is not supported, as the schema is predetermined based on the data provided by PreCise MRM.
- Velocity subscription
license levels have limits on how much data can be
ingested by a feed.
If feeds exceed the ingestion limit of your license level, a
message is written to the logs, and an email is sent
notifying you that the limit has been reached. If data ingestion remains above the limit for
more than an hour, the feed is stopped. Work with
your Esri representative or Esri Technical Support to
explore Velocity license
levels that
support your
workflow if necessary. License
levels are as follows:
- Standard—Ingest and process data at 25 KB/second (approximately 100 events per second).
- Advanced—Ingest and process data at 250 KB/second (approximately 1,000 events per second).
- Dedicated—Ingest and process data at 2,500 KB/second (approximately 10,000 events per second).
Parameters
The following are the parameters for the feed:
| Parameter | Description | Data type |
|---|---|---|
| Username (Required) | The username required to access PreCise MRM API. Refer to the usage notes above to learn how to obtain the username from PreCise MRM. | String |
| API Key (Required) | The API key required to authenticate with PreCise MRM API. Refer to the usage notes above to learn how to obtain the API key from PreCise MRM. | String |
| Your PreCise MRM company ID (Required) | A unique identifier assigned by PreCise MRM. Refer to the usage notes above to learn how to obtain the company ID from PreCise MRM. | String |
| Additional logging (Optional) | Specifies whether logging is turned on for raw HTTP requests and responses issued by Velocity to PreCise MRM API. Note:Only turn on this parameter for troubleshooting purposes and turn it off when troubleshooting is complete. Once turned on, start the feed, the debug level logs are available on the feed logs page. Contact Esri Technical Support for assistance with troubleshooting, if necessary. | Boolean |
Considerations and limitations
Consider the following when using the feed:
- A PreCise MRM subscription and API Key are required to use this feed type. Request a trial of PreCise telematics solutions.
- The minimum polling interval for the PreCise MRM API is 10 seconds.
- The PreCise MRM feed always returns the last known positions for all permitted assets (vehicles), regardless of whether new data has been received since the last polling interval.