Eligible User’s COOP Sample Clauses

Eligible User’s COOP. When writing the COOP, the Contractor shall coordinate with the Eligible User and shall integrate the specific needs and processes of the Eligible User into the Contractor’s COOP. If requested by the Eligible User, the SLA shall include adjustments to the Contractor’s COOP.
AutoNDA by SimpleDocs

Related to Eligible User’s COOP

  • 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

  • LEAST RESTRICTIVE ENVIRONMENT/DUAL ENROLLMENT CONTRACTOR and XXX shall follow all LEA policies and procedures that support Least Restrictive Environment (“LRE”) options and/or dual enrollment options if available and appropriate, for students to have access to the general curriculum and to be educated with their nondisabled peers to the maximum extent appropriate. CONTRACTOR and XXX shall ensure that LRE placement options are addressed at all IEP team meetings regarding students for whom ISAs have been or may be executed. This shall include IEP team consideration of supplementary aids and services, goals and objectives necessary for placement in the LRE and necessary to enable students to transition to less restrictive settings. When an IEP team has determined that a student should be transitioned into the public school setting, CONTRACTOR shall assist the LEA in implementing the IEP team’s recommended activities to support the transition.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • 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.

  • Acceptable Use Policy The Services must be used in accordance with RingCentral’s Acceptable Use Policy, available at xxxxx://xxx.xxxxxxxxxxx.xxx/legal/acceptable-use-policy.html. Notwithstanding anything to the contrary in this Agreement, RingCentral may act immediately and without notice to suspend or limit the Services if RingCentral reasonably suspects fraudulent or illegal activity in the Customer’s Account, material breach of the Acceptable Use Policy, or use of the Services that could interfere with the functioning of the RingCentral Network provided such suspension or limitation may only be to the extent reasonably necessary to protect against the applicable condition, activity, or use. RingCentral will promptly remove the suspension or limitation as soon as the condition, activity or use is resolved and mitigated in full. If Customer anticipates legitimate but unusual activity on its Account, Customer should contact Customer Care in advance to avoid any Service disruption.

  • 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.

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

  • Use of Basement and Service Areas The basement(s) and service areas, if any, as located within the

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.1.3.1 Definition 4.1.3.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for <<customer_name>> when <<customer_name>> serves end-users with four (4) or more voice-grade (DS-0) equivalents or lines in locations served by BellSouth’s local circuit switches, which are in the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non-discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.1.3.3 In the event that <<customer_name>> orders local circuit switching for a single end user account name at a single physical end user location with four (4) or more 2-wire voice-grade loops from a BellSouth central office in an MSA listed above, BellSouth shall charge <<customer_name>> the market based rate in Exhibit C for use of the local circuit switching functionality for the affected facilities. 4.1.3.4 A featureless port is one that has a line port, switching facilities, and an interoffice port. A featured port is a port that includes all features then capable or a number of then capable features specifically requested by <<customer_name>>. Any features that are not currently then capable but are technically feasible through the switch can be requested through the NBR/BFR process. 4.1.3.5 BellSouth will provide to <<customer_name>> customized routing of calls: (i) to a requested directory assistance services platform; (ii) to an operator services platform pursuant to Section 10 of Attachment 2; (iii) for <<customer_name>>’s PIC’ed toll traffic in a two (2) PIC environment to an alternative OS/DA platform designated by <<customer_name>>. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers. 4.1.3.6 Remote Switching Module functionality is included in Switching Capability. The switching capabilities used will be based on the line side features they support. 4.1.3.7 Switching Capability will also be capable of routing local, intraLATA, interLATA, and calls to international customer’s preferred carrier; call features (e.g. call forwarding) and Centrex capabilities. 4.1.3.8 Where required to do so in order to comply with an effective Commission order, BellSouth will provide to <<customer_name>> purchasing local BellSouth switching and reselling BellSouth local exchange service under Attachment 1, selective routing of calls to a requested directory assistance services platform or operator services platform. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers, but obtain a <<customer_name>> branded service.

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment. 5.2 If a ECI Customer is served by resold Verizon dial tone line Telecommunications Service or a Verizon Local Switching UNE, to the extent reasonably feasible, Verizon will route Voice Information Service Traffic originating from such Service or UNE to the appropriate Voice Information Service connected to Verizon’s network unless a feature blocking such Voice Information Service Traffic has been installed. For such Voice Information Service Traffic, ECI shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to ECI. ECI shall pay Verizon such charges in full regardless of whether or not ECI collects such charges from its Customer. 5.3 ECI shall have the option to route Voice Information Service Traffic that originates on its own network to the appropriate Voice Information Service connected to Verizon’s network. In the event ECI exercises such option, ECI will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow ECI to route Voice Information Service Traffic originated on its network to Verizon. For such Voice Information Service Traffic, unless ECI has entered into a written agreement with Verizon under which ECI will collect from ECI’s Customer and remit to Verizon the Voice Information Service provider’s charges, ECI shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to ECI. ECI shall pay Verizon such charges in full regardless of whether or not ECI collects such charges from its own Customer.

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