LRBAA CY09_PART II_7jan09.doc

Part II:

TECHNICAL SUBMISSION PROCESS

LONG RANGE BROAD AGENCY ANNOUNCEMENT (BAA)

FOR

THE DEPARTMENT OF HOMELAND SECURITY

SCIENCE AND TECHNOLOGY DIRECTORATE

INTRODUCTION:

This solicitation is a Broad Agency Announcement (BAA) as contemplated in Federal Acquisition Regulation (FAR) 6.102(d)(2) and 35.016. A formal Request for Proposal (RFP) will not be issued.

The Department of Homeland Security (DHS) Science & Technology (S&T) Directorate will not issue paper copies of this announcement. DHS S&T reserves the right to select for award and fund all, some, or none of the Full Proposals received in response to this solicitation. No funding for direct reimbursement of proposal development costs will be allowed. Technical and cost proposals (or any other material) submitted in response to this BAA will not be returned. However, depending on the markings on the proposal, DHS S&T will adhere to FAR policy on handling source selection information and proprietary proposals. It is the policy of DHS S&T to treat all proposals as sensitive competitive information and to disclose their contents only for the purposes of evaluation.

Multiple awards are anticipated to be issued through this BAA and will be based on an assessment of the overall best value to the government. Awards will be made based upon the proposal evaluation, funds availability, and other programmatic considerations. Awards may take the form of contracts, grants, cooperative agreements, or other transaction agreements (OTAs). Therefore, the applicable laws and regulations governing the legal vehicle used for award will depend on the legal vehicle chosen by DHS S&T. In the event an Offeror or subcontractor is a Federally Funded Research and Development Center (FFRDC), Department of Energy National Laboratory, or other Federally funded entity, DHS S&T will work with the appropriate sponsoring agency to issue an interagency agreement pursuant to the Economy Act (31 U.S.C. 1531) or other appropriate authority.

Part I of this BAA contains the Technical areas of interest, Divisional Points of Contact, and Divisional requirements. Please refer to Part I to determine if your specific area of interest will assist a DHS division in fulfilling its goals. The DHS publication “High Priority Technology Needs” of June 2008 will also describe areas of interest that are currently being developed. If you determine you have an idea that will be of interest, please open and print this Part II Volume, which will guide you through the requirements of the BAA submission process. It provides details on what shall be included in your White Paper or Full Proposal, explains the process and how to submit, and the evaluation criteria.

I. GENERAL INFORMATION

Business Point of Contact:

Susan Eicher Contracting Officer

Department of Homeland Security

Office of Procurement Operations

Science & Technology Acquisition Division

Washington, DC 20528

Phone: (202) 254-2363 susan.eicher@dhs.gov

1. Catalog of Federal Domestic Assistance (CFDA) Number – 97.065

2. Catalog of Federal Domestic Assistance (CFDA) Title – Homeland Security Advanced Research Projects Agency

3. Other Information -

This announcement is restricted to work relating to basic and applied research and that portion of advanced technology development not related to a specific system or hardware procurement. Purchase of capital equipment, that will then be the subject of research and development to effect a modification and ensure that the purchased equipment fulfills DHS requirements is allowed. Contracts, grants, cooperative agreements, and other transaction agreement awards made under this BAA are for scientific study and experimentation directed towards advancing the state-of-the art or increasing knowledge or understanding.

Please note: THIS ANNOUNCEMENT DOES NOT COVER TECHNICAL, ENGINEERING AND OTHER TYPES OF SUPPORT SERVICES. Any submissions that indicate this is the intent will be rejected by the Long Range BAA Advisory Board and will be considered as not compliant with the BAA guidelines. It will not be further reviewed. The Contracting Officer will send a rejection letter stating the submission was not compliant with the BAA.

II. AWARD INFORMATION

The amount and period of performance of each selected Full Proposal will vary depending on the research area and the technical approach to be pursued by the selected Offeror.

If Offerors are extending work performed under other projects, it must clearly identify the point of departure and what existing work will be brought forward and what new effort will be performed under this BAA. Please ensure that it is clear that the work being submitted is independent of what may have happened previously (i.e. the next logical step in the research, or investigating a situation that was discovered and not funded under the previous award). Submitting existing Statements of Work and indicating which steps have been completed is not sufficient justification for an independent award under the LRBAA.

