EMRP-template (document) - EMPIR Participant...

EMPIR

Annex I – JRP protocolVersion Date: DD Month YYYY

<JRP Number Short Name>

<Full title>

Start date: 01 Month 201X

Duration: XX months

Coordinator<First name Last name>

<Coordinating organisation short name>

of 24 document.docx

EMPIR

Glossary

of 24 document.docx

EMPIR

ContentsSection A: Key data................................................................................................................................... 4

A1 Project data summary..........................................................................................................................4A2 Financial summary............................................................................................................................... 5A3 Work packages summary.................................................................................................................... 5

Section B: Overview of the research........................................................................................................6B1 Scientific and/or technical excellence..................................................................................................6

B1.a Summary of the project.........................................................................................................6B1.b Overview of the scientific and technical objectives................................................................6B1.c List of deliverables.................................................................................................................7B1.d Need for the project...............................................................................................................7B1.e Progress beyond the state of the art......................................................................................8

B2 Potential outputs and impact from the project results..........................................................................8B2.a Projected early impact on industrial and other user communities..........................................8B2.b Projected early impact on the metrological and scientific communities.................................8B2.c Projected early impact on relevant standards........................................................................8B2.d Projected wider impact of the project.....................................................................................9B2.e Data management................................................................................................................. 9

B3 The quality and efficiency of the implementation.................................................................................9B3.a Overview of the consortium...................................................................................................9

Section C: Detailed project plans by work package.............................................................................10C1 WP1: Title.......................................................................................................................................... 10

C1.a Task 1.1: Title...................................................................................................................... 10C1.b Task 1.2: Title...................................................................................................................... 10C1.c Task 1.3: Title...................................................................................................................... 10C1.d Task 1.4: Title...................................................................................................................... 11

C2 WP2: Title.......................................................................................................................................... 11C2.a Task 2.1: Title...................................................................................................................... 11C2.b Task 2.2: Title...................................................................................................................... 11C2.c Task 2.3: Title...................................................................................................................... 12

C3 WP3: Title.......................................................................................................................................... 12C3.a Task 3.1: Title...................................................................................................................... 12C3.b Task 3.2: Title...................................................................................................................... 12C3.c Task 3.3: Title...................................................................................................................... 13

C4 WPN-1: Creating impact.................................................................................................................... 13C4.a Task N-1.1 Knowledge transfer...........................................................................................13C4.b Task N-1.2 Training.............................................................................................................14C4.c Task N-1.3 Uptake and exploitation.....................................................................................14

C5 WPN: Management and coordination................................................................................................15C5.a Task N.1: Project management...........................................................................................15C5.b Task N.2: Project meetings.................................................................................................15C5.c Task N.3: Project reporting..................................................................................................15

C6 Gantt chart......................................................................................................................................... 17Section D: Risk and risk mitigation........................................................................................................18

D1 Scientific/technical risks..................................................................................................................... 18D2 Management risks............................................................................................................................. 19D3 Ethics................................................................................................................................................. 20

Section E: Operational capacity.............................................................................................................21Section F: Potential collaborators.........................................................................................................22Section G: References............................................................................................................................. 23

of 24 document.docx

EMPIR

Section A: Key data

A1 Project data summaryCoordinator contact details:

Coordinator:Address:Phone:Email:

Chief Stakeholder: **for Pre & Co-Normative proposals only**Chief Stakeholder OrganisationAddressPhone:Email:

Participant details:a. Partners (participants who will accede to the Grant Agreement)

no. Participant Type Short Name Organisation legal full name Country1 Internal Funded Partner

2 Internal Funded Partner

3 Internal Funded Partner

4 External Funded Partner

5 Unfunded Partner

b. Linked Third Parties (participants who will NOT accede to the Grant Agreement)no. Participant Type Short Name Organisation legal full name Country

Linked Third Party(Linked to <Partner Short Name>)

of 24 document.docx

EMPIR

A2 Financial summaryInternal Funded

Partners

External Funded

Partners

Unfunded Partners

Total

Labour (€)

Subcontracts (€)

T&S (€)

Equipment (€)

Internally Invoiced Goods and Services (€)

Other Goods and Services (€)

Large Research Infrastructure (€)

Indirect (€)

Total eligible costs (€)

Total eligible costs as % of total costs

EU contribution (€)

EU contribution as % of total EU contribution

Months

A3 Work packages summaryWP No Work Package Title Active Partners (WP leader in bold) Months

WP1

WP2

WP3

WPN-1 Creating impact

WPN Management and coordination

Total months

of 24 document.docx

EMPIR

