Database Maintenance Sample Clauses
Database Maintenance. The administrator will continue to maintain an accurate database for benefits administrative and valuation purposes. This will include:
a. Year over year reconciliation of status and data changes for valuation purposes.
b. Monitoring active-employee terminations to cash out participants in a timely manner.
c. Tracking of lump sum cash outs:
(i) If checks are cashed by the participant, the database record needs to be adjusted to show that no future payments are due.
(ii) If checks are not cashed by participants, reasonable follow up is required to demonstrate a legitimate attempt to locate and cash out the individual was made. Adjustment of database and financial information to reflect that a lump sum amount was not paid.
(iii) Decisions on how to handle nonresponsive participants must be discussed with the County.
d. Maintenance of current retirees receiving annuities.
e. Monitoring to ensure monthly payments continue until the participant dies.
f. Tracking current retirees when participant dies.
g. Cease payments.
h. Determine if there is a beneficiary. Calculate the lump sum payable to beneficiary, if any based upon employee’s account balance with interest offset by annuities received.
i. Update database to reflect death and status of beneficiary payment.
j. Researching uncashed or returned check. Adjustment of database and financial information to reflect annuity for month(s) not paid and status of retiree.
k. Correctly honoring terminated employees who opted to delay payment to receive a monthly annuity beginning at age 65 per the County’s direction.
l. Tracking and maintain records substantiation of all benefits payments.
Database Maintenance. Silver Spring will maintain the database on a regular basis (i.e., weekly or monthly depending on the size of the database) for proper performance and functionality. ***.
Database Maintenance. Activities
Database Maintenance. 2.01 Helion will provide on-going consulting on procedures for the backup and restoration of all databases required to run the ORCATS software.
2.02 Helion will consult with the County technical staff as needed on the status of all databases required to run the ORCATS software and ensure that all database indexes and database features are configured appropriately to ensure the proper functioning of all Helion supported software.
2.03 If requested, Helion will ensure that database backups are performed prior to any modification to the database structure and/or schema as part the implementation of new ORCATS software through new version release or problem resolution.
2.04 Helion will perform all database repair and recovery due to database corruption, malfunction, or inconsistency brought about by implementation of new ORCATS software through new version release or problem resolution, by defects in or improper functioning of the client software, or by third party software used within any Helion supported software.
2.05 The obligations described in Sections 1.00 through 2.05 are hereafter referred to as “Maintenance.”
Database Maintenance. Company agrees to transmit information each month on use of the Service by Customer (including, Cardmember account number and service used), to AMEX's database maintenance facility. The mechanism for this transmission to be agreed to by the parties.
Database Maintenance. The applications programming group is responsible for the Database maintenance of the Worldflight System. The loading, updating, and validation of the data entered into the Worldflight database is the responsibility of the user groups that the applications support. Database maintenance does include, file sizing, and the repair of corrupted data that was caused due to programming errors. The Worldflight system supports communications with other systems with both real-time and batch traffic. Worldflight provides real-time feeds to the following systems; Acars—uplinks, CFT—Corporate Flight Times, CMS—Crew Management (NWA), Cargo, MSG—TTY traffic, Sceptre—Aircraft Maintenance (NWA), Ramp/Fids—Gate Managemnet, Worldspan—Reservations / Common use, and ODB—Operations Database. Worldflight has the following batch feeds out; Stats—statistics, Mapper—Fuel Usage (NWA only), Worldspan—Microfiche. Worldflight is updated by the following systems; Acars—downlinks, MSG—TTY traffic, Sceptre—Aircraft Maintenance, Worldspan—Pass/Bag information, and ODB—Operations Database. Batch file feeds into Worldflight; Schedules—Airflight System, Aircraft Performance Data (via TSO). Enhancement requests are requests for new funtionality, or requests for cosmetic changes with the functionality remaining the same. These requests will require a Computer Service Request (CSR), and need to be submitted to the Operations Automation group for evaluation and priority assignment. The following will be measured and available on request; System Availability/Outages, Transaction Response Time, and Reliability of Outgoing Feed. N/A (See Appendix L1A) 37 ▇▇▇▇▇▇▇▇ ▇▇▇ Worldflight Products/Services System Availability—This measurement is the availability of the hardware and software within the Building J computer center. Outages of the various pieces affecting Worldflight availability are cumulative—that is, an outage to a communications front-end (that affects Worldflight users) is counted as a Worldflight availability outage. This measurement is not the end-to-end availability to the agent or customer at a terminal in the field. Future monitoring tools may provide an end-to-end measurement. Transaction Response Time—This measurement is the mainframe existence time of selected Worldflight transactions. This measurement is not the end-to-end availability to the agent or customer at a terminal in the field. Future monitoring tools may provide an end-to-end measurement. The selected transactions are tho...
Database Maintenance. AUM shall establish, hold and maintain a shared database for Drug Candidate(s). Newsoara shall provide data arising from the discovery program(s) in the Territory to AUM according to agreed procedures and processes.
Database Maintenance. The Developer will re-index the database and making Minor Modifications (as defined below) to the database structures as needed. ("Minor Modifications" are defined as adding not more than four fields and not more than two tables to the database in any one month. Any other modifications are outside the scope of this Agreement).
Database Maintenance. Conduct regular maintenance of databases associated with the AEM environment, including performance tuning and indexing. Ensure data integrity and manage database backups and recovery procedures.
Database Maintenance. Plan will keep all data bases updated and current; new information or changes will be entered within thirty (30) days of receipt of completed provider forms. - Inactive providers will be indicated by the correct provider status flag (Y for deactivated). - Any errors in the provider, membership, fee schedule or other databases that result in incorrectly adjudicated claims must be fixed within thirty (30) calendar days of written notification and the claim(s) backed out and reprocessed within the timeliness guidelines. Plan shall be required to correct all errors, in such time frame, even if funds, which may have been incorrectly paid to other parties, cannot be recovered. Any overpayments will be refunded to the Claims Payment Account, or the Plan, as appropriate, within ten (10) business days after the parties agree that amounts should be refunded.