Lecture 12 System Architectures - KTH · Lecture 12 System Architectures Course map . 24/4/2013! 2!...
Transcript of Lecture 12 System Architectures - KTH · Lecture 12 System Architectures Course map . 24/4/2013! 2!...
24/4/2013
1
Professor Lars Nordström Dept of Industrial Information & Control systems, KTH [email protected]
Lecture 12 System Architectures
Course map
24/4/2013
2
Outline of the lecture
• System Architecture – introduction
- Architecture Models – why? - Architecture Models – what? - SGAM - Smartgrid Reference Architecture Model
• Smartgrid Architecture Example
The Smart grid & its implications
24/4/2013
3
How to know what to build?
Market Model
ICT Architecture
ICT capabilities
”Who” controls what in a distribution system? Voltage? Frequency?
Is there a price for storage? Can production be curtailed? Can the system supply itself? Can the DSO shift load in time?
Is the ICT system architecture distributed? Hierarchical control Peer to Peer? Who owns data?
Is the ICT architecture secure? Is the performance sufficient? Are the measurements of high quality? Can all the systems communicate?
Gridwise Interoperability framework
24/4/2013
4
Outline of the lecture
• System Architecture – introduction
- Architecture Models – why? - Architecture Models – what? - SGAM - Smartgrid Reference Architecture Model
• Smartgrid Architecture Example
When and why to use which model?
24/4/2013
5
How to make things understandable
What is an architecture
24 april 2013 10
• Approach: One bite at a time - Describe parts, build, deploy,
and integrate them
What is the system used for?
How is the system used?
Who interacts with the system?
…
Development of Complex Systems Requires the Ability to Identify Them
24/4/2013
6
ISO/IEC/IEEE 42010
24 april 2013 11
Stakeholder
System-‐of-‐ Interest
Architecture View
Concern
Architecture Viewpoint
Architecture
Architecture Model
governs
exhibits
identifies
frames
expresses has interest in
has
addresses
Model Kind governs
identifies
identifies
Architecture Descrip5on
Architecture “fundamental concepts or
properties of a system in its environment embodied
in its elements, relationships,
and in the principles of its design and evolution”
Conceptual Model for Architecture Descriptions (ISO/IEC/IEEE 42010)
SCADA system With RTUs
Mandate 490 Task to European SDO
• The EC has issued a mandate (M/490) for the standardization of Smart grid functionalities to CEN, CENELEC and ETSI.
• The expected framework will consist of the following deliverables: - A technical reference architecture, which will represent the
functional information data flows between the main domains and integrate many systems and subsystems architectures.
- A set of consistent standards, which will support the information exchange (communication protocols and data models) and the integration of all users into the electric system operation.
- Sustainable standardization processes and collaborative tools to enable stakeholder interactions, to improve the two above and adapt them to new requirements based on gap analysis, while ensuring the fit to high level system constraints such as interoperability, security, and privacy, etc.
24/4/2013
7
What is a reference architecture?
In short: it is the specification of which language you should use to describe the system you are describing.
Example: Reference architecture for for Power systems
A set of symbols
Sort of similar for ICT systems
One line diagram (just one possible form of description)
Rules on how you can combine them
24/4/2013
8
Outline of the lecture
• System Architecture – introduction
- Architecture Models – why? - Architecture Models – what? - SGAM - Smartgrid Reference Architecture Model
• Smartgrid Architecture Example
The context– the Smartgrid Plane
24/4/2013
9
Architecture Domains
Architecture Zones
Zone
24/4/2013
10
Condensed model in the SGAM
Complete Reference architecture
24/4/2013
11
System Development
24 april 2013 21
SGAM: A Viewpoint on the System “Smart Grid“
Process Field
Station Operation
Enterprise Market
Zones
Protocol Protocol
Data Model Data Model
Generation Transmission
Distribution DER
Customer Premise Domains
Business Objectives ���Polit. / Regulat.. Framework
Component Layer
Communication Layer
Information Layer
Function Layer
Business Layer
Inte
rope
rabi
lity
Dim
ensi
on
Architecture Framework Stakeholder
Concern
Architecture Viewpoint
identifies has
identifies
frames
Business Layer
24/4/2013
12
Function layer
Information Layer
24/4/2013
13
Communication Layer
Component Layer
24/4/2013
14
Step 1 – Develop Physical setup
Describe the components from the Use Case Diagram as tangible objects
Step 2 – Develop Business layer
Useful to de-lineate the scope of the use case
24/4/2013
15
Step 3 – Develop the functional layer
Assign the functions to the components. Not necessarily one-to-one.
Step 4 – Develop the Information layer
Identify (from the Use case description) which data is to be exchanged between which components & function.
24/4/2013
16
Step 5 – determine datamodels to use
Based on type of information exchanged, determine suitable standardised datamodel
Step 6 – Determine communication protocols to use.
Define standard for communication protocol, including physical and link layer protocols to use
24/4/2013
17
The end
• After following the process we should have:
A total of 5 architecture ”drawings” that present different views of the System
Why all this? It hopefully provides good information to make it possible for others to review, find faults and then finally design the actual systems
Outline of the lecture
• System Architecture – introduction
- Architecture Models – why? - Architecture Models – what? - SGAM - Smartgrid Reference Architecture Model
• Smartgrid Architecture Example
- You are encouraged, but not mandated to use the SGAM to describe the systems you design in Part 2 of the Project Assignment.