The documents in this repository are posted to e-Buy under RFQ1250830. The documents in e-Buy should always be considered the documents of record. Please submit any questions as GitHub issues in this repository by November 13, 2017 at 4:00 pm EST. TTS and the Contracting Officer will only be responding to questions submitted via this Issue Template. We cannot commit to responding to comments or questions submitted in other manners.

Offers are due by November 17, 2017, at 4:00 pm EST.

This procurement is to acquire labor to continue development of a cloud marketplace tool that is anticipated to allow government program offices to discover, obtain, and manage licenses for software-as-a-service (SaaS) products in an efficient and compliant manner.

Currently, the process for buying, managing, and distributing SaaS licenses is manual, decentralized, and unstandardized. As a result, agencies—and the program offices within them—are working in parallel to buy and use similar products. This approach lacks the benefit of collective action and is less transparent from an oversight perspective. Procurement and compliance obstacles may cause offices to settle for less-than-optimal products in order to get working more quickly. This tool with provide civil servants with the SaaS tools they need to stay current with evolving best practices.

The new tool will provide the ability to discover, obtain, and manage licenses for approved SaaS products, ideally from an already acquired inventory of licenses. Such a tool would improve transparency, and consequently, inventory management of SaaS licenses while enabling easier access to the tools necessary for program offices to deliver on their mission. This supports the mission of the TTS Office of Acquisition to make federal procurement a simpler, more enjoyable process.

To fulfill the objectives for performance of this task order, the Vendor must meet the requirements outlined in section 9.0, but in sum, we are an Agile software development team.

Detailed instructions about how to respond are explained in section 8.0 of our RFQ, but in sum, the following forms must be filled out and submitted, in full:

RFQ Technical Response Form RFQ Pricing Response Form

Details about what we're looking for from Key Personnel are explained in section 10.2 of our RFQ.

Details are explained in section 4.0 of our RFQ, but in sum:

one (1) Base Period of three (3) months and three (3) Option Periods of three (3) months each

1. RFQ

2. QASP

Please remember: The documents in e-Buy should always be considered the documents of record.

See CONTRIBUTING for additional information.

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.