Overall Strategy of Work Plan. The project’s networking activities have been designed to xxxxxx collaboration between the project participants (WP1), between the project and its targeted communities (WP2), and between the project and other related projects (WP3). WP1, the project management work package, is primarily responsible for ensur-‐ ing that all of the project communicate and that important information is passed from one work package to another. This will be accomplished through regular meetings of all work package managers. Where sustained technical dialogs are necessary, work package managers will appoint technical personnel as liaisons to ensure efficient communication. The full management structure is described in Section B.2. Within WP2, Interactions with Targeted Communities, a group of bioinformatics researchers will act as “internal” users of the StratusLab software. They will pro-‐ vide rapid feedback on pre-‐production releases to ensure that production re-‐ leases are sufficiently stable for the wider community and contain coherent func-‐ tionality. They will intensively interact with the StratusLab system administra-‐ tors and developers during their evaluations of pre-‐production releases. They will act as a quality control check to prevent releases with serious deficiencies from reaching our targeted communities. WP2 also manages the communication between users of the StratusLab software (end-‐users and system administrators) and the project. It will survey those communities to identify existing expertise with cloud and virtualization tech-‐ nologies, to determine common use cases, and to solicit feedback on StratusLab releases. All of these interactions are intended to improve the stability, relia-‐ bility, manageability, and functionality of the StratusLab software. Lastly, WP3 will coordinate the communication with the general public and interactions between the StratusLab project and other related projects. There will likely be other European-‐funded projects that revolve around the grid middleware itself. StratusLab must interact with those projects to ensure that their services are compatible with cloud and virtualization technologies. Simi-‐ larly there will be many projects from the Virtual Research Communities call that will provide excellent mechanisms for contacting scientists interested in cloud and virtualization technologies. Overall, the networking activities will xxxxxx collaboration over the complete spectrum of actors, from project par...

Overall Strategy of Work Plan. Service activities will provide vital support to the other activities. In order to cer-‐ tify the StratusLab toolkit, WP5 will deploy and maintain a small, yet representa-‐ tive, infrastructure. This ‘pre-‐production’ environment will provide the required platform for deploying incrementally the results of the WP4 cloud integration activity, but also provide a testbed for JRA activities to deploy and test their re-‐ search results. The StatusLab infrastructure will also serve as an important plat-‐ form for assessing the economical impact of cloud technologies in the provision of grid services both in terms of human resources (e.g. for administration and system maintenance) and environmental costs (power consumption, carbon footprint etc.) WP4 and WP5 have clear and distinct mandates, but will also work closely, to ensure that the StratusLab open source cloud distribution meets the high quality expectations of production-‐like systems. As WP4 identifies software component candidates, from the state-‐of-‐the-‐art as well as proven solutions, but also inte-‐ grates research results from the JRA activities, WP5 will deploy, upgrade and maintain the StratusLab infrastructure. This continuous integration and infra-‐ structure maintenance will provide quick feedback Similarly, as WP4 defines, develops and integrates reference test suites for the distribution, WP5 will in-‐ strument its infrastructure to trigger these test suites on a regular basis. Our goal is to create a continuous feedback process where as the project unfolds, the system is continuously rebuilt and deployed to trap any disruption that might be inadvertently introduced, such that it can be identified early and cor-‐ rected swiftly. This will ensure that no hidden issue is kept from the project stakeholders, which could cause undesirable delays in the work plan. As the project moves from the development and integration phase (year one) to a more user and deployment phase (year two), the support services provided by the SA activities will also evolve. At the start of the project, WP4 will have most of the knowledge in terms of StratusLab toolkit. However, as WP5 deploys and maintain the project pre-‐production infrastructure, it will build not only build knowledge in the distribution, but critically, built knowledge in operations of StratusLab powered infrastructure. This will be invaluable in providing support to external users, both in terms of system administrator, but also in te...

Overall Strategy of Work Plan. Research activities in StratusLab have to be understood as very specific and fo-‐ cused actions to achieve the main goal of the project that is to integrate a toolkit for offering Cloud and Grid Services. Having into account this, next figure shows the relationship between the research activities and the rest of the project activi-‐ ties:

