Skip to content
This repository has been archived by the owner on Aug 30, 2019. It is now read-only.

Solicitation documents related to document authentication services.

License

Notifications You must be signed in to change notification settings

18F/tts-buy-document-authentication-services

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Login.gov Document Authentication Services

This is the GitHub repository for TTS_DOCAUTH, posted on FedBizOpps.gov. Please submit any questions as an Issue in this repository by November 17, 2017 at 1:00pm EST. The Contracting Officer will only be responding to questions submitted using the Issue Template. Comments from other parties or in other formats will still be considered but we cannot commit to responding to them.

Proposals are due by December 8, 2017 at 1:00pm EST.

Background

The Login.gov program is undergoing significant modifications in direct response to recent laws passed in Congress and executive orders released by the Executive Office of the President instructing federal agencies to protect citizen data in transactions with the Government, including:

  • The Cybersecurity Information Sharing Act (CISA) passed in October 2015;
  • The Cybersecurity National Action Plan (CNAP) released in March 2016 by the Executive Office of the President to identity short- and long-term actions to meet CISA; and
  • The Implementation Plan Draft released in April 2016 as a plan for action to Executive Order 13681 - Improving the Security of Consumer Financial Transactions.

What we're hoping to end up with

Additional information is provided in Sections 2, 6, and 9 of the RFQ, but in short:

The vendor will collect documentary evidence of identity data via the login.gov platform. The login.gov application will electronically transfer these data elements to the contractor. The contractor will return a real-time verification from the data received via the login.gov platform and the results of the comparison. Based on the response, GSA will determine whether documentary evidence meets our requirements as evidence of the individual’s identity.

How to respond

Additional information is provided in Section 4 of the RFQ, but in short:

The competition for this RFQ is expected to take longer than usual. Quotes should be valid for not less than 90 days from submission. Offerors will need to submit written technical quotes as well as their proposed solution for evaluation, see paragraphs 9 and 10. Offerors must read, complete, and submit all attachments as well as the representations and certifications below and submit them with their offer.

Period of performance

Additional information is provided in Section 3 of the RFQ, but in short:

1 Base Year with 1 Option Year

Contents

  1. Request for Quotation (RFQ)

  2. Attachment A - Requirements

  3. Attachment B - Template Sources

  4. Attachment C - SLA Requirements

  5. Attachment D - Deployment Options

  6. Past Performance Questionnaire Note: Link is to a document hosted on FBO.gov.

Contributing

See CONTRIBUTING for additional information.

Public domain

This project is in the worldwide public domain. As stated in CONTRIBUTING:

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.

Releases

No releases published

Packages

No packages published