Planned deliverables and delivery dates Sample Clauses

Planned deliverables and delivery dates. The ISG MEC will maintain and revise its specifications and produce new specifications to support capabilities such as: • Support for non-3GPP access technologies in terms of access specific network capability and information exposure to the applications • Expanding the support of virtualization (e.g. containers, Platform-as-a-Service, distributed virtualization) • Support for new charging models, in collaboration with the 3GPP and other relevant SDOs • Support for lawful interception, in collaboration with the 3GPP and ETSI XX XX. New compelling use cases may identify additional missing parts that the ISG will agree to work on. The ISG will produce specifications that will support the additional requirements. Depending on the Agreement with the ETSI NFV ISG, the MEC ISG may work on normative reference points which will support the integration of MEC in NFV environment. In addition, the ISG plans to develop specifications on testing and test methodologies. All work in ISG MEC, including what has been outlined above, will be further described in their related work item proposals that will be submitted for approval by the ISG MEC. The proposed target delivery dates (completion) of the ISG MEC deliverables will be agreed when the New Work Items (NWIs) are accepted. It is expected that the specifications will be drawn up during 2017 and 2018.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Planned deliverables and delivery dates. ISG CIM intends to meet monthly (physical and/or electronic meetings) as needed to draft, discuss, review and approve the deliverables to be developed. ISG CIM plans to develop an ISG CIM Group Report (informative) and several ISG CIM Group Specifications (normative). A detailed plan will be made in the first meeting when Work Items will be discussed. According to the ISG CIM time plan, the intent is to finalize an ISG CIM Group Report (GR) and a set of ISG CIM Group Specifications (GS) within one (1) year after the first meeting. The initial plan involves delivering the following results: − (T0+01) Liaisons to major organisations informing of the work and requesting comment/input. Invite participation/membership. − (T0+03) Group Report describing the overall architecture and identifying standardization gaps − (T0+03) Joint f2f-workshop (with webinar attendance possible) with ETSI SmartM2M and possibly other organisations. − (T0+05) Group Specification for a Context Information Management API (preliminary) together with a preliminary example data model (e.g. tourism) − (T0+05) Group Specification for Data Publication platforms to support CIM-API required metadata. − (T0+05) Group Specification of languages, processes and domains for data modelling − (T0+07) Group Specification: First set of data models (e.g. mobility, participation, tourism) − (T0+09) Group Specification for a Context Information Management API (v1.0) − (T0+09) Group Specification: Second set of data models − (T0+12) Group Specification: Third set of data models − (T0+12) ISG CIM Review of Work and proposal to ETSI for next period − (T0+18) Review of suitability of the Group Specifications and data models based on evidence gathered from (open source) software implementations − (T0+22) If needed: Create and publish Version 2 of the Group Specifications based on the previous Review. − (T0+24) ISG CIM Review of Work and (if needed) proposal to ETSI for next period To maintain a tight focus, the ISG CIM will at the end of the first and of the second year make a review of its work and a proposal to ETSI on how to evolve the ISG CIM’s future activities: • terminate the ISG, or • transfer the work and continue the activity in a (existing or new) ETSI Technical Body or other standards body, or • continue the ISG CIM for an additional period with (potentially revised) Terms of Reference.
Sample 1

