1) Discussion on the Geographical Location Profile

As per email discussion the Geographical Location Profile differs from the CDPSM profile. The difference is the association between Location and PSR.

IOP participants agree that:

·         the current version that was defined for the IOP 2011 has advantages for data exchanges among TSOs.

·         By agreement the profile uses WGS84 system. The following note is added to the profile "The CoordinateSystem.crsUrn uses WGS84 (latitude, longitude), i.e. urn:ogc:def:uom:EPSG::4236  if not specified otherwise in a network code or another ENTSO-E document defining TSO data exchange processes."

·         the URI of the profile in the file header is changed to: http://entsoe.eu/Secretariat/Geographical/1

2)  Boundary EQ and TP

Add EquipmentContainer, ConnectivityNodeContainer, PowerSystemResourse as abstract classes. Associations Line-ConnectivityNode and Line-SubGeographicalRegion added as in the EQ profile

Add ConnectivityNodeContainer as abstract and ConnectivityNode in the Boundary TP

3) Add ReportingGroup in the TP profile for the association with TopologicalNode

4) Operational state profile

All classes that were added in the SV profile should be deleted.

IOP 2012 will not test operational state profile issue. The profile will wait for WG13 resolution on the operating profile. It is important to exchange operational state related classes separately from EQ. This issue is a major issue that will be addressed together with HVDC package development.

Depending on the discussion during the IOP there might be some follow up testing for HVDC package and operating state profile

Thedecision of removing the Operational State classes from SV for this IOP wastaken by a majority of vendors, due to the lack of time left forimplementation.

5) Issues waiting for WG13

- naming issue

- rdfID issue

- the cardinality between HydroPowerPlant and HydroGeneratingUnit

- there is an issue with Wind modelling and impact on Wires package. Pat will inform Kurt to change.

Other issues:

·         We agreed to have 1h time slot per day during IOP test in order to discuss issues and give recommendation to WG13. In the same time WG13 members will be invited to present current CIM topics and gather input from IOP participants.