Scope of Deliverable Sample Clauses

Scope of Deliverable. 2.1 Contractor shall procure and install the field equipment for the Municipal Systems and TTC Initial System as set out in Final Design Review, the GTA Fare System Technical Specifications and the Project Blueprint.
Sample 1
Scope of Deliverable. 2.1 As described in GTA Fare System Technical Specification Part 10 – Launch 1 System (“Part 10”), the Launch 1 System is a proof-of-concept farecard based fare collection system that shall be implemented in advance of the full roll-out of the GTA Fare System (the “Launch 1 System”). In order to demonstrate this proof-of-concept, the Launch 1 System shall offer a subset of the functionality that will be provided by the GTA Fare System. The primary objective of the Launch 1 System is to test customer acceptance of farecards as a means of fare payment and demonstrate GTA Fare System functions and features ahead of the full roll out of the GTA Fare System. 2.2 Contractor shall implement the Launch 1 System to demonstrate and provide the necessary functionality to allow card holders to use the system in a realistic manner. 2.3 Contractor shall provide the Launch 1 System in compliance with the GTA Fare System Technical Specifications as referenced herein, within the specific confines of Part 10 of the GTA Fare System Technical Specifications.
Sample 1
Scope of Deliverable. 1.1 In accordance with the provisions of the Master Supply and Services Agreement, Contractor and Ministry shall collaborate on the development of the Project Blueprint.
Sample 1
Scope of Deliverable. 2.1 Contractor shall develop, implement, procure and install the various components of the Central System, including the GO Transit System and the Municipal Systems, as set out in Final Design Review, the GTA Fare System Technical Specifications and the Project Blueprint.
Sample 1
Scope of Deliverable. ‌ This deliverable is part of WP2 (Cognitive network & system architecture and de- sign), which is a research and technological development activity. The overall objective of this work package is to design a cognitive routing system and engine by combining machine learning and networking techniques in order to efficiently address the future In- xxxxxx challenges. This cognitive routing engine will enhance the existing routing system by combining machine learning methods that allow it to derive a number of observations from the data collected by its routing and forwarding engines and its interactions with other cognitive routing engines. The overall objective of this work package is drawn (i) from a set of networking use cases representative of the Internet challenges, and referred to as technical objectives, and (ii) from applying novel machine-learning mechanisms (by designing a cognitive engine) to these use cases so as to address these challenges. The first technical objective requires to develop adaptive methods for traffic xxx- pling in core networks in order to take the appropriate actions either at the router level or the network-wide level (based on the sampling and processing results). It is also necessary to monitor the path performances (e.g., delay, loss rate, etc.) Monitoring is performed by means of a collaborative measurement tool that can be used to determine the best suited routing strategies. Finally, a cooperative intrusion and attack / anomaly detection system is required. It consists on a distributed tool enabling anomaly, attack, and intrusion detection by monitoring traffic and detecting changes in the measure- ments. The second technical objective aims at determining the availability of the paths and their qualities. If a path is not reachable anymore, a resiliency mechanism ensures that the network recovers from the failure. Finally, the third technical objective aims at enforcing the quality requirements in a scalable way. To achieve these objectives, the architecture is composed of four parts: 1. An experimental prototype is implemented on the XORP routing platform as detailed deliverable D2.2 and consolidated by the present document. XORP is an open source routing platform. XORP provides a fully featured control-plane platform that imple- ments routing protocols and a unified platform to configure them. XORP’s modular architecture allows rapid introduction of new protocols, features, and functionalities. Our prototypes are imple...
Sample 1
Scope of Deliverable. 2.1 Contractor shall operate the Central System and shall provide all human, material and other resources required for the Operation of the Central System as set out in Final Design Review, the GTA Fare System Technical Specifications and the Project Blueprint.
Sample 1
Scope of Deliverable. 2.1 Contractor shall procure and install the field equipment for the GO Transit System as set out in Final Design Review, the GTA Fare System Technical Specifications and the Project Blueprint.
Sample 1

