CIM for Environmental Data

1. CIM for Environmental Data Australian CIMug Meeting February, 2014 Henry Dotson, James Horstman - SCE Pat Brown – EPRI Alan McMorran – Open Grid Systems

2. The Storyof CIM for Environmental Data There’s no Weather model in CIM… Dave had an idea Jim had a problem Let’s do a project!!

3. The Storyof CIM for Environmental Data Jim & Dave hired Alan … and drafted Henry & Pat

4. The Storyof CIM for Environmental Data They: • Gathered requirements • Documented use cases • Designed a model • Tested a prototype service Alan & Henry & Jim & Pat worked.

5. The Storyof CIM for Environmental Data … and they thought they were done (at least with the hard work) Nice model.. But what about WXXM? But then Marty said

6. The Storyof CIM for Environmental Data So Alan & Henry & Jim & Pat & Marty worked some more … and the model got better

7. The Storyof CIM for Environmental Data … and they thought they were done (at least with the hard work) Nice model.. Working Group 16 could use it for markets!! All that was left was to submit the model to a CIM IEC Working Group

8. The Storyof CIM for Environmental Data So Alan & Henry & Jim & Pat presented the model to Working Group 16 WG16

9. The Storyof CIM for Environmental Data … and they thought they were done (at least with the hard work) Nice model.. We’d like to implement it But then Todd & Chris said Vendor

10. The Storyof CIM for Environmental Data So Alan & Henry & Jim & Pat & Todd & Chris worked some more (& WG16) … and the model got better

11. The Storyof CIM for Environmental Data … and they thought they were done (at least with the hard work) So WG16 said Nice model.. Let’s propose it as a new CIM standard

12. The Storyof CIM for Environmental Data … and after commenting, the IEC countries voted to approve it Nice model.. Let’s use it!!

13. The Storyof CIM for Environmental Data … and everyone lived happily ever after…

14. The Storyof CIM for Environmental Data ~ The End ~

15. The Storyof CIM for Environmental Data • So, it’s all true so far.. • We’re here: So Alan & Henry & Jim & Pat & Todd & Chris worked some more (& WG16)

16. Extending the CIM for Environmental Data • Background and Drivers • Data Requirements • The Model • Profiles & Transformations • Current Status • Next Steps • Lessons Learned

17. Extending the CIM for Environmental Data • The project • Sponsored by Southern Cal Edison, executed jointly with EPRI and Open Grid Systems • Extend CIM to cover Environmental information • Allow utilities a way to share environmental data (correlated to other utility information) internally between multiple utility applications in a familiar manner • Use case driven (SCE and other utilities)

18. Extending the CIM for Environmental Data • Use of environmental data is pervasive in utilities • Load forecasting • Pre-storm resource deployment • Restoration • Root cause analysis (lightning strikes) • Litigation • Current utility picture • Many sources (some external, some internal) • Procurement silos (multiple providers on department-by-department basis) • Multiple formats • Manual correlation, communication and data entry within the utility

19. Extending the CIM for Environmental Data • Data requirements • Multiple weather domains (atmospheric/geospheric/hydrospheric/space) • Multiple time frames (historic, current, future) • Multiple kinds of data (raw, phenomena) • Need for definition of alerts

20. Model Evolution • The model was designed to enable the representation of raw environmental data and classified phenomena • The current work is extending this into modeling what could be classified as derived data (e.g. warning codes, average temperatures over a period) • There is also requirements to model the parameters and return types of service methods (e.g. requests for derived data)

21. Stateless Transformation • The intent was not to “copy & paste” existing standards into the CIM, this benefits nobody • This does not mean re-inventing the wheel and the aim was to allow bi-directional transformation between CIM for Environmental Data and other standards (e.g. WXXM or TMY3) where they overlap • They were harmonized, not unified • CIM modeling conventions were be used and existing elements re-used and extended where necessary

22. A Single Model • The reason for extending the CIM to cover environmental data is that the CIM is more than just an information model • With the CIM comes processes, tools and formats that are widely used in utilities • SCE wanted all data exchanges within their enterprise to be defined by a single common model • CIM for Environmental Data thus becomes a package within the overall CIM that covers a large number of systems within a utility

23. Extending the CIM for Environmental Data • High Level Data Organization Observations Forecasts Alerts Phenomenon ValueSets Phenomenon ValueSets Analogs CodedValues Analogs CodedValues

24. Environmental Information - Observations & Forecasts • [REVIEW COMPLETE]

25. Environmental Phenomenon • [REVIEW COMPLETE]

26. Environmental ValueSets • [REVIEW COMPLETE]

27. Environmental Alerts [REVIEW COMPLETE] EnvironmentalAlertNWS createdDateTime: 2013-04-13T15:23.000 alertKind: iceStorm alertAbbrText: “…A WINTRY MIX HEADED FOR THE REGION TONIGHT…” alertFullText: “…ICE STORM WARNING IN EFFECT FROM 10 PM THIS EVENING TO 1 PM…” inEffect: 2013-04-13T22:00:000 – 2013-04-14T13:00:000 alertCategoryKind: warning

28. Example

29. Environmental Data Profiles • Two profiles were derived from the CIM for Environmental Data UML model • These profiles were for two interfaces that exchange atmospheric environmental data • Historical weather station data covering the scope of TMY3 • Current atmospheric data readings as defined by METAR, the most popular format in the world for exchanging atmospheric (and hydrospheric for sea temperature) environmental data

30. Historical Station Data • The Station Data covers the data requirements of the National Renewable Energy Laboratory (NREL) TMY3 format • Multiple AtmosphericValueSets for different time periods can be included in a single message • Each message is for a single Monitoring Station with a Geographical Location

