Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF OCTOBER 08, 2009 FBO #2875
SOURCES SOUGHT

70 -- Identify Industry Capability to provide an Automated Tool to Create Contractual Documents

Notice Date
10/6/2009
 
Notice Type
Sources Sought
 
NAICS
511210 — Software Publishers
 
Contracting Office
Department of Homeland Security, Transportation Security Administration, Headquarters TSA, 601 S. 12th Street, TSA-25, 10th Floor, Arlington, Virginia, 20598, United States
 
ZIP Code
20598
 
Solicitation Number
HSTS01-10-I-ACQ900
 
Archive Date
11/6/2009
 
Point of Contact
Kirsten M O'Brien, Phone: 571-227-5633, Isabel Roman-Cogswell, Phone: 571-227-2461
 
E-Mail Address
kirsten.o'brien@dhs.gov, isabel.cogswell@dhs.gov
(kirsten.o'brien@dhs.gov, isabel.cogswell@dhs.gov)
 
Small Business Set-Aside
N/A
 
Description
A. Introduction. The Transportation Security Administration (TSA) Office of Acquisition (OA) is issuing this Request for Information (RFI) to be used for market research purposes only and shall not be construed as a Request for Proposal (RFP) or as an obligation on the part of the Requestor to acquire any products or services. If an RFP or an RFQ is issued, it will be officially issued by the TSA Office of Acquisition and will be synopsized in FedBizOpps unless the use of GSA Schedule is deemed more appropriate. Instructions on how to provide a response are provided below. Businesses of any size are encouraged to submit a response to this RFI, particularly small businesses. The requestor does not intend to pay for the information requested. All information provided is for Government planning purposes only. B. Anticipated Requirement. The TSA seeks to identify industry capability to provide TSA OA an automated tool to create contractual documents, including Request for Proposal, Request for Information, Request for Quotes, Invitation for Bids, contracts, solicitations, leases, grants, modifications, purchase orders, etc. Note that this functionality is not sought to be a module within a system but rather a stand-alone solution. The TSA OA has approximately 80 contract specialists and contracting officers who issue over 4,000 contract actions and obligate approximately $3,000,000,000 annually. TSA OA acquires services and supplies using the uniform contract format and is subject to the Federal Acquisition Regulations (FAR), the Homeland Security Acquisition Regulation, the Homeland Security Acquisition Manual, and TSA-specific contract provisions and requirements. Acquiring both commercial and non-commercial items and services, TSA OA issues all types and combination of contracts, including indefinite delivery/indefinite quantity, blanket purchase agreements, purchase orders, cost reimbursable, fixed price, fixed fee, incentive fee, and award fee. TSA also exercises its unique direct leasing, grants and other transaction authority. The TSA OA computing environment consists of desktop, windows-based personal computers with industry standard black-and-white and color printing capabilities. Windows XP, Microsoft Office 2003 and 2007 product suites, and Internet Explorer are standard desktop applications. TSA currently has financial management, workflow management, information storage, and business intelligence systems in place. As such, duplication of these functionalities or integration with these systems is not required. TSA is potentially seeking a single solution to generate contract documents in Microsoft Word format to all members of the OA. This solution should manage clauses and their prescription to ensure appropriate use and have real or near time integration with updates from the FAR and HSAR. The solution should provide for a method of selecting clauses and provisions based upon 'wizard' questions, checklists, templates or some other automated process. The system should force the use of 'required' clauses and provisions, as well as provide recommendations and rational for optional clauses based upon their prescribed usage. The solution should assist in creating a Contract Line Item Number (CLIN) structure. C. Submission of Information. Any vendor responding to this Request for Information shall provide a narrative description, not to exceed five (5) pages in length, a vendor's experience summary, not to exceed two (2) page, and a one (1) page cover letter for a total submission not to exceed eight (8) pages. A sheet of paper containing text on both sides is considered two pages. Also, the proposal text may not be smaller than 12-pitch type on standard 8 ½ by 11 inch paper. If proprietary information is provided, please mark as "Proprietary for Government Use Only". Information should be organized in accordance with the instructions in this document in order to permit a thorough capabilities assessment by the TSA for the purposes of market research. 1. Cover Letter (1 Page maximum). The cover letter must clearly identify the following information: (a.) Company's Name (b.) Company's Address (c.) DUNS number (d.) Points of Contact(s) (Name, E-mail, phone number, etc.) (e.) Business Size (f.) Known Teaming Partners, Subcontractors, or Technology Providers (g.) Identification of company's GSA Federal Supply Schedule or other Government-wide Acquisition Contract(s) (including contract numbers) (h.) Company Overview (e.g. type of services/ products offered) 2. Narrative Description (5 Pages maximum). Description of available solutions that satisfies the anticipated requirement. Specifically, vendor's should discuss: (a.) Overview of available solutions (b.) Method of delivery - on-line, client, network application, etc. (c.) User experience and navigation (d.) Method of clause/provision selection - wizard, checklist, template, etc. (e.) Method of contract line item number creation (Section B) (f.) Use of standard forms (g.) Ability to easily add, remove, or edit clauses/provisions (h.) Unique Features (i.) Supported contract document types (j.) Training (k.) Implementation details and timelines (l.) On-going maintenance requirements and estimated costs (m.) System/user requirements (n.) Method of update of clauses, provisions, and forms (o.) Degree of customer system administration permitted (p.) Potential for future integration with Oracle and/or Microsoft SQL Server products (q.) Pricing/cost structure - identify estimated costs typical for complete implementation 3. Vendor's Experience Summary (2 page maximum). Providing a solution that satisfies the anticipated requirement. Specifically, identify other government users of the product, (a.) Description of similar projects completed for government customers - including points of contact, phone number, and email address. (b.) Description of Vendor's government contracting and procurement experience D. Due Date. Responses to this Request for Information must be submitted to the TSA via e-mail to Kirsten.O'Brien@dhs.gov not later than 12:00 PM EST, Thursday, October 22, 2009. Responses not received by the closing date and time may not be considered for assessment by the TSA. All comments, inquiries, and responses should be directed in writing via email to the following individual: Kirsten O'Brien, Contract Specialist, Kirsten.O'Brien@dhs.gov
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/DHS/TSA/HQTSA/HSTS01-10-I-ACQ900/listing.html)
 
Place of Performance
Address: 701 South 12th Street, Arlington, Virginia, 20598, United States
Zip Code: 20598
 
Record
SN01980817-W 20091008/091006234838-68541958b7c874dbfd6d9da42cf83b44 (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.