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.
Changes in Insurance Requirements Not more frequently than once annually, if in the opinion of District the amount of the foregoing insurance coverages is not adequate or the type of insurance or its coverage adequacy is deemed insufficient, Contractor shall amend the insurance coverage as required by District's Risk Manager or designee.
Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct the following activities in accordance with the indicated procedural and operational requirements: a. LPHA must operate its Communicable Disease program in accordance with the Requirements and Standards for the Control of Communicable Disease set forth in ORS Chapters 431, 432, 433 and 437 and OAR Chapter 333, Divisions 12, 17, 18, 19 and 24, as such statutes and rules may be amended from time to time. b. LPHA must use all reasonable means to investigate in a timely manner all reports of Reportable Diseases, infections, or conditions. To identify possible sources of infection and to carry out appropriate control measures, the LPHA Administrator shall investigate each report following procedures outlined in OHA’s Investigative Guidelines or other procedures approved by OHA. OHA may provide assistance in these investigations, in accordance with OAR 333-019-0000. Investigative guidelines are available at: xxxx://xxx.xxxxxx.xxx/oha/PH/DiseasesConditions/CommunicableDisease/ReportingCommuni cableDisease/ReportingGuidelines/Pages/index.aspx c. As part of its Communicable Disease control program, LPHA must, within its service area, investigate the Outbreaks of Communicable Diseases, institute appropriate Communicable Disease control measures, and submit required information in a timely manner regarding the Outbreak to OHA in Orpheus (or Opera for COVID-19 Cases and XXXXX for COVID-19 contacts) as prescribed in OHA CD Investigative Guidelines available at: d. LPHA must establish and maintain a single telephone number whereby physicians, hospitals, other health care providers, OHA and the public can report Communicable Diseases and Outbreaks to LPHA 24 hours a day, 365 days a year. LPHA may employ an answering service or 911 system, but the ten-digit number must be available to callers from outside the local emergency dispatch area, and LPHA must respond to and investigate reported Communicable Diseases and Outbreaks. e. LPHA must attend Communicable Disease 101 and Communicable Disease 303 training. f. LPHA must attend monthly Orpheus user group meetings or monthly Orpheus training webinars.
Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.
Financial Requirements A report of monthly and cumulative financial requirements; and
Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.
Operating Plan To Agent and Lenders, as soon as available, but not later than thirty (30) days after the end of each Fiscal Year, an annual combined operating plan (the "Operating Plan") for Parent and its Subsidiaries, approved by the Board of Directors of Parent, for the following Fiscal Year, which (i) includes a statement of all of the material assumptions on which such plan is based, (ii) includes projected monthly income statement, balance sheets and source and use of funds for the following year and (iii) Borrowing Availability projections, all prepared on the same basis and in similar detail as that on which operating results are reported (and in the case of cash flow projections, representing management's good faith estimates of future financial performance based on historical performance), and including plans for personnel, Capital Expenditures and facilities.
Financial Reporting Requirements The Charter School shall follow the financial requirements of the Charter Schools Section of the Department’s Financial Management for Georgia Local Units of Administration Manual. The Charter School shall submit all information required by the State Accounting Office for inclusion in the State of Georgia Comprehensive Annual Financial Report.
Staffing Plan The Board and the Association agree that optimum class size is an important aspect of the effective educational program. The Polk County School Staffing Plan shall be constructed each year according to the procedures set forth in Board Policy and, upon adoption, shall become Board Policy.
Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.
