16 December 2004

1
16 December 2004
2
Objectives

• Agree upon methodology and planning first work
  packages
• Find out what tools and templates can be used
• Prepare kick off meeting 2 February 2005
• Sub objectives
• Work packages use same terminology
• Work done for one work package be used at a
  maximum at another work package

3
Agenda

• Overview of the starting points for the
  definition of the methodology (milestones and
  deadlines)
• Brief overview of how the work packages interact
  (Oene Kerstjens)
• Presentation ideas on methodology and planning of
  WP1 and WP2 (Francois Malbrunot and Volker
  Vierroth)
• Discussion
• Presentation ideas for templates, tools and
  exercises to make for WP1 and WP2 (Francois
  Malbrunot and Volker Vierroth)
• Discussion
• Kick off meeting, AOB and conclusions

4
Proposal to proceed today

• Check starting points work packages,
  deliverables, milestones and deadlines as in the
  Part B (see hard copy)
• Refresh on relations between first work packages
  (brief presentation)
• Discuss methodology and planning for WP1 and WP2
  in terms of key exercises that the consortium has
  to carry out and create list of activities
• Start creating the template and tools for
  implementation of the methodology above by
  filling up an almost empty deliverable template
• at 15h discuss an agenda for the kick off and
  identify what we need to prepare

5
Preparing kick off

• - Introduction and RCI vision (OK make also clear
  relation to other projects like CESARE and GST)
• - Objectives and approach ? overall methodology,
  VV
• Work package planning -? put outcome of 16
  december meeting into the RCI template and show
  this to the people
• Committing persons to tasks in addition to
  company commitment? prepare by having proposal
  for meeting dates and list with people who should
  attend
• - Management issues (management reports, audits,
  travel refunding, etc, )
• - AOB and conclusions ? next meetings (work
  shops date and audience needed)

6
Actions

• Update template and current presentation Oene
  Kerstjens, asap
• Circulate for work package presentations Oene
  Kerstjens, asap
• Investigate ftp server and version control (VV
  could help)
• Investigate if ERTICO can organise the
  hotel/restaurants
• Use agreed template to put in the key activities
  for the work packages that we agreed upon and
  send to ERTICO TSI and ASFA 14 January 2005
• Prepare and send to ERTICO presentation for work
  package desxcription for kick off, TSI and ASFA
  14 January 2005
• Prepare presentation send to ERTICO for overall
  methodology desxcription for kick off, TSI, 21
  January 2005
• ERTICO circulate to appropriate people when
  available

7
Scope

• To specify and implement the RCI prototype that
  can operate in any of the existing RCI road
  charging environments
• Technical validation of 2 prototypes (among
  others the RCI OBU produces the correct data for
  charging )
• But also operational the validation that the
  system could be used in the real world of
  existing systems

8
WP1 methodology, task 1.1

• Functional decomposition and derive on this basis
  the requirements
• Sub functions description (for example for the
  function collecting road use charging data
  measurement of distance, time and segments)
• Analyse existing RCI systems and previous related
  work to find how the sub functions are realised
• Deriving requirements (interoperability
  functional and for OBU)
• Architectural decomposition (in parallel with the
  functional dec.)
• definition of entities and roles
• Analyse existing RCI systems and previous related
  work to find how the sub functions are realised
• Deriving requirments form the entities
• Note type approval in the RCI context means a
  statement that the RCI OBU is a valid alternative
  but NOT that it is compliant to all kinds of
  regulation, type approval therefore means
  compliance to technical specifications

9
WP1 methodology, task 1.2

• Derive generic requirements (availability,
  performance, costs.)
• Proposal drafted by ASFA and perhaps a few others
• Proposal circulated to operators inside RCI for
  suggestions/improvements
• ??Collect additional requirements coming form the
  business aspects deliverable (operational costs,
  maintenance, hardware, costs for registration,
  for certification, etc..)

10
WP1 methodology, task 1.3

• Develop procedural interoperability use cases
• Define step-wise the different use cases (but
  only those that are within the scope as defined)
• Validate and identify additional requirements
  that followed form 1.1 by link this task by
  making an iteration

11
WP1 methodology, task 1.4

• Involve the new partners (they have at about 5
  PMs) for validation of the requirements
• Workshop validation of the requirements

12
WP2 methodology

• Define the exact scope of the work package
• Architectural decomposition entities and roles
• definition of entities and roles (who owns the
  customer, who brands, etc..)
• Deriving requirments form the entities and roles
• Identify existing business contexts (motivations)
  and relate them to the interoperability issue
• Define magnitude of order numbers for volumes for
  use, if opportune categorise for different user
  groups
• Identify high level valid business strategy of
  main stakeholders for interoperability and do
  this for each of the key stakeholder categories
• Note among others make use of the MEDIA project,
  PISTA, CESARE II but extend with view of
  non-operator stakeholders
• Note RAPP could use some resources from WP1 for
  WP2 to bridge with MEDIA
• Note deadline for final deliverable preferably
  to month 10