Update to UCA-EIMon

California ISO Enterprise Model Management System Project

Brian JacobsenEnterprise Model Management

California ISO

June 2012 OpenSG User Group

The Case for Change

• No enterprise-wide model strategy leads to– Fragmented repositories with common elements– Processes to merge models in run-time applications– Heavy burden on integration layer– Inherent risks of data mismatch errors in applications– Data duplication– Recreation of composite model (or reversion) is very difficult– Variations in semantics and overhead to ensure consistency– Excessive effort to ensure consistency when expanding models– Minimizing IT Project costs leads to inefficient enterprise model– Limited utilization of modeling standard (CIM)

Page 2

CAISO EMM Roadmap• Develop CAISO Enterprise UML Model

(CEM)– Establish UML maintenance

strategy• Static model management

– Centralized reference model (instance) management

– Phased migration of legacy systems

– Time based model– Fundamental business process

changes• Dynamic model management

– Initially, CEM transformations at integration layer

– Roadmap for full CIM interoperability through SOA

UCA EIM Vision• Standardized information around the

utility boundary• Changes to information and

technology • End-to-End information management

• Single version of the truth• A frame work to deal with many

system sharing information• Framework & Methodology to handle

big data• Unified model will not support this.• Leveraging more than one model

loosely (bridging models)• Standards to support integration

• Operations & Analytics • BI (historic data)

• Operational BI (near real-time)]

CAISO EMM Road Map – Step OneEnterprise Semantic Model (CEM)

• Consistent information representation across business domains in stand-alone semantic model to be used as enterprise logical data model

• Minimize semantic conflicts by referencing industry standard (CIM 15)– Upgrade from legacy CIM v10 based model

• Strategy for maintenance and standards upgrade– Create autonomy for information model growth

• Proceduralize Enterprise Model Strategy to enforce (internally) consistent use of CEM

• SOA integration to standardize how data is exchanged

Page 5

CAISO EMM Road Map – Step TwoConsolidate Static Model Maintenance

• Roadmap for migrating legacy models and repositories– Consolidation and centralization– Significant business process and continuity planning

• Synchronize with legacy technology roadmaps• Significant corporate investment

– Requires high-level, long term management support– Multi-year investment– Measuring tangible and abstract ROI

Page 6

CAISO EMM Road MapAchievements and Current Activities

• Four-phase EMM roadmap approved by officers and Board

• CEM v1.0 is developed– Network model + commercial reference data– CIM v.15 (61968 + 62325), plus extensions

• Migration to EA for UML maintenance tool set• EMM System Phase 1 in development

– Proof of concept– Upgrade network model deployment to market systems

• Implanting EMM strategy in IT development processes

Page 7

CAISO EMM Road MapNext Steps

• Complete EMMS Phase 1• Get EMMS Phase 2 scope ratified and project charter

• Expand on static model maintenance and validation• First phase of static model SOA integration roadmap

• Continue IT process improvements for EMM• Migrate dynamic model (transactional data models) to

CEM in EA• Initially in legacy CIM 10 model• Roadmap for upgrade to CIM 15 (looking for catalyst projects)

• Planning for EMMS Phase 3 : Migration of network Model to EMMS

Page 8

Page 9