Version: 10.1 |
The data model exchange contract between GIS and DMS in a GIS-DMS CIM export is described in a CIM “profile”. Essentially, this is a schema file defining what DMS expects GIS to provide in the export. The following profiles are targeted in the GIS-DMS CIM export:
NA Version
Profile Name
Description
10.0.3
DMSv3.2
The CIM profile supported by Telvent DMS v.3.2
10.0.3
(targeted but not tested)CDPSM 2nd Edition
The CDPSM profile (Common Distribution Power System Model) used in March 2011 CIM interoperability tests
The primary implementation task of a GIS-DMS CIM integration is the mapping of classes and fields from the source GIS model to the target CIM profile. This mapping is defined by the implementer with the “mapping XML”, which is then leveraged by Network Adapter with the MapToCIM pipeline rule. The Network Adapter installation includes the following sample XMLs for mapping GIS to CIM:
File Name
Maps From
Maps To
CIMMapping.Minerville.DMSv3.2.xml
(this is the configured default mapping XML for the CIM export)
ArcGIS Electric Distribution Data Model, also known as “Minerville”
The Telvent DMS v3.2 CIM profile
CIMMapping.GRU.DMSv3.2.xml
Enhanced GRU database used for Telvent testing and demos
The Telvent DMS v3.2 CIM profile
CIMMapping.Minerville.CDPSM2ndEd.xml
(not tested)
ArcGIS Electric Distribution Data Model, also known as “Minerville”
CDPSM 2nd Edition profile
The mapping XML file is made up of operators that take the form of XML tags. These operators generally fall under two categories, CIM operators and mapping operators. Many operators support attributes which provide options for the operators.
Creating a mapping XML requires some expertise. This section describes mapping configuration in greater detail and provides examples with explanation. Also it is recommended that the implementer begin with one of the sample mapping XMLs that is most similar to the GIS-CIM mapping required in an integration project.