S/T methodology and associated work plan Sample Clauses

S/T methodology and associated work plan. 3.3.1. Overall strategy and general description The project will develop tools and applications in parallel. The leading idea is to have working prototypes from the beginning, and deliver updates frequently. The work is divided into four kinds of packages: • Management and dissemination: WP1 and WP10. These run throughout the project. • Generic tools: WP2–5. These start early in the project.
AutoNDA by SimpleDocs
S/T methodology and associated work plan. B.1.3.1 Overall strategy of the work plan The overall strategy of SHARE is to start with defining the engineering requirements to guide in assembling the required databases and scientific and technical knowledge for the assessment of earthquake occurrence probabilities and of ground-motion models. These models will be combined in the assessment of seismic hazard, performed in a quality-controlled computational infrastructure. The hazard models in turn will serve as input for engineering applications and for dissemination to the wider community (Figure 1).
S/T methodology and associated work plan. B1.3.1 Overall strategy and general description Given the rather small number of partners (five) and the short duration (two years) of the project, we propose a rather simple structuring of the work plan of the project into three work packages (see also Table WT1):
S/T methodology and associated work plan. B.1.3.1 Overall strategy and general description OPPORTUNIY pursues a high risk, yet well thought through and promising approach to the development of opportunistic activity recognition systems. It is based on a large body of previous research performed by the project partners and a thorough understanding of all the components and possible variations of a recognition system. A hierarchical decomposition of the activity recognition problem enables the project to claim that the OPPORTUNITY solution generalizes well to a broad range of problems. Based on the hierarchical breakdown, an incremental approach has been designed for the project that allows us to pursue an ambitious, high risk end goal without the risk of an ‘all or nothing’ strategy. Instead we work towards the goal in incremental steps, each of them in itself representing a significant scientific advance. The breakdown is also the basis for an incremental approach to validation which will start with simple activity components and then proceed to increasingly complex case studies finally leading to a system demonstrator motivated by and closely related to relevant real life applications such as personal healthcare and adaptive energy management in home and office environments. The work is divided into work packages following a logical partitioning of work. Each work package is lead by a partner with a long history of internationally recognized research work in the corresponding area. Project deliverables and milestones ensure ambitious yet realistic project timing with well defined synchronisation points between different work packages and tasks. The project proposes a complex, large and ambitious work program. The consortium can handle this work program with the requested resources, because a huge amount of experience, algorithms, equipment and conventional activity recognition and sensing setups already exist at the partners labs.
S/T methodology and associated work plan. 1.3.1 Overall Strategy of the Work Plan WP1: Project Management and Coordination This Work package will organise and implement decision-making, external and internal communication, administrative and technical control of the project. It will set the basis for coordination of the technical activities of WP2-7 and the interaction of partners, and establish links between project partners and the EU, as well as the ICT community.
S/T methodology and associated work plan. B.1.3.1 Overall strategy and general description‌ The project objectives will be implemented according to the following work plan. The project’s S&T achievements will be guided by WP1 where the application scenarios will be defined in detail, as well as the collection of data sets and their annotation. The scientific and method- ological foundations will be developed in four workpackages: WP2, WP3, WP4, and WP5, along the objectives defined by WP1. The outcomes of these workpackages will be twofold:‌
S/T methodology and associated work plan. This section presents the work plan of the project. It presents the detailed work packages, deliver- xxxxx and milestones and the involvement of the different partners.
AutoNDA by SimpleDocs
S/T methodology and associated work plan. B 1.3.1 Overall strategy and general description The project has eight work packages (WPs) to achieve the objectives. WP8 concerns non- technical management, monitoring and evaluation. The technical work packages are as follows: • WP1 = Value-chain assessment and management • WP2 = Reduced post-harvest losses of fresh produce • WP3 = Alternative market development to reduce post-harvest losses • WP4 = Adding value to waste products • WP5 = Food safety, quality and compliance • WP6 = Demonstration of technologies with beneficiaries • WP7 = Dissemination and support to replication. WP1 seeks to evaluate value chains for cassava and yams (fresh and processed) from the farm to the consumers. Specific emphasis will be placed on understanding the levels and causes of post-harvest losses and identifying and evaluating alternative options for reducing such losses. It will also document for specific cases the levels of waste generated, examine related value chains for these products and the impact of developing these alternative value chains. In WP2 technologies for the reduction of post-harvest losses of fresh yam in particular will be developed and validated. This will focus on storage losses in yams looking at improved storage systems and controlling dormancy which are major causes of loss. In WP3 alternative novel markets for processed cassava and yam products will be developed and validated that reduce levels of post-harvest loss and provide increased incomes for small-holder farmers. The key issue in this WP will be the development of viable processing options for yam and cassava that provide options for households to sell their produce for reasonable prices and that result in reduced physical or economic losses. There will be an important balance to strike between products prepared and stored for household use and the generation of income – with the income contributing to food security. Understanding these different processing options and their implications for food security will be an important element of WP1. WP4 seeks to develop new technologies and products and add value to the waste products from processing (mainly from cassava and to a lesser extent from yam). Work will focus on added value products that feed into the human food supply chains, e.g. mushroom production using peels as substrate; use of peels as a raw material for animal feed and using peels as a raw material for added value products, such as sugars and other raw materials for the food in...
S/T methodology and associated work plan. 1.3.1 Describe the overall strategy of the work plan To achieve FIGARO's objectives, a work plan has been designed for the duration of 48 months. The overall RTD approach of FIGARO approach is application oriented research, and industry driven; the goal is to convert research and development results into industrial products developed with significant input from stakeholders, including calibration, validation and demonstration at multiple end-user sites across Europe. This work plan foresees 10 Work Packages ("WP") structured in three stages and a set of ongoing horizontal activities accommodates for the interaction among the WPs. Each WP is assigned a WP Leader and has a set of tasks that cover the assignment of that work package. Partners that participate in these tasks are allocated the resources that will facilitate the successful, on schedule completion of the tasks. Most of the WPs are active only partially throughout the entire project as some of the results obtained by a certain WP may provide the input for the subsequent WP. We have grouped the WPs into four blocks as follows:
S/T methodology and associated work plan. B1.3.1 OVERALL STRATEGY OF THE WORK PLAN NOPTILUS comprises 9 Work-Packages (WP), each consisting of several tasks. The project is organized along 7 technical work packages, one of them dedicated to integration and evaluation, and 2 work packages for management and dissemination, respectively. Each partner takes on one side the responsibility for his research topic, but is also strongly involved in the integration, demonstration and evaluation of the overall system. The common research platform (multi-AUV system) and the integrated demonstrations guarantee a strong interaction and collaboration between the partners. The overall duration of NOPTILUS is scheduled for 4 years (48 months) and is divided in 4 main stages (see Xxxxx chart in Section B1.3.2):  Development and design of the individual methodological and algorithmic components and elements addressing the low-level NOPTILUS objectives (i.e. related to communications, sensing, and localization) as well as definition and specification of all hardware components of the NOPTILUS system (WP2 and WP3).  Development and design of all methodological and algorithmic components and elements addressing the medium-level NOPTILUS objectives (WP4 and WP5).  Development and design of all methodological and algorithmic components and elements addressing the high-level NOPTILUS objectives (WP6 and WP7).  Integration, demonstration and evaluation of the overall NOPTILUS system (WP8). Project management and dissemination, training and exploitation activities (WP1 and WP9) constitute a continuous phase that is active during the whole project life. The first 3 of the above stages end with an integration week and are managed along a list of milestones and deliverables. The integration weeks assemble the key project engineers at the Test Case location for 2-3 weeks. The main objective of these meetings is to integrate and test all elements, track progress, identify and resolve potential problems, and define the next phase in more detail. Moreover, these meetings help to integrate the team and their developed technologies, and serve as the main points of reference for the progress of the project. In addition to the integration weeks involving all partners, individual integration will be realized by exchange of PhD students and semester-long visits of individual partners. Furthermore, CERTH will have a technical project manager that will regularly (at least once every year) visit each partner’s lab and discuss all upcom...
Time is Money Join Law Insider Premium to draft better contracts faster.