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.

• Motorola Symbol PD8750 Signature Capture Solution. The offeror’s must provide a<br />

statement that the proposed solution uses Motorola Symbol PD8750 Signature Pad as<br />

specified in Supplement Twenty and meets the signature capture solution capabilities.<br />

• The offeror must describe how the proposed solution is capable of compliance with REAL ID<br />

requirements.<br />

FUNCTIONAL REQUIREMENTS<br />

• The offeror must provide detailed narratives describing its proposed solutions, including all<br />

functionality, system capabilities and limitations, and performance capabilities and limitations<br />

of the proposed solution.<br />

• The offeror must provide information on each equipment component (i.e. printer, camera)<br />

that is a part of the proposed solution by listing which State or government jurisdiction the<br />

equipment is currently in use (name and phone numbers).<br />

• The offeror must describe means for implementing future enhancements and expansion to<br />

the proposed solution (i.e. Federal or State Regulations).<br />

• The offeror must propose a DL/ID solution that can achieve the anticipated volumes, and<br />

remain fully operational and supported by the Contractor throughout the period of the<br />

Contract.<br />

• The offeror must describe a proposed written test plan which includes, but is not limited to, all<br />

necessary criteria and tests to be performed to ensure that the DL/ID solution as a whole,<br />

and all components thereof, satisfy the requirements agreed to in this <strong>RFP</strong>, a description of<br />

all phases of testing, provisions for the documentation of testing results, problem detection,<br />

and corrective measures taken to permanently address problems, and a description of the<br />

resources, including the ODPS and offeror’s proposed staffing, necessary to conduct testing.<br />

• The offeror must furnish a list and description of all necessary materials and supplies<br />

required for the successful operation of its proposed DL/ID solution with its proposal.<br />

• The offeror must fully describe its proposed solution for maintaining and delivering the<br />

necessary materials and supplies to each DR and CSC location. The ODPS will develop<br />

accountability procedures, based on the offeror’s proposed solution, which include<br />

verifications and controls from when secure items are received through issue to the<br />

customer. The offeror must propose its method of controlling secure items and the features to<br />

be provided to assist the ODPS with accounting for secure items.<br />

• The offeror must itemize and describe all proposed hardware and software product<br />

components. The offeror must include a breakdown of each separate component and feature<br />

of the proposed solution along with the corresponding technical specifications. All required<br />

software driver components must be documented in detail in the offeror’s response.<br />

• The offeror must provide a detailed discussion regarding its knowledge and understanding of<br />

how such state/federal (U.S.)/International standards involving personal identity verification,<br />

security and privacy of confidential information fit in with the initial deployment of the<br />

proposed DL/ID solution. The offeror must also discuss the flexibility and adaptability of its<br />

proposed DL/ID solution to meet federal or international standards related to personal identity<br />

verification, security and privacy of confidential information. The offeror should provide<br />

specific references to pertinent standards / publications / programs.<br />

Page 68 of 115

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

Saved successfully!

Ooh no, something went wrong!