Section B: Overview of the research

B1 Scientific and/or technical excellence

B1.a Summary of the project Overview

Need

Objectives

Progress beyond the state of the art and results

Impact

Impact on industrial and other user communities

Impact on the metrology and scientific communities

Impact on relevant standards

Longer-term economic, social and environmental impacts

B1.b Overview of the scientific and technical objectives The overall objective of the project is to

The specific objectives of the project are:

1.

2.

3.

4.

5.

of 24 document.docx

EMPIR

B1.c List of deliverables

Relevant objective (Activity delivering the deliverable)

Deliverable number

Deliverable description Deliverable type Partners (Lead in bold)

Delivery date

(AX.X.X)D1 BBB, AAA,

CCCMXX

(AX.X.X)D2 MXX

(AX.X.X)D3 MXX

(AX.X.X)D4 MXX

(AX.X.X)D5 MXX

(AX.X.X)D6 MXX

(AX.X.X)D7 MXX

(AX.X.X)D8 MXX

(n/a) D9 Evidence of contributions to or influence on new or improved international guides, recommendations and standards with a specific focus on the following guides and committees: XXXXXX.Examples of early uptake of project outputs by end-users

Reporting documents

BBB, all partners

M36

n/a D10 Delivery of all technical and financial reporting documents as required by EURAMET

Reporting documents

AAA, all partners

M36+ 60 days

B1.d Need for the project

of 24 document.docx

EMPIR

B1.e Progress beyond the state of the art

B2 Potential outputs and impact from the project results

B2.a Projected early impact on industrial and other user communities

B2.b Projected early impact on the metrological and scientific communities

B2.c Projected early impact on relevant standards

of 24 document.docx

EMPIR

Standards Committee / Technical Committee / Working Group

Partners involved

Likely area of impact / activities undertaken by partners related to standard / committee

B2.d Projected wider impact of the project

B2.e Data management

B3 The quality and efficiency of the implementation

B3.a Overview of the consortium

of 24 document.docx

EMPIR

Section C: Detailed project plans by work package

C1 WP1: TitleThe aim of this work package is to ….

C1.a Task 1.1: Title The aim of this task is to ………

Activity number

Activity description Partners (Lead in bold)

A1.1.1MXX

AAA, BBB, CCC

A1.1.2MXX

CCC, AAA, BBB

A1.1.3MXX

BBB, AAA

A1.1.4MXX

AAA, BBB, CCC

A1.1.5MXX

AAA, CCC

C1.b Task 1.2: Title The aim of this task is to ………

Activity number


A1.2.1MXX

A1.2.2MXX

A1.2.3MXX

C1.c Task 1.3: Title The aim of this task is to ………

Activity number


A1.3.1MXX

A1.3.2MXX

A1.3.3MXX

A1.3.4

of 24 document.docx

EMPIR

MXX

A1.3.5MXX

C1.d Task 1.4: Title The aim of this task is to ………

Activity number


A1.4.1MXX)

A1.4.2MXX

A1.4.3MXX

A1.4.4MXX



Activity number


A2.1.1MXX

A2.1.2MXX)


Activity number


A2.2.1MXX

A2.2.2MXX

A2.2.3MXX

A2.2.4MXX

of 24 document.docx

EMPIR


Activity number


A2.3.1MXX

A2.3.2MXX

A2.3.3MXX



Activity number


A3.1.1MXX

A3.1.2MXX

A3.1.3MXX

A3.1.4MXX


Activity number


