Task T5 Sample Clauses

Task T5. 3: The ENVISAGE Work Flow (Lead: FRH)
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. 8: 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 ...

Related to Task T5

  • TECHNICAL TASKS Products that require a draft version are indicated by marking “(draft and final)” after the product name in the “Products” section of the task/subtask. If “(draft and final)” does not appear after the product name, only a final version of the product is required. Subtask 1.1 (Products) describes the procedure for submitting products to the CAM.

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

  • Master Contract Sales Reporting System Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile.

  • ANNUAL MASTER CONTRACT SALES REPORT Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by MS Excel.

  • TASK 1 GENERAL PROJECT TASKS PRODUCTS

  • 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 Services 3.3.1 Based on the Owner’s approval of the Schematic Design Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

  • Design Development Phase INDICATE IN STATEMENT OF WORK “NOT APPLICABLE” IF SECTION IS NOT APPLICABLE

Time is Money Join Law Insider Premium to draft better contracts faster.