03.08.2013 Views

REQUEST FOR PROPOSALS RFP NUMBER: 0A1031 DATE ISSUED

REQUEST FOR PROPOSALS RFP NUMBER: 0A1031 DATE ISSUED

REQUEST FOR PROPOSALS RFP NUMBER: 0A1031 DATE ISSUED

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

measurements of performance against the manufacturer specifications at any time during this<br />

period.<br />

3. Demonstrates ease of operation.<br />

4. Operates effectively and efficiently, without equipment, component, or software driver<br />

failures, for a sustained period of 30 consecutive calendar days, or less at ODPS’ option,<br />

during which the DL/ID solution performs at an effectiveness level of 99.5% uptime per<br />

location per week.<br />

5. Demonstrates problem-free interfaces to the ODPS BASS DL/ID issuing application.<br />

6. Produces acceptable DL/ID cards that meet the specified security and durability criteria.<br />

D. The Contractor must, in order to achieve Final System Acceptance, demonstrate its ability to<br />

provide adequate service and maintenance of the DL/ID solution statewide throughout the entire<br />

Final System Acceptance period.<br />

E. In order to achieve Final System Acceptance, any and all equipment provided pursuant to this<br />

<strong>RFP</strong> (including all addenda and any resulting Contract), and the DL/ID solution as a whole, must,<br />

to the satisfaction of the ODPS, conform to all specifications published or provided by the<br />

Contractor or manufacturer, including but not limited to, physical characteristics, operating<br />

characteristics, space requirements, power requirements, performance requirements, and<br />

maintenance.<br />

F. In order to achieve Final System Acceptance, any and all software drivers, including but not<br />

limited to any customizations thereto, shall, to the satisfaction of the ODPS, conform to all<br />

specifications published or provided by the Contractor or developer in all respects, including, but<br />

not limited to, operating performance and interfacing with the ODPS systems.<br />

G. If the DL/ID solutions does not meet or sustain performance at an effectiveness level of 99.5%<br />

uptime per location per week and meet all of the other criteria set forth in this requirement and<br />

any other criteria determined by the ODPS, during the 30 consecutive calendar days of the Final<br />

System Acceptance period, the Final System Acceptance period may continue at ODPS’ sole<br />

discretion, on a day-to-day basis until the DL/ID solution, in ODPS’ sole judgment, meets all such<br />

criteria for 30 consecutive calendar days, or less at ODPS’ option.<br />

Performance Level<br />

A. All components of the DL/ID solution (including all equipment and software drivers) shall be<br />

capable of continuous operation. It is the expectation that the operational up-time be 99.5%<br />

uptime per location per week.<br />

B. The ODPS will be entitled to direct damages from the Contractor if any component of the DL/ID<br />

solution under current maintenance becomes inoperable for a period of more than 6 ODPS<br />

business hours. The compensation will be calculated by the ODPS based on a combination of<br />

factors (including, but not limited to the ODPS operating expenses and costs for implementing<br />

work-around solutions for each hour over the 6 ODPS business hour limit). The period of<br />

inoperability shall commence when the ODPS reports the malfunction to the Contractor at its<br />

designated contact point, and shall end when the malfunctioning component(s) becomes<br />

available for operational use.<br />

C. The Contractor must provide a new replacement, at no cost to the ODPS, of any DL/ID solution<br />

or system component, at the ODPS’ sole discretion, if any DL/ID solution component remains<br />

inoperable for more than twenty-four consecutive ODPS business hours.<br />

Page 49 of 115

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!