Ordering Services API Sample Clauses
Ordering Services API. Description of Item/Unit of Measure Frequency Fee
Related to Ordering Services API
Ordering Services a) By submitting an Order to Megaport: 1. Customer warrants that the information Customer provides to Megaport in an Order is true and correct and that Megaport may rely upon it; and 2. Customer is making a binding offer to acquire the Services described in the Order on the terms set out in this Agreement, which Megaport may accept at its discretion. An agreement to supply a Service is formed on the date Megaport provisions that Service and charges apply from the Billing Commencement Date.
Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].
Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.
Monitoring Services IDT staff shall, using methods that include face-to-face and other contacts with the member, monitor the services a member receives. This monitoring shall ensure that: a. The member receives the services and supports authorized, arranged for and coordinated by the IDT staff; b. The services and supports identified in the MCP as being provided by natural and community supports are being provided; and c. The quality of the services and supports received is adequate and still necessary to continue to meet the needs and preferences of the member and support the member’s outcomes identified in the MCP.
Engineering Services Definition: Engineering Services includes any service or creative work, the adequate performance of which requires education, training and experience in the application of special knowledge in consulting, investigating, evaluating, planning and designing, engineering principles. Engineering Services covered by the ▇▇▇▇▇▇ Architect-Engineers Act (40 U.S.C. 1102) are not covered in the primary scope of OASIS SB. Examples: Service areas that are included under the Engineering Services discipline include, but are not limited to the following: 1. Systems Engineering 2. Advanced Technology Pilots and Trials 3. Alternative Energy Sources and Engineering 4. Configuration Management 5. Concept Development