Updates to Database Sample Clauses
The "Updates to Database" clause defines the responsibilities and procedures for making changes or modifications to a database covered by the agreement. Typically, this clause outlines who is authorized to perform updates, the process for requesting or implementing changes, and any requirements for notifying relevant parties about updates. For example, it may specify that only certain personnel can alter database content or that updates must be documented and communicated in advance. The core function of this clause is to ensure that database modifications are controlled and transparent, reducing the risk of unauthorized changes and maintaining data integrity.
Updates to Database. GTE and AT&T will work together to develop the process by which the 911/E911 database will be updated with AT&T's end user 911/E911 information. AT&T shall have the right to verify the accuracy of the information regarding AT&T's end users in the 911/E911 database.
Updates to Database. V-2 2.5 Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V-2 3. Information Services Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V-2 3.1. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V-2 3.2 Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V-2 3.3 Rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V-2 3.4 Billing and Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V-2 3.5 Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V-3 4. Directory Assistance (DA) and Operator Services V-3 ARTICLE VI 1. Physical Collocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VI-1 2. Existing Virtual Collocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VI-1 ARTICLE VII ACCESS TO POLES, DUCTS, CONDUITS AND RIGHTS-OF-WAY . . . . . . . . VII-1 APPENDIX A ▇▇▇▇▇▇▇▇ ▇ SERVICE ATTACHMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 APPENDIX C RATES AND CHARGES FOR TRANSPORT AND TERMINATION OF TRAFFIC . . . . . . . . . . . . . . . . . . . . . . . . C-1 This Interconnection Agreement (the "Agreement"), is entered into by and between GTE South Incorporated, with its address for purposes of this Agreement at ▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇, ▇▇▇▇▇▇, ▇▇▇▇▇ ▇▇▇▇▇ ("GTE"), and Contel Cellular Inc., on behalf of the following entities: GTE Mobilnet of Clarksville Incorporated; GTE Mobilnet of Indiana Incorporated; GTE Mobilnet of Kentucky Incorporated; and, Kentucky RSA No. 1 Partnership (collectively “Mobilnet”) in its capacity as a certified provider of two-way wireless mobile telecommunications service, with its address for this Agreement at ▇▇▇ ▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇ (GTE and Mobilnet being referred to collectively as the "Parties" and individually as a "Party"). This Agreement covers services in the state of Kentucky (the "State").
Updates to Database. The 911/E911 database will be updated with RECONEX’s end user 911/E911 information. If RECONEX provides its updated data to GTE as frequently as does GTE’s internal systems, the update will be as timely. In any case, GTE will not update the ALI database any later than one working day subsequent to receipt of data from RECONEX.
Updates to Database. The 911/E911 database will be updated with First Choice’s end user 911/E911 information. If First Choice provides its updated data to GTE as frequently as does GTE’s internal systems, the update will be as timely. In any case, GTE will not update the ALI database any later than one working day subsequent to receipt of data from First Choice.
Updates to Database. The 911/E911 database will be updated with PCS’s end user 911/E911 information. If PCS provides its updated data to GTE as frequently as does GTE’s internal systems, the update will be as timely. In any case, GTE will not update the ALI database any later than one working day subsequent to receipt of data from PCS.
Updates to Database. The 911/E911 database will be updated with EZ Talk’s end user 911/E911 information. If EZ Talk provides its updated data to GTE as frequently as does GTE’s internal systems, the update will be as timely. In any case, GTE will not update the ALI database any later than one working day subsequent to receipt of data from EZ Talk.
Updates to Database. The 911/E911 database will be updated with TEL - LINK's end user 911/E911 information. If TEL - LINK provides its update data to GTE as frequently as does GTE's internal systems, the update process will be as timely. In any case, GTE will not update the ALI database any later than one working day subsequent to receipt of data from TEL - LINK.
Updates to Database. The 911/E911 database will be updated with eti’s end user 911/E911 information. If eti provides its updated data to GTE as frequently as does GTE’s internal systems, the update will be as timely. In any case, GTE will not update the ALI database any later than one working day subsequent to receipt of data from eti.
Updates to Database. The 911/E911 database will be updated with dPi’s end user 911/E911 information. If dPi provides its updated data to GTE as frequently as does GTE’s internal systems, the update will be as timely. In any case, GTE will not update the ALI database any later than one working day subsequent to receipt of data from dPi.
Updates to Database. GTE and ACSI will work together to develop the process by which the 911/E911 database will be updated with ACSI's end user 911/E911 information. ACSI shall have the right to verify the accuracy of the information regarding ACSI's end users in the 911/E911 database.