Basic 911 and E911 Database Requirements Sample Clauses

Basic 911 and E911 Database Requirements. (a) The ALI database shall be managed by CenturyLink, but is the property of CenturyLink and CLEC for those records provided by CLEC. (b) To the extent allowed by the governmental agency, and where available, copies of the SIG shall be provided within three Business Days from the time requested and provided on diskette, or in a format suitable for use with desktop computers. (c) CLEC shall be solely responsible for providing CLEC database records to CenturyLink for inclusion in CenturyLink’s ALI database on a timely basis. (d) CenturyLink and CLEC shall arrange for the automated input and periodic updating of the E911 database information related to CLEC end users. CenturyLink shall work cooperatively with CLEC to ensure the accuracy of the data transfer by verifying it against the SIG. CenturyLink shall accept electronically transmitted files that conform to NENA Version #2 format. (e) CLEC shall assign an E911 database coordinator charged with the responsibility of forwarding CLEC end user ALI record information to CenturyLink or via a third-party entity, charged with the responsibility of ALI record transfer. CLEC assumes all responsibility for the accuracy of the data that CLEC provides to CenturyLink. (f) CLEC shall provide information on new subscribers to CenturyLink within one (1) business day of the order completion. CenturyLink shall update the database within two (2) Business Days of receiving the data from CLEC. If CenturyLink detects an error in the CLEC provided data, the data shall be returned to CLEC within two (2) Business Days from when it was provided to CenturyLink. CLEC shall respond to requests from CenturyLink to make corrections to database record errors by uploading corrected records within two (2) Business Days. Manual entry shall be allowed only in the event that the system is not functioning properly. (g) CenturyLink agrees to treat all data on CLEC subscribers provided under this Agreement as confidential and to use data on CLEC subscribers only for the purpose of providing E911 services.
Sample 1Sample 2
AutoNDA by SimpleDocs
Basic 911 and E911 Database Requirements. (a) The ALI database shall be managed by Embarq, but is the property of Embarq and CLEC for those records provided by CLEC. (b) To the extent allowed by the governmental agency, and where available, copies of the SIG shall be provided within three Business Days from the time requested and provided on diskette, or in a format suitable for use with desktop computers. (c) CLEC shall be solely responsible for providing CLEC database records to Embarq for inclusion in Embarq’s ALI database on a timely basis. (d) Embarq and CLEC shall arrange for the automated input and periodic updating of the E911 database information related to CLEC end users. Embarq shall work cooperatively with CLEC to ensure the accuracy of the data transfer by verifying it against the SIG. Embarq
Sample 1
Basic 911 and E911 Database Requirements. (a) The ALI database shall be managed by Embarq, but is the property of Embarq and CLEC for those records provided by CLEC. (b) To the extent allowed by the governmental agency, and where available, copies of the SIG shall be provided within three Business Days from the time requested and provided on diskette, or in a format suitable for use with desktop computers. (c) CLEC shall be solely responsible for providing CLEC database records to Embarq for inclusion in Embarq’s ALI database on a timely basis. (d) Embarq and CLEC shall arrange for the automated input and periodic updating of the E911 database information related to CLEC end users. Embarq shall work cooperatively with CLEC to ensure the accuracy of the data transfer by verifying it against the SIG. Embarq shall accept electronically transmitted files that conform to NENA Version #2 format. (e) CLEC shall assign an E911 database coordinator charged with the responsibility of forwarding CLEC end user XXX record information to Embarq or via a third- party entity, charged with the responsibility of ALI record transfer. CLEC assumes all responsibility for the accuracy of the data that CLEC provides to Embarq. (f) CLEC shall provide information on new subscribers to Embarq within one (1) business day of the order completion. Embarq shall update the database within two (2) Business Days of receiving the data from CLEC. If Embarq detects an error in the CLEC provided data, the data shall be returned to CLEC within two
Sample 1
Basic 911 and E911 Database Requirements. 2.3.1 Where ACS-ANC is the primary 911-service provider or is otherwise responsible for maintaining the E911 database for any service area covered under this agreement, ACS-ANC will be responsible for maintaining the E911 database(s) for XXXXX 0. XXXXX 0 xxxxx xx solely responsible for providing XXXXX 0 database records to ACS-ANC for inclusion in the E911 database. LEVEL 3 shall provide database records according to a format provided by ACS-ANC. ACS-ANC shall accept electronic updates from LEVEL 3 no less frequently than daily. The National Emergency Number Association (“NENA”) code for XXXXX 0 xx “XXXXX 0” (XXXXX 0 followed by two (2) spaces). ACS-ANC shall work cooperatively with LEVEL 3 to ensure the accuracy of the data transfer by verifying it against the Master Street Address Guide (MSAG). If ACS-ANC detects an error in LEVEL 3 provided data, the data shall be returned to LEVEL 3 within one (1) business day of the time the error was detected. LEVEL 3 shall respond to requests from ACS-ANC to make corrections to errors by providing corrected records within two (2) business days. ACS-ANC shall update the database with LEVEL 3 records within one (1) business day or with the same frequency that ACS-ANC updates the database with its own records, whichever is less. These time frames are guidelines and are established in the interest of public safety. ACS-ANC will make every effort to meet these response times; however, LEVEL 3 recognizes that seasonal impacts or other extraordinary circumstances may impact ACS-ANC’s ability to meet these requirements. Where ACS-ANC is responsible for maintaining the E911 routing database for any service area covered under this agreement, ACS-ANC will be responsible for maintaining the E911 routing database for LEVEL 3. 2.3.2 LEVEL 3 shall assign an E911 database coordinator charged with the responsibility of forwarding LEVEL 3 end user ANI/ALI record information to ACS-ANC or via a third-party entity, charged with the responsibility of ANI/ALI record transfer. LEVEL 3 assumes all responsibility for the accuracy of the data that LEVEL 3 provides to ACS-ANC. ACS-ANC and LEVEL 3 shall jointly research each ANI/ALI discrepancy report. Corrective action shall be taken immediately by the responsible party. 2.3.3 XXXXX 0 will provide the Emergency Service Bureaus with a single point of contact for inquiries about LEVEL 3’s customers. 2.3.4 Where there are multiple ANI/ALI databases involved, ACS-ANC will provide a single point o...
Sample 1
Basic 911 and E911 Database Requirements. 10.3.1 The telephone number (“TN”) data is managed in ALI/DBMS by BellSouth, but the responsibility for providing the data resides with each Local Service Provider. 10.3.2 Copies of the MSAG shall be provided within ten (10) business days from the time requested and provided on CD-ROM or such other medium as the Parties may agree. 10.3.3 Universal shall be solely responsible for providing Universal database records to BellSouth for inclusion in BellSouth’s ALI/DBMS database on a timely basis. 10.3.4 BellSouth and Universal shall arrange for the automated input and periodic updating of the E911 database information related to Universal End Users as stated in the BellSouth E911 Local Exchange Carrier Guide for Facility Based Providers. BellSouth shall work cooperatively with Universal to ensure the accuracy of the data transfer by verifying it against MSAG. 10.3.5 Universal shall assign an E911 database coordinator charged with the responsibility of forwarding Universal end user ALI/DBMS record information to BellSouth or via a third-party entity, charged with the responsibility of ALI/DBMS record transfer. Universal assumes all responsibility for the accuracy of the data that Universal provides to BellSouth. 10.3.6 Automatic Location Identification/Data Base Management System (ALI/DBMS). The ALI/DBMS Database contains subscriber information (including name, address, telephone information, and sometimes special information from the local service provider or subscriber) used to determine to which Public Safety Answering Point (PSAP) to route the call. The ALI/DBMS database is used to provide more routing flexibility for E911 calls than Basic 911. This subsection 1.3.6 supplements the requirements for SCPs/Databases set forth in the technical references in Attachment 3, Appendix 1 of this Agreement. BellSouth shall provide the Emergency Services Database in accordance with the following:
Sample 1