Related to Planned deliverables and delivery dates

  • Tasks and Deliverables A description of and the schedule for each task and deliverable, illustrated by a Xxxxx chart. Start and completion dates for each task, milestone, and deliverable shall be indicated. Must include deliverables specified in SOW-RFP as well as other deliverables that may be proposed by Contractor.

  • Services and Deliverables The Services and the required Deliverables for the Services are specified below. SPID: Service outlet: MDS ID: Funding ID: Service Type Output Measure Quantity per annum Number of Service Users Funding amount per annum (excl. GST) $ $ $ Description of Services Funding amount one-off (excl. GST) $ Geographic Catchment Area: SPID: Service outlet: MDS ID: Funding ID: Service Type Output Measure Quantity per annum Number of Service Users Funding amount (excl. GST) $ $ $ Description of Services Funding amount one-off (excl. GST) $ Geographic Catchment Area: *Note: Refer to clause 4.3 in the Funding and Service Details about permitted variations in Output Quantities.

  • Scope of Work and Deliverables 9.1 Background and Scope

  • Reports and deliverables 1. The consortium shall submit a periodic report to the REA for each reporting period within 60 days after the end of each respective period. The report shall comprise:

  • Shipment and Delivery Seller grants the Company the right at any time to specify the carrier and/or method of transportation to be employed in conveying any part or all of the Goods covered herein. In the event that Seller uses an unauthorized carrier and/or method of transportation, then all shipping expenses shall be assumed by Seller. Unless otherwise stated in the Order, all Goods will be shipped FCA shipment point. FCA shall be interpreted in accordance with the version of Incoterms valid at the time of the Seller’s acceptance of the Order. The Seller shall be responsible for preparing and filing all export documentation for all shipments. The Company shall not be obligated to accept early deliveries, partial deliveries or excess deliveries. If Goods are incorrectly delivered, the Seller shall be responsible for any additional expense incurred in delivering the Goods to the correct destination. The delivery date set forth on the Order is of the essence of the Contract. If the Seller anticipates that it will not be able to deliver the Goods upon the agreed delivery date, then the Seller shall immediately notify the Company thereof in writing; provided, however, that such notice shall not relieve the Seller of its responsibilities and liabilities with respect to on-time delivery hereunder. In such event, the Company may request that the Seller expedite delivery to the maximum extent possible at the Seller’s sole expense. If the Seller does not deliver the Goods by the agreed delivery date, then the Company shall be entitled to liquidated damages as agreed between the parties, up to and including the total Order value. Notwithstanding the foregoing, the Company reserves the right to claim repayment for any and all costs, losses, expenses and damages incurred by the Company that are attributable to the Seller’s delay in delivery. Such liquidated damages shall be paid at the Company’s written demand. Partial deliveries shall not relieve the Seller from liability for any late delivery hereunder. If the Seller discovers that it has shipped any non-conforming Goods to the Company, it shall immediately (and not more than 24 hours after such discovery) notify the Company thereof in writing; provided, however, that such notice shall not relieve the Seller of its responsibilities and liabilities with respect to defective goods hereunder.

  • License and Delivery a. Subject to Customer's compliance with the terms of this Agreement, including payment of fees, for any Software delivered to Customer, Licensor grants Customer a limited, non- transferable, non-sublicensable, non-exclusive license to install, run, and use the Number of Units of Software stated in an Order Form in accordance with the Documentation for the Term solely for Customer's internal business purposes. Maintenance, if purchased or provided, is delivered pursuant to the Order Form.

  • Project Delivery Contractor shall construct the Project in accordance with the Contract Documents, and Contractor shall deliver the Project completed in accordance with the Contract Documents, substantially free from defects, and within the Contract Time.

  • Orders and Delivery 7.1 The Post Office will from time to time, please written orders by way of the Purchase Orders with the Service Provider in respect of Goods.

  • Order and Delivery The Contract shall bind the Contractor to furnish and deliver the Goods or Services in accordance with Exhibit A and at the prices set forth in Exhibit B. Subject to the sections in this Contract concerning Force Majeure, Termination and Open Market Purchases, the Contract shall bind the Client Agency to order the Goods or Services from the Contractor, and to pay for the accepted Goods or Services in accordance with Exhibit B.

  • Required Acceptance of Daily Load Deliveries and Notification If the State is harmed by purchaser’s refusal to accept up to 10 truck deliveries of any one sort per day, Purchaser will be in breach of contract and subject to damages as per the D-026.2 and D-027.2 clauses. A truck delivery is all the wood delivered including sorts on super trucks, mule trains and pups brought to the delivery point by a single truck. The Purchaser shall notify the Contract Administrator at least 48 hours in advance if:

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