Integration makes our product easy to implement while maximizing returns. One of the many functions of LiGO® ACCESS is its API functionality; our customers can keep the existing business systems with which staff are comfortable and familiar with, reducing training efforts and accelerating implementation. This means that the entirety of the telematics data collected by our software solutions can be interpreted, and then fed to a number of secondary systems for other purposes.
What are API’s how do they help?
API’s short for Application Programming Interface, is a characteristic of any software which allows it to connect different devices, and applications by allowing the transfer of data. It is what allows us to book a reservation at a hotel with just a few clicks on a device. It is the link between a command and results in times when the system in which you create the command, and the system in which the results derive from are separate. One analogy would compare an API to the pizza hut employee who takes your call places the order, and then sends the delivery driver in your direction. API’s effectively make communication between different applications possible whilst also enabling the use of the same data for different functions. The beauty of API’s is that the work they do is all behind the scenes, similar to code on a webpage; even though you can’t see it the code is constantly working to do whatever the input demands of it.
LiGO® ACCESS web services, was first developed to enhance GeoKNX – a mature MarshallGIS product that pulls and pushes work orders and service requests to and from Lucity, Infor/Hansen and IBM/Maximo’s Enterprise Asset Management, and Work Management Systems (EAM/WMS) for over 100 customers and hundreds of thousands of service requests. We now have this functionality for LiGO®, and have added Cityworks and Esri integration.
All modules are integrated together, but can be turned off or on based on permissions (uncheck modules if you don’t want them). MarshallGIS has extensive experience with integrating Mobile Work Order Management and Service Requests with location based systems such as ArcGIS including creates, updates and deletes.
Esri GIS Integration
LiGO® provides for multiple interface options with Esri ArcGIS. ArcGIS Server maps in LiGO®, live LiGO® vehicle feeds to your ArcGIS operations map, KML import/export, and CSV exports.
MarshallGIS has been partnered with Cityworks for over 5 years and is committed to support Cityworks integration. API’s are designed to fluidly transition without breaks during a software version change.
No third party tools are needed to maintain integration.
We’ve also developed a work flows to push odometer readings from LiGO® into Cityworks and create a vehicle work order for activities such as vehicle inspections, oil changes and tire rotations base on miles and or time.
LiGO® can be optionally provisioned with Garmin’s for dispatch/jobs, routing and chat features, and even real time (based on traffic) estimated time of arrival. This can be enabled simply by checking Garmin as an option. Garmin integration brings a lot of additional functionality – including turn by turn directions, proximity sensors, additional driver ID with NFC, camera, video, and chat.
To display live vehicles/crew locations from LiGO® on your Cityworks Operation map or any ArcGIS map (Desktop, Server, Online) there are two methods. As always each have pros and cons.
- LiGO® can use, but does not require, ArcGIS GeoEvent Processor to update a vehicle feature class on a user defined schedule. This method requires the user to have a Esri GEP license.
- LiGO® can also send position updates to a user defined REST endpoint. The REST endpoint may be hosted at your location. If you prefer to simply publish a feature service with editing rights to the underlying vehicle feature class, LiGO® can host the REST endpoint and perform the transformation from the LiGO® output to JSON.
With LiGO® ACCESS API, Users can also populate data within Cityworks such as Work Orders or Service requests.