For the past few months, we were involved in a subsequent project for one of our long-term customers, where we were extending our Smallworld DH.GIS system for district heating network management. We developed the integration of DH.GIS with IBM’s Maximo – a system used by the company for physical asset management.
The project covered building two separate interfaces – attribute and graphical:
The attribute interface allows exchanging alphanumeric data of asset components, such as:
- Heat Centres with Circulations
- Chambers
- Line Segments
- Heat sources
- Address Data (Cities, Streets, Addresses)
The lifecycle process was established for all integrated objects: the objects are always created in DH.GIS and then transferred to the Maximo system. Technical data attributes are transferred from DH.GIS to Maximo, while operational statuses and ordered power amounts – from Maximo to DH.GIS. Attribute interface is based on SOAP web-services technologies and uses standard Globema’s solutions, which are used in many implementations for our other customers.
The graphical interface transfers geometric data to external PostGIS database – it enables displaying the data on maps embedded in Maximo. Besides of geometry, some alphanumeric attributes are also transferred, which allows customizing/styling objects on the map in the Maximo system. Interface transfers data of following objects:
- Heat Centers
- Chambers
- Line Segments
- Address points (locations)
Data is transferred unidirectional – from DH.GIS to PostGIS database, using dedicated scripts developed in FME. Prepared data is retrieved from PostGIS by ArcGIS Server, which serves it for Maximo Spatial component as WMS service.