A3.2.1(MXX

A3.2.2MXX

A3.2.3MXX

A3.2.4MXX

A3.2.5MXX

of 24 document.docx

EMPIR


Activity number


A3.3.1MXX

A3.3.2MXX

A3.3.3MXX

A3.3.4MXX

A3.3.5MXX

A3.3.6MXX

A3.3.7MXX

C4 WPN-1: Creating impact

C4.a Task N-1.1 Knowledge transfer

Activity number


AN-1.1.1MXX

The project will create a Stakeholder Committee of at least XX members from organisations such as XXXXXXX, YYYYYY, ZZZZZ.The aim of the stakeholder committee is to XXXXX. Interaction of the Stakeholder Committee will be achieved via XXXXXX.

CCC, all partners

AN-1.1.2MXX

A project webpage will be created by BBB and will include XXXXX.The webpage will be regularly updated with XXXXXX and used for YYYYY.

BBB, all partners

AN-1.1.3(MXX

The partners plan to present at least XX papers at the following international conferences;

XXXX YYYYY ZZZZZ

Further relevant conferences may be identified during the project.

CCC, all partners

AN-1.1.4MXX)

The partners will submit at least XX papers in total to peer-reviewed journals during the project.The expectations are that at least XX out the XX publications will be the result of a collaborative effort from partners from different countries.Target journals include

XXXX YYYYY ZZZZZ

The authors of the peer reviewed papers will clearly acknowledge the financial support provided through the EMPIR as required by EURAMET.

CCC, all partners

AN-1.1.5 Information on the results of the project will be disseminated to a range of standards bodies and committees and feedback sought (see details below and in the table in

CCC, all partners

of 24 document.docx

EMPIR

MXX Section B2.c).

Standards Committee / Technical Committee / Working Group

Partners involved

Likely area of impact / activities undertaken by partners related to standard / committee

The representatives on the corresponding committee or WG from the partners will jointly ask the chairperson to include a point in the agenda to briefly present the outputs of the project related to the WG activities and ask for comments. Where appropriate a written report will be submitted for consideration by the committee or WG.

AN-1.1.6MXX

AN-1.1.7MXX

C4.b Task N-1.2 Training

Activity number


AN-1.2.1MXX

AN-1.2.2MXX

AN-1.2.3MXX

C4.c Task N-1.3 Uptake and exploitation

Activity number


AN-1.3.1MXX

An exploitation plan will be created at the beginning of the project by AAA with support from all partners and reviewed and updated at least at each project meeting.

AAA, all partners

AN-1.3.2MXX

AN-1.3.3MXX

All IP and potential licencing/exploitation will be handled in accordance with the Grant Agreement and the Consortium Agreement.

C5 WPN: Management and coordination

C5.a Task N.1: Project management

Activity number


AN.1.1 The project will be managed by the coordinator from AAA, who will be supported by AAA, all

of 24 document.docx

EMPIR

M36 the project management board consisting of XXXXX.The members of the project management board will guide the project, attend the project meetings, organise the progress meetings and call additional meetings if needed to ensure the overall project’s success.

partners

AN.1.2M36

The work package leaders will report on the on-going progress of the project to the coordinator by XXXX.

AAA, all partners

AN.1.3M36

The coordinator, with support from the partners, will manage the project’s risks to ensure timely and effective delivery of the scientific and technical objectives and deliverables.

AAA, all partners

AN.1.4MXX

The consortium will ensure that any ethics issues identified (see Section D3) are addressed.

AAA, all partners

AN.1.5M36

AAA, all partners

C5.b Task N.2: Project meetings

Activity number


AN.2.1M1

The kick-off meeting involving all partners will be held approximately one month after the start of the project, at AAA.

AAA, all partners

AN.2.2M36

There will be XXX formal project meetings. These meetings include XXX and will be held XXXX. The meetings will review progress and will be used to ensure partners are clear as to their role for the next period. The location of the meetings will XXXXX.

AAA, all partners

AN.2.3M36

In addition, technical meetings of work package groups may be held whenever necessary, and will be arranged on an ad hoc basis.

AAA, all partners

AN.2.4MXX

AAA, all partners

C5.c Task N.3: Project reporting

Activity number


AN.3.1M1

One month after the start of the project a publishable summary and data management plan (DMP) (if applicable) will be produced and submitted to EURAMET.

AAA, all partners

AN.3.2M36+60 days

Following Articles 17 and 20 of the grant agreement, information will be submitted to EURAMET, in accordance with the procedures issued by them to enable EURAMET to comply with its obligations to report on the programme to the European Commission.• Progress reports will be submitted at months 9, 27 (+ 45 days), 18, 36 (+ 60 days).• Impact/Output reports and data management plans (if applicable) will be submitted

at the same times.All partners will provide input to these reports and the coordinator will provide these and updated publishable summaries to EURAMET.

AAA, all partners

AN.3.3M36+60 days

Periodic Reports (including financial reports and questionnaires) will be delivered at months 18 and 36 (+ 60 days) in accordance with Article 20 of the grant agreement.All partners will provide input to these reports and the coordinator will provide these to EURAMET.

AAA, all partners

AN.3.4M36+60 days

Final Reports will be delivered at month 36 (+ 60 days) in accordance with Article 20 of the grant agreement.All partners will provide input to these reports and the coordinator will provide these to EURAMET.

AAA, all partners

Formal reporting will be in line with EURAMET’s requirements and will be submitted in accordance with the Reporting Guidelines.

of 24 document.docx

EMPIR

of 24 document.docx

EMPIR

C6 Gantt chart

of 24 document.docx

EMPIR

Section D: Risk and risk mitigation

D1 Scientific/technical risksRisk (description) Likelihood and impact of

occurrenceMitigationi.e. what the consortium will do to decrease the likelihood of the risk occurring

Contingencyi.e. what the consortium will do if despite the mitigation the risk still occurs

Task X.X: Likelihood without mitigation: High/Medium/Low

Impact:

Likelihood after mitigation: Medium/Low/Very low


Impact:



Impact:



Impact:



Impact:



Impact:



Impact:



Impact:


of 24 document.docx

EMPIR

D2 Management risksRisk (description) Likelihood and impact of

occurrenceMitigationi.e. what the consortium will do to decrease the likelihood of the risk occurring

Contingencyi.e. what the consortium will do if despite the mitigation the risk still occurs

Key personnel are lost to the project

Likelihood without mitigation: Low

Impact: The loss of key team members would create difficulties in delivering the project, or specific tasks or deliverables.

Likelihood after mitigation: Very low

None of the team members are planning to leave or retire within the project.

The grouping of experts within the consortium should minimise the areas where knowledge is held by a single person. All the partners will identify backups for key workers wherever possible to reduce the overall risk to the project. Project plans will be shared within the consortium and results and methodology will be documented.

If a key member leaves the project, then the partner concerned will be responsible for appointing a replacement. However this may still lead to a delay in delivery.

Complexity of managing a large consortium

Likelihood without mitigation: Medium

Impact: Failure to fully cooperate or communicate effectively within the consortium could endanger efficient delivery of the project.

Likelihood after mitigation: Low

The partners are all experienced with complex multinational projects. Many have previously developed close relationships through collaborating within other European consortia. Regular communication and feedback will ensure that potential problems are identified early and that all partners are clear on their roles.

WP leaders will play an important role in flagging up potential problems to the coordinator and the project management board, who will then decide on the best course of action to take. If necessary, work will be reassigned to an alternative partner, or parts of the work re-scoped in agreement with EURAMET.

Inter-dependencies between technical activities and tasks are too complex


Impact: Tasks are delayed or it is not possible to deliver them.


Technical meetings run by WP leaders have been scheduled to ensure proper sharing of knowledge. The interdependencies between tasks will be considered at meetings to ensure that this is addressed properly in the planning of the work.

The technical WPs will be closely managed by their WP leaders to ensure that they deliver their own outputs.

In most cases, activities on the critical path have some overlap in time and thus a delay in the output of one deliverable does not necessarily cause an immediate delay in another.

Problems dealing with Intellectual Property (IP) ownership and/or exploitation might occur and could be a source of potential conflict


Impact: Disagreement between the partners could delay the progress of the project (in implementing the work and publishing results).


All partners will sign the grant agreement and consortium agreement, which includes IP clauses.

Independent arbitrators will be used in the event of disagreement between partners.

Likelihood without mitigation: High/Medium/Low

Impact:


Likelihood without mitigation: High/Medium/Low

Impact:


of 24 document.docx

EMPIR

D3 Ethics

of 24 document.docx

EMPIR

Section E: Operational capacityPartner 1 - Organisation’s short name (Coordinator, Internal Funded Partner)

Partner 2 - Organisation’s short name (Internal Funded Partner)



Partner 5 - Organisation’s short name (External Funded Partner)

Partner 6 - Organisation’s short name (External Funded Partner)

Partner 7 - Organisation’s short name (Unfunded Partner)

Partner 8 - Organisation’s short name (Unfunded Partner)

Linked Third Partner – Organisation’s short nameXXX is a third party linked to partner YYY.

of 24 document.docx

EMPIR

Section F: Potential collaboratorsCollaborators do not sign the Grant Agreement or deliver any work necessary for the completion of the project or deliverables, but have a relationship with the consortia defined via a Letter of Agreement.

The following organisations below have indicated their potential willingness to collaborate:

Short name Organisation legal full name

Country Area of collaboration including WP

of 24 document.docx

https://msu.euramet.org/downloads/documents/Attachment5_(Letter_Agreement).docx

EMPIR

Section G: References[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

of 24 document.docx

EMPIR

Please delete this page before you submit your application

NOTE: EURAMET uses the filename in the footer for internal control purposes. Please do not delete the automatic filename from the footer. Please save the document in “.docx” format.

Document Control Page

Document Title: EMPIR Call Process

Template 4: JRP protocol

Document Code: P-CLL-TMP-103 Version 1.4

Document Control: Approved: Programme Manager 2018-06-03

of 24 document.docx

EMRP-template (document) - EMPIR Participant...

Documents

Transcript of EMRP-template (document) - EMPIR Participant...