Task T5 Sample Clauses

Task T5. Standardization Efforts (Lead: ENG) This task will promote active contributions to developing and advancing standards in the area of ENVISAGE and addresses the work package objective O6.3 and the overall objective O6. Current lack of standardization poses a threat to the rapid growth of cloud computation, according to industry observers, especially with respect to interoperability and security. A number of standardization initiatives and in-progress standardization efforts address similar aspects of cloud computation, whereas other aspects are not yet addressed [165]: in particular, standards for virtualization are needed to make cloud providers interoperable by introducing common APIs for the interaction between virtual machines and different storage and network architectures. The Open Virtualization Format [166] is an emerging standard which enables the migration of virtual machines between clouds and is now recognized by ANSI and ISO. The Open Cloud Computing Interface [160] is similarly an emerging standard for management tasks such as deployment, scaling, and network monitoring. With respect to SLA, on-going efforts include OASIS’ Symptoms Automation Framework and SNIA’s Cloud Data Management Interface. An updated overview of standardization efforts is available as a Cloud Standards Wiki [69]. In ENVISAGE, we will mainly focus on standardization efforts on interoperability. Given the rapidly evolving standardization efforts in cloud computing, we plan to take advantage of the emerging standards on virtualization, and seek to contribute to efforts on quality of service and SLA. Standards in the area of ENVISAGE need to be monitored in order to identify those likely to be adopted and those for which a contribution from the project is expected. This task is devoted to identify and monitor the relevant standardization bodies and standardization initiatives, European and International. Examples are different WGs in OCCI, ETSI, OMG and W3C. Standards relevant for the project will be identified and project outcomes, as appropriate, will be presented to the standardization bodies. This will be operated by participating to the public events organized by these organization (e.g., the Plugfests organized jointly by XXXX, ETSI, OCCI) or by proposing dedicated presentations during the periodical meetings. As it can be challenging for STREP projects like ENVISAGE to directly impact standards, we plan to actively involve other projects and research groups in our sta...
AutoNDA by SimpleDocs
Task T5. 7: Business Models and Exploitation Strategy (Lead: ATB) The task estimates the business potential of ENVISAGE technologies, and in particular for joint exploitation. It addresses work package objective O5.8 and contributes to the overall objective O6 of ENVISAGE. This task aims at assessing the potential for a transfer of results from the ENVISAGE project to the partners as well as to other academic and industrial organizations that could gain technical, commercial, or research benefit from the project outcomes. The task will create exploitation plans describing how the individual partners envisage the commercial and academic exploitation of project results, and how the consortium as a whole sees the additional potential for joint exploitation. First, all partners will contribute from their different perspectives to an overall analysis of the exploitation opportunities for the ENVISAGE technologies, especially with respect to existing cloud platforms and standards in the market. This will be the starting point for • individual exploitation plans of the partners, and • assessing the potential for joint exploitation. The exploitation plans of the individual partners will be developed, based on the experiences with ENVISAGE technology that the partners have gained during the execution of the case studies. Based on these individual exploitation plans and the market analysis (D6.1), the task identifies the potential for joint exploitation and documents this potential in an overall ENVISAGE exploitation plan. For the joint exploitation plan, we will also take into account the feedback from partners outside the consortium which we reach through the dissemination and evaluation activities of WP5. The joint exploitation plan will consider the potential for commercialization of the ENVISAGE technologies and framework, as well as for follow-up RTD activities, by planning the activities needed to develop the RTD outcomes of ENVISAGE from prototypes into marketable products. Organization. This task will be led by ATB, who have considerable experience in identifying commercializable technologies through involvement in several start-ups and in assessment of technology for venture capital. All partners will contribute to the identification of exploitable items, both at the level of the individual partner and jointly at the level of the consortium. Relation to other work tasks and deliverables.
Task T5. The ENVISAGE Work Flow (Lead: FRH)

