Modifications; Private Label Operations Manual Sample Clauses

Modifications; Private Label Operations Manual. (a) Sprint may from time to time modify, amend, change, update or supplement (x) the Facilities, (y) Sprint’s operations, equipment, software or procedures and (y) the Private Label Operations Manual; provided that with respect to any modifications, amendments, changes, updates or supplements that would reasonably be expected to require changes to, updates of or modifications to any SIG Party’s or any of its End Users’ Devices or other products, accessories, systems or procedures, Sprint shall (i) provide as much advance notice of the proposed modifications, amendments, changes, updates or supplements as is reasonably possible under the circumstances, (ii) thereafter and to the extent necessary, cooperate with such SIG Party in developing and executing a transition plan to reduce the impact of the proposed modifications, amendments, changes, updates or supplements on such SIG Party and its business, operations and End Users (including considering in good faith alternative means of accomplishing Sprint’s objectives that would have less of a burden on such SIG Party and its business, operations and End Users) and (iii) use commercially reasonable efforts to address the interoperability and compatibility of such SIG Party’s or its End Users’ Devices or other products, accessories, systems or procedures in existence prior to such modification, amendment, change, update, or supplement with Sprint’s operations, equipment, software, procedures, services and infrastructure following such modification, amendment, change, update or supplement (i.e., backwards compatibility) for a commercially reasonable period of time. Any such modification, amendment, change, update or supplement to the Facilities, Sprint’s operations, equipment, software, procedures or services or the Private Label Operations Manual shall not discriminate against any SIG Party or its businesses or operations relative to Sprint’s retail operations; provided that in the case of any modifications, amendments, changes, updates or supplements to the Private Label Operations Manual, such modifications, amendments, changes, updates or supplements must be made to the operations manuals of each other reseller and consistently applied across Sprint’s resale operations. Subject to Sprint’s compliance with the foregoing, Sprint will not be liable to any SIG Party or its End Users if such modifications, amendments, changes, updates or supplements require changes to, updates of or modifications to such SIG Part...
Sample 1
AutoNDA by SimpleDocs

Related to Modifications; Private Label Operations Manual

  • Operations Manual The Franchisor agrees to loan to the Franchisee one or more manuals, technical bulletins, cookbooks and recipes and other written materials (collectively referred to as “Operations Manual”) covering Factory Candy ordering, Store Candy manufacturing, processing and stocking and other operating and in-store marketing techniques for the ROCKY MOUNTAIN CHOCOLATE FACTORY Store. The Franchisee agrees that it shall comply with the Operations Manual as an essential aspect of its obligations under this Agreement, that the Operations Manual shall be deemed to be incorporated herein by reference and failure by the Franchisee to substantially comply with the Operations Manual may be considered by the Franchisor to be a breach of this Agreement.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA): (a) we are liable for any remedy or rebate specified by the SLA; and (b) subject to clauses 40 to 42, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.

  • Support and Services ISD and HC agree to the following conditions: A. HC agrees to the following for both the mathematics and English language arts courses: i. To share data and provide feedback regarding student success on entry‐level college mathematics and English language arts courses; ii. To train advisors to recognize and honor course(s) on school district transcripts; iii. To ensure that eligible students are counseled directly into college level mathematics, English language arts, and all other courses that require mathematics and English language arts college readiness; B. HC agrees to the following for the college preparatory mathematics courses: i. To provide the Student Learning Outcomes; ii. To provide the syllabi for the courses being offered. iii. To provide regular meetings between the HC faculty and ISD faculty teaching the course. C. HC agrees to the following for the college preparatory English language arts course: i. To provide the Student Learning Outcomes for Integrated Reading/Writing (INRW 0303) course; ii. To provide the syllabi, including types of essays required (i.e., expository, persuasive, and critical analysis). iii. To provide regular meetings between the HC faculty and ISD faculty teaching the course. D. ISD agrees to the following for both the mathematics and English language arts courses: i. To provide highly qualified instructors for the courses being taught; ii. To identify students who are not college ready as stated in HB 5; iii. To provide professional development and resources required to teach the mathematics and English language arts courses; iv. To identify successful completion of the course(s) on the student transcripts as determined by the State of Texas PEIMS number; v. To provide curriculum for the course that is consistent with HC Student Learning Outcomes; vi. To provide assistance with admission, enrollment, and financial aid applications; E. ISD agrees to the following for the college preparatory mathematics course: i. To teach a math course designed to focus on college mathematics (algebraic or non‐algebraic) concepts; ii. Require students to meet college readiness scores on the TSI Assessment; iii. To meet regularly with HC faculty. F. ISD agrees to the following for the college preparatory English language arts course: i. To teach an integrated Reading and Writing course that focuses on critical reading and college‐level writing; ii. Require students to meet college readiness scores on the TSI Assessment; iii. To meet regularly with HC faculty.

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