Transcript CIM and the D2.24 Information Architecture

CIGRE D2.24 Information Architecture
** where CIM fits in **
Jay Britton
[email protected]
Transition from Applications Era to Systems Era
1975-1990
Business Process Space
A
A
Business Process Space
A
System
System
AAA
AA
A
ra
e
n
A
tio A
a
lic
p
ap
IT Technology Space
System
A
AAA
System
em
st
sy A
ra
e
s
System
AAA
IT Technology Space
Database, disk storage, minicomputers, TCP/IP,
workstations, PCs, unix, ...
Languages, File systems
3
Languages, File systems
3
Transition from Systems Era to Enterprise Era
2005-2020
Business Process Space
AAA
AAA
App
App
App
App
App
App
App
System
App
ra
e
System
ms
e
t
bridge
s
sy A
System
System
ra
e
ise
r
p
ter
n
e
App
System
- II
System
App
e
dg
bri
System
AA A
App
A A
App
bridge
App
System
Enterprise integration layer
A
App
System
Business Process Space
Common Services
IEC Industry Standards
4
IT Technology Space
IT Technology Space
Database, disk storage, minicomputers, TCP/IP,
workstations, PCs, unix, ...
Languages, File systems
Internet, message bus, security, webservices, ...
Database, disk storage, minicomputers, TCP/IP,
workstations, PCs, unix, ...
Languages, File systems
4
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.
5
5
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.
6
6
Scope of Information Architecture
7
7
Static
Model
Analogs
Orchestration
Status
SCADA
Topology
Result
SE
Enterable
SE
Solution
Schedules
Topology
EMS Operator
New Model
SCADA
Initialization
Topology
Initialization
v1
v1
v2
v3
SE
Result
SA
Result
Voltage
Security
SA
Solution
v1
System
Border
v1
v1
State Estimation
Initialization
v6
v2
Security Analysis
Initialization
v3
event
v1
v2
v1
event
event
v3
v11
Data Entry
v2
v2
v1
This is the point in time discussed in the use case.
v4
State Estimation
Periodic
event
v4
v18
v3
Data Entry
v2
State Estimation
Periodic
Security Analysis
Periodic
v18
v5
event
v5
Realtime
Market
event
v4
v5
v2
System
Border
Producer – Consumer Data Exchange
Producer
Consumer
Results
business
code
Results
pds ‘A’
Inputs
business code
code
code
Inputs
pds ‘A’
active output
pds ‘A’
Results
Inputs
pds ‘A’
Results
Inputs
pds ‘A’
shared read access to
last complete version
vk+1
vk
Data Service
9
vk-1
9
PDS Producer
Producer
business
code
e
et
l
e
/d
Results
fi y
od
m
d/
pds ‘A’
d
a
active transaction
...
context ‘X’ / pds ‘A’
k+1
vk+1
k
k-1
Public Data Service
10
vk
vk-1
10
PDS Consumer
PDS Event Notification
Consumer
PDS State View Consumer
Results
business
code
A+
B
event access
Inputs
View A
ew
event queries
business
code
ac
ce
business
code
ss
PDS Event History
Consumer
vi
View B
A update
incremental view update
event history
event notification
A+B init
full view update
view creation
context ‘X’ / pds ‘A’
vk
context ‘X’ / pds ‘B’
k-1
Public Data Service
11
vk
on
s
k
ve
rs
i
vk-1
to
ry
on
s
vk+1
ev
en
th
is
k-1
ve
rs
i
ev
en
th
is
k
to
ry
k+1
vk-1
11
User Interface Architecture
Consoles
Display Configuration
Console Management Standardization:
Required coordination between UI engines to achieve a
practical level of consistency and interoperability.
UI
UI
Engine A
Engine B UI
(Private Application
UI
Displays)
Engine C
Engine X
Display
Display
Display
Editor
Display
Editor
A Editor
B Editor
Cx
Display
Def.
Display
Def.
Display
Format
A BDef.
Display
Def.
Format
Format
Cx
Format
Display
Definition
Standardization:
Data bindings.
Standards for
object placement
aimed at
exchanging
schematic display
layout.
Data Access Standardization:
Standard access methods and standard definitions of public data.
Proprietary
Data
Service
Public
Data
Service
Application A
Proprietary
Data
Service
Public
Data
Service
Application B
Proprietary
Data
Service
Public
Data
Service
Application C
Proprietary
Data
Service
Public
Data
Service
Application x
Business Applications
12
12