1. MIT Communication & Risk Management Language Workshop - Middleware Improved Technology for Interdependent Critical Infrastructures 8 February 2007, Rome Felix Flentge

2. IRRIIS MIT Communication Need of Communication Concepts for Communication Example Internal Processes Risk Management Language Summary

3. IRRIIS Distribution Systems Clients Transmission System Generators Qualified Clients IPP Trading Companies Market Operator System Operator Private Communications Network Public Communications Network Source: Antoni Diu Masferrer, Aplicaciones en Informática Avanzada, Spain Example: Dependency of Electricity on Telecommunication

4. IRRIIS Distribution Systems Clients Transmission System Generators Qualified Clients IPP Trading Companies Market Operator System Operator Private Communications Network Public Communications Network Source: Antoni Diu Masferrer, Aplicaciones en Informática Avanzada, Spain Example: Dependency of Electricity on Telecommunication Communication within the electric power infrastructure Even more communication ???

5. IRRIIS Need for Communication Recommendation #4 „Information Sharing“: Member States and the Private Sector should establish formal means for sharing information that can improve the protection and rapid restoration of infrastructure critical to the reliability of communications within and throughout Europe. Source: Study on Availability and Robustness of Electronic Communications Infrastructures  MIT Communication as bottom up approach for information sharing.

6. IRRIIS Need for Communication Within the same sector communication between different actors exist (e.g. UCTE information highway) Usually, between different sectors even between dependent actors no (formal) communication exists

7. IRRIIS First Use Cases Distribution System Operator  Qualified Client Electricity – Information about a possible outage – Negotiation about time or place Mobile or Fixed Telecommunication  Qualified Client Telecommunication – Information about a degradation of a telecommunication service ???

8. IRRIIS Concepts: Implementation – Service - Effect Effect Service Implement. Infrastructure  physical  cyber  human / management Products For example:  delivery of electricity  provision of communication Effects (internal)  monetary  image  …  Complex Structures  Confidential Information  Modells are available  Manageable Number  Public Information  Definitions are available  Measures / Models exist  Confidential Information  Procedures are available

9. IRRIIS Concepts: Implementation – Service - Effect Effect Service Implement. Infrastructure  physical  cyber  human / management Products For example:  delivery of electricity  provision of communication Effects (internal)  monetary  image  … Effect Service Implement. Infrastructure  physical  cyber  human / management Products For example:  delivery of electricity  provision of communication Effects (internal)  monetary  image  … Provision of a service Service Level Agreement Communication

10. IRRIIS Risk Management Language Different sectors speak different languages  Common language is needed IEC 61850 ???

11. IRRIIS Risk Management Language XML based Extensible, open design Independent from specific ways of communication RML service A, QoS !!!

12. IRRIIS Information & Negotiation Service Provider provides service A RML Service Consumer consume service A internal process risk „50% prob. of failure for A at time X and place Y“ proposal „Preference to have failure at place Z.“ accept „Proposal accepted“ Info Negotiation Info Negotiation

13. IRRIIS Example: DSO – Telco communication DSO Rome  Telco; ServiceInfo Service power supply, 19.00-23.00, Rome West, probability 1.0, inoperability 1.0 The DSO of Rome informs a telecommunication company of a planned outage.

14. IRRIIS Example: DSO – Telco communication Telco  DSO Rome; ServiceNegotiation Proposal 1, priority 1 Suggestion: Service power supply, 19.00-23.00, Rome South, inoperability 1.0 Suggestion: Service power supply, 19.00-23.00, Rome West, inoperability 0 Proposal 2, priority 2 Suggestion: Service power supply, 19.00-21.00, Rome West, inoperability 0 Suggestion: Service power supply, 21.00-01.00, Rome West, inoperability 1

15. IRRIIS Example: DSO – Telco communication DSO Rome  Telco; ServiceNegotiation Proposal 1 reject Proposal 2 accept The DSO accepts to change the time.

16. IRRIIS Example: DSO – Telco communication DSO Rome  Telco; ServiceInfo Service power supply, 21.00-01.00, Rome West, probability 1.0, inoperability 1.0 A new info message with the change time is send.

17. IRRIIS Generation of Info Messages

18. IRRIIS Generation of Negotiation Msg.

19. IRRIIS Responding to Negotiation Msg.

20. IRRIIS Distributed Risk Assesment

21. IRRIIS Structure of an RML Message

22. IRRIIS ServiceInfo Element

23. IRRIIS ServiceNegotiation Element

24. IRRIIS ServiceSubscription Element

25. IRRIIS TCP/IP based XML Encryption XML Signature Service-oriented Architecture for whole MIT system Technical Implementation

26. IRRIIS Summary (Intra-sector) communication between service provider and service consumer Risk Management Language – Information about estimated (future) QoS – Negotiation about (future) QoS – open, extensible design based on XML Integration in company internal (MIT) processes Distributed risk assessment