CIGRE D2.24 Information Architecture ** where CIM fits in ** Jay Britton jay.britton@areva-td.com

Transition from Applications Era to Systems Era 1975-1990

Transition from Systems Era to Enterprise Era 2005-2020

Goals of Enterprise Architecture Completeness. All of the enterprise business processes may be automated, whether they cross departments or not. Orderliness. This is enterprise architecture, not a collection of individually unique systems. Component independence. Design minimizes the impact of change outside the component being changed. Re-usability. Avoid duplicate implementation of similar functionality. Openness. The architecture encourages industry standard interoperation between components, increasing the customer’s freedom to use different vendors.

Approach – Service Oriented Architecture Collects successful software architecture patterns for achieving enterprise goals. Tool support evolving around architectural consensus. Information Architecture is a critical item in achieving “arms-length” design of business components: “Canonical Data Model” (CDM) Proxy data service eliminates direct data interaction among components. CIM is our CDM.

Scope of Information Architecture

Producer – Consumer Data Exchange

PDS Producer

PDS Consumer

User Interface Architecture