REQUEST FOR PROPOSALS RFP NUMBER: 0A1031 DATE ISSUED

during which the DL/ID solution performs at an effectiveness level of 99.5% uptime at per
location.
5. Demonstrates problem-free interfaces to the ODPS system applications BASS DL/ID issuing
software.
6. Produces acceptable DL/ID cards that meet the specified security and durability criteria.
E. The Contractor must, in order to pass the Beta/Pilot Test Period, demonstrate its ability to provide
the required service and maintenance of the DL/ID solution throughout the entire Beta/Pilot Test
Period.
F. In order to pass the Beta/Pilot Test Period, any and all equipment provided pursuant to this RFP
(including all addenda and any resulting Contract), and the DL/ID solution as a whole, must, to
the satisfaction of the ODPS, conform to all specifications published or provided by the
Contractor or manufacturer, including but not limited to, issued DL/ID physical characteristics,
operating characteristics, space requirements, power requirements, and maintenance.
G. In order to pass the Beta/Pilot Test Period, any and all software drivers, including, but not limited
to any customizations thereto, shall, to the satisfaction of the ODPS, conform to all specifications
published or provided by the Contractor or developer in all respects, including, but not limited to,
operating performance and interfacing with the ODPS system applications.
H. If the DL/ID solution does not meet or sustain performance at an effectiveness level of 99.5%
uptime per location per week and meet all of the other criteria set forth in this RFP, during the 30
consecutive calendar days of the Beta/Pilot Test Period, the Beta/Pilot Test Period may continue
at ODPS’ sole discretion, on a day-to-day basis until the DL/ID solution, in ODPS’ sole judgment,
meets all such criteria for 30 consecutive calendar days, or less at ODPS’ option.
System Testing and Acceptance Period – Final System Acceptance
Once the Beta/Pilot Test Period is declared successful in writing by the ODPS, system training and
system installations shall commence at the remaining sites as determined and scheduled by the
ODPS in preparation for Final System Acceptance. The Contractor must conduct an operational site
systems test and review after each site is installed and certified ready for production implementation.
A. Once the remaining sites are declared ready for production implementation by the Contractor and
the ODPS in writing, Final System Acceptance will begin. Final System Acceptance must be a
statewide production monitoring period where the Contractor must successfully demonstrate all
requirements of this RFP (including all addenda and any resulting Contract) for 30 consecutive
calendar days, or less at ODPS’ option.
B. In order to pass Final System Acceptance testing, the Contactor must successfully demonstrate
that the DL/ID solution meets all requirements of this RFP (including all addenda and any
resulting Contract) and performs all functions at an effectiveness level of 99.5% uptime per
location per week, for 30 consecutive calendar days, while operating statewide in full production
mode.
C. Final System Acceptance monitoring must include, but not be limited to monitoring to confirm, to
the satisfaction of the ODPS, that the DL/ID solution:
1. Performs successfully in accordance with all the mandatory requirements specified in this
RFP (including all addenda and any resulting Contract).
2. Continues to perform successfully in accordance with all manufacturer’s and Contractor’s
technical specifications and user specifications; the ODPS reserves the right to conduct
Page 48 of 115