Annex I - “Description of Work” - Hlandata

CIP-ICT PSP-2009-3Pilot BHLANDATARegarding the technical implementation of the HLANDATA Project, there exist some risks to betaken into account, which will have to be contemplated in the frame of a risk management plan. Forinstance, the proposed harmonization model may be difficult to implement as related to the availableinformation for the development of the 3 pilot projects. This issue may be solved by adapting thestructure of the pilot project available data to the already defined model. This may imply an increaseof the foreseen costs which would have to be compensated through an adjustment of the overallproject budget.Other hypothetical setbacks to be overcome could be the withdrawal of a key expert from a member ofthe Consortium, or even the justified withdrawal of a partner. In the first case, the missing expertwould have to be substituted by another person from the same organization, whereas in the secondcase, the necessity of searching for another partner (depending on the punctual situation of the projectand on the particular role of the missing partner within the Consortium) would have to be analyzed.Moreover, some of the partners could fail to fulfil their expected tasks within the correspondingdeadlines. In such case, the mechanisms described at the Consortium Agreement would have to beaccordingly launched.It is especially important to ensure an adequate participation of the final users from the beginning ofthe project. Communication failures, lack of involvement from the partners’ side, changingrequirements, among others, could lead to unjustified delivery delays. The inclusion of a set of veryheterogeneous (or very numerous) final users within the Consortium could also entail greaterdifficulties when trying to harmonize their respective necessities. In addition, a validation plan for thefinal products, involving a wide enough amount of well-capable validators should be set out.As for the expertise and experience of the appointed work team of the project, main risks would berelated to the amount of personnel dedicated to the project, as well as their degree of involvement,their degree of awareness of the common and homogeneous objectives for the project, and also thehypothetical unexpected effect of the personnel rotation within the different work teams.From a technological point of view, different databases, whose functionalities and results have neverbeen proved yet, have been foreseen to interact together, which constitutes an added risk for thetechnological success of the project. A specific user interface will be required, new harmonizedutilities will have to be developed, new development tools will have to be integrated, and usersinteraction issues will also have to be contemplated, resulting in many possible causes for the rise oftechnological contingencies.During the mass production process, the main risks for the project will be associated to the clearnessand strictness of the defined development plan, as well as of the normalization and follow-up policiesapproved. The degree of knowledge of the standards and the methodology of the required technicalreviews will also turn out to be crucial in order to avoid risks and face any incidence at this point.Another incidental possibility to be considered could be the lack of continuity of the project once ithad been completed. However, this is not a realistic situation to be contemplated, since the existenceof a consistent Viability and Exploitation plan for the project flatly disables such a possiblecontingency.In addition, the risk management plan for the project must also contemplate the possible risksassociated to the foreseen implementation of the pilot projects. For pilot project 1, the harmonizationmodel elaborated at WP2 may not adjust properly to the content of the data to be included within suchpilot project. As already considered, this contingency could be solved by modifying the structure ofthe original data and by adapting it to the proposed model.Another risk to be taken into account would be the fact that some functionalities included within pilotproject 1 could show themselves to be more difficult to implement than expected, giving rise to delaysand increases of the foreseen expenses. A possible solution for this would be to try to make use of23/03/10 v11 51