SHF Project meeting 1718th March 2005 Introduction Hugues Vinet

1
SHF Project meeting17-18th March
2005Introduction Hugues Vinet
2
Main meeting objectives

• Show/ discuss M4 deliverables - First prototypes
• Welcome Sony EuTEC and re-start collective work
  on Hi-fi system
• Start Reference specification / integration
  process
• define method, organisation and schedule
• start process with technical exchanges between
  partners
• Meet EU/ Review meeting requirements
• finalize proposal to be issued by 25th March for
• new versions of deliverables
• date of new review meeting
• finalize new Technical Annex by 25th March
• final schedule, deliverables, MM and budget
  reallocations, standardization efforts, links
  with SIMAC
• Discuss Consortium Agreement amendment process

3
Meeting schedule

• Thursday 17th
• Morning
• Introduction to Sony EuTEC
• M4 and other demos
• discussion
• Lunch at  Le Petit Basque  restaurant
• Afternoon
• Method for integration Authoring, Hi-fi system
• Technical meetings
• Friday 18th
• Morning
• synthesis of done work and workplan according to
  new planning
• Technical meetings
• Invited lunch at  La table des gourmets 
  restaurant
• Afternoon
• Technical meetings
• Project management committee synthesis and
  decisions on all points

4
New project planning proposal
5
Project risk management

• Major risk of project suspension avoided
  (replacement of Sony NCSE)
• Main risks (short term next 6 months period)
• unsufficient quality of deliverables
• A2MR effort on new deliverables (M4-February and
  M6-September)
• failure of integration process
• A2MR specific effort expected from all partners,
  around EuTEC and NI, with priority on
  Specification process above all others
• A2MR strict respect of deadlines
• Consequences for short-term management
• A2MR strict monitoring and publishing of
  deliveries (time, quality)
• A2MR importance of quarterly reports
• A2MR financial counterpart proved successful
  with Sony NCSE
• Main risks (longer term)
• uncompletion of application development process
• A2MR define a clear planning for each app. and
  monitor its execution (reference spec)
• A2MR define explicit partner roles for
  development (reference spec)
• market inadequacy
• A2MR involve concerned business units as soon as
  possible
• A2MR anticipate the preparation of the final
  user feedback process
• A2MR implement result-oriented dissemination in
  order to diversify marketing applications and
  maximize RD output.

6
(No Transcript)