Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes.
8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities.
8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs.
8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs.
8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.
CLEC to CLEC Conversions for Unbundled Loops 2.1.10.1 The CLEC to CLEC conversion process for unbundled Loops may be used by Lightyear when converting an existing unbundled Loop from another CLEC for the same end user. The Loop type being converted must be included in Lightyear’s Interconnection Agreement before requesting a conversion.
2.1.10.2 To utilize the CLEC to CLEC conversion process, the Loop being converted must be the same Loop type with no requested changes to the Loop, must serve the same end user location from the same serving wire center, and must not require an outside dispatch to provision.
2.1.10.3 The Loops converted to Lightyear pursuant to the CLEC to CLEC conversion process shall be provisioned in the same manner and with the same functionality and options as described in this Attachment for the specific Loop type. Order Coordination (OC) Order Coordination – Time Specific (OC-TS) Test Points DLR Charge for Dispatch and Testing if No Trouble Found SL-1 (Non- Designed) Chargeable Option Chargeable Option Not available Chargeable Option – ordered as Engineering Information Document Charged for Dispatch inside and outside Central Office UCL-ND (Non- Designed) Chargeable Option Not Available Not Available Chargeable Option – ordered as Engineering Information Document Charged for Dispatch inside and outside Central Office Unbundled Voice Loops - SL-2 (including 2- and 4-wire UVL) (Designed) Included Chargeable Option Included Included Charged for Dispatch outside Central Office Unbundled Digital Loop (Designed) Included Chargeable Option (except on Universal Digital Channel) Included (where appropriate) Included Charged for Dispatch outside Central Office Unbundled Copper Loop (Designed) Chargeable in accordance with Section 2 Not available Included Included Charged for Dispatch outside Central Office For UVL-SL1 and UCLs, Lightyear must order and will be billed for both OC and OC-TS if requesting OC-TS.
List of Members Upon written request of any Member, the Managers shall provide a list showing the names, addresses and Percentage Interests of all Members in the Company.
Condominiums/Planned Unit Developments If the Mortgaged Property is a condominium unit or a planned unit development (other than a de minimis planned unit development) such condominium or planned unit development project such Mortgage Loan was originated in accordance with, and the Mortgaged Property meets the guidelines set forth in the Originator's Underwriting Guidelines;
Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
Management meetings 31.1 Either the Engineer or the Contractor may require the other to attend a management meeting. The business of a management meeting shall be to review the plans for remaining work and to deal with matters raised in accordance with the early warning procedure.
31.2 The Engineer shall record the business of management meetings and is to provide copies of his record to those attending the meeting and to the Employer. The responsibility of the parties for actions to be taken is to be decided by the Engineer either at the management meeting or after the management meeting and stated in writing to all who attended the meeting.
Labour Management Meetings The committee meeting shall normally be held every second month however, either party may call a meeting of the Joint Labour Management Committee. The meeting shall be held at a time and place fixed by mutual agreement but no later than fourteen (14) calendar days after the initial request, unless mutually agreed.
Partnership Name The name of the Partnership is “OZ Management LP.” The name of the Partnership may be changed from time to time by the General Partner.
Parent-Teacher Conferences A. Unit member shall be available at mutually arranged times during the regular school day to confer with parents regarding learning difficulties, student progress and/or behavioral problems a student may be experiencing. Unit members are encouraged to arrange a meeting or conference with parents before or after the regular school day if both time and place are mutually agreeable.
B. In the event that a bargaining unit member does not communicate with a parent on the established date for parent unit member conferences as per the calendar adopted by the Board, a reasonable attempt to contact that parent will be made. A reasonable attempt constitutes a phone call or email. If that contact is not returned, the bargaining unit member shall not be obligated to make further contact.
S&P Standard & Poor’s Ratings Services, a division of The XxXxxx-Xxxx Companies, Inc., or its successor.