Related to Basic 911 and E911 Database Requirements

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • Training Requirements Grantee will: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS. B. Appropriately budget funds to meet training requirements in a timely manner, and ensure staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met. C. Follow the appropriate DSHS POPS by funding opportunity (as per Section I: General Requirements for All Grantees) for training and observation requirements.

  • Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

  • CERTIFICATION REGARDING DRUG-FREE WORKPLACE REQUIREMENTS 1. The Contractor certifies that it will provide a drug-free workplace by: a. Publishing a statement notifying employees that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Contractor’s workplace and specifying the actions that will be taken against employees for violation of such prohibition;

  • Screening Requirements Extendicare shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements: a. Extendicare shall screen all prospective Covered Persons against the Exclusion Lists prior to engaging their services and, as part of the hiring or contracting process, shall require such Covered Persons to disclose whether they are Ineligible Persons. b. Extendicare shall screen all Covered Persons against the Exclusion Lists within 90 days after the Effective Date and on an annual basis thereafter. c. Extendicare shall implement a policy requiring all Covered Persons to disclose immediately any debarment, exclusion, suspension, or other event that makes that person an Ineligible Person. Nothing in Section III.G affects Extendicare’s responsibility to refrain from (or its liability for) billing Federal health care programs for items or services furnished, ordered, or prescribed by excluded persons. Extendicare understands that items or services furnished by excluded persons are not payable by Federal health care programs and that Extendicare may be liable for overpayments and/or criminal, civil, and administrative sanctions for employing or contracting with an excluded person regardless of whether Extendicare meets the requirements of Section III.G.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

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