1. Model Exchange and Naming TF ENTSO-E Model Exchange Standard –TSO tool users are still using old procedures (editing simple ascii files) to edit models for analytical applications. –Any local editing tool embedded in an app implies export of models through translation into CIM. –Drawback is that such models probably cannot use all of the CIM constructs. –Preferred pattern is that there is a model editing tool that has full CIM functionality, and analytical programs only import. Distribution Model Exchange Issues –First priority is to finish unifying transmission and distribution network modeling. –To look at asset model exchanges, we need more detailed use cases. Object Registry –Reviewed the proposed new use cases. Enterprise data modeling –Good discussion around ideas of data mastership, consolidated modeling, use of object registry and use of transformations in integration. –Next three slides show some of the concepts.

2. How do all these parties acquire a common understanding of widget MRID = X?

3. Situation 1: Each system has its own modeling function and users must enter new widgets into each system manually.

4. Situation 2. A common modeling source is responsible as the master source for widget data. CIM functional equivalent modeling

5. Situation 1: Each system has its own modeling function and users must enter new widgets into each system manually. Object Registry

6. Situation 2. A common modeling source is responsible as the master source for widget data. Object Registry