Update on Progress July, 2018 DEMSWG: CIM Task Force Update on Progress July, 2018

Goals Common use of CIM that all WECC members can exchange their Power System Models with each other. One “WECC CIM” model to conform to. Provide efficiencies in modeling maintenance. Outage Management is using the entity’s exact model (no interpretation loss). Minimize the amount work for exporting and importing. Power System Models include the entity’s network model in CIM format and the associated ICCP SCADA objects that, at a minimum, is sufficient to run a real-time assessment.

Both would have the exact same ID though (mRID) Both would have the exact same ID though (mRID). There is only one substation object but it has multiple names, one given to it by the AZPS and the other by SRP. A closer reading of the UML and considering what is done in practice, the NameType is used to identify the name of the IT System where this name is used, not used to describe the type of object name. Type of object is defined elsewhere in the model. Therefore, you wouldn’t use NameType=”Substation”. You would use NameType=”SCADA-EMS”. Strictly speaking, the NameTypeAuthority can chose any names they want.

Answers to previous discussion points… Some classes of the CPSM are not utilized by all entities and in some cases, utilized differently. For example: SubGeographicalRegion is used by CAISO to represent each entity within the ISO and APS uses it for identifying different zones within its footprint. Naming Conventions and Limitations Pub/Sub? Central Administration much like the Westwide model? It is completely up to the importing utility. It may make most sense to leave alone since it is not your footprint and makes for doing a delta easier if you keep the exporting entities format. However, again it is completely up to the importer. (example: CAISO would replace value with an import script). With the advent of CIM 15 and the Name/NameType/NameAuthority class relationships, this isn’t a limitation anymore. Proof of concept will test this out. 3. And 4. Not necessary but could be useful and more efficient if everyone publishes each time there is an update. Much like TOP-003 Directory hosted at PEAK. Only one export needed and each is subscribed with an alert to each entity they typically need updates from.

Proof of Concept Right now, APS, SRP, and CAISO are working together on CIM exports for purpose of EIM. However, SRP is exporting CIM 10 due to limitations of EIM export capability by OSI (they are updating CIM15 now). APS & SRP could be POC with each other outside of EIM. Can both exchange CIM 15 natively. Have already met to agree on Tie Line authority and IDs. Some things to note: SRP had to identify beyond “SRP” owned modeling to include the additional stations where had ties with APS where APS was owner of tie. Model exports properly. Each entity has to replace the IDs with the other entity’s IDs if they did not own the tie. Helps with future mergers and performing a delta for incremental updates.