Related to Overall Strategy of Work Plan

Work Plan Coordinate a work plan including a list of the proposed meetings and coordination activities, and related tasks to be performed, a schedule and an estimate. The work plan must satisfy the requirements of the project and must be approved by the State prior to commencing work.
Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.
Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.
Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.
Scope of Work For the 2022/2023 Grant Period, the Provider will maintain a victim services program that will be available to provide direct services to victims of crime who are identified by the Provider or are presented to the Provider, as specified in the Provider’s 2022/2023 Grant Application as approved by the OAG and incorporated herein by reference.
Development Program RWJPRI shall be [**] and have [**] in consultation with the JDAC, to select LICENSED COMPOUNDS which shall then be designated PRODUCTS for further DEVELOPMENT by RWJPRI and marketing by ORTHO and its AFFILIATES. RWJPRI shall provide KOSAN with written notice of its decision to select a LICENSED COMPOUND for DEVELOPMENT. Once a PRODUCT has been selected for further DEVELOPMENT, RWJPRI, with the advice of the JDAC, shall have the [**] right to develop the PRODUCT through STAGES O, I, II and III and shall have the [**] right to prepare and file, and shall be the owner of, all applications for MARKETING AUTHORIZATION throughout the world. During such DEVELOPMENT efforts, KOSAN will assist RWJPRI as may be mutually agreed, at RWJPRI's expense, in chemical development, formulation development, production of labeled material and production of sufficient quantities of material for STAGE O and initial STAGE I studies. RWJPRI shall exercise diligent efforts, commensurate with the efforts it would normally exercise for products with similar potential sales volume and consistent with its overall business strategy, in developing such PRODUCT in accordance with the DEVELOPMENT PLAN established by RWJPRI. In the course of such efforts RWJPRI shall, either directly or through an AFFILIATE or SUBLICENSEE to which the license shall have been extended, take appropriate steps including the following: (i) in consultation with the JDAC, select certain LICENSED COMPOUNDS for STAGE O DEVELOPMENT; and (ii) establish and maintain a program reasonably designed, funded and resourced to obtain information adequate to enable the preparation and filing with an appropriate and properly empowered national regulatory authority all necessary documentation, data and [**] CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. other evidence required for IND non-rejection to commence and conduct human clinical trials of such PRODUCT. (iii) proceed following IND non-rejection to commence PHASE I, II, and III clinical trials, associated studies and such other work which RWJPRI reasonably deems to be required for subsequent inclusion in filings for MARKETING AUTHORIZATION; (iv) after such submissions are filed prosecute such submissions and file all reasonably necessary, reports and respond to all reasonable requests from the pertinent regulatory, authorities for information, data, samples, tests and the like.
Scope of Works (a) Users with an appropriate licence type may be able to create and access Scope of Works. (b) The parties acknowledge and agree that: (i) any wording contained in a Scope of Works is established by the Customer, is customisable and within the Customer's absolute control; (ii) Users make decisions within ProcurePro on how to draft Scope of Works and ProcurePro is not responsible for those decisions; (iii) the Supplier is not liable for the Customer's use or reliance upon any Scope of Works; and (iv) the Supplier is not responsible for controlling the use, copying, modification or export of a Scope of Works by any User to which the Customer allows access to that Scope of Works.
Development Work The Support Standards do not include development work either (i) on software not licensed from CentralSquare or (ii) development work for enhancements or features that are outside the documented functionality of the Solutions, except such work as may be specifically purchased and outlined in Exhibit 1. CentralSquare retains all Intellectual Property Rights in development work performed and Customer may request consulting and development work from CentralSquare as a separate billable service.
000 SCOPE OF WORK 5. 100 The scope of this Agreement covers all work of a maintenance, repair and renovation nature, assigned by the Owner to the Company and performed by the employees of the Company covered by this Agreement, within the limits of the Owner's plant site.
Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

Overall Strategy of Work Plan Sample Clauses

Filter & Search

Related Clauses

Parent Clauses

Related to Overall Strategy of Work Plan