architectural methodology
DESCRIPTION
Architectural Methodology. IEC WG 19 Meeting Geneva, CH 2012/May/11. Joint NIST-SGAC / EU-M.490 RAWG Efforts. NIST SGAC Conceptual Architecture. Automation Technologies. Business. Input from strategy & context. Automation Architecture. Interaction Architecture. Technical Architecture. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/1.jpg)
IEC WG 19 MeetingGeneva, CH2012/May/11
Architectural Methodology
Joint NIST-SGAC / EU-M.490 RAWG Efforts
![Page 2: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/2.jpg)
NIST SGAC Conceptual Architecture
TechnicalArchitectur
e
Interaction Architectur
e
Automation
Architecture
Business Architectur
e
Business
Input from strategy &
context
Goals/Contextual
Why?
Con
cept
ual
Wha
t?
What services does the business
fulfill
What types of
applications are required
What information
must be exchanged
What ICT services are
required
Automation Technologies
BBusiness
Prelim & A
CIT Sys
TOGAFPhase
CData
![Page 3: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/3.jpg)
Interaction Messaging Artifact
<Business Service Name>
<Input>
<Input>
<Output>
<Output>
<Actor>
<Actor>
Archetypical:• 20 Actors• 25 Message (interaction)• 213 Business Services
![Page 4: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/4.jpg)
Example: Iteration Services for Forecast Intermittent Generation
Forecast Intermittent Generation
Market Manag
er
Measurement
Environment Forecast
Forecast
![Page 5: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/5.jpg)
Suggested Methodology Alignment
Semantics relating to EU M490 RAWG Apply Conceptual Architecture elements to DEWG DER use
cases Integrate EU and DEWG Point-of-View
Use Cases Business Services
Business Processes
(Interactions)
![Page 6: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/6.jpg)
Suggested Methodology Alignment
Cross-Cutting Requirements Define/create fundamental
Solution Blocking Blocks (SBB) Example: adopt/modify
Open Group SOA practices Leverage common Smart
Grid messaging and Cross-cutting requirements as SBB)
Open Group SOA Quality of Service Building Block
![Page 7: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/7.jpg)
Refinement of GWAC stack to SGAM layer associations
Before: Business context associated to Function Layer After: Business context associated to Information Layer Reason:Business context deals with information used in specific context
System A
Business Context
Semantic Understanding
Network Interoperability
Syntactic Interoperability
Basic Connectivity
Business Procedures
Business Objectives
Economic / Regulatory Policy
Function
System B
Business Layer
Function Layer
Information Layer
Communication Layer
Component Layer
![Page 8: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/8.jpg)
Methodology Alignment Activities
Map EU’s Smart Grid Architectural Methodology to NIST Conceptual Architecture & CSWG approach
Interactions,Automation Services Semantics-CDMs
Use Cases, Business Services/Actors
Business goals & requirements
GWAC Stack Based
Syntax &CommunicationsStandards
![Page 9: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/9.jpg)
Ongoing Work Aligning Processes9
What services, standards semantics and interoperability requirements are needed support Smart Grid?
Result• Traceable architecture• Set of architecture
templates identified
GenerationTransmission
DistributionDER
CustomerPremise
Process
Field
Station
Operation
Enterprise
Market
Domains
Zones
Component Layer
Communication Layer
Information Layer
Function Layer
ProtocolProtocol
Data ModelData Model
Outline of Usecase
Subfunctions
Business Layer
Inte
rope
rabi
lity
EG1 Report6 High level services
2. StepCreate ArchitecturesMap onto Architecture Model
Architecture Model
3. StepLocate standardsusage
4. StepIdentify commonstandards First set of standardsSources
Expected outcome
ExistingStandardsCEN, CLC,
ETSI WG-RAArchitecture Model
t.b.d
t.b.d
US Laws & Regulations
TechnicalArchitecture
Interaction Architecture
Automation Architecture
Business Architecture
Business
Input from
strategy &
context
Goals/Contextua
l Why?
Con
cept
ual
Wha
t? What services does the business
fulfill
What types of applications are
required
What information
must be exchanged
What ICT services are
required
Automation Technologies
![Page 10: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/10.jpg)
Ongoing Work Aligning Processes10
Result• Identify “new” gaps• Systematically investigate
need for new standards
How to systematically identify future gaps?
GenerationTransmission
DistributionDER
CustomerPremise
Process
Field
Station
Operation
Enterprise
Market
Domains
Zones
Component Layer
Communication Layer
Information Layer
Function Layer
ProtocolProtocol
Data ModelData Model
Outline of Usecase
Subfunctions
Business Layer
Inte
rope
rabi
lity
Further findings:R&D, Pilots, Implementation
3. StepLocate require-ments for standards
4. StepIdentify new gaps
NEW Gap List(follow process 2. from here)
Source
Expected outcome
t.b.dTarget datefrom 2013
SGAMGeneration Transmission Distribution Customer PremiseDER
Process
Field
Station
Operation
Enterprise
Market
HV MV LV
G H
RTUDER
Controller
HMI HES
DMS Computer
Gateway
CRM Computer
HAN Controller
DataConcentrator
IEC
618
50-7
-420
IEC
618
50-7
-4
CIMIEC 61968-4
GAP
2. StepCreate ArchitecturesMap onto Architecture Model
TechnicalArchitecture
Interaction Architecture
Automation Architecture
Business Architecture
Business
Input from
strategy &
context
Goals/Contextua
l Why?
Con
cept
ual
Wha
t? What services does the business
fulfill
What types of applications are
required
What information
must be exchanged
What ICT services are
required
Automation Technologies
![Page 11: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/11.jpg)
Methodology Results11
Provide base architecture and process to vet future Smart
Grid requirements
Identify gaps in Smart Grid standardization Compare different architectures Identify Cross-cutting requirements Map regional differences Identify new services and interoperability requirements Coordinate work between different TCs and stakeholders
![Page 12: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/12.jpg)
Next steps
Continue on term definitions Continue on SGAM mapping process definition Review of SGAC comments on RAWG document Prioritize crosscutting requirements Refine processes for semantic mapping and business
context mapping Gain more exercise with SGAM mapping (DER
management UC)
![Page 13: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/13.jpg)
Refinement of SGAM mapping process / 1
Required Input UC including actors, roles, functions/services (acc.
definition), sequence diagrams, func. and non-func. requirements
![Page 14: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/14.jpg)
Refinement of SGAM mapping process / 2
Function Layer Develop Function Layer1. Identify functions/services (in the functional layer,
functions and services can be treated in the same manner)
2. Identify interactions of functions/services3. Place functions/services on appropriate domain and
zone
![Page 15: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/15.jpg)
Refinement of SGAM mapping process / 3
Information LayerNeed for business context and canonical data model (CDM) views to cover both instances and data model aspects of information
Develop Business Context Layer1. Place sequence of exchanged information between
functions/services on smart grid plane on appropriate domain and zone
![Page 16: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/16.jpg)
Refinement of SGAM mapping process / 4
Information Layer cont. Develop Canonical Data Model (CDM) Layer1. Identify Canonical Data Model (CDM) that supports
interfaces2. Identify Canonical Data Model (CDM) that supports
functions3. Place CDMs on smart grid plane on appropriate domain
and zone
![Page 17: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/17.jpg)
Refinement of SGAM mapping process / 5
Communication Layer Tbd.
![Page 18: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/18.jpg)
Example Use Case
UC: DMS System controls reactive power of DER unit Business Service: Voltage control
in distribution system Service: RTU Data-acquisition Service: Voltage/Var control Service: Control/Supervision of
DER Service: Audit of control actions
Precondition: Data-acquisition is running Feeder electric models are
current
Sequence of events:
RTU sends measurement to DMS Voltage/Var-Control is triggered by
event Voltage/Var-Control calculates control
value Voltage/Var-Control sends control
value to DMS DMS sends controlable setpoint to DER DER receives setpoint and
acknowledges DER adjusts reactive power injection DMS posts DER control action to audit
of control actions CRM system obtains audit actions
![Page 19: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/19.jpg)
Component Layer
Generation Transmission Distribution Customer PremiseDER
Process
Field
Station
Operation
Enterprise
Market
HV MV LV
G H
RTUDER
Controller
HMI HES
DMS Computer
Gateway
CRM Computer
HAN Controller
DataConcentrator
![Page 20: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/20.jpg)
Business Layer / Function Layer
Generation Transmission Distribution Customer PremiseDER
Process
Field
Station
Operation
Enterprise
Market
HV MV LV
G H
RTUDER
Controller
HMI HES
DMS Computer
Gateway
CRM Computer
HAN Controller
DataConcentrator
Business objectives
Business processes
Economic and regulatory
constraints
Generation Transmission Distribution Customer PremiseDER
Process
Field
Station
Operation
Enterprise
Market
HV MV LV
G H
RTUDER
Controller
HMI HES
DMS Computer
Gateway
CRM Computer
HAN Controller
DataConcentrator
Business Service
„Voltage Control in
Distribution System
RTUSupervision
DER Control &
Supervision
Voltage/VarControl
Audit
![Page 21: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/21.jpg)
Information Layer
Generation Transmission Distribution Customer PremiseDER
Process
Field
Station
Operation
Enterprise
Market
HV MV LV
G H
RTUDER
Controller
HMI HES
DMS Computer
Gateway
CRM Computer
HAN Controller
DataConcentrator
RTUSupervision
DER Control &
Supervision
Voltage/VarControl
Audit
Measurement ControlValue
Ackn
CTRL ACTAckn
Generation Transmission Distribution Customer PremiseDER
Process
Field
Station
Operation
Enterprise
Market
HV MV LV
G H
RTUDER
Controller
HMI HES
DMS Computer
Gateway
CRM Computer
HAN Controller
DataConcentrator
IEC
618
50-7
-420
IEC
618
50-7
-4
CIMIEC 61968-4
Business Context (Message) View Can. Data Model View
![Page 22: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/22.jpg)
Communication Layer
Generation Transmission Distribution Customer PremiseDER
Process
Field
Station
Operation
Enterprise
Market
HV MV LV
G H
RTUDER
Controller
HMI HES
DMS Computer
Gateway
CRM Computer
HAN Controller
DataConcentrator
IEC 61968-100
ESB IEC 61968-100
IEC 61850-8-1GPRS
IEC 61850-8-1IEEE 1901.1
IEC 61850-8-1ADSL
![Page 23: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/23.jpg)
Questions ?
How does this work?
![Page 24: Architectural Methodology](https://reader035.vdocuments.us/reader035/viewer/2022062310/5681638c550346895dd47f5e/html5/thumbnails/24.jpg)
Back-up Slides
STEPHAN AMSBARYDirector, Utility Enterprise Architecture
[email protected]: +1.828.559.1110
FAX: 865.218.89991993 Grants Mountain Rd, Marion, NC, 28752-9513
Electric Research, Engineering, and Consulting