DHS S&T reserves the right to select for award and fund all, some, or none of the Full Proposals received in response to this solicitation. If an award decision is made, understand that a negotiation process will determine how much of the selected proposal is actually funded. A Division may select a proposal but only be interested in specific portions.

A Full Proposal may be “Selected but not Funded” immediately. This must not be considered as a guarantee to fund but as an indication that the proposed effort has merit and if and when funds become available, contract negotiations will begin. There could be many reasons for this, including the Subject Matter Expert (SME) believes it is a good investment but does not have the money at the time of selection. A proposal that is Selected but not Funded may also be of interest to another division who may have money to fund. Changing priorities or expected changes in focus areas could also delay an award. An Offeror will receive notification that its proposal was selected but not funded and the divisional Contracting Officer will be in touch with it to determine the duration that the cost proposal will be valid. The Offeror may be required to revise that portion prior to contract award.

III. ELIGIBILITY INFORMATION

This BAA is open to ALL responsible sources. Foreign or foreign-owned Offerors are advised that their participation is subject to foreign disclosure review procedures, applicable export control laws, and other applicable Federal laws, regulations, and policies pertaining to U.S Government business with foreign entities.

Offerors may include single entities or teams from private sector organizations, Government laboratories, airport authorities, Federally Funded Research and Development Centers (FFRDCs), and academic institutions.

Federally Funded Research & Development Centers (FFRDCs), including the Department of Energy National Laboratories and Centers, are eligible to respond to this BAA, individually or as a team member of an eligible principal Offeror, as so long as they are permitted to respond to solicitations such as this under the applicable sponsoring agreement between the Government and the specific FFRDC.

Historically Black Colleges and Universities (HBCU), Minority Institutions (MI), Small Business concerns, Small Disadvantaged Business concerns, Women-Owned Small Business concerns, Veteran-Owned Small Business concerns, Service-Disabled Veteran-Owned Small Business concerns, and HUBZone Small Business concerns are encouraged to submit proposals and to join other entities as team members in submitting proposals. However, no portion of this BAA will be set-aside pursuant to FAR Part 19.502-2.

Independent organizations and teams are encouraged to submit proposals. However, Offerors must be willing to cooperate and exchange software, data and other information in an integrated program with other contractors, as well as with system integrators, selected by DHS S&T.

Organizational Conflict of Interest issues will be evaluated on a case-by-case basis as outlined below. Offerors who have existing contract(s) to provide scientific, engineering, technical and/or administrative support directly to DHS S&T will receive particular scrutiny.

Organizational Conflict of Interest:

(a) Disclosure. The Offeror must represent, as part of its proposal and to the best of its knowledge that: (1) It is not aware of any facts which create any actual or potential organizational conflicts of interest relating to the award of this contract; or (2) It has included information in its proposal, providing all current information bearing on the existence of any actual or potential organizational conflicts of interest, and has included the mitigation plan in accordance with paragraph (d) of this provision.

(b) Determination. The Contracting Officer may determine that this effort may result in an actual or potential conflict of interest, or may provide one or more Offerors with the potential to attain an unfair competitive advantage based on the information provided or based on knowledge of the Contracting Officer.

(c) If any such conflict of interest is found to exist, the Contracting Officer may (1) disqualify the Offeror, or (2) determine that it is otherwise in the best interest of the United States to contract with the Offeror and include the appropriate provisions to mitigate or avoid such conflict in the contract awarded. After discussion with the Offeror, the Contracting Officer may determine that the actual conflict cannot be avoided, neutralized, mitigated, or otherwise resolved to the satisfaction of the Government, and the Offeror may be found ineligible for award.

(d) Mitigation/Waiver. If an Offeror with a potential or actual conflict of interest or unfair competitive advantage believes it can be mitigated, neutralized, or avoided, the Offeror may submit a mitigation plan to the Contracting Officer for review. Award of a contract where an actual or potential conflict of interest exists shall not occur before Government approval of the mitigation plan.

