PROPOSAL PART B

ICT PSP call for proposals 2007 - ICT PSP/2007/1

Pilot Type B

ICT PSP Main Theme identifier and title:	………………………………………….
							(e.g. 2.2 ICT for Ageing)

[Proposal full title]

[Proposal acronym]

Date of preparation: 									

Version number (optional): 								

Name of coordinating person: [Coordinator person name, organisation] 		

e-mail: [Coordinator email] 								

fax: [Coordinator fax] 									

List of participants: 

Participant no.*	Participant organisation name	Participant short name	Country	
1 (Co-ordinator)				
2 (Participant)				
3 (Participant)				
4 (Participant)				
…				

* Please use the same participant numbering as that in section A2 of the administrative forms 
A: Table of Contents Page

PROJECT PROFILE

B1. Project description and objectives
B1.1. Project objectives
B1.2 EU dimension
B1.3. Rationale for EU Funding
B2. Impact
B2.1. Target outcomes and characteristics
B2.2. Expected impacts
B2.3. Consortium and key personnel
B2.4. Long term viability
B2.5. Maturity of the technical solution
B3. Implementation
B3.1. Chosen approach
B3.2. Work plan
B3.3. Project management
B3.4. Dissemination
B3.5. Resources to be committed
B3.6. Security, privacy, inclusiveness, interoperability; standards and open-source

PROJECT PROFILE  

(Short, precise, verifiable) – maximum 2 pages

Proposal acronym: 						

Proposal full title: 						

Information on the service
	
Describe the proposed service focusing on its innovative aspects (maximum 10 lines).

	
Who will be the owner / provider / maintainer of the service?

	
Who will be the actual users of the service?

	
How will it be used (describe the typical usage case from users point of view)?

	
How will the service be sustained? Who will pay the cost? (e.g. end-user / public authority /mixed model etc.)

	
What technology will be used ? (hardware, software, delivery channels)

	
Does the service need specific content? If yes, how is it provided, who provides it?

	
Optional: Any specific issue (not covered by this project profile) the consortium wants to highlight 

	

Information on the project phase and impact
	
With how many users will the service be piloted?

Where will it be piloted? (List all locations and the number of estimated users per location - should sum up to the figure above)

Information on what already exists
	
A technically tested prototype of the service exists ?	Yes/No	
A business plan has been developed already for the service ?	Yes/No	
A service already exists?	Yes/No	
Further localisation work is needed?	Yes/No	
Further integration work is needed?	Yes/No	
Describe the existing prototype / service and highlight any necessary adaptation work to transform it into the targeted service (as described above). If necessary distinguish between different locations.

	
If running service exists: 	
	Where is it running?

	How many users does the service currently have?

	Who is the owner / provider / maintainer of the running service? 

	How is it currently sustained?

	

B1. Project description and objectives

B1.1. Project objectives
(This section should provide an analysis of the specific ICT based innovative service that is going to be addressed by the project, and should explain the concept of the project, i.e. its objectives and the proposed service. This section should also explain in detail how the proposed action aligns with the general objectives of the Work Programme and its addressed specific objectives relevant for the project. 

This section should in particular:

•	describe the proposed service itself which the project aims to deliver, 
•	describe what does it offer and which is its added value for the users, 
•	describe what is the innovative aspect, 
•	describe what are the benefits compared to existing solutions,	
•	describe the objectives of the proposed service / solution: The objectives should be those achievable within the project, not through subsequent development after the project duration. The expected results should be stated in a measurable and verifiable form, attainable with the available resources and realistic within the time span of the project.
•	describe briefly the project starting point of the proposed work (further details on the completed R&D work or the tested prototype service or any other partial solutions, based on which the proposed service will be developed are requested in section B.2.5 of the proposal) 
•	describe the envisaged usage of the service.)

B1.2 EU dimension
(This section should explain in detail the relevance of the proposed project to EU political objectives. It should describe the relevance of the project to EU policies.

Show how your pilot relates to the relevant policies, strategies and activities on European and national level. Indicate whether the outcome of the pilot will reinforce existing national initiatives. Give examples of references to national or European strategies.)