31. Current Station Readings • The Station Readings represent the METAR data as an EnvironmentalAlert • It supports multiple observations of atmospheric and hydrospheric value sets from different Monitoring Stations • Different structure from the Historical Station Data due to the different use-cases • Common classes and attributes shared between profiles

32. Data Transformation • To test compatibility and demonstrate harmonisation a transform between METAR data in WXXM and CIM for Environmental Data was developed • The CIM for Environmental Data message was defined with the contextual profile defined in the previous section and realised as an XML Schema file • The WXXM Schema and Sample WXXM message were taken from official WXXM release (1.1).

33. CIM for Environmental Data Message • The CIM for Environmental Data Message was built to deliver an Environmental Alert for Observed weather readings • The CIM for Environmental Data profile and XSD were built and generated by CIMTool • A Model-Driven Transformation then mapped WXXM to CIM for Environmental Data

34. Transform • Majority of elements mapped 1 to 1 • As the CIM uses SI units and WXXM allows multiple units data translation converted to SI units mappingWindSpeedType::windSpeed() : CIM::AtmosphericValue{ switch{ case (self.uom = UomSpeedType::mS){ result.value := self.value;} case (self.uom = UomSpeedType::mph){ result.value := self.value * 0.44704;} case (self.uom = UomSpeedType::kmH){ result.value := self.value * 0.277777778;} case (self.uom = UomSpeedType::kt){ result.value := self.value * 0.514444444;} }; result.type := CIM::AtmosphericValueKind::WindSpeed; } mappingWindDirectionType::windDirection() : CIM::AtmosphericValue{ switch{ case (self.uom = UomAngleType::deg){ result.value := self.value;}; case (self.uom = UomAngleType::rad){ result.value := self.value / (180/PI);}; case (self.uom = UomAngleType::arcminute){result.value := self.value * 0.0166666667;}; case (self.uom = UomAngleType::arcsecond){result.value := self.value * 0.000277777778;}; }; result.type := CIM::AtmosphericValueKind::WindDirection; }

35. Transform • Data sets were split into Atmospheric and Hydrospheric where appropriate mappingAVWX::AerodromeWxType::aerodromeWxValues() : avs : CIM::AtmosphericValueSet, hvs : CIM::HydrosphericValueSet{ result.avs.atmosphericValue += self.airPressure.mappressure(); result.avs.temperatureValue += self.airTemperature.maptemperature(CIM::TemperatureKind::DryBulb); result.avs.temperatureValue += self.dewpointTemperature.maptemperature(CIM::TemperatureKind::DewPoint); result.avs.atmosphericValue += self.verticalVisibility.mapverticalVisibility(); result.avs.atmosphericValue += self.windDirection.mapwindDirection(); result.avs.atmosphericValue += self.windSpeed.mapwindSpeed(); self.seaWx->forEach(sea){ result.hvs.hydrosphericValues += sea.seaWx.surfaceTemperature.mapseaTemperature(); }; } mappingTemperatureType::seaTemperature() : CIM::HydrosphericValue{ switch{ case (self.uom = UomTemperatureType::C){ result.value := self.value}; case (self.uom = UomTemperatureType::K){ result.value := self.value + 273.15}; case (self.uom = UomTemperatureType::F){ result.value := (self.value - 32) * (5/9); }; }; type := CIM::HydrosphericValueKind::Temperature; }

36. Transform • GML Locations were converted to CIM Location + PositionPoint + CoordinateSystemReference • (The WXXM Test Data contained only single point data but multi-point data could also be converted) mappingGML::LocationPropertyType::location() : CIM::Location{ mRID := getUUID(); if (self.abstractGeometry.oclIsKindOf(GML::PointType)) then{ var point := self.abstractGeometry.oclAsType(GML::PointType); result.coordinateSystem := objectCIM::CoordinateSystem{ crsUrn := point.srsName; }; varpt := point.pos; var x := pt.value->at(1); var y := pt.value->at(2); var z := pt.value->at(3); varposPoint := objectCIM::PositionPoint{ xPosition := x.repr(); yPosition := y.repr(); zPosition := z.repr(); }; result.positionPoints += posPoint; }endif; }

38. Transform Summary • There were some small gaps identified in the CIM for Environmental Data as part of this work and so the model was enhanced to reflect this • The majority of data mapped across 1:1 • The whole transform for a METAR (a standard for Meteorological Observation Data for Aviation) message from WXXM to CIM was ~200 lines code

39. Extending the CIM for Environmental Data • Use Cases Under Consideration for Inclusion • Wind Forecast • Solar Forecast • Predict resource requirements for storm (or other event) • Situational Awareness • Customer bill complaint (i.e. it was hot that day, what did you expect when you ran your air conditioner) • Weather Forecast for Load Forecast • Validate Downwind Concentration Compliance Using Historic Weather Conditions • Outage Management use of Lightning Strike Information • Sample Request and Response for Environmental Value Set information • METAR Weather Data Profile • TMY3 Weather Station Data

40. Extending the CIM for Environmental Data • Next steps: • Refine and define some useful profiles [3/1/2014] • Determine what standard number, how it fits in 62325 standards library • Write NWIP (New Work in Progress) • Produce CDV (Committee Draft for Vote) • Using jCleanCIM

41. Extending the CIM for Environmental Data • Lessons learned It only takes… • Persistence, Time, Money, Patience More input really does make the model better… Engaging WG members in a project makes it easier (or possible)… Utility input and vision are vital..

42. Extending the CIM for Environmental Data • To learn more • Visit the CIMug website www.cimug.org Project>CIM for Weather>Public Documents> • Contact Jim Horstmanjames.horstman@sce.com Henry Dotson henry.dotson@sce.com Alan McMorran alan@opengrid.com Pat Brown pbrown@epri.com

43. Extending the CIM for Environmental Data Questions?