Related to Scope of Deliverable

  • SCOPE OF DELIVERY Seller agrees to accept deliveries of natural gas belonging to Buyer at Seller's delivery point from the upstream pipeline located near Columbia, South Carolina, and to transport Buyer's gas and redeliver to Buyer. Service provided hereunder is in lieu of natural gas provided from Seller's system supply to satisfy Buyer's fuel requirements in Priority-of-Service Category 3C. Xxxxx agrees that the transportation service is provided on an interruptible basis. Interruptions of transportation service shall be at the sole discretion of Seller or whenever service is interrupted by any upstream pipeline.

  • Description of Deliverables The Contractor shall Perform as set forth in Exhibit A.

  • Acceptance of Deliverables The State’s Project Manager shall be responsible for the sign-off acceptance of all Deliverables required and performed/submitted pursuant to this Agreement. Upon successful completion of a Deliverable, Contractor shall provide the State’s Project Manager with a completed Acceptance and Signoff Form (Exhibit E). The State’s Project Manager will apply the standards established in Exhibit D and the acceptance criteria set forth in subparagraph B of this article, as appropriate, to determine the acceptability of the Deliverable provided by Contractor. If the State’s Project Manager rejects the Deliverable, the parties agree to any dispute(s) resulting from such rejection(s) will be resolved as set forth in this article. Acceptance Criteria for Deliverables (“Criteria”) provided by Contractor pursuant to this Agreement include: Timeliness: The Work was provided on time; according to schedule; Completeness: The Deliverable contained all of the, Data, Materials, and features required by the Agreement; and Technical accuracy: The Deliverable complied with the standards of this Agreement, or, if this Agreement lacks a standard for provision of the Work, the currently generally accepted industry standard. Contractor shall provide the Deliverable to the State, in accordance with direction from the Project Manager and as provided for in Exhibit D. The State shall accept the Deliverable, provided that Contractor has delivered the Deliverable in accordance with the Criteria. The State’s Project Manager shall assign the Acceptance and Signoff Form to notify Contractor of the Deliverable’s acceptability. If the State rejects the Deliverable provided, the State’s Project Manager shall submit to Contractor’s Project Manager a written rejection describing in detail the failure of the Deliverable as measured against the Criteria. If the State rejects the Deliverable, then Contractor shall have a period of ten (10) Business Days from receipt of the Notice of rejection to correct the stated failure(s) to conform to the Criteria.

  • Ownership of Deliverables Unless otherwise agreed in this Agreement, Contractor hereby assigns to the JBE ownership of all Deliverables, any partially-completed Deliverables, and related work product or materials. Contractor agrees not to assert any rights at common law, or in equity, or establish a copyright claim in any of these materials. Contractor shall not publish or reproduce any Deliverable in whole or part, in any manner or form, or authorize others to do so, without the written consent of the JBE.

  • Date of Delivery Any notice so addressed shall be deemed to be given or received (i) if delivered by hand, on the date of such delivery, (ii) if mailed by courier or by overnight mail, on the first business day following the date of such mailing, and (iii) if mailed by registered or certified mail, on the third business day after the date of such mailing.

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • OWNERSHIP AND USE OF DELIVERABLES The City shall own all rights, titles, and interests throughout the world in and to the deliverables.

  • Time of Delivery Any notice delivered personally or by fax during normal business hours at an address specified above shall be deemed to be received the same Business Day, and any notice sent by mail or otherwise will be deemed to be received on the following Business Day. Any Party shall be entitled to change its address for notice to an address elsewhere in Alberta by notice in writing to the other Parties.

  • DATE OF DELIVERY OF PUT NOTICE A Put Notice shall be deemed delivered on (i) the Trading Day it is received by facsimile or otherwise by Investor if such notice is received on or prior to 12:00 noon New York time, or (ii) the immediately succeeding Trading Day if it is received by facsimile or otherwise after 12:00 noon New York time on a Trading Day or at anytime on a day which is not a Trading Day.

  • Contract Deliverables The Contractor shall provide information technology staff augmentation services, including comprehensive management of staff, as set forth in this Contract. The term “staff” refers to the temporary staff provided by the Contractor to render information technology services identified by Customers, but that staff shall not be deemed an employee of the State or deemed to be entitled to any benefits associated with such employment. Contracts resulting from this solicitation should not be structured as fixed-price agreements or used for any services requiring authorization for payment of milestone tasks. Contractor shall only provide information technology staff augmentation services for those Job Titles awarded to the Contractor and shall be paid on an hourly basis. The Department’s intent is for Contractor’s information technology staff to provide services closely related to those described in the Job Family Descriptions document. Detailed scopes of work, specific requirements of the work to be performed, and any requirements of staff shall be provided by the Customer in a Request for Quote. The Contractor shall possess the professional and technical staff necessary to allocate, outsource, and manage qualified information technology staff to perform the services requested by the Customer. The Contractor shall provide Customers with staff who must have sufficient skill and experience to perform the services assigned to them. All of the information technology staff augmentation services to be furnished by the Contractor under the Contract shall meet the professional standards and quality that prevails among information technology professionals in the same discipline and of similar knowledge and skill engaged in related work throughout Florida under the same or similar circumstances. The Contractor shall provide, at its own expense, training necessary for keeping Contractor’s staff abreast of industry advances and for maintaining proficiency in equipment and systems that are available on the commercial market. The Contractor shall be responsible for the administration and maintenance of all employment and payroll records, payroll processing, remittance of payroll and taxes, and all administrative tasks required by state and federal law associated with payment of staff. The Contractor shall, at its own expense, be responsible for adhering to the Contract background screening requirements, testing, evaluations, advertising, recruitment, and disciplinary actions of Contractor’s information technology staff. The Contractor shall maintain during the term of the Contract all licenses, permits, qualifications, insurance and approvals of whatever nature that are legally required to perform the information technology staff augmentation services.