(e) Other Relevant Information. In addition to the mitigation plan, the Contracting Officer may require further relevant information from the Offeror. The Contracting Officer will use all information submitted by the Offeror, and any other relevant information known to DHS, to determine whether an award to the Offeror may take place, and whether the mitigation plan adequately neutralizes or mitigates the conflict.

(f) Corporation Change. The successful Offeror shall inform the Contracting Officer within thirty (30) calendar days of the effective date of any corporate mergers, acquisitions, and/or divestures that may affect this provision.

(g) Flow-down. The contractor shall insert the substance of this clause in each first tier subcontract that exceeds the simplified acquisition threshold.

IV. APPLICATION AND SUBMISSION INFORMATION

1. Application and Submission Process -

Oral Presentations – Prospective Offerors are NOT provided the opportunity to make oral presentations as part of the submission process for the Long Range BAA. Offerors may still meet with divisional representatives on occasion regarding initiatives they are working on but this does not constitute a submission to the Long Range BAA. Pre-submission meetings or discussions may be requested by the division to fully understand the application and full breadth of the research being undertaken. When these pre-submission meetings take place, White Papers will still be required to be submitted for consideration under the Long Range BAA (and must be submitted through the website or will not be accepted and tracked under the Long Range BAA process.)

If an Offeror is not encouraged (discouraged) to submit a White Paper, it is expected the Offeror will not submit a White Paper to any division. The SME who evaluated the Offeror’s original input (whether through e-mail or a presentation) has already considered how well it has met the requirements and goals of what the division is currently working on, how unique its solution is (for situations not considered yet) as well as the current funding levels available. If it is a worthy idea but the money is simply not available, most SMEs will indicate that and request the Offeror submit a White Paper at a later date. Submission of a White Paper that has already been discouraged may not be evaluated depending on the documentation the SME can provide to support the original decision to discourage you to submit a White Paper Submitting a response to this BAA:

A. Submission instruction for the BAA Website.

White Paper and Full Proposal submissions will not be accepted from organizations that have not registered. Any organization that wishes to participate in this solicitation must register at https://baa.st.dhs.gov before the due date and time established in this BAA. There will be no exceptions. It is very important to follow the registration instructions. Offerors who have not registered by the mandatory White Paper website registration deadline will not be permitted to submit a White Paper and thus will not be able to submit a proposal later. Offerors must coordinate with all members of their team to ensure the registration process is done correctly and in a timely manner.

To begin the registration process, go to https://baa.st.dhs.gov and select BAA 09-05 from the list on the left side of the screen then select the appropriate topic area. Upon proper selection, buttons for registration and submission will appear. Select the appropriate registration button and fill in the requisite fields, then submit your registration for White Paper (or Full Proposal) submission. Once the registration process is complete, registrants will receive a control identification number via email. This control number is necessary to begin the White Paper submission process. It is not used internally at DHS to track your paper (a new number is generated once your submission has been received thought the website and that is what is tracked for the review by the Advisory Committee and release to an SME for evaluation).

To submit a White Paper, select the appropriate submission button, fill out the requisite fields, upload the files and then submit. Users will receive confirmation of their submission via email. An Offeror may revise its White Paper submission until the deadline. There is no limit to the number of White Paper submissions per Offeror; however, if a White Paper or Full Proposal is not accepted, do not resubmit the same White Paper or Full Proposal under this BAA with the intent to have another division evaluate it. The Advisory Committee pre-screens all submissions for compliance with the BAA instruction and, when appropriate, recommends that SMEs that cross divisional boundaries evaluate the paper to ensure all possible applications are considered.

In teaming situations, the lead organization must remain the same on both the White Paper and, if selected, the Full Proposal. Any Full Proposal submitted by entities who were not the prime for the White Paper submission will be considered non-responsive.

Full Proposals shall be uploaded in accordance with instructions provided during registration. As with the White Papers, only unclassified volumes are to be submitted via the website.

For classified submissions, see Section IV, Paragraph 5 below for handling instructions; additionally, Offerors shall submit to the website a placeholder portable document format (PDF) file consisting of a single page with the words “Classified Volume Forthcoming” in the center of the page.