B1.3. Rationale for EU Funding
(This section should describe the rationale for ICT PSP funding. It should describe how the project funding would complement or surpass existing national activities. It should contain a clear link to section B1.1, in particular with regard to the innovative aspect and the added value of the service for the users.)

B2. Impact 

B2.1. Target outcomes and characteristics
(Describe how your project will contribute towards the expected target outcome and characteristics listed in the addressed specific objective in the ICT PSP Work Programme.) 

B2.2. Expected impacts 
(Describe how your project will contribute towards the expected impacts listed in the Work Programme in relation to the objective in question. Mention the steps that will be needed to bring about these impacts. Explain why this contribution requires a European (rather than a national or local) approach. Mention any assumptions and external factors that may determine whether the impacts will be achieved, including the main barriers and foreseeable risk factors.)

	 
B2.3. Consortium and key personnel
(Describe each consortium partner, highlight their specific expertise for and their role in the project and indicate the key personnel (brief CV) foreseen to work on the project. Clearly indicate the co-ordinator, all of the participants of the consortium (including sub-contractors and sub-contractor's task if they have not yet been identified) and the role of each in the proposed project. Include all necessary stakeholders in the value-chain. The organisation proposed to manage the project should be able to demonstrate competence and experience of managing large-scale international cooperation projects.

The composition of the consortium should be justified, in terms of presenting its capabilities and commitment for the tasks to be carried out in the project phase and to reach the objectives of the project.)

B2.4. Long term viability
(Explain the intended long term impact at European level. Describe how the consortium intends to reach viability, sustainability and scalability after the end of the project and the Community funding. 
This section should describe how the envisaged solution will be maintained and should /could be further developed beyond the end of the project and the Community funding. A business plan for the service should describe the funding flow, demonstrating the long term viability of the service.)

B2.5. Maturity of the technical solution
(Describe in this section the maturity of the technical solution which is the starting point of the work in the proposal (e.g. completed R&D work, or already tested prototype services, or several existing partial solutions to be combined, etc.). 

This section should explain the developments completed in the past and how the technical viability has been assessed. Evidence should be provided to demonstrate the scale of the past technical tests performed, and the number of users.

Should the proposed service need integration of several partial technical solutions, a separate description of each of them should be included, along with the work foreseen for the integration.)

B3. Implementation 

B3.1. Chosen approach 
(Explain the structure of your work plan, its overall strategy, and the methodology used to achieve the objectives. Attention should be given to the description of the technical work to be performed (e.g. localisation, merge of several existing separated services, ...))

B3.2. Work plan 
(A detailed work plan should be presented, broken down into work packages (WPs). A work package is a major sub-division of the proposed project with a verifiable end-point - normally a deliverable in the overall project. Work Packages should follow the logical phases of the implementation of the project, and include consortium management, assessment of progress and evaluation work package, dissemination activities. 

Present your plans as follows:
•	Show the timing and dependencies of the different WPs and their components through a GANTT chart. 
•	Provide a detailed work description broken down into work packages:
o	Work package list (use table 1 template);
o	Deliverables list (use table 2 template);
o	Work package description (use table 3 template);
o	Summary effort table (use table 4 template)

Note that the figures in these tables must equal the corresponding figures in the cost breakdown table (section A3).

•	The number of work packages used must be appropriate to the complexity of the work and the overall value of the proposed project. The planning should be sufficiently detailed to justify the proposed effort and allow progress monitoring by the Commission.

•	Any significant risks should be identified, and contingency plans described.)

Table 1: Template - Work package list 

Work package list 

Work package 
No.(i)	Work Package 
Title 	Lead 
Participant No. (ii)	Lead Participant
Short name (iii)	Total person months 
per WP (iv)	Start 
Month (v)	End 
Month (vi)	
WP 1							
WP 2							
WP 3							
-							
-							
	TOTAL						

Notes:
i.	Work package number: WP 1 – WP n.
ii.	Number of the participant leading the work in this work package.
iii.	As chosen in section A3
iv.	The total number of person months allocated to each work package. 
v.	Relative start date for the work in the specific work packages, month 0 marking the start
 of the project, and all other start dates being relative to this start date. Measured in months from the project start date (month 1). 
vi.	Relative end date, month 0 marking the start of the project, and all ends dates being 
relative to this start date. Measured in months from the project start date (month 1).
Table 2: Template - Deliverables list

List of deliverables

Deliverable
No (i)	Deliverable name	WP 
No.
	Nature
(ii)	Dissemination
level (iii)	Delivery 
date (proj. month) (iv)	

						

Notes:
i.	Deliverable numbers in order of delivery dates. Please use the numbering convention 
	<WP number>.<number of deliverable within that WP>. 
	For example, deliverable 4.2 would be the second deliverable from work package 4.

ii.	Please indicate the nature of the deliverable using one of the following codes: 
	P = Prototype; R = Report; D = Demonstrator, SP = Specification, O = Other.

iii.	Please indicate the dissemination level using one of the following codes:

	P = Public, for wide dissemination (public deliverables shall be of a professional 
	standard in a form suitable for print or electronic publication); 

	C = Confidential, limited to project participants. Irrespective of the status, all reports and 	deliverables must be made accessible to the other project participants and the 
	responsible European Commission services.

iv.	Month in which the deliverables will be available. Month 0 marking the start of the 
	project, and all delivery dates being relative to this start date. 

Table 3: Template – Work package description

Work package description

Work package number :		Start date or starting event:		
Work package title:		
Participant number:								
Participant short name								
Person-months per participant:								

Objectives (i)	

Description of work (ii)	

Deliverables (iii)	

Notes

i.	Provide a concise description of the objectives to be achieved within the work package and 	how these objectives will be pursued. Use quantifiable and verifiable elements. Refer to the 	tasks to be carried out.

ii.	Provide a short description of the work broken down into tasks of the work package. State 	the role of the participants for each task. State the amount of effort (in person months) per 	participant and task.

iii.	Provide a brief description of the deliverables including the month of delivery.
Table 4: Template – Summary of staff effort

A summary of the staff effort is useful for the evaluators. Please indicate in the table number of person months over the whole duration of the planned work, for each work package by each participant. 

Identify the work package leader for each WP by showing the relevant person months figure in bold. 

Participant No.	Participant Short name	WP1	WP 2	WP 3	…	Total person months	
1							
2							
3							
etc.							
Total							

B3.3. Project management
(Describe the organisational structure and decision-making mechanisms of the project. Show how they are matched to the complexity and scale of the project.
Organisational and change management should be properly addressed in the Pilot Type B proposal, with a detailed specification of the approach and methods to be used.)

B3.4. Dissemination 
(Describe the measures you propose for the dissemination and/or exploitation of project results, and the management of knowledge, of intellectual property, especially in view of impact on national and European level.)

B3.5. Resources to be committed
(In addition to the costs indicated on form A3 of the proposal, and the summary of staff effort shown in B3.2. table 4 above, please identify and substantiate any other major cost items (e.g. equipment, software, subcontracting). Describe how the totality of the necessary resources will be mobilised, including any resources that will complement the EC contribution. Show how the resources will be integrated in a coherent way, and show how the overall financial plan for the project is adequate.

For personnel costs only the actual monthly rate needs to be given here, as the rationale on the amount of effort should be given in the project work plan. For “subcontracting”, “indirect cost” and "other costs" a detailed breakdown and rationale must be given here. 

Eligible costs of Pilots Type B cover only activities related to the first implementation of the innovative service. The EC will therefore fund exclusively the costs related to the first implementation. Applicants cannot claim costs related to further research.)

B3.6. Security, privacy, inclusiveness, interoperability; standards and open-source 
(State clearly how interoperability between products and services from different sources will be ensured and, where appropriate, how interconnection and interoperability of networks and services will be achieved. State any security and privacy issues involved in the proposed service, and, if so, how they are addressed in the proposal.
The main standards being used should be identified. The proposal must (where applicable) clearly identify where a proprietary approach is used and the reasons for its use.
Proposals addressing problems connected with standardisation or regulation, should explain what these problems are and how they will be addressed.
Describe the inclusiveness and accessibility of the service, both by its nature and the way it shall be provided.)

(The completed proposal Part B has to be submitted in PDF format)