1. WP1 INERTIA Framework Requirements, Specifications and Architecture
Task 1.4 – Architectural Design - Functional and Technical Specifications
CERTH/ITI

2. MS3 “INERTIA Provisional Architecture available”
T1.4 Overview
Task 1.4 – “Architectural Design - Functional and Technical Specifications”
Involved Partners:
CERTH/ITI 5
ENG 4
TECHALIA 2
CNet
ALMENDE
TUK
HYPERTECH
PPC 1
ENELSI
We are here
Deliverable
D1.3 “INERTIA Framework Architecture including functional elements and technical specifications”
(Report, Restricted, M12 September 2013)
Milestone
MS3 “INERTIA Provisional
Architecture available”
(M12 September 2013)

3. Today’s meeting
CERTH will shortly present efforts achieved so far towards :
Defining INERTIA overall architectural and architectural elements
Preparing documentation needed for deliverable D1.3
Go through each deliverable chapter
Discuss any architectural issues still pending
Try to close any open issues and come to decisions
Define and agree on contributions expected by each partner
Define a time-planning for document completion + revision

4. Defining INERTIA Architecture
During the last 4 months (after Bilbao Meeting) great progress has been achieved towards defining INERTIA Architecture & respective architectural elements
Decided on conceptual architecture and local & global control hub distribution
Process of Holistic Flexibility calculation within the respective agents of the Local Control Hub were analysed
Multi-Agent system architecture was introduced by ALMENDE
Decided on final list of components and responsibilities per partner
Aggregator control hub was thoroughly analysed between responsible partners

5. Deliverable Sections: 1.Introduction – 2.Methodology
Nearly finalised
Some feedback already received by partners
CERTH with revise this section towards its completion

6. Deliverable Sections: 3.Conceptual Architecture
Almost complete
Figure refined (next slide)
CERTH will further refine the figure
to reflect some changes in component naming
Aggregator Hub MAS and other components positioning
version will be circulated for feedback/comments
CERTH will specify description of major conceptual elements that need refinement by corresponding partners

7. Deliverable Sections: 3.Conceptual Architecture

8. Deliverable Sections: 4. Structural View – Component Diagrams
Mostly covered – some refinements pending
Initial description of all components have already been provided
ALL PARTNERS - Changes may be needed following discussions during last telco (3 Sep) on communication between components, use of IAM etc.
Diagrams harmonization based on Visio sample from CERTH
Still waiting for final list of Requirements (deliverable D1.2) to be addressed by each component

9. Deliverable Sections: 4. Structural View – Component Diagrams
Meeting discussion:
Local Control Hub - Multi-Agent System Topology as provided by ALMENDE through 2 different diagrams:
a component diagram, highlighting dependencies between components
a diagram showing agent topology and attached components
Positioning of Event Handler (in Middleware or represented by an agent?)
Other interfacing issues need to be discussed ? (eg. IAM use for exchange of information)

10. Deliverable Sections: 4.Structural View – Component Diagrams
Local Control Hub /
MAS Component &
Agent topology Diagram

11. Deliverable Sections: 5. Development View
Still missing contributions
ALL PARTNERS –revise section and identify inputs needed for each responsible components
ALL PARTNERS – Specify use of Existing Software / Platforms etc.
ALMENDE proposed to provide an overview section here, giving a high-level overview of major principles of MAS architecture
CERTH will refine introductory sections

12. Deliverable Sections: 6. Deployment View
Still missing contributions
ALMENDE has provided initial contribution on MAS deployment
CERTH will coordinate a holistic deployment approach, preceding separate deployment sections
ALL PARTNERS – revise section and identify inputs needed for each responsible components
CERTH will refine introductory sections

13. Deliverable Sections: 7. Dynamic View Use Cases/Sequence Diagrams
Needs revision on some parts – mainly to commonly agree on the information flow between components
Contributions and feedback is needed by all partners, mainly focusing on the correct positioning and information exchange with other component
Still waiting for final list of User & Requirements definition (deliverable D1.2) to be included in the corresponding UCs
CERTH and HYPERTECH will further refine section and deliver most of the work

14. Deliverable Sections: 7. Dynamic View – Use Cases/Sequence Diagrams
Meeting discussion:
Use Case Real time Control Operation of each Local Hub
Covers most of Local Hub’s real-time operation – decision making from Holistic Flexibility component after consulting all LCH components
Needs to be checked in parallel with agent-approach provided by ALMENDE
As already identified by TECNALIA, missing DER Modeling interactions

15. Deliverable Sections: 7. Dynamic View – Use Cases/Sequence Diagrams

16. Deliverable Sections: 7. Dynamic View – Use Cases/Sequence Diagrams

17. Deliverable Sections: 8. Detailed Specification
8.Core Architectural Elements Detailed Specification
Still missing contributions from most partners
CERTH and TECNALIA has already added input in this section
Input / Output sections need to be tranferred here from component view
ALL PARTNERS need to add relevant information here
CERTH will revise the introductory paragraphs

18. T1.4 Next Steps Planning for next efforts
ALL PARTNERS need to provide contributions pending, as already identified one week after the meeting (by 18/9)
Plan a first telco ~ 19-20/9, to update status on deliverable work
CERTH will provide a refined – close to final version by 23/9, including contributions received and work addressed to CERTH
Organise more telcos (as needed) to quickly decide and forward any issues that may arise
Provide final document on time for Peer Review (as decided based on overall deliverable planning)