Enterprise Integration

CIM Users Group Meeting

Austin, Texas

October 25, 2007

Jovita WilliamsOncor Electric DeliveryJovita.Williams@oncor.com

Greg RobinsonXtensible Solutionsgrobinson@xtensible.net

2

Topics• Current State

• Future State Goals

• First Project ‘Up to Bat’ - SmartGrid

• 3 Key Concepts for Making Goals Achievable

• First 3 Steps Underway

- Today

- Future State

3

Application Portfolio: Present State Assessment

• Electric Delivery has over 175 applications in its portfolio

• Many applications used by different internal departments cater to similar needs

• Same Commercial Off the Shelf (COTS) products are used differently by various departments

• Sub optimized processes developed by individual departments

• Separate solutions and implementations covering similar processes

- E.g. Multiple Mapping solutions / home grown mapping solutions

• Complex network of interfaces

• Inconsistent and often inaccessible reports

• Major integration and maintenance issues

4

Our Goal

5

How do we move ahead?• Technology Guiding Principles:

• Business Alignment

• Technology Governance

• Application Portfolio Management

• Utility Standards Adoption

• Industry Standards Adherence

• Technology Strategic Plan:• Multi-year view

• Charts course for all upgrades, enhancements, replacements

SmartGrid is the first project to apply this set of principals…

6

Future IT Systems

ERCOT Market

ERCOT Market

Data Data

AMR System 1 AMR System 2 Existing AMR System

Future SystemsMeter Data Management System

Power Information Platform by eMeter (PIPe)

Cellular IDR, POTS IDR,

MV90

MeterData

Portal

Enterprise Service Bus

7

SmartGrid VisionApplications

OMS/DMS/SCADA/MWMBPL Smart Grid

EMS/SCADA

Communications InfrastructureBPL – Fiber Network

PLC, Cellular, Paging and Satellite

Control & TelemetryAMi (PLC and BPL)

Substation MonitoringDistribution Automation

8

SmartGrid Functional Objectives1. Replace aging mobile workforce management (MWM) system that is

no longer supported by vendors

2. Implement a fully integrated OMS/DMS/MWM system suite replacing a “legacy” home-grown Outage Management System (OMS) and several unrelated distribution control systems

3. Leverage the “new” data available through AMIS into system operations activities

4. Utilize “intelligent” field mounted equipment in true “smart grid”activities

5. Provide near real-time data and control to distribution operations control centers

6. Improve reliability to customers while controlling costs

9

1. Utilize “completely off the shelf” (COTS) applications wherever possible and work with vendors to update/improve applications

2. Implement utility standards, such as those based on the CIM, to allow improved interoperability between various applications

3. Leverage the “new” technologies available for enterprise application integration (EAI) by using a state-of-the-art middlewaresuite for new application implementations

4. Utilize service oriented architecture (SOA) concepts to keep access to vital information open and easily accessed by any application

5. Provide near real-time data and value-added information to all market participants (customers, retail electric providers, ERCOT, and other participants) via Web Portals and specialized information transfers

SmartGrid Interoperability Objectives

10

Enterprise integration will be the key!

• Integrates disparate systems

• Enables Business Process Management across systems

• Presents a real-time view of data

• Creates business process flexibility by assembling components

• Speeds development through improved tools and reuse

• Supports both internal processes and “business to business”activities

Portal SOAPService Request(e.g. J2EE, .NET)

B2BInteractions

Data

ExistingApplications

New Service Logic

ServiceFlow

11

This is Not a Good Practice For Wires Integration; It’s Not Good For Data Integration Either!

Wires Integration Anarchy!

12

Implementing Typical Approaches on New Technology Will Result in the Same Old Problems

Integration anarchy is a chaos of:(1) duplicated logic, (2) duplicated data, (3) duplicated effort,(4) newly acquired integration difficulties,(5) lack of ability to easily create new application functionality from

services, and(6) lack of ability to support business processes with applications

A ‘Typical’ ESB

OMS CISGIS

AMRDMSWMS

Data Integration Anarchy!

13

Key Concept: Incremental Integration - in Step With Business Needs