The 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.

DHS S&T’s initial evaluation of Offerors’ White Papers will give Offerors an indication of whether a Full Proposal may result in an award. Notification of the completion of DHS S&T evaluations of the White Papers will likely be issued via E-mail. Detailed technical and cost proposals will be subsequently encouraged from those Offerors whose proposed technologies have been selected through the aforementioned notification as being of "particular value" to DHS S&T. However, any such selection does not assure a subsequent award.

Full Proposals will not be accepted unless a White Paper is first submitted. The website will be modified to not accept a Full Proposal unless there is an accompanying White Paper number. This change in the process from last year will allow DHS to conduct the review in a “2 step” fashion. To remain partial and not provide any Offeror with information not available to all potential Offerors, once a White Paper is submitted by the Offeror, DHS personnel will not be permitted to engage in a discussion regarding the content of the White Paper, except as provided below. The only exceptions will be handled by the Contracting Officer who could contact the Offeror for clarification on a specific statement, like a delivery date (as an example). Once the White Paper has been officially reviewed and the Offeror has received notification of the result (either encouraged or not encouraged for the submission of a Full Proposal), the SME/Division will be free to dialogue with the selected Offeror only on the topic again until the Full Proposal is actually submitted. Then, all dialogue between DHS personnel and the Offeror must cease again until the Full Proposal is evaluated. If an Offeror is discouraged from submitting a Full Proposal based upon SME/Division review of the Offeror’s White Paper, the Offeror is still not precluded from submitting a Full Proposal. An Offeror whose White Paper is not selected may not contact the SME/Division after receiving notification. All communication after not being selected shall be handled by the Contracting Officer.

Due to the large number of White Papers typically submitted, DHS S&T may not offer debriefings to Offerors. The due date for receipt of White Papers or Full Proposals is 4:30 PM (Eastern Standard Time) on December 31, 2009. White Papers or Full Proposals WILL NOT BE ACCEPTED after December 31, 2009, with the exception of a proposal that resulted from a White Paper Selected near that date. A new deadline will be provided to those select vendors.

2. Content and Format of White Papers/Full Proposals - 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.

Full Proposal Format – Volume 1 - Technical and Volume 2 - Cost Proposal

· Paper Size – 8.5 x 11 inch paper

· Margins – 1 inch

· Spacing – single or double-spaced

· Font – Times New Roman, 12 point

· Number of Pages – Volume 1 is limited to no more than 40 single-sided pages. Volume 2 has no page limitations. Limitations within sections of the Technical Proposal are indicated in the individual descriptions shown below. The cover page, table of contents, and resumes are excluded from the page limitations. See description of a cover page and cover sheet below.

· 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) and excel spreadsheet (include all calculations).

· Full Proposals exceeding the page/file size limit may not be evaluated and shall be considered as unresponsive.

· 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.

White Paper Content

· 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 09-05

2) Title of Proposal

3) Topical Area (as described in Section I, Paragraph 5);

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

5) Technical contact (name, address, phone/fax, electronic mail address);

6) Administrative/business contact (name, address, phone/fax, electronic mail address); and,

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

8) 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 I, Paragraph 6 of this BAA.

9) Dunn & Bradstreet Number;

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

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

12) 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 will 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.

Full Proposal Content

Volume 1: Technical Proposal Volume 1 of the Full Proposal shall include the following sections.

· 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: This shall include the words “Technical Proposal” and the following:

1) BAA Number 09-05;

2) Title of Proposal

3) Topical Area (as described in Section I, Paragraph 5);

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

5) Technical contact (name, address, phone/fax, electronic mail address);

6) Administrative/business contact (name, address, phone/fax, electronic mail address); and,

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

8) 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 I, Paragraph 6 of this BAA.

9) Dunn & Bradstreet Number;

10) Acknowledgement the Offeror is registered in Central Contractor registration (CCR);

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

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

· Official Transmittal Letter: This is an official transmittal letter with authorizing official signature. For an electronic submission, the letter can be scanned into the electronic proposal. The letter of transmittal shall state whether this proposal has been submitted to another government agency, other than DHS S&T, and if so, which one and when.

