Operating Code Sample Clauses

The Operating Code clause defines the specific rules, procedures, or standards that govern how certain operations or activities must be conducted under the agreement. Typically, this clause references a set of technical or procedural guidelines—such as industry standards, safety protocols, or internal company policies—that parties are required to follow during the performance of their contractual obligations. By clearly identifying the applicable operating code, this clause ensures consistency, safety, and compliance, thereby reducing the risk of misunderstandings or disputes about operational expectations.
Operating Code. The provisions of the Operating Code shall be applicable to the extent that the Operating Code expressly deals with certain provisions not contained herein. If the terms and conditions of this Agreement (including the Annexure and Exhibits attached hereto other than Operating Code) and the Operating Code are in conflict, the terms and conditions of this Agreement (including the Annexure and Exhibits attached hereto other than Operating Code) shall prevail.
View SourceView Similar (3)
Operating Code. The Operating Code shall apply to Transportation Service provided under this Framework Agreement and the relevant GTA.
View SourceView Similar (2)
Operating Code. The provisions of the Operating Code- Exhibit D shall be applicable to the extent that the Operating Code expressly deals with certain provisions not contained herein. If the terms and conditions of this Agreement (including the Annexure and Exhibits attached hereto other than Operating Code) and the Operating Code are in conflict, the terms and conditions of this Agreement (including the Annexure and Exhibits attached hereto other than Operating Code) shall prevail.
View Source
Operating Code. The Authority’s Operating Code, as it may be amended from time to time, is hereby incorporated into this Agreement by reference. The Contractor hereby agrees to comply strictly with the requirements contained in the Operating Code.
View Source

Related to Operating Code

  • Operating Rules 6.1 Merchant must comply with the Operating Rules, as the same may be amended from time to time. The Operating Rules may change with little or no advance notice to Merchant and Merchant will be bound by all such changes. If Merchant objects to any change in the Operating Rules, it must immediately stop accepting new Transactions for Cards governed by the change. The Operating Rules will govern in the event that there is any inconsistency between the Merchant Agreement and the Operating Rules. However, nothing in the Merchant Agreement shall be construed to impose on Merchant a requirement (including a requirement under the Operating Rules) which is prohibited by mandatory provisions of applicable law (i.e., where the applicability of such provisions of law to the Merchant Agreement, and of the law’s prohibition to the particular requirement which otherwise would be imposed on Merchant hereunder, cannot lawfully be waived by agreement), but the requirement hereunder shall be construed to continue in effect and to be imposed on Merchant in all respects and at all times to the fullest extent possible without violating the law’s prohibition, with only those particular applications of the requirement which would violate the law’s prohibition deemed severed from the provisions hereof. 6.2 Operating Rules of the Debit Networks may differ among them with respect to the Transactions they allow. Bank, at its discretion, may require that the most restrictive requirements of one Debit Network apply to all of Merchant’s On-line Debit Card Transactions, regardless of Card type.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Compliance with Texas Privacy Laws and Regulations In performing their respective obligations under the Agreement, the LEA and the Provider shall comply with all Texas laws and regulations pertaining to LEA data privacy and confidentiality, including but not limited to the Texas Education Code Chapter 32, and Texas Government Code Chapter 560.

  • Operational Requirements The Client will adhere to the deadlines and other operational requirements set out in the Client Publications, to facilitate meeting the requirements of CSD’s, Third Party Agents and Market Participants.

  • COMPLIANCE WITH GOVERNMENTAL RULES AND REGULATIONS; RECORDS The Trust assumes full responsibility for its compliance with all securities, tax, commodities and other laws, rules and regulations applicable to it.