PROPOSAL PART B ICT PSP call for proposals 2007 – ICT-PSP/2007/1 Pilot Type A
ICT PSP Main Theme identifier: ………………………………………….
(e.g. 1.1. Enabling EU wide public eProcurement)
[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 organisation name
Participant short name
Certified representative of a national administration?
* Please use the same participant numbering as that in section A2 of the administrative forms List of National Administrations which are represented by one of the above participants:
Describe the common interoperable service solution that the Pilot aims to implement and demonstrate (maximum 10 lines)
Describe the existing services related to the Pilot for each of the countries involved. Indicate the extent to which these services are already operational at national, regional or local level and the national initiatives/strategies to which they belong (maximum 1 page)
Describe the methodology and the roadmap of main milestones and tasks to be carried out during the Pilot (maximum 10 lines)
Describe briefly the composition of the consortium and the extent to which it includes the whole service value chain (maximum 10 lines)
Describe the mechanisms that will be put in place during the project to ensure the openness of the work and the involvement of other states and stakeholders not participating directly in the Pilot. (maximum 10 lines)
Describe the expected impact of the Pilot at EU level (maximum 10 lines)
(This section should provide an analysis of the specific interoperability issue/problem that is going to be addressed. It should explain the concept of the project, i.e. its objectives and the proposed solution. The project objectives must be fully aligned with the objectives description of the chosen theme (provided in the Work Programme in chapter 3).
The objectives should be those achievable within the project, not through subsequent development. The results should be stated in a measurable and verifiable form, attainable with the available resources and realistic within the time span of the project. This section should explain the project in technical terms; where legal, organisational and political terms are important these should also be explained. The section should:
describe the interoperability issue it will tackle,
describe the existing national infrastructures it will base itself on (i.e. the existing national, regional, local initiatives),
describe the way how those national initiatives will be “connected” together,
describe the expected final result of the project.)
B1.2 EU dimension
(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. 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 directives,
describe the relevance of the proposed solution to political objectives,
explain the EU relevance of the solution to be demonstrated.)
B1.3. Consensus building
(Demonstrate the capability to build support across the EU in view of EU wide consensus. This section must describe in detail
(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. Mention any assumptions and external factors that may determine whether the impacts will be achieved, including the main barriers and foreseeable risk factors. Further, this section must detail the way in which benefits of the pilot will be measured and assessed. The proposal needs to define both quantitative and qualitative criteria to measure the progress of the pilot and the benefits achieved by the pilots' services. These figures should be available both on a country-by-country basis, as well as collectively.)
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 public entities, sub-contractors – if known at the stage of the submission) 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 prior 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. Indicate whether a national administration is represented in the consortium by a designated legal entity to act on its behalf for the purpose of the project and explain why this representative was chosen. If you are planning to enlarge the consortium during the course of the project, please include the profile of the envisaged new partners.)
B2.4. Long term impacts
(You should 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.
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. As regards viability you should address all aspects of financial technical and political nature. The project should explain how legal barriers could be lifted to enable an effective EU wide interoperable service.)
B2.5. Availability of results
(Outline how you intend to spread results and disseminate knowledge of the specification of interfaces, protocols, architecture, etc, as well as – where appropriate - open source reference implementations of necessary components and building blocks for interoperability.
This section should particularly describe
how IPR (intellectual property rights) will be managed in line with the Work Programme requirements, and
how public procurement rules will be respected beyond the project phase for the full deployment of the service.)
(Explain the structure of your work plan, its overall strategy, and the methodology used to achieve the objectives.)
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:
Work package list (use table 1 template);
Deliverables list (use table 2 template);
Work package description (use table 3 template);
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.
Number of the participant leading the work in this work package.
As chosen in section A3
The total number of person months allocated to each work package.
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).
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
date (proj. month) (iv)
Deliverable numbers in order of delivery dates. Please use the numbering convention .. For example, deliverable 4.2 would be the second deliverable from work package 4.
Please indicate the nature of the deliverable using one of the following codes:
P = Prototype; R = Report; D = Demonstrator, SP = Specification, O = Other.
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.
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.
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.
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.
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 (WP) by each participant. Identify the work package leader for each WP by showing the relevant person months figure in bold.)
(Describe the organisational structure and decision-making mechanisms of the project. Show how they are matched to the complexity and scale of the project. The proposal should outline plans for the Pilot Type A that conform to governmental standards for large scale ICT-projects. Plans should be produced for project management, document and software life cycle management, quality management and software development management. The project management plan should outline clearly resources, milestones, review and reporting procedures.
Organisational and change management should be properly addressed in the Pilot Type A proposal, with a detailed specification of the approach and methods to be used.)
(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 A cover only activities and costs related to the interoperability issue. Applicants cannot claim costs related to national activities/services.)
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 proposal and/or nature of the proposed service, and if so, how they are addressed in the proposal.
If they exist, 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. The architecture should be compliant with the guidelines that each Member State has produced (if any), regarding the interoperability of information systems in both the public administration and in the application sector.
Describe the inclusiveness and accessibility of the service, both by its nature and the way it shall be provided.)
(The completed proposal Part B is submitted in PDF format)
[Proposal acronym] Proposal Part B: page [x] of [y]