· Table of Contents.

· Executive Summary: Summarize the proposal and the expected benefits of the solution.

· Proposed Use for DHS S&T: A detailed summary of how the proposal’s product(s) supports the targeted end user (e.g., the first responder community) in an operational context. Include quantitative specifications for how the products will improve operational performance.

· Statement of Work: A Statement of Work (SOW) and a Work Breakdown Structure (WBS) clearly detailing the scope and objectives of the effort, the technical approach, and the performance goals. It is anticipated that the proposed SOW and WBS will be incorporated as an attachment to the resultant award instrument. To this end, such proposals must include a severable stand-alone SOW and WBS without any proprietary restrictions, which can be attached to the contract or agreement award. The WBS must include a detailed listing of the technical tasks/subtasks in hierarchical fashion for the tasks required to accomplish the effort. The WBS format must be complete to at least WBS level 3. Each task in the SOW shall describe the work to be carried out, the end result of the task, the time allocated, the organization performing the task, the predecessor tasks, the performance goals of the task, and the resources (labor, materials, and services) required. The resources shall be costed to provide a baseline budgeted cost for the applicable task. The SOW shall be at a level sufficient to define the nature of the work to be carried out, measure progress, and understand the relationship of the tasks to one another.

· Project Schedule and Milestones: A summary of the schedule of events and milestones.

· Assertion of Data Rights: Include here a summary of any assertions to any technical data or computer software that will be developed or delivered under any resultant award. This includes any assertions to pre-existing results, prototypes, or systems supporting and/or necessary for the use of the research, results, and/or prototype. Any rights asserted in other parts of the proposal that would impact the rights in this section must be cross-referenced. If less than unlimited rights in any data delivered under the resultant award are asserted, the Offeror must explain how these rights in the data will affect its ability to deliver research data, subsystems, and toolkits for integration as set forth below. Additionally, the Offeror must explain how the program goals are achievable in light of these proprietary and/or restrictive limitations. If there are no claims of proprietary rights in pre-existing data, this section shall consist of a statement to that effect.

Proposals submitted in response to this solicitation shall identify all technical data or computer software that the Offeror asserts will be furnished to the Government with restrictions on access, use, modification, reproduction, release, performance, display, or disclosure. Offeror's pre-award identification shall be submitted as an attachment to its offer and shall contain the following information:

(1) Statement of Assertion. Include the following statement: “The Offeror asserts for itself, or the persons identified below, that the Government's rights to access, use, modify, reproduce, release, perform, display, or disclose only the following technical data or computer software should be restricted:”

(2) Identification of the technical data or computer software to be furnished with restrictions. For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process as specifically as possible (e.g., by referencing specific sections of the proposal or specific technology or components). For computer software or computer software documentation, identify the software or documentation by specific name or module or item number.

(3) Detailed description of the asserted restrictions. For each of the technical data or computer software identified above in paragraph (2), identify the following information:

(i) Asserted rights. Identify the asserted rights for the technical data or computer software.

(ii) Copies of negotiated, commercial, and other non-standard licenses. Offeror shall attach to its offer for each listed item copies of all proposed negotiated license(s), Offeror's standard commercial license(s), and any other asserted restrictions other than Government purpose rights; limited rights; restricted rights; rights under prior government contracts, including SBIR data rights for which the protection period has not expired; or government’s minimum rights.

(iii) Specific basis for assertion. Identify the specific basis for the assertion. For example:

(A) Development at private expense, either exclusively or partially. For technical data, development refers to development of the item, component, or process to which the data pertains. For computer software, development refers to the development of the software. Indicate whether development was accomplished exclusively or partially at private expense.

(B) Rights under a prior government contract, including SBIR data rights for which the protection period has not expired.

(C) Standard commercial license customarily provided to the public.

(D) Negotiated license rights.

(iv) Entity asserting restrictions. Identify the corporation, partnership, individual, or other person, as appropriate, asserting the restrictions.

Previously delivered technical data or computer software. The Offeror shall identify the technical data or computer software that are identical or substantially similar to technical data or computer software that the Offeror has produced for, delivered to, or is obligated to deliver to the Government under any contract or subcontract. The Offeror need not identify commercial technical data or computer software delivered subject to a standard commercial license.