Semantically Consistent ESB

OMSCIS

GIS

AMR

DMS

WMS

TTOR

IEC 61968 IRM Interface

CIS OMS DMS

TT

OR

Trouble Ticket

Outage Record

Information Flow Design

14

Key Concept:Replace Large Monolithic Applications

‘a Chunk at a Time’

WMSM

aint

enan

ce &

Insp

ectio

n

Con

stru

ctio

n

Wor

kS

ched

ulin

g

Des

ign

Fiel

dR

ecor

ding

Other AppsOther Apps

Other AppsMDI/CIM Messages

15

Today: Service Work

16

Step 1: Service Work with new Mobile Workforce Management (MWM) System

ESB (Tibco)

Intergraph MWM(New)

CIS(Legacy)

PIPe (MDM)

FMIS

TIBCO ESB

MDSI MWM(Legacy)

Manual

MQ

AMRAMRP

olar

is

Vendor API

MDI/CIM Interface

MDI/CIM InterfaceMDI/CIM Interface

Vendor API

CD

W

ERCOT

TX Set EDI TX Set EDI

17

Today: Outage Management

18

Step 2: Outage Management System (OMS) Replacement

ESB (Tibco)

OMS(New)

CIS

PIPe (MDM)

IVR

FMIS

TIBCO ESB (RV)

Manual

MQ

AMRAMR

Vendor API

MDI/CIM Interface

MDI/CIM InterfaceMDI/CIM Interface MDI/CIM Interface

Vendor API

MDI/CIM Interface

MWM(New)

Vendor API

MDI/CIM Interface

DIS(Legacy)

DNA/DSCADA(New)

Vendor API

MDI/CIM Interface

19

Today: Data Management• With Vision and Guiding Principals, Oncor Electric Delivery has

declared its direction for true ‘enterprise’ integration

• However, specificity is currently at too high of a level and insufficient to realize the business value sought.

• Need more detailed processes to guide projects to achieve concrete deliverables in a manner that fits appropriately into the enterprise context

• IEC standards provide a good ‘jump start’ – but there are many integration matters that need to be specified as part of ESB services:

-E.g., Data management that governs how data is managed through it’s life-cycle (mastership, synchronization, transaction mgmt., persistence, etc.)

• These issue are being addressed in an overall Enterprise Information Management (EIM) program.

20

Enterprise Information Management (EIM)

Gartner’s definition of EIM: • An organizational commitment to structure, secure and improve the accuracy and integrity of information assets,

• to solve semantic inconsistencies across all boundaries,

• and support the technical, operational and business objectives within the organization's enterprise architecture strategy.

• A commitment to EIM is recognition that information in the enterprise is as important as process (application development) and infrastructure (technology)

21

Key Concept:Leveraging the CIM in an EIM Context

Enterprise Integration Platforms

Application Information

Process Integration

Business Intelligence

BPM/Workflow

EnterpriseSemantic

Model

EnterpriseSemantic

Model

Open Standards

ApplicationsMetadata

Bus

ines

sD

efin

ition

s

22

EIM Vision & Strategy EIM Governance EIM Core

Processes EIM Organization EIM Infrastructure

Enterprise Vision & Strategy

Enterprise Architecture

Enterprise Business & IT Core Processes

Enterprise Business & IT Organizations

Enterprise Infrastructure

Vision

Mission

Strategy

Goals & Objectives

Value Propositions

Sponsorship

Stewardship

Policies, Principles &

Tenets

Alignment

Structure

CSFs & KPIs

Structure (Virtual,

Hybrid……)

Roles & Responsibilities

Functional Services

Business Value and Relationship

Management

Information Architecture

Blueprint Management

Technologies(DBMS, Content Mgmt, ETL, EAI,

EII, Data Modeling, BI/DW, Collaboration…..)

Knowledgebase and Repositories

Standards & Best Practices

Data Quality

Data Integrity

Data Security & Protection

Data Lifecycle Management

Data Movement

Semantics Management

Database ManagementMaster Data ManagementInformation

ServicesServices &

Support

Step 3: Building the EIM Roadmap

23

Questions