Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.2 When One-Way or Two-Way Interconnection Trunks are provisioned using a DS3 interface facility, if Onvoy orders the multiplexed DS3 facilities to a Frontier Central Office that is not designated in the NECA 4 Tariff as the appropriate Intermediate Hub location (i.e., the Intermediate Hub location in the appropriate Tandem subtending area based on the LERG), and the provision of such facilities to the subject Central Office is technically feasible, the Parties shall negotiate in good faith reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.3 Each Party will identify its Carrier Identification Code, a three or four digit numeric code obtained from Telcordia, to the other Party when ordering a trunk group. 5.2.4 For multi-frequency (MF) signaling each Party will out pulse ten (10) digits to the other Party, unless the Parties mutually agree otherwise. 5.2.5 Each Party will use commercially reasonable efforts to monitor trunk groups under its control and to augment those groups using generally accepted trunk- engineering standards so as to not exceed blocking objectives. Each Party agrees to use modular trunk-engineering techniques for trunks subject to this Attachment.
Permitted Uses and Disclosures of Phi by Business Associate Except as otherwise indicated in this Agreement, Business Associate may use or disclose PHI, inclusive of de-identified data derived from such PHI, only to perform functions, activities or services specified in this Agreement on behalf of DHCS, provided that such use or disclosure would not violate HIPAA or other applicable laws if done by DHCS.
Skidding and Yarding Methods of skid- ding or yarding specified for particular areas, if any, are indicated on Sale Area Map. Outside Clearcutting Units and construction clearings, insofar as ground conditions permit, products shall not be skidded against reserve trees or groups of reproduction and tractors shall be equipped with a winch to facilitate skidding. B6.421 Rigging. Insofar as practicable, needed rigging shall be slung on stumps or trees desig- nated for cutting.
Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.
Compliance with Consensus Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <xxxx://xxx.xxxxx.xxx/general/consensus-‐policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”).
SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.
Use of Interconnection Facilities by Third Parties 6551 Error! Hyperlink reference not valid.9.9.1 Purpose of Interconnection Facilities. 6551
Permitted Uses and Disclosures by Business Associate Except as otherwise limited by this Agreement, Business Associate may make any uses and disclosures of Protected Health Information necessary to perform its services to Covered Entity and otherwise meet its obligations under this Agreement, if such use or disclosure would not violate the Privacy Rule if done by Covered Entity. All other uses or disclosures by Business Associate not authorized by this Agreement or by specific instruction of Covered Entity are prohibited.
Permitted Uses and Disclosure by Business Associate (1) General Use and Disclosure Provisions Except as otherwise limited in this Section of the Contract, Business Associate may use or disclose PHI to perform functions, activities, or services for, or on behalf of, Covered Entity as specified in this Contract, provided that such use or disclosure would not violate the HIPAA Standards if done by Covered Entity or the minimum necessary policies and procedures of the Covered Entity.
Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service and Capacity Resource Interconnection Service to Interconnection Customer at the Point of Interconnection. 1.3.2 This Agreement does not constitute an agreement to purchase or deliver the Interconnection Customer’s power. The purchase or delivery of power and other services that the Interconnection Customer may require will be covered under separate agreements, if any, or applicable provisions of NYISO’s or Connecting Transmission Owner’s tariffs. The Interconnection Customer will be responsible for separately making all necessary arrangements (including scheduling) for delivery of electricity in accordance with the applicable provisions of the ISO OATT and Connecting Transmission Owner’s tariff. The execution of this Agreement does not constitute a request for, nor agreement to, provide Energy, any Ancillary Services or Installed Capacity under the NYISO Services Tariff or any Connecting Transmission Owner’s tariff. If Interconnection Customer wishes to supply or purchase Energy, Installed Capacity or Ancillary Services, then Interconnection Customer will make application to do so in accordance with the NYISO Services Tariff or Connecting Transmission Owner’s tariff.
