Towards Standard CIMbased Services

1
Towards Standard CIM-based Services

• MRTU Project Experience at CAISO
• Stipe Fustar
• KEMA Inc.
• MRTU ICC/AI Program Manager

2
MRTU Real-Estate

3
Integration Challenge

• Integrate All Systems and Applications on time
• Ensure that All New Systems and Applications are
  built-to-integrate
• Enforce SOA wherever appropriate
• Meet Performance and Availability Requirements
• Orchestrate Services Effectively

4
Integration Risks

• Vendors Ability to deliver (Siemens, Areva,
  Delinea, Others)
• On time
• Meet business objectives
• Standard-based solutions
• Integration Vendors ability to implement the
  proposed SOA-based architecture
• ICC ability to communicate, educate and enforce
  effectively a coordinated approach based on SOA
• Unclear or Changing Requirements

5
Integration Strategy

• Distribute Activities
• Implement Service-Oriented Architecture (SOA)
• Force all new applications and systems to be
  Integration Ready with service-enabled
  interfaces
• Achieve Loose Coupling
• Data Integration
• Enterprise Information Integration as Objective
• Business Process Orchestration
• Unlocking of rigid processes through run-time
  configuration as much as possible

6
Service-Oriented Architecture The architecture
of interfaces
What is Service? Software component that is a
business-complete logical unit of work,
accessible programmatically from independently
designed contexts via a direct openly documented
interface
Service Interface
Service Implementation
What is SOA? Application software topology
consisting of services and service consumers
(clients) in loosely coupled 1-to-1 relationships
Service Consumer
Interface
Interface proxy
7
Service ImplementationWhat Happens Behind the
Interface
New Service
Wrapped Service
Service Consumer
Composite Service
Serviceinterface
Serviceimplementation
Non-SOAapplications
8
Service InvocationWhat Happens on the Wire?
Alternative Transports
SOAP/XML/JMS
SOAP/XML/SMTP
XML/HTTP
Service Consumer
Service Implementation
SOAP/XML/HTTP
RMI/Remoting
Generator
Shared Memory
JMS/MSMQ/MOM
Interface (WSDL)
9
SOAP Message Payload

• The Common Web Services Architecture supports two
  types of message payload.
• Payload in SOAP Body
• Payload in SOAP Attachment

10
Service Orchestration

• Defining process execution order
• Establishing conditional flow patterns
• Invoke sequence of execution
• Manage message routes
• Manage intervention points

Runtime
Design time
Order
Flow
11
Structuring Integration Effort
ICC will follow RUP
Analysis
Design
Development
Testing
Projects Dev
Projects Design
Pre-FAT
BusinessRequirements
Conceptual Architecture
Unit Test
FAT
Integration ScopePlan Schedule
High-LevelDesign
SAT
EAI Design
EAI Dev
IntegrationTesting
Unit Test
Legacy Design
Legacy Dev
Integration Business Model and Use Cases
Sequence Diagrams Service Definition
End-to-EndTesting
Unit Test
12
Organizing for Integration
Conceptual Architecture
Stage 1 Project and First Production Deployment
Common Practice
Architecture Group
Project Team
Architecture Group
Project Team
Integration Center
Project Team
Integration Center
Architecture Group
Project Team
1. Plan and Justify
13
Integration Competency Center (ICC) Structure
IS Infrastructure
ICC
Testing Team
Technical Team
Program Management Tier
Architecture
Data Integration
Service Management
Integration Implementation
Core Integration Tier
SIBR
IFM/RTN/FNM
DMA
SaMC
MF
Legacy
CRR
Portal
Projects Tier
ICC
14
Service Definition Guidelines

• BPMs - Gathering and reviewing business
  processes, systems, applications, and databases
  information that are involved in the scope of
  services definition.
• Use Cases and Sequence Diagrams -
  Develop/Elaborate To-Be service orchestration
  requirements in the forms of Use Cases and
  Sequence Diagrams.
• CIM/CME Develop common semantic based service
  payload definition in the form of the UML
  diagram. Extend the CIM/CME, where necessary, to
  accommodate CAISO requirements. The extended
  CIM/CME will be the Common Semantic Model for the
  MRTU program.
• Payload - Create CIM base and service payload XML
  Schema files
• Map source and target data format(s) to the
  common semantic model based service payload
  definitions. Document any business rules of
  service payload and mappings
• Payload Template - Verify and validate XML Schema
  files, and create sample XML instance data files
  for reference
• WSDL - Develop WSDL service definition files
  using a WSDL template, and validate WSDL files.
• Document the service definition artifacts in one
  document for a given business integration
  (interface) area.

15
Services Definition and Management Process
Initiate
Model

• Kickoff
• Plan
• Gather
• Review
• Analyze
• Architect
• Fact Modeling

Design
Manage
16
Services Definition and Management Process

• Business Process
• Use Cases
• CIM Extensions
• Class Diagrams
• Sequence Diagrams
• Semantic Mappings and Business Rules

Initiate
Model
Design
Manage
17
Services Definition and Management Process
Initiate

• XML Schema (XSD)
• XML Instance
• WSDL
• Business Rules
• Design Document

Model
Design
Manage
18
Services Definition and Management Process
Initiate
Model
Design

• Release
• Review
• Update
• Approve
• Manage Versions
• Change Request

Manage
19
Frameworks Standards
Initiate
Model
Design
Manage

• CAISO SOA
• Architecture
• SOA Patterns
• SOA Conceptual
• Architecture
• POC

• Service Payload
• Design Methods
• Service Definition
• Methodology
• Service Definition
• Guidelines
• MDI Framework
• WS-I

• Design Tools
• Rational Rose
• MDI Workbench
• XML Suite
• WSDL Tools
• XML Spy
• MindReef SOAPScope

• Configuration
• Management
• Documentum
• VSS or Clear Quest
• UDDI Repository

Industry Standards (XML, XSD, RDF, XSLT, WSDL,
SOAP/HTTP, UDDI, WS-I, CIM/CME, IEC 61967/61968)
20
WSDL Definition Process

• Create Sequence Diagram
• Create WSDL
• Validate WSDL
• Stubs Code generation based on WSDL

Sequence Diagram
WSDL
Validation
Code Generation
21
Services Classification Overview
22
Interface Examples
23
Integration Layer
System A
broadcastMarketMeterData
WS
receiveMarketMeterData
WS
PI
WS
retrieveMarketMeterData
broadcastMarketMeterData
WS
receiveMarketMeterData
WS
BITS
retrieveMarketInterchange
WS
broadcastInvoiceData
WS
receiveInvoiceData
WS
broadcastStatusInvoiceData
WS
WS
broadcastGeneralLedgerData
receiveGeneralLedgerData
WS
MC
24
(No Transcript)
25
(No Transcript)
26
Vision Of Standard Services

• Leverages CIM
• All payloads are forward engineered from CIM
• Standard Services
• WSDL (serves as Interface Definition Language)
• Message payloads
• XML Schema
• XML Templates (message instances send/response)
• Benefits
• True Plug-And-Play functionality
• Publicly Available
• Easy Interoperability Testing
• Can be provided On-line

27
How to validate a WSDL

• WSDL well-formedness validation
• WSDL WS-I compliance validation

28
Validation Tool
29
(No Transcript)
30
Questions?