Estimated Cost of Development. The estimated cost of development for that technical data or computer software to be delivered with less than Unlimited Rights.

Supplemental information. When requested by the Contracting Officer, the Offeror shall provide sufficient information to enable the Contracting Officer to evaluate the Offeror’s assertions. Sufficient information must include, but is not limited to, the following:

(1) The contract number under which the data or software were produced;

(2) The contract number under which, and the name and address of the organization to whom, the data or software were most recently delivered or will be delivered; and

(3) Identification of the expiration date for any limitations on the Government’s rights to access, use, modify, reproduce, release, perform, display, or disclose the data or software, when applicable.

Ineligibility for award. An Offeror's failure to submit or complete the identifications and assertions required by this provision with its offer may render the offer ineligible for award.

This section must be severable, i.e., it will begin on a new page and the following section shall begin on a new page. It is anticipated that the proposed Assertion of Data Rights will be incorporated as an attachment to the resultant award instrument. To this end, proposals must include a severable self-standing Assertion of Data Rights without any proprietary restrictions, which can be attached to the contract or agreement award.

· Deliverables: A detailed list and description of all deliverables and data deliverables the Offeror proposes to provide to the government, the schedule for delivery, and acceptance criteria.

This section must be severable, i.e., it must begin on a new page and the following section must begin on a new page. It is anticipated that the proposed detailed list and description of all deliverables will be incorporated as an attachment to the resultant award document. To this end, proposals must include a severable self-standing detailed list and description of all deliverables without any proprietary restrictions, which can be attached to the contract or agreement award.

· Operational Utility: A detailed plan for assessing the operational utility of the key products of this effort during an operational exercise, including proposed metrics.

· Qualifications: A discussion of the Offeror’s previous accomplishments and work in this area, or closely related area, and the qualifications of the investigators. Key personnel resumes must be attached to the proposal and will not count toward the page limitations.

· Detailed Risk Mitigation Plan: Discuss in detail the technical risk involved with the project and how they will be approached.

· Management Approach: A discussion of the overall approach to the management of the effort, including brief discussions of the total organization, use of personnel, project/function/subcontractor relationships, government research interfaces, and planning, scheduling and control practice. Identify which personnel and subcontractors (if any) will be involved. Include a description of the facilities that are required for the proposed effort with a description of any Government-Furnished Equipment/Hardware/Software/Information required, by version and/or configuration.

· 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.

VOLUME 2: Cost Proposal

· 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.

· The Cost Proposal must consist of a cover page and two parts.

· Part 1 must provide a detailed cost breakdown of all costs by cost category by calendar/fiscal year.

· Part 2 must provide a detailed cost breakdown by task/sub‑task using the same task numbers in the Statement of Work.

Options must be separately priced. The cost of preparing White Papers and/or Full Proposals in response to this solicitation is not considered an allowable direct charge to any resulting contract or any other award, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18.

· Cover Page: The use of the SF 1411 is optional. The words “Cost Proposal” must appear on the cover page in addition to the following information:

· BAA Number BAA 09-05

· Title of Proposal;

· Topical Area;

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

· Technical contact (name, address, phone/fax, electronic mail address)

· Administrative/business contact (name, address, phone/fax, electronic mail address);

· Duration of effort (separately price out the basic effort and any options) and;

· DUNS number and CAGE code.

· Identify the cognizant Defense Contract Audit Agency (DCAA) Point of Contact (POC) with a telephone number.

· Part 1: Detailed breakdown of all costs by cost category by calendar/fiscal year and include a summary explaining how each element is applied in the cost proposal:

Direct Labor – Individual labor category or person, with associated labor hours and unburdened direct labor rates;

Indirect Costs – Fringe Benefits, Overhead, G&A, COM, etc. (Must show base amount and rate);

If available, a copy of the Offeror’s Forward Pricing Rate Agreement (FPRA) or Defense Contract Audit Agency (DCAA) Approved and/or Recommended Rates.

