Unidentified Features Encountered During Development Sample Clauses

Unidentified Features Encountered During Development. Activities If a previously unidentified cultural heritage resource is encountered by the Agreement holder while conducting a forest practice, operations will be modified or cease to the extent necessary to protect the resource, until a cultural heritage resource evaluation can be carried out.
AutoNDA by SimpleDocs

Related to Unidentified Features Encountered During Development

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Transit Traffic 7.2.2.3.1 CenturyLink will accept traffic originated by CLEC’s network and/or its end user(s) for termination to other Telecommunications Carrier’s network and/or its end users that is connected to CenturyLink's Switch. CenturyLink will also terminate traffic from these other Telecommunications Carriers’ network and/or its end users to CLEC’s network and/or its end users. For purposes of the Agreement, transit traffic does not include traffic carried by Interexchange Carriers. That traffic is defined as Jointly Provided Switched Access. 7.2.2.3.2 The Parties involved in transporting transit traffic will deliver calls to each involved network with CCS/SS7 protocol and the appropriate ISUP/TCAP messages to facilitate full Interoperability and Billing functions. 7.2.2.3.3 The originating company is responsible for payment of appropriate rates to the transit company and to the terminating company. The Parties agree to enter into traffic exchange agreements with third party Telecommunications Carriers prior to delivering traffic to be transited to third party Telecommunications Carriers. In the event one Party originates traffic that transits the second Party’s network to reach a third party Telecommunications Carrier with whom the originating Party does not have a traffic exchange agreement, then the originating Party will indemnify, defend and hold harmless the second Party against any and all charges levied by such third party Telecommunications Carrier, including any termination charges related to such traffic and any attorneys fees and expenses. In the case of IntraLATA LEC Toll traffic where CenturyLink is the designated IntraLATA Toll provider for existing LECs, CenturyLink will be responsible for payment of appropriate usage rates. 7.2.2.3.4 When CenturyLink receives an unqueried call from CLEC to a telephone number that has been ported to another local services provider, the transit rate will apply in addition to any query rates. 7.2.2.3.5 In the case of a transit call that terminates in the Local Calling Area but in a different state than the call originated, and the CLEC does not have an agreement with CenturyLink in the state where the transit call terminated, CLEC must execute an agreement for that state if it is a state served by CenturyLink. In the absence of a second agreement, the transit rate in Exhibit A of this Agreement will be billed to the CLEC.

  • EVENTS OUTSIDE OUR CONTROL 10.1 We will not be liable or responsible for any failure to perform, or delay in performance of, any of our obligations under this XXXX that is caused by any act or event beyond our reasonable control, including failure of public or private telecommunications networks (Event Outside Our Control). 10.2 If an Event Outside Our Control takes place that affects the performance of our obligations under this XXXX: (a) our obligations under this XXXX will be suspended and the time for performance of our obligations will be extended for the duration of the Event Outside Our Control; and (b) we will use our reasonable endeavours to find a solution by which our obligations under this XXXX may be performed despite the Event Outside Our Control.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Tandem Transit Traffic ‌ 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that Xxxxx has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

  • Interconnection Customer Compensation for Actions During Emergency Condition The CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff for its provision of real and reactive power and other Emergency Condition services that the Interconnection Customer provides to support the CAISO Controlled Grid during an Emergency Condition in accordance with Article 11.6.

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