Obligations of Parties Sample Clauses

Obligations of Parties. Nothing herein shall relieve a Party of its obligations under the Federal Rules, the Bankruptcy Rules, the Federal Rules of Evidence, and the Local Rules, or under any future stipulations and orders, regarding the production of documents or the making of timely responses to Discovery Requests in connection with the Cases.
AutoNDA by SimpleDocs
Obligations of Parties. Both Parties will participate in LNP testing in accordance with North American Numbering Council (NANC) standards. Both Parties will follow recommended National Emergency Number Association (NENA) standards for LNP until such time the standards are superceded by federal, state, or local legislation. Carrier is required to send to Frontier a completed Bona Fide Request Form for LNP deployment in non LNP capable offices. See Exhibit A. Carrier is responsible to coordinate with the local E911 and Public Services Answering Point (PSAP) coordinators to insure a seamless transfer of End User emergency services. Carrier is required to meet all mutually agreed upon testing dates and implementation schedules. Both Parties will perform testing as specified in industry guidelines and cooperate in conducting any additional testing to ensure interoperability between networks and systems. Each party shall inform the other Party of any system updates that may affect the other Party’s network and each Party shall, at the other Party’s request perform tests to validate the operation of the network. Each Party is responsible for the following: Adhere to all Number Portability Administration Center (NPAC) and North American Numbering Council (NANC) requirements and in providing its own access to regional NPAC. For providing its own access to the Service Order Administration (SOA). EXHIBIT A LOCAL NUMBER PORTABILITY (LNP) BONA FIDE REQUEST (BFR) DATE: (date of request) TO: (name of service provider) (address of service provider) (contact name /number) FROM: (requester/service provider name/ID) (requester/operating company number (OCN)) (requester switch(es)/CLLI) (authorized by name) (authorized by title) (contact name/address/number) Affidavit attesting requester as authorized agent should accompany request. SWITCH(ES): CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 All: Y or N All: Y or N All: Y or N All: Y or N All: Y or N Please provide Requestor’s information below: CARRIER/REQUESTOR: CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 DATES: Requested date switch(es) should be LNP capable: (mm/dd/yy) Requested code opening date: (mm/dd/yy) Notes: See following page. Acknowledgment of BFR is to be sent to the requester within ten business days. EXHIBIT A LOCAL NUMBER PORTABILITY (LNP) BONA FIDE REQUEST (BFR) (Continued) Notes: 1 List each switch targeted for LNP by its specific CLLI code. 2 Enter associated Rate Center information from LERG, including: Rate Ce...
Obligations of Parties. 1. Both parties will share in the education process.
Obligations of Parties. Both Parties will participate in LNP testing in accordance with North American Numbering Council (NANC) standards. Both Parties will follow recommended National Emergency Number Association (NENA) standards for LNP until such time the standards are superceded by federal, state, or local legislation. CLC is required to send to Frontier a completed Bona Fide Request Form for LNP deployment in non LNP capable offices. See Exhibit A. CLC is responsible to coordinate with the local E911 and Public Services Answering Point (PSAP) coordinators to insure a seamless transfer of End User emergency services. CLC is required to meet all mutually agreed upon testing dates and implementation schedules. Both Parties will perform testing as specified in industry guidelines and cooperate in conducting any additional testing to ensure interoperability between networks and systems. Each party shall inform the other Party of any system updates that may affect the other Party’s network and each Party shall, at the other Party’s request perform tests to validate the operation of the network. Each Party is responsible for the following: Adhere to all Number Portability Administration Center (NPAC) and North American Numbering Council (NANC) requirements and in providing its own access to regional NPAC. For providing its own access to the Service Order Administration (SOA). ATTACHMENT 5 UNBUNDLED NETWORK ELEMENTS ATTACHMENT 5 – UNBUNDLED NETWORK ELEMENTS
Obligations of Parties. (A) The Local Government agrees as follows:
Obligations of Parties. 3.1 Each Party must offer proof of its certification with applicable regional Number Portability Administration Center (NPAC) prior to requesting SPNP from the other Party.
Obligations of Parties. A. The Government, using funds and in-kind services provided by the Sponsor and funds appropriated by the Congress of the United States, shall expeditiously prosecute and complete the Study, in accordance with the provisions of this Agreement and Federal laws, regulations, and policies.
AutoNDA by SimpleDocs
Obligations of Parties. The District is under no obligation to make payroll deductions for periods during which a unit member is either terminated from active employment or not on the District's active payroll for any reason, including, but not limited to, layoff and voluntary leave of absence for more than thirty (30) days. Upon rehiring of any unit member, or upon the recalling of a unit member from layoff status, the District will resume or initiate dues or representation fee deductions for such member only upon a valid dues/representation fee deduction authorization as defined herein.
Obligations of Parties. 4.1. The Operator undertakes the following obligations:
Obligations of Parties. Each Party shall:
Time is Money Join Law Insider Premium to draft better contracts faster.