EBT Database Conversion Requirements Sample Clauses

EBT Database Conversion Requirements. Requirement 758 The Contractor shall participate in weekly Transition Services planning meetings with the State and the incumbent EBT contractor. 759 The Contractor shall receive and load into the production Food and Cash EBT Host System the following Conversion Files: a. Transaction history (online and offline). b. Benefit Data. c. Demographic Data. d. Retailer Data (Retailer database and FNS REDE Files). 760 The Contractor shall transfer existing Cardholder Card numbers. 761 The System shall enable Cardholders to use the same Food and Cash Card used prior to Cutover. 762 The Contractor shall transfer existing Cardholder PINs. 763 The System shall enable Cardholders to use the same active PIN used prior to Cutover. 764 The System shall not reset status or aging Data in the Conversion Files. 765 The Contractor shall work with the incumbent EBT contractor to determine the File transfer methodology to be used during Conversion. 766 The Contractor shall conduct unit and integration testing of Files to be transferred during Conversion. # Requirement 767 The Contractor shall conduct full integration and System testing of Files to be transferred during Conversion. 768 The Contractor shall conduct no less than three (3) rehearsals of the database Conversion. 769 The Contractor shall conduct all rehearsals of the database Conversion in the same manner and sequence as will be done during Cutover. 770 The Contractor shall allow for at least two (2) weeks between database Conversion rehearsals. 771 The Contractor shall successfully complete all database Conversion testing and at least two (2) successful rehearsals of the database Conversion prior to Cutover. 772 The duration of Cutover processes from the disablement of Cardholder transaction processing by the incumbent EBT contractor to the enablement of Cardholder transaction processing on the Contractor’s EBT System shall be no more than twenty four (24) hours. 773 The Contractor shall participate in Go/No-Go meetings for database Conversion with the State. 774 The Contractor shall participate in additional Go/No-Go meetings for database Conversion with the State, at no additional cost to the State, in the event that a No-Go decision is made for database Conversion. 775 Following database Conversion and prior to allowing Cardholder or administrative access to the System during Cutover, the Contractor shall reconcile the new System Accounts with the record counts and Account balances from the former EBT system to en...
Sample 1
AutoNDA by SimpleDocs

Related to EBT Database Conversion Requirements

  • Installation requirements 7.8 We (if we install the System) or our contractor (if we procure a contractor to install the System) must:

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

  • Distribution Requirements Arts 3 A course in history, philosophy, theory, or practice of the creative and interpretive arts.

  • Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED)‌ 200. OPERATIONAL AGREEMENT.‌‌

  • Submission Requirements The Contractor shall submit inventory disposal schedules to the Plant Clearance Officer no later than—

  • Construction Requirements a) All Life and Safety and applicable Building Codes will be strictly enforced (i.e., tempered glass, fire dampers, exit signs, smoke detectors, alarms, etc.). Prior coordination with the Building Manager is required.

  • Notification Requirements 1. If the Family Leave is foreseeable, the employee must provide the agency/department with thirty (30) calendar days notice of his or her intent to take Family Leave.

  • Publication Requirements Those seeking to include renderings of more than 10 images from the UND Biometrics Database in reports, papers, and other documents to be published or released must first obtain approval in writing from the UND Principal Investigator. In no case should the face images be used in a way that could cause the original subject embarrassment or mental anguish.

  • Design Requirements 9.2.1. Metal liner The compressive stress in the liner at zero pressure and 15 °C shall not cause the liner to buckle or crease.

  • Admission Requirements USERs and Participants are subject to the administrative and technical supervision and control of CONTRACTOR; and will comply with all applicable rules of CONTRACTOR and DOE with regard to admission to and use of the User Facility, including safety, operating and health- physics procedures, environment protection, access to information, hours of work, and conduct. Participants shall execute any and all documents required by CONTRACTOR acknowledging and agreeing to comply with such applicable rules of CONTRACTOR. Participants will not be considered employees of CONTRACTOR for any purpose.

Time is Money Join Law Insider Premium to draft better contracts faster.