TELEMAC kickoff meeting

1
WP5 Software IntegrationSimon LambertCCLRC
Rutherford Appleton LaboratoryUK
2
An overview of WP5

• The main goal of WP5 is to make everything work
  together.
• But that is not sufficient in itself.
• There must be some principles behind it, embodied
  in the TELEMAC architecture.
• In particular there must be some commonality
  between sites, and the possibility of
  customisation to future sites.
• Other goals of WP5 are
• To develop user interfaces (Web-based) for the
  local technician and remote expert, and
  communication tools between them.
• To deal with information security issues.

3
An overview of WP5

• Expected results
• System architecture
• Integrated functioning pilot systems
• Customisation principles and methods
• Working environments for local technician and
  remote expert
• Analyses of information security issues and
  recommendations for priorities

4
Barchart for WP5
T0
T06
T012
T018
T024
T030
T036
WP5.1 Information security
(continued)
D5.1b Final report on security issues in the
light of experience in the project
D5.1aInitial report on security issues
WP5.2 Web technologies and user interfaces
No formal deliverable, but assume a final version
of the user interfaces
D5.2a Selection and acquisition of tools for
info. gathering and cooperative working
D5.2bFirst functioning user interfaces
WP5.3 TELEMAC software
D5.3a Initial system architecture and system
management strategies
D5.3b First functioning middleware and
integrated systems on pilot sites
D5.3dCustomisable software and final report on
TELEMAC software
D5.3c Final functioning middleware and
integrated systems on pilot sites
5
Partners in WP5, and their intentions
Effort figures are in person-months red denotes
task leader
My queries are shown in red. They are simply my
lack of understanding, not criticisms!
6
Partners in WP5, and their intentions
7
Partners in WP5, and their intentions
8
Important issues in WP5.1

• Aim of WP5.1 to perform analysis of security
  aspects of TELEMAC software
• At early requirements stage and design stage
• Final review near end of project
• Roadmap
• T06 security analysis of requirements to
  identify hazards
• T012 security analysis of design
• Both these must proceed in parallel with the work
  they analyse.
• T036 final report on how well we did

9
Important issues in WP5.1

• To decide at this meeting
• Unity of approach is CORAS the only approach to
  be taken?
• How will the findings of the analysis influence
  the development?
• To decide soon
• How can analyses be done while the requirements
  and design are being produced? (A boot-strapping
  problem)

10
Important issues in WP5.2

• Aim of WP5.2 to develop user interfaces for the
  local technician and the remote expert, in
  particular facilitating communication between
  them
• Real user needs are important
• Emphasis on taking advantage of existing tools
• Roadmap
• T06 view of requirements for user interfaces
  (NB task does not start until T06 but this is
  important and should be done in the scope of
  WP5.3)
• T018 simple functioning user interfaces
  allowing evaluation with users
• T030 final user interfaces

11
Important issues in WP5.2

• To decide at this meeting
• How do we obtain user needs?
• To decide soon
• What sort of existing tools are we going to
  consider? What is available, what is useful, how
  will it be integrated?
• How far do we want to go with CSCW? My opinion
  not very far

12
Important issues in WP5.3

• Aim of WP5.3 to design a sound software
  architecture, and then to implement it!
• Communications between (very diverse) modules
• Managing of multiple plants
• Customisation issues
• Validation, verification and testing
• Roadmap
• T06 coherent, agreed view of system
  architecture
• T012 dummy integrated system running somewhere
• T018 first functioning integrated system (on
  how many sites?)
• T030 final integrated system installed on all
  sites

13
Important issues in WP5.3

• To decide at this meeting
• What verification, validation and testing do we
  intend to do? (For example, will simulators be
  needed?)
• To what extent have we already got a coherent
  vision of the system architecture?
• To decide soon
• What is the fundamental basis for the system
  architecture? (CORBA, XML, other approaches, )

14
The basis for the TELEMAC architecture
Developed in scope of WP4
15
Interfaces to other WPs

• WP1 Experimentation and validation
• gtgtgt Characteristics of pilot sites
• ltltlt Installation of integrated systems
• WP2 Smart sensor development
• gtgtgt Architectural considerations from sensor
  network
• ltltlt Interfaces and integration of sensors
• WP3 Advanced control
• gtgtgt Architectural considerations from
  models/controllers
• ltltlt Interfaces and integration of
  models/controllers
• WP4 Supervision system
• gtgtgt Architectural considerations from fault
  detection system
• ltltlt Interfaces and integration of fault detection
  system
• gtgtgt Presentation through user interface
• ltltlt Integration of communications into
  data/knowledge base

16
Relation with Latin American partners

• The Latin American partners have no effort in
  WP5.
• But a project policy may be needed to cover
• Input of requirements (e.g. user interfaces)
• Integration of developments by Latin American
  partners into the architecture and final
  customisable software