CAUTION: Not compatible with ArcGIS GeoEvent Server 10.8.1 (an update is pending)
Cartegraph provides an operations management system that allows governments to manage assets, maintain infrastructure, and track resources. It is common to integrate Cartegraph with GIS to provide a spatial aspect to all those capabilities. Recently, I developed a Cartegraph Connector for GeoEvent Server that would allow GeoEvent to write events out to the Cartegraph OMS to track labor and equipment resources against specific tasks. This post provides the components and instructions for deploying this Connector.
This connector was designed to allow GeoEvent to provide updates for both labor and equipment that are operating on specific tasks within the Cartegraph system. The underlying assumptions for this connector are as follows:
- AVL Data Feed - Labor and/or equipment identification is provided in the incoming data feed. This may be a Vehicle Tracking feed that contains an equipment’s
- GPS Location
- The ID of the equipment (such as a VIN)
- And/or the ID of the equipment operator (labor)
- Shared IDs - The IDs provided by the AVL Data feed are shared by the Cartegraph system. If they are not shared, the IDs can be translated or looked up in GeoEvent using a Field Enricher.
- Spatially Defined Cartegraph Assets – The GEoEvent Server will have access to an Esri Feature Service that provides the location and details for the Cartegraph Assets that need to be cross-referenced with the equipment and labor above.
- Each Task feature will contain an AssetID that identifies the Cartegraph asset (such as a roadway).
- GeoEvent will use this AssetID to create a Task in the Cartegraph system and assign the equipment and/or the labor to that task.
When an equipment and/or labor location event is sent to GeoEvent, it will GeoTag that event with an AssetID by intersecting the GPS location with the Cartegraph Asset Features. The resulting GeoTag will indicate which Asset(s) the equipment/labor is currently active in. The resulting event containing equipment, labor, and asset information is sent to the Cartegraph system as a Task. The name of the task is defined in the GeoEvent Output and can represent any sort of operation that currently exists in the Cartegraph system, such as “Snow Plowing” or “Mowing”.
Finally, the output will maintain a state of the task and will update the information for that task according to the lifetime of the task. At the completion of a task, a Cartegraph log will be created to track the equipment and labor work done on the asset for that task.
- If the equipment location is entering the asset’s area for the first time, a new task will be created.
- If the equipment location was previously in the asset’s area, an existing task will be updated.
- If the equipment location leaves an asset’s area, the existing task will be closed and a log item will be created for the equipment and/or labor.
Detailed Instructions for installing this connector can be found in the zip file attached to this post.
GeoEventServer-CartegraphConnector-r1.zip