Related to Task T5

  • 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.

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

  • 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.

  • Contract Schedule The information set forth in the Contract Schedule is true and correct.

  • Contract Quarterly Sales Reports The Contractor shall submit complete Quarterly Sales Reports to the Department’s Contract Manager within 30 calendar days after the close of each State fiscal quarter (the State’s fiscal quarters close on September 30, December 31, March 31, and June 30). Reports must be submitted in MS Excel using the DMS Quarterly Sales Report Format, which can be accessed at xxxxx://xxx.xxx.xxxxxxxxx.xxx/business_operations/ state_purchasing/vendor_resources/quarterly_sales_report_format. Initiation and submission of the most recent version of the Quarterly Sales Report posted on the DMS website is the responsibility of the Contractor without prompting or notification from the Department’s Contract Manager. If no orders are received during the quarter, the Contractor must email the DMS Contract Manager confirming there was no activity.

  • Design Development Phase 1.3.1 Based on the approved Schematic Design Documents, model(s) and any adjustments to the Program of Requirements, BIM Execution Plan or Amount Available for the Construction Contract authorized by the Owner, the Architect/Engineer shall prepare, for approval by the Owner and review by the Construction Manager, Design Development Documents derived from the model(s) in accordance with Owner’s written requirements to further define and finalize the size and character of the Project in accordance with the BIM Execution Plan, “Facility Design Guidelines” and any additional requirements set forth in Article 15. The Architect/Engineer shall review the Design Development documents as they are being modeled at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Design Development. The Architect/Engineer shall allow the Construction Manager to utilize the information uploaded into Owner’s PMIS to assist the Construction Manager in fulfilling its responsibilities to the Owner. 1.3.2 As a part of Design Development Phase, Architect/Engineer shall accomplish model coordination, aggregation and “clash detection” to remove conflicts in design between systems, structures and components. Architect/Engineer shall utilize Owner’s PMIS to accomplish model coordination and collaborate with Construction Manager in the resolution of critical clashes identified by the Construction Manager. Architect/Engineer shall demonstrate and provide written assurance to Owner that conflicts/collisions between models have been resolved. 1.3.3 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments. 1.3.4 Before proceeding into the Construction Document Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Design Development documents and approval of the mutually established Amount Available for the Construction Contract and schedule. 1.3.5 The Architect/Engineer shall prepare presentation materials including an animation derived from the model(s) as defined in “Facility Design Guidelines” at completion of Design Development and if so requested shall present same to the Board of Regents at a regular meeting where scheduled within the state. 1.3.6 The Architect/Engineer shall prepare preliminary recommended furniture layouts for all spaces where it is deemed important to substantiate the fulfillment of program space requirements, or to coordinate with specific architectural, mechanical and electrical elements. 1.3.7 Architect/Engineer shall assist the Owner, if requested, with seeking approval of the Project by the Texas Higher Education Coordinating Board (THECB). Such assistance shall include (i) the preparation of a listing of the rooms and square footages in the Project, and (ii) the preparation of project cost information, in accordance with THECB Guidelines. This information shall be provided at the completion of the Design Development Phase when requested by the Owner. The listing of rooms and square footages shall then be updated to reflect any changes occurring during construction and provided to the Owner at Substantial Completion. 1.3.8 At the completion of the Design Development Phase, or such other time as Owner may specify to Architect/Engineer, at Owner’s sole option and discretion, Owner will furnish Architect/Engineer with a Guaranteed Maximum Price proposal prepared by Construction Manager based upon the Design Development documents prepared by the Architect/Engineer and approved by the Owner. The Architect/Engineer shall assist the Owner and endeavor to further and advocate the Owner’s interests in Owner’s communications with the Construction Manager in an effort to develop a Guaranteed Maximum Price proposal acceptable to Owner, in Owner’s sole option and discretion. If the Owner does not accept the Construction Manager’s Guaranteed Maximum Price proposal, the Architect/Engineer shall participate with the Owner and Construction Manager in constructability reviews and shall revise the documents as necessary in order to reach an agreement. If the Construction Manager’s Guaranteed Maximum Price proposal exceeds the Schematic Design Phase Estimated Construction Cost prepared by, or otherwise accepted by the Construction Manager due to an increase in the scope of the Project caused by further development of the design documents by the Architect/Engineer to the extent that such could not be reasonably inferred by the Construction Manager from the Schematic Design documents, and Owner directs Architect/Engineer to revise the documents, the Architect/Engineer shall revise the documents at its own expense so that the Guaranteed Maximum Price proposal for constructing the Project shall not exceed the Owner’s Amount Available for the Construction Contract and any previously approved Estimated Construction Costs. If it is determined to be in the Owner’s best interest, instead of requiring the Architect/Engineer to revise the Drawings and Specifications, the Owner reserves the right to accept a Guaranteed Maximum Price proposal that exceeds the stipulated Amount Available for the Construction Contract. The Architect/Engineer shall analyze the final Guaranteed Maximum Price proposal document, together with its supporting assumptions, clarifications, and contingencies, and shall submit a detailed written analysis of the document to the Owner. Such analysis shall include, without limitation, reference to and explanation of any inaccurate or improper assumptions and clarifications. The A/E will not be required to make revisions to the documents at its own expense under the provisions of this paragraph if the Owner’s rejection of the Guaranteed Maximum Price proposal is not due to a failure of the A/E to provide the services otherwise required herein. 1.3.9 After the Guaranteed Maximum Price has been accepted, the Architect/Engineer shall incorporate necessary revisions into the Design Development documents. The A/E will not be required to make revisions to the documents at its own expense under the provisions of this paragraph if the revisions are required as the result of inaccurate assumptions and clarifications made in the development of the Guaranteed Maximum Price proposal that are not due to a failure of the A/E to provide the services otherwise required herein.

  • Work Plan [Procuring Entity shall provide main features of the work plan that the Tenderer should provide in the tender for carrying out the contract, from beginning to the end].

  • Timescale It is recognised that discussions around actual salary increases have a dependency on top level Company decisions. However, it is agreed that more general discussions can start before this point, these will include: The Company providing the latest pay and benefit guidelines/comparators (if updated) By end of January Identify and attempt to agree deviations from information detailed in appendix 4. By 16th March The Company providing information as detailed in Appendix 4 (snapshot as of 1st April) (incorporating any agreed deviations from the standard list) By 10th April Joint team produce cost-model ready for negotiations By end of April Unite Submit and present to the Company negotiating team their annual pay claim By end of April Line Managers completing Appraisals (including Company checking of employees who don’t have a PAC) January – March where possible By end of April in all cases Company provides remainder of appraisal PAC information By 7th May Negotiate non-budget related matters By end May Once the Company decisions referred to above have been made, the pay negotiations can further progress. Steps will be taken earlier where practicable. Stage 1 negotiations Offer voted on by 14th June If required stage 2 negotiations Offer voted on by 30th June If required stage 3 negotiations Offer voted on by 14 th July Guidelines issued to line managers (following discussions between Unite & the Company) By 22nd July Pay planning complete By end July Pay review effective 1st August Company provides UNITE with information, snapshot at 1st August By 10th August Notification of pay review to individuals by managers Before August pay date At the start of the process, UNITE and the company will jointly review the timetable and agree any variations that are required.

  • Timeline Contractor must perform the Services and deliver the Deliverables according to the following timeline:

  • 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.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!