I3 EURONS: a status report to NuPECC

1

• I3 EURONS a status report to NuPECC
• March 2005

2
EURONS - Milestones

• May/June 2002 Information to the European
  nuclear structure community by FINUPHY
  (Frontiers in Nuclear Physics, EU funded project
  within FP5)
• FINUPHY Meeting at Trento (28 Oct.2002) First
  presentation of ideas for JRAs
• FINUPHY Meeting of the Writing Committee at Mainz
  (7 Dec.2002) Selection of JRAs, suggestion of
  fundings for JRAs, TNAs, and Networks
• FINUPHY Meeting of Writing Committee,
  Coordinator, and Managing Institution at the
  occasion of the NuPECC Town Meeting at Darmstadt
  (31 Jan.2003) Status and follow-ups of former
  decisions
• FINUPHY Meeting at Catania (27/28
  Feb.2003) Presentation of status, assignment of
  individual and overall budgets
• 11-14 April submission to the EC, handing in in
  person Concerted action by A. C. Mueller, C.
  Scheidenberger, and Jean Vervier (!)
• End of August 2003 Evaluation Summary Report

3
(No Transcript)
4

• It was difficult to be on the "pole position"
  on the
• reserve list......
• ....and help and lobbying was needed
• - NuPECC meeting at Frascati, 5.-6.Dec. 2003
• - Initiative by Sydney Galès (joined
  action by former NuPECC chairs)
• ....and a positive outcome to enter contract
  negotiations

5
Contract negotiations
Negotiated 48 months to stay in-line with
original timing
Contained "hidden" additional reduction and the
most negative interpretation for EXL and EXOCHAP
6
On the cancellation of EXOCHAP

• May 2004
• action by Muhsin Harakeh and Alex C. Mueller to
  coordinate EXL and EXOCHAP
• June/July 2004
• negotiation with EC to increase budget for
  reasonable execution of EXOCHAP
• appeal to EC infrastructure director R.J.Smits
• (by Walter F. Henning and Alex C. Mueller)
• September 2004
• impossibility to achieve a reasonable budget for
  EXOCHAP
• cancellation of EXOCHAP

7
Start of EURONS

• November 2004
• Contract signature by EC and managing institution
• EURONS starting date 1. Jan. 2005
• December 2004
• Signature with contractors launched
• 80 of first 18-months budget received from EC
• January 2004
• preparation of 1st PCC meeting
• February 2004
• PCC meeting at Madeira (7.-8.Feb.),
  implementation of decisions
• March 2004
• Money transfer to contractors
• Finalization of Consortium Agreement

8
Budgets for Access, Networks, and JRAs

• Networking and integrating activities 1.456 k
• Access to infrastructures 6.590 k
• Joint research activities 6.010 k
• total14.056 k

9
Access facilities within EURONS
Jyväskylä
Groningen
Louvain
Darmstadt
GANIL
CERN
Trento (ECT)
Legnaro
10
JRAs - Overview
11
Networks - Overview
12
Management Issues

• How to manage the consortium?
• Formally consortium agreement
• Practically the following questions should be
  discussed/answered
• How is the consortium organized?
• How can decisions be taken?
• What and how will be monitored?
• How will results be disseminated?

13
How is the consortium organized?

• Activity Coordinators
• PCC
• GA
• Project Coordinator
• Project Controlling

14
What and how will be monitored?

• Standard "tools" of Project Management
• Tasks
• Milestones
• Deliverables
• Implemented in an overall coherent database via
  the "activity sheets" of
• each activity, basically one page, to be updated
  by the activity coodinator
• every 6 month.

15

• Task
• "Active" contribution to the objectives of the
  activity
• Start and end-date (milestone and/or
  deliverable)
• Responsible participant / lead contractor
• A task usually comprises several sub-tasks and
  participants

16
Milestones Milestones are "landmark" results
that are to be achieved during the project and
are crucial to the successful continuation of the
project and also to reliable periodic progress
assessments of the project. For every sub-task
there must be at least one milestone (if
necessary, there might be more than one).
17

• Deliverables
• Deliverables are expected to be realised from a
  particular task. Typical deliverables may include
  
• reports
• guidelines
• protocols
• technical description of prototypes, etc.
• The type and dissemination level of a deliverable
  should be indicated
• report, prototype, demonstrator, other
• confidential, restricted access or public
• For every task there must be at least one
  deliverable(there might be more than one if
  necessary)
• Lead contractor/responsible participant

18
Activity Information Sheet

• Purpose
• Update and "point of reference" at time T0
• Keep track of activities in 6-month intervals
• monitor progress of the work (to some extent)
• monitor financial information (dto.)
• complemented by cost statements
• Evaluate and judge the obtained information
• is the project on target?
• what efforts have been made?
• Last but not least
• facilitate the work of activity coordinators
• review and control work, budget, individual
  costs, etc.

19
Example for monitoring
20

• Essence
• monitoring and controlling
• instead of
• administration, prescriptions, and
  micro-management

21
EURONS

• Summary
• EURONS is an I3 (Access Networking JRAs)
• (successor of FINUPHY)
• The "heart" of EURONS are its worldclass
  facilities
• Goals are
• focus on activities that are in general relevant
  to more than one facility
• reach coherence in ongoing developments, pooling
  and efficient use of resources,
• improve existing infrastructures
• increase access to infrastructures
• foster networking activities
• ensure that the European Nuclear Structure
  Community concentrates on the most prominent
  Joint Research Activities
• preserve and even extend the leading role of
  Europe in nuclear structure physics
• install an efficient project management culture
  in the nuclear physics community, for future
  endeavors