· Travel – Separate by destinations and include number of trips, durations-number of days, number of travelers, per diem (hotel and meals in accordance with the Federal Travel Regulations), airfare, car rental, if additional miscellaneous expense is included, list description and estimated amount, etc.;

· Subcontract – A cost proposal as detailed as the Offeror’s cost proposal will be required to be submitted by the subcontractor. The subcontractor’s cost proposal can be provided in a sealed envelope with the Offeror’s cost proposal or will be requested from the subcontractor at a later date. The subcontractor’s cost proposal must include on company letterhead the complete company name and mailing address, technical and administrative/business point of contacts, email address, and telephone number. Include the DUNS number. Include the DCAA Office and POC with telephone number.

· Consultant – Provide consultant agreement or other document which verifies the proposed loaded daily/hourly rate and labor category;

· Materials must be specifically itemized with costs or estimated costs. Where possible, indicate purchasing method (e.g., competition, engineering estimate, market survey, etc.). Include supporting documentation, i.e. vendor quotes, catalog price lists, and past invoices for similar purchases;

· Other Directs Costs (ODCs), particularly any proposed items of equipment or facilities. Equipment and facilities generally must be furnished by the Offeror. Justifications must be provided when Government funding for such items is sought.

· Fee/Profit including fee percentage.

· Provide a time-phased spend plan which includes all costs proposed, i.e., labor, travel, materials, and ODCs (contractor format is acceptable),

· Provide a basis of estimate (BOE) for all proposed labor. The BOE must provide the rationale for the proposed labor category (ies) and proposed labor hours for each labor category (contractor format is acceptable).

· Part 2 : Cost breakdown by task/sub‑task using the same task numbers in the Statement of Work.

3. Significant Dates and Times -

This announcement will remain open until December 31, 2009. White Papers and Full Proposals may be submitted in accordance with Section IV, Paragraph 1. Evaluations and awards will occur on “rolling selection” basis. Generally evaluations will occur within 60 - 90 days from receipt the White Paper or Full Proposal. This is not a firm commitment to 60 – 90 days as the Subject Matter Experts must balance their commitments but efforts will be made to keep the time delay to a minimum. Contract award resulting from a selected Full Proposal should occur approximately within 90 days from awardee notification, successful negotiations and/or subject to availability of funds.

4. Submission of Late White Papers and Full Proposals –

White Papers and Full Proposals WILL NOT BE ACCEPTED after the published due dates.

5. Address for Submission of Classified White Papers and Full Proposals – CLASSIFIED SUBMITTALS CANNOT BE TRANSMITTED VIA THE WEB SITE. Regardless, the submitter must first register online following the registration instructions provided in Section IV, Paragraph 1 to obtain a registration number. Offerors shall print out the registration form and attach it as a coversheet to the classified submittal located after the classification coversheet. 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. The classified submittal must be submitted via proper classified courier or proper classified mailing procedures as described in the National Industrial Security Program Operating Manual (NISPOM). Offerors may view the NISPOM document online at http://www.dss.mil/isec/nispom.htm. Classified submittals must include ten (10) printed copies and one electronic copy on compact disc recordable (CD-R) media (do not use re-writable media (CD-RW/RW-/RW+)). Each copy must be accompanied by the coversheet, which does not count towards the page limitations described in Section IV, Paragraph 1.

Classified documents MUST be received by the applicable due date and time.

Classified proposals can be delivered by courier to:

Director of Security

Department of Homeland Security

Science and Technology Directorate

1120 Vermont Avenue NW

Room 10-112 Washington, DC 20005

Electronic copies can be emailed to:

chris.featherston@dhs.sgov.gov NOTE: Please send an unclassified alert email to Christopher.featherston@dhs.gov and BAA09-05@dhs.gov before emailing classified information to chris.featherston@dhs.sgov.gov.

Classification does not eliminate the requirement for offerors to comply with all instructions and deadlines in this BAA.

6. Further Assistance Needed for this BAA

The applicable electronic address for all correspondence for this BAA is:

BAA09-05@dhs.gov.

7. Proprietary Protection

