Loren Data's SAM Daily™

FBO DAILY ISSUE OF APRIL 08, 2012 FBO #3788
DOCUMENT

D -- PIV Sites Identity Proofing Creditional Enhancement - Attachment

Notice Date

4/6/2012
 

Notice Type

Attachment
 

NAICS

541519 — Other Computer Related Services
 

Contracting Office

Department of Veterans Affairs;Technology Acquisition Center;260 Industrial Way West;Eatontown NJ 07724
 

ZIP Code

07724
 

Solicitation Number

VA11812I0281
 

Response Due

4/20/2012
 

Archive Date

6/19/2012
 

Point of Contact

Brian M Triggiano
 

E-Mail Address

8-5461<br
 

Small Business Set-Aside

N/A
 

Description

Request for Information Implementation of Identity Proofing Document Validation, Homeland Security Presidential Directive 12 (HSPD-12) SOURCES SOUGHT NOTICE & REQUEST FOR INFORMATION. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is for planning purposes only and shall not be construed as an obligation on the part of the Government. This is NOT a Request for Quotations or Proposals. No solicitation document exists, and a formal solicitation may or may not be issued by the Government as a result of the responses received to this RFI. The Government will not pay for any response or demonstration expenses. Any information received will become the property of the Government and will not be returned to the submitter. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. The Office of Information Technology (OIT) and the Office of Operations, Security, and Preparedness (OSP) of the Department of Veterans Affairs (VA) issue this RFI for an identity proofing document validation capability to support VA HSPD-12 Personal Identity Verification (PIV) credential issuance processes. The VA PIV credential issuance process must enforce knowledge-based identity proofing to augment and verify presented I-9 documents at the time of registration, and/or to substitute for I-9 documents. An incremental capability is envisioned that may not directly interface with the HSPD-12 PIV system initially, but will validate I-9 identity documents as a basis for PIV credential issuance and interface with the VA PIV system in future increments as the capability matures. The concept and requirements associated with identity proofing are depicted throughout the recent Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, Version 2.0 ; the National Institute of Standards and Technology (NIST) Federal Information Processing Standards Publication 201 (FIPS-201); and associated NIST special publications. BACKGROUND The HSPD-12 PIV System contains authoritative data on VA employees, contractors, affiliates, and others. External systems will use this data to make logical and physical access control decisions. The integrity of the data stored within the PIV system must be improved so external system business owners can rely on and have a high level of confidence in the data. HSPD-12 PIV system authoritative data must be complete, current, accurate, and valid. The validation of I-9 documents contributes to improving the integrity of PIV system data. Data integrity will become increasingly important as more and more systems leverage the data stores within the PIV system over the life cycle of the HSPD-12 PIV system. The security and personnel information is necessary to meet critical FIPS 201 requirements, and ensure completeness of HSPD-12 PIV system data stores. Identity proofing contributes to increased data integrity ensuring that PIV applicants are issued credentials based on validated I-9 documents and ensuring this data is available for audit and reporting purposes. I-9 document verification is currently performed by visual inspection of the documents by PIV Registrars. The VA requires a common, verifiable, and traceable solution that can be deployed to all PIV Registrar sites and that achieves compliance with the FIPS 201 requirement. A Registrar must electronically verify the authenticity of any source document, when the issuer of that document provides such services. NIST FIPS-201-2, the standards publication for PIV, states that "During identity proofing, the applicant shall be required to provide two forms of identity source documents in original form. The primary identity source document shall be neither expired nor cancelled and qualify as acceptable form of identifications as per the comprehensive list provided in FIPS 201. The VA Office of Inspector General (OIG) published several recommendations in their "Audit of Enrollment Centers' Implementation of Personal Identity Verification Requirements" in September 2011. Recommendation 6 states that "We recommend the Assistant Secretary of Operations, Security, and Preparedness issue guidance to ensure Registrars authenticate the source and integrity of identity documents used during the Personal Identity Verification credential enrollment process through official Federal and State databases." The scope of this requirement includes approximately 284 PIV site locations with approximately 3 registered users per site, throughout a range of VA facilities across the United States. This identity proofing document validation solution shall deliver the following benefits: "Increased security in user identification and authentication, logging, and auditing "Compliance with laws, regulations, and standards "Improved customer service via single authoritative data capture of credentials and elimination of redundancy "Secure infrastructure for the protection of all Personally Identifiable Information (PII) REQUIREMENTS The PIV applicant registration process must enforce knowledge-based identity proofing to augment and verify presented I-9 documents at the time of registration, and/or provide other identity validation capability as a substitute for I-9 documents. The PIV System shall incorporate mechanisms that permit the validation of I-9 identity documents as a legitimate source of identification. The initial capability may not have a direct interface with the HSPD-12 PIV system, but will validate I-9 identity documents as a basis for PIV credential issuance. Responses should address the following requirements about the envisioned solution and/or technologies. "Validate extensive list of primary and secondary identity source documents. Listing exceptions to I-9 documents that cannot be validated. Talk to the reliability of the document validation (what is the error rate, false positives, false negatives, etc.). "Must include costs related to subscription services including and not limited to annual and/or multiple year renewals. "May include hardware and software configurations. oIncluding customization options and capabilities "Must include maintenance options including patches, upgrades, hardware repair and replacement, and phone support. "Must include training for all PIV personnel and VA help desk personnel as deemed appropriate by VA. "Must include an outline of the process, procedures, and capabilities offered for consulting and customization services. "Must include details on any APIs and standards available for interfacing with system Topic 1 - I-9 Document Verification 1.Describe functionality, and basic components of the document verification solution including but not limited to the technologies used, document types verified, and services provided. 2.The Contractor shall provide a recommended architecture that ensures initial capability of the recommended document verification solution. The document verification systems shall be physically located in the same locations as the current PIV Registrar systems. 3.Provide an open standards based interface (compliant with VA security standards) to various systems to allow for information exchanges to occur. 4.Provide a consolidated view of identity proofing data and associated attributes to VA applications, data sources, and personnel from disparate authoritative data sources. 5.Provide logging and audit capability for document verification activities. 6.Define the process by which the new document verification solution will be accepted, used, operated, and maintained. a.Provide transition plans that address aspects of transition management (including training, operation, transition timing, staging of transition, contingency measures, etc.) which pertain to the actual acceptance, use, operations, and maintenance of the solution. b.Provide training materials for all hardware and software for each site facility (manuals, reference guides, operating instructions, support procedures, etc.) and methods (online, train-the-trainer, classroom, etc.) to facilitate a smooth transition to the new solution. 7.Provide Operations and Maintenance (O&M) support of the document verification solution. The solution should have the ability to: a.Provide 24/7 tier/level 2 and 3 Help Desk support through subject matter experts/vendors and problem diagnosis documentation for tier/level 1 help desk. Level 1 help will be performed by VA National Service Desks that are already in place; b.Provide Inventory and Asset Management records of the solution that can be imported/exported into the corresponding VA inventory/ asset management system; c.Provide preventive and corrective maintenance support for the systems and all subsystem elements to include product warranties and maintenance agreements. Additionally, provide maintenance procedures and the recommended periodicity of maintenance procedures enterprise components and support audit of maintenance actions; d.Perform diagnostics and troubleshooting of solution; 8.Provide an identity proofing document verification hardware/software component bill of materials necessary for each site or facility to achieve the capability. RESPONSE We are requesting industry to provide a written Statement of Capability to this RFI that includes the following: (1) A Rough Order of Magnitude (ROM) cost estimate range for implementing an enterprise end-to-end solution for 1-year. This cost estimate should include a solution that satisfies the basic requirements. Any additional capabilities should be represented separately. This estimate should break out product and support costs separately. (2) Describe the capability. (3) Describe the initial approach for integrating all identity proofing document validation systems into the PIV environment that meet the objectives of HSPD-12. (4) A general explanation of how the document verification system or technologies address the technical requirements. (5) Explain the commercial software licensing approach, if applicable, that minimizes license management costs and leverages COTS products availability under VA enterprise license vehicles. (6) Identify any schedules, if any, that these products and services are currently on. (7) Identify a suggested appropriate NAICS code for this effort along with your business size status for that particular NAICS. The page limit for the response is thirteen (13) pages. The page limit for the technical response is ten (10) pages. Responses should also include a one (1) page company profile (to include, but not limited to, history, company size and socioeconomic category, applicable North American Industry Classification [NAICS], and primary line of business). Responses should also include two (2) pages of estimated cost ranges separating product costs, support costs, and a cost per site estimate. A cover page and table of contents will not count towards the page limit. Your response shall be submitted electronically to Brian Triggiano, Contract Specialist by email at brian.triggiano@va.gov. Response due date: no later than 5:00 p.m. Eastern Time on Friday, April 20, 2012. Contracting Office Address: Department of Veterans Affairs Office of Acquisition Operations Technology Acquisition Center 260 Industrial Way West Eatontown, NJ 07724 Place of Performance: United States Primary Point of Contact: Brian Triggiano Contract Specialist Email: Brian.Triggiano@va.gov Secondary Point of Contact: Charles Ross Contracting Officer Email: Charles.Ross@va.gov
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/notices/4e72a1d66e13e3558fd0fe29235829b2)
 

Document(s)

Attachment
 

File Name: VA118-12-I-0281 VA118-12-I-0281.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=318548&FileName=VA118-12-I-0281-000.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=318548&FileName=VA118-12-I-0281-000.docx

 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN02716577-W 20120408/120406235325-4e72a1d66e13e3558fd0fe29235829b2 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |