2010_LRBAA_AMENDMENT 0002_White Papers.doc

DOC document 57 KB Posted

Attached to
2010 DHS S&T LRBAA Federal contract opportunity
Solicitation number
DHSS-TLRBAA10-01
Issued by
Department of Homeland Security Office of Procurement Operations

About this file

Amendment 0002 is attached

View the file

Other files for this federal contract opportunity

Other files attached to 2010 DHS S&T LRBAA, newest first.
File Type Posted
LRBAA 11-03 FedBizOpps Notice.docx DOCX document
2010 PART II BAA_19MAY2010_AM00004doc.doc DOC document
2010 PART II BAA_MAY2010.doc DOC document
10-01 Long Range BAA Part 1_11JAN10.pdf PDF
10-01 Long Range BAA Part 2.pdf PDF
10-01 Long Range BAA Part 1_11JAN10.pdf PDF
2010_LRBAA_PART I_FBO_FINAL.pdf PDF
2010_LRBAA PART II_FBO FINAL.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

BAA 10-01

Amendment 0002 4 March 2010

IV. APPLICATION AND SUBMISSION INFORMATION

2. Content and Format of White Papers/Full Proposals - Content and Format of White Papers

The Proposals submitted under this BAA are expected to be unclassified. However, classified proposals are permitted. All proposal submissions will be protected from unauthorized disclosure in accordance with FAR 15.207, applicable law, and DHS regulations. Offerors are expected to appropriately mark each page of their submission that contains proprietary information.

White Paper Format

· Paper Size – 8.5 x 11 inch paper. 11 x 17 pages may be used but shall count as two pages.

· Margins – 1 inch

· Spacing – single or double-spaced

· Font – Times New Roman, 12 point

· Number of Pages – White Papers shall not exceed ten (10) single-sided pages (excluding cover page, resumes, cost, schedule, and socio-economic commitment). Do not include a cover sheet, as one will be automatically generated for submitted White Papers using the information provided during registration. If a cover sheet is submitted with the White Paper, it will be counted toward the total 10 page White Paper limit.

· Files are not to exceed 10 megabytes in size. A proposal shall consist of ONE electronic file in portable document format (PDF), readable by IBM-compatible personal computers (PCs).

· White Papers exceeding the page/file size limit may not be evaluated and shall be considered as un-responsive.

· Classified volumes must follow the same submission process as provided below in Section IV, Paragraph 5; additionally, Offerors shall submit to the website a placeholder pdf file consisting of a single page with the words “Classified Volume Forthcoming” in the center of the page.

· Cover Sheet – The Cover Sheet is automatically generated during the submission of the White Paper to the BAA website. This is not the same as the Offeror’s Cover Page.

· Cover Page – The Cover Page shall be labeled “WHITE PAPER”, and must include the following:

1) BAA Number 10-01

2) Title of Proposal

3) Topical Area;

4) Size of Business of the Prime and Subcontractors’(Large, Small, Non-Profit, etc)

5) Identity of prime Offeror’s name and address and complete list of subcontractors name and address, if applicable;

6) Technical contact (name, address, phone/fax, electronic mail address for Prime and Subcontractors’);

7) Administrative/business contact (name, address, phone/fax, electronic mail address for prime and Subcontractors’); and,

8) Duration of effort (separately identify the basic effort and any options);

9) DHS S&T Point of Contact (name of the S&T individual that was contacted prior to submission). A list of organizations is provided in Section II, Paragraph 8 of this BAA 10-01.

10) Dunn & Bradstreet Number;

11) Number of employees of Prime and each Subcontractor

12) Acknowledgement the Offeror is registered in Central Contractor Registration (CCR);

13) Statement on whether or not the Prime and Subcontractors; have been audited by a Government organization (Defense Contract Audit Agency, Office of Naval Research, etc.), and if each Offeror has a Government-approved accounting system.

14) Statement specifying compliance with FAR Clause 52.222-54 “Employment Eligibility Verification”.

Executive Summary – An overview of the White Paper.

· Technical Concept – A description of the technical concept, including anticipated risks and approaches to mitigate the risks. Describe the basic scientific or technical concepts that will be used in each component or subsystem comprising your proposed solution to the problem described above. What is unique about your solution and what advantages might it afford compared to alternate approaches other workers in this field have taken? What has been the extent of your or your team’s past experience in working with or developing the technologies comprising your system? What particular scientific, technical and/or engineering issues need to be addressed and resolved to demonstrate feasibility?

· Operational Concept - A description of the operational concept used in the proposed technical solution to accomplish the objectives. Explain how the performance of your proposed solution can be expected to meet or exceed and be measured against each of the specific technical attributes and/or performance enhancements. What are the key scientific, technical, or engineering challenges and the timing for each that must be met in order to successfully complete this project? Describe all required material and information, which must be provided by the Government to support the proposed work.

· Operational Utility Assessment Plan – A plan for demonstrating and evaluating the operational effectiveness of the Offeror’s products in exercises, including evaluation metrics. Briefly explain your concept of how you will develop and demonstrate a system or system component. Point out the critical path technologies or key technical challenges you will face when building this system or component and your plans for meeting these challenges. Explain how you will demonstrate the system or component performance relative to the performance or enhancement goals described in the proposal.

· Deliverables – A list of any deliverables (including data deliverables and asserted limited rights or restricted rights in such data deliverables) for the effort; with due date(s) (the number of calendar days after the effective date of award).

· Technology Risk Assessment- Briefly describe the technical risk involved with the concept and what the plan is to mitigate/address those risks. A more detailed Risk Mitigation Plan will be required for the Proposal should one be requested.

· Management Plan – Briefly describe the Offeror’s qualifications and experience in similar development efforts. Present the qualifications of the principal technical team leaders, including short resumes. What has been the extent of your team’s past experience in working with or developing the technologies comprising your system? Describe any partnering arrangements.

· Costs – A one-page summary of anticipated costs segregated by tasks.

If available, a copy of the Offeror’s Forward Pricing Rate Agreement (FPRA) or

Defense Contract Audit Agency Recommended Rates. If an FPRA or Recommended Rates do not exist, provide the proposed indirect and direct rates by year for the prime and subcontractors, including interdivisional transfers.

· Schedule – A one or two page schedule of activities culminating in an operational prototype. Activities the Offeror anticipates to be conducted by the Government must be clearly annotated.

· Small Business Considerations – If the prime Offeror is a large business, a commitment of the Offeror to the use of small business concerns. All Offerors shall indicate their business size status and list all subcontractors and its business size status.

File details come from the government source that posted it. Updated .