S&T has contracted for various business and staff support services, some of which require contractors to obtain administrative access to White Papers, Full Proposals, and Offerors’ presentations (all of which may include proprietary information). Contractors involved in providing technical assistance and administrative assistance to S&T have signed general non-disclosure agreements and organizational conflict of interest statements. Any objection to contractor access for purposes of technical assistance or administrative assistance must be in writing to the Contracting Officer and shall include a detailed statement of the basis for the objection.

Proposals will be considered source selection information and will be protected accordingly, if appropriately marked. Proposals will be reviewed only by authorized Government representatives and assigned evaluators, which may include support contractors. Only Government representatives will make selection decisions.

V. EVALUATION INFORMATION

1. White Papers and Full Proposals will be evaluated in accordance with the following criterion.

The evaluation of White Papers and Full Proposals will be accomplished through an independent technical review of each; using the evaluation factors listed below which are in descending order of importance. The subfactors are of equal weight within each factor.

A. Overall scientific and technical merits of the proposal

1. The degree of innovation and potential to offer a revolutionary increase in capability or a significant reduction in cost commensurate with the potential risks of the innovative approach;

2. The soundness of the technical concept;

3. The Offeror’s awareness of the state-of-the-art and future technology trends;

4. The Offeror’s understanding of the scope of the problem and the technical effort needed to address it; and

5. Intellectual property rights offered.

6. The Offeror’s understanding of what the risks of the project are and how those risks are being identified and addressed, as well as how the proposed solution compares to similar work performed.

B. The Offeror’s capabilities, related experience, and past performance, including the qualifications, capabilities, and experience of the proposed principal investigator and personnel.

1. The quality of technical personnel proposed;

2. The Offeror’s experience in relevant efforts with similar resources; and

3. The ability to manage the proposed effort.

C. Cost/Price, including cost realism and reasonableness analyses. Each response will be reviewed for cost realism, reasonableness, and overall best value to the Government. Members of the evaluation team may presume that the technical approach provided by the Offeror serves as a rationale for the labor mix and labor hours used.

D. Extent of subcontracting commitment. For proposed awards to be made as contracts to large businesses, the small business consideration section of each proposal will be evaluated based on the extent of Offeror’s commitment in providing meaningful subcontracting opportunities for small businesses, small disadvantaged businesses, woman-owned small businesses, HUBZone small businesses, veteran-owned small businesses, service disabled veteran-owned small businesses, historically black colleges and universities, and minority institutions. All Offerors shall indicate their business size status (listed above) and list each subcontractor and its business size status.

The Factors and Subfactors will be evaluated using the Ratings provided below.

FACTOR A – OVERALL SCIENTIFIC AND TECHNICAL MERITS OF THE PROPOSAL.

EXCELLENT: The proposed research, technical approach, system and/or system component fully and completely meets the expectations of the Broad Agency Announcement, and sets forth plans, approaches and analyses that show a high probability of meeting all of the Department of Homeland Security’s desired attributes and performance parameters given in BAA 09-05. The risks and technical challenges associated with simultaneously achieving all of the desired attributes and performance parameters are fully and completely understood, and the strategy to address those issues is robust.

VERY GOOD: The proposed research, technical approach, system and/or system component nearly meets the expectations of the BAA, and sets forth plans, approaches and analyses that show a strong promise of nearly meeting all of the Department of Homeland Security’s desired attributes and performance parameters given in BAA 09-05. Planning considerations demonstrate that the Offeror is able to interpret system attribute and performance parameter goals and project them into plans/analyses, etc., in a clear, concise manner. The technical and managerial approach to the proposed work displays sufficient innovation, technical competence and managerial ability.

GOOD: The proposed research, technical approach, system and/or system component almost meets the expectations of the BAA, and sets forth plans, approaches and analyses that show a reasonable possibility of meeting the Department of Homeland Security’s desired attributes and performance parameters given in BAA 09-05. The Offeror has presented an orderly plan to meet the stated goals, but the proposal does not necessarily demonstrate any exceptional features, innovations, analysis or originality. The technical analyses satisfactorily meet requirements and are technically correct.

FAIR: The proposed research, technical approach, system and/or system component indicates a shallow or less than full understanding of the problem.