FBO 6.6.16 -ApexSaS-BAA.pdf

HSHQDC-16-R-B0004

Department of Homeland Security Science and Technology (S&T) Directorate

EXPLOSIVES DIVISON

BROAD AGENCY ANNOUNCEMENT (BAA)

Apex Screening at Speed Program (Apex SaS)

June 2016

Table of Contents

1. GENERAL INFORMATION

1.1 Introduction

1.2 Program Mission and Objectives

1.3 Foreign Government Participation

1.4 Agency Name

1.5 Research Opportunity Title

1.6 Program Name

1.7 Research Opportunity Number

1.8 Response Dates

1.9 Government Representatives

1.10 Inquiries

2. RESEARCH OPPORTUNITY DESCRIPTION

2.1 Anticipated Topic Areas (TAs)

2.2. Type Classifications

3. TESTING AND EVALUATION FACILITIES

4. AWARD INFORMATION

4.1 Anticipated Funding for the Program

4.2 Anticipated Number of Awards

4.3 Anticipated Award Types

4.4 Expected Amount of Individual Awards

4.5 Anticipated Period of Performance for Individual Awards

5. ELIGIBILITY INFORMATION

6. DOWNLOAD OF THIS BAA

7. REGISTRATION IN DHS S&T BAA PORTAL (Must be completed prior to uploading any submissions.)

7.1 Access to DHS S&T BAA Portal

7.2 Company/Organization Registration

8. WHITE PAPER SUBMISSION REQUIREMENTS

8.1 Calls May Request White Papers

8.2 Submission Dates and Times

8.3 No Classified Documents

8.4 No Proposal Submission Authorized Without White Paper Submission

8.5 Multiple White Papers

8.6 White Paper Format

8.7 White Paper Content

8.8 Non-compliant White Papers

9. PROPOSAL SUBMISSION REQUIREMENTS

9.1 Submission Requirements

9.2 Submission Dates and Times

9.3 No Classified Documents

9.4 Multiple Proposals

9.5 Proposal Format

9.6 Proposal Content

9.7 Non-compliant Proposals

10. PROCEDURES FOR SUBMITTING WHITE PAPERS AND PROPOSALS IN DHS

S&T BAA PORTAL

10.1 Company/Organization Registration

10.2 White Paper and Proposal Registration

10.3 DHS S&T BAA Portal Help Desk

11. EVALUATION OF WHITE PAPERS AND PROPOSALS

11.1 General

11.2 Evaluation Criteria

11.3 Basis for White Paper and Proposal Selection

11.4 Evaluation Panel

11.5 Notification to Offerors of Evaluation Findings

12. OTHER TERMS AND CONDITIONS

12.1 NAICS

12.2 System for Award Management (SAM)

12.3 Information for White Paper and Proposal Respondents

12.4 Organizational Conflict of Interest

12.5 Export Control

12.6 Intellectual Property

12.7 Publication of Research Results

12.8 Adequate Accounting System for Cost Reimbursement Type Contracts

12.9 Certificate of Current Cost or Pricing Data

12.10 Applicable Provisions and Contract Clauses

12.11 Government Property, Government Furnished Equipment (GFE) and Facilities

12.12 Safety Act

12.13 Security Classification

12.14 Subcontracting Plan

12.15 Additional Deliverables

12.16 Types of Changes That May Occur to Awards Under This BAA

12.17 Reporting

Appendix A. Company to Company Agreement

1. GENERAL INFORMATION

1.1 Introduction.

This solicitation is a Broad Agency Announcement (BAA) as contemplated in Federal Acquisition Regulations (FAR) 6.102(d)(2) and 35.016. A formal Request for Proposal (RFP) will not be issued in this matter. This announcement does not request any proposals at this time.

Solicitations (or Calls) requesting white papers or proposals will be accomplished via amendments to this BAA. This BAA is issued in support of Department of Homeland Security (DHS) Science and Technology Directorate (S&T) Homeland Security Advanced Research Projects Agency (HSARPA) Explosives Division (EXD) targeted research and development (R&D) projects.

This Apex Screening at Speed (Apex SaS) BAA will be open for five years from the date publicized on the Government’s Point of Entry (GPE), Federal Business Opportunities (FBO) website. The strategy for a five-year BAA with the ability to make Calls throughout the life of the BAA will allow for quick and efficient delivery of practical R&D services to generate potential solutions for each Topic Area.

Periodically during the five years, individual Calls for white papers or proposals responding to the specified Apex SaS program capability need will be solicited in FBO against this BAA.

Each Call will (1) identify specific details regarding the Call Topic Area, (2) identify submission instructions in addition to those outlined in this BAA, and (3) contain a common cutoff date for submissions. The Call details will be such that interested and capable contractors can tailor a response and provide a submission in response to the Call.

1.2 Program Mission and Objectives.

Evolving threats have created a need for technological improvements in order to securely screen the growing number of people who pass through security checkpoints each year. This applies to many law enforcement and security agencies at the federal, state, local, tribal and territorial level.

As an example, before 9/11, the average aviation checkpoint processed 350 passengers per hour.

Today, increased security measures have reduced that number below 150. Limitations in current technology require people to divest, and later collect, some categories of their accessible belongings (refers to carry-on items, personal electronics, and carry-on baggage, here after refer to as “carry-on items”) prior to transiting the checkpoint. This divesting and collecting process can take significant time (35 seconds and 40 seconds per passenger, respectively), heavily burden Transportation Security Administration (TSA) resources, and pose a major inconvenience to people. As the Federal Aviation Administration (FAA) forecasts a 2.1% annual increase in passenger volume over the next 20 years, technology must quickly become more efficient as it becomes more secure.

System limitations also lead to false alarms, requiring additional time and resources to resolve.

As the threat environment continues to evolve, current technology and procedures are limited in their ability to adapt rapidly. In some cases, neither the technology nor the procedures are adequate. Advanced threats have compelled TSA to institute regulations (e.g., ‘3-1-1’ quantity restrictions on liquids/aerosols/gels (LAGs), shoe removal, electronics divestiture) which inevitably force people to surrender benign items (such as drinks and cosmetics) and increase the number of discrete items that must be screened. Finally, the Automated Target Recognition

(ATR) capability of currently deployed screening systems is only certified to detect lower TSA Threat Tiers in baggage and on people. The handling of higher threat levels (lower masses, different form factors, etc.) is an identified gap for the TSA that requires new hardware and software to overcome.

The primary component driving requirements for Apex SaS is TSA. S&T will, however, work closely with other DHS operational organizations such as United States Secret Service (USSS) and Federal Protective Service (FPS) to identify and incorporate their unique requirements as funding and time allows.

The end goal of the Apex SaS is to develop and demonstrate faster and more robust person and personal item / carry-on technologies before the end of 2020. For the TSA example, technologies are expected to have the following capabilities:

Detect threats at TSA’s highest standard (Tier IV)

Screen 300+ people per lane per hour (double 2013 throughput) as well as their personal and carry-on baggage by:

o Screening people without the divestiture of outerwear, shoes, belts, or headwear o Screening LAGs without removal from carry-on baggage o Lifting restrictions on the quantity and size of LAGs in carry-on baggage o Screening personal electronics without removal from carry-on baggage o Significantly reducing false alarms

Support TSA’s development and implementation of the:

o Security Technology Integrated Program (STIP) o Dynamic Aviation Risk Management System (DARMS) strategy

Other DHS stakeholders’ requirements will be similarly scoped with throughput of people per hour, characteristics of threats to be detected and systems with which to be integrated.

1.3 Foreign Government Participation.

Security is a global concern and DHS has collaborative activities with several countries. As a result, this BAA intends to have foreign government participation, to include access to both white papers and proposal submissions for purposes of determining joint-funding and to include joint participation in overseeing projects throughout the contract period of performance. Foreign government participation will be determined by Topic Area for each Call based on DHS collaboration and may include any of the following international partners: (a) the United Kingdom of Great Britain and Northern Ireland; (b) the Government of Australia; (c) the Government of Canada; (d) the Kingdom of the Netherlands; (e) the European Union; (f) the Government of Germany; (g) the Government of Israel; (h) the Kingdom of Sweden; (i) the Government of New Zealand; and (j) the Government of Singapore.

In addition, foreign government personnel from any one of the aforementioned countries may participate in the evaluation process as peer/scientific reviewers of submitted white papers and/or proposals if their respective nation has been identified in the individual Call made under this BAA. In the event that foreign government personnel do participate in the evaluation process, DHS will share white papers and proposals subject to the provisions for handling both

“Controlled Unclassified Information” and “Business Confidential Information,” as stated in each country’s international agreement with the DHS or the U.S. Government. In addition, foreign government personnel are not permitted to release any information to third parties, including others in their organization. By the act of submitting any material in response to this BAA, offerors are therewith consenting to allowing access to financial, confidential, proprietary, and/or trade secret marked information, and any other material contained therein to foreign government personnel.

Intellectual Property Implications: Offerors should note that, in the case of individual calls where a foreign government is a participant, the technical annex or other governing document may require that the foreign government acquire the same rights as the United States.

1.4 Agency Name.

Department of Homeland Security Science & Technology Directorate Washington, DC 20528

1.5 Research Opportunity Title. Aviation Security Research and Development

1.6 Program Name. Screening at Speed

1.7 Research Opportunity Number. The number on the cover page of this BAA.

1.8 Response Dates. This announcement does not request any white papers or proposals at this time. Individual Calls will be made against this BAA via solicitations posted in FBO at http://www.fbo.gov/. Each individual Call will identify submission requirements for white papers or proposals.

1.9 Government Representatives.

Science and Technology.

John Fortune Apex Screening at Speed (Apex SaS) Manager Explosives Division, Homeland Security Advanced Research Projects Agency DHS Science & Technology 245 Murray Lane, #0200 Washington DC, 20528

Business.

Duane Schatz Contracting Officer Department of Homeland Security Office of Procurement Operations Science & Technology Acquisitions Division 245 Murray Lane, #0210 Washington, DC 20528-0210

1.10 Inquiries.

All contractual or technical inquiries to this BAA must be submitted to: BAA16- B0004@hq.dhs.gov. The program and technical staff will not acknowledge, forward, or respond to any inquiries received in any other manner concerning this BAA or Calls issued against this BAA. Contractual questions and answers will be posted periodically in www.fbo.gov under the announcement for this BAA. All inquiries must be in writing and will not be answered verbally.

For inquiries regarding use of the DHS S&T BAA Portal, refer to paragraph 10.3 below for information on contacting the portal Help Desk.

2. RESEARCH OPPORTUNITY DESCRIPTION

2.1 Anticipated Topic Areas (TAs). The following TAs are representative only.

Computed Tomography for the checkpoint X-ray backscatter (XBS) Diffraction and scatter Phase contrast imaging Photon counting x-ray detectors Millimeter wave (MMW) imaging using meta-materials Standoff trace detection Nuclear quadrupole resonance (NQR) Reconstruction and automated target recognition (ATR) Secondary alarm resolution Computer simulations of scanners, objects and testing Integration at the checkpoint Risk-based screening (RBS) Game theory Deterrence Over- versus under-screening Controlled cognitive engagement

The above TAs are provided to help interested offerors understand the potential Apex SaS program technical areas. A specific TA will be identified in each Call.

2.2. Type Classifications. The Type Classification assigned depends on the maturity of the technology proposed. Offerors submitting white papers and proposals will be required to identify which of the following Type Classifications align with your submission. DHS S&T has the ability to use a phased or stepped approach on Calls, as needed, for various technology levels, e.g., progressing from Type I to Type II, then to Type III.

For actions classified as Type I (New Technologies), the award will include an applied research phase and a development phase, while also including technology demonstrations in an operational environment. The emphasis for this type classification is on R&D with the technology demonstrations in an operational environment. Type I awards will have up to a three year total period of performance, not including operational evaluation, pilot, and/or transition options.

For actions classified as Type II (Prototype Technologies), the award will include a development phase, while also including technology demonstrations in an operational environment. Type II awards will have up to a two year total period of performance, not including operational evaluation, pilot, and/or transition options.

For actions classified as Type III (Mature Technologies), the award will follow a demonstration-upgrade/development-demonstration structure including technology demonstrations in an operational environment. Type III awards will have up to a 12 months total period of performance, not including operational evaluation, pilot, and/or transition options.

3. TESTING AND EVALUATION FACILITIES.

Performers in Apex SaS will be required to test and evaluate their technologies with respect to project goals. DHS uses test results from several different venues to assess program capability and maturity:

Vendor in-house testing to determine status of development and risk mitigation

Transportation Security Laboratory for three levels of Developmental Test and Evaluation (DT&E) for most explosive and threat types

Tyndall Reactive Materials Group for DT&E of certain explosive types/quantities

TSA Systems Integration Facility (TSIF) for integration testing, concept of operations development, and OT&E

Offerors should consider the specific test and evaluation requirements of the proposed technical solutions, identify in the proposal the primary test environment to be used to conduct testing and evaluation, and include a description of the test and evaluation methodology appropriate for the proposal.

4. AWARD INFORMATION

4.1 Anticipated Funding for the Program.

Although subject to official fiscal appropriation, it is anticipated that Apex SaS will have a total of $96M over the next 5 years to support this BAA. The estimated value is not a promise of assured funding in that amount. Funding is uncertain and is subject to change. Changes in availability may occur as a result of Government discretion.

Depending on interest in particular submissions, individual awards may be jointly funded from any of the foreign countries identified in paragraph 1.3 above.

4.2 Anticipated Number of Awards.

The total number of awards under this solicitation is unknown. However, one or more awards may be made from each Call issued during the 5-year open period of this BAA.

4.3 Anticipated Award Types.

It is anticipated awards made for each Call issued against this BAA will be in the form of cost reimbursement type contracts. However, the Government reserves the right to award firm-fixed price contracts, cooperative agreements, Other Transactions (OTs) (if authorized by law at time of award), or interagency agreements to appropriate parties should the situation warrant.

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 EXD will work with the appropriate sponsoring agency to issue an interagency agreement pursuant to the Economy Act (31 U.S.C. 1535) or other appropriate authority.

4.4 Expected Amount of Individual Awards.

Individual award amounts will vary per Call. Therefore, any specified award per Type Classification will be identified on a Call by Call basis.

4.5 Anticipated Period of Performance for Individual Awards.

Paragraph 2.2 above identifies the period of performance for awards made under each Type Classification. Note that submissions must propose the first year of performance as a base period with each additional year as a severable option period. In order for a period of performance to be severable, each period of performance must have a usable/meaningful deliverable(s) that should the Government be unable to obtain funds for any option period, the Government can clearly show value for the money expended to date.

5. ELIGIBILITY INFORMATION

This BAA is open to ALL responsible sources domestic or foreign. Foreign or foreign-owned offerors are advised that their participation is subject to the foreign disclosure review procedures, applicable export control laws, and other applicable federal laws, regulations, and policies pertaining to foreign entities. It is the intent of R&D contracting to obtain a broad base of the best contractor resources from the scientific and industrial community, to include small businesses and as a result, no portion of this BAA will be set aside pursuant to FAR Part 19.502-

2. Offerors may include (but are not limited to):

Single entities or teams from private-sector organizations;

Government laboratories;

FFRDCs, including 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, so long as they are permitted under a sponsoring agreement between the Government and the specific FFRDC.

Historically Black Colleges and Universities (HBCUs);

Minority Institutions (MIs);

Small & Small Disadvantaged Business concerns, including Women-Owned Small Business concerns, Veteran-Owned Small Business concerns, Service-Disabled Veteran- Owned Small Business concerns, and Historically Underutilized Business Zone (HUBZone) Small Business concerns; and

Any academic institutions or non-profit organizations not included in the above categories.

6. DOWNLOAD OF THIS BAA

This BAA should be read in its entirety by any entity considering a submission in response to any Call issued against this BAA. This BAA can be downloaded in its entirety from the FBO website at http://www.fbo.gov. A link to the direct FBO location for this BAA in FBO can be found in the DHS S&T BAA Portal located at https://baa2.st.dhs.gov. Registration is not required to access the FBO link in the DHS S&T BAA Portal to this BAA; however, registration in the portal is required to upload any submissions responding to any Calls issued against this

BAA.

7. REGISTRATION IN DHS S&T BAA PORTAL (Must be completed prior to uploading any submissions.)

7.1 Access to DHS S&T BAA Portal. The DHS S&T BAA Portal located at https://baa2.st.dhs.gov offers electronic access to BAA Calls, frequently asked questions (FAQs), answers to FAQs, abstracts of previously funded projects, and hyperlinks to other useful information.

7.2 Company/Organization Registration. As stated in paragraph 1.8 above, this announcement does not request any white papers or proposals at this time. Calls requesting white papers or proposals will be accomplished via solicitations posted in FBO. The DHS S&T BAA Portal will not allow submissions (white papers or proposals) in response to Calls issued against this BAA to be uploaded for any entity that has not completed a company/organization registration in the portal.

IMPORTANT: Any entity responding to any Call issued against this BAA must first register your company or organization at https://baa2.st.dhs.gov. For specific information regarding how to register and regarding the submission of documents in the DHS S&T BAA Portal, refer to paragraph 10 below.

8. WHITE PAPER SUBMISSION REQUIREMENTS

8.1 Calls May Request White Papers. Calls issued against this BAA may request the submission of white papers. Submission requirements for white papers, when requested, shall be in accordance with this announcement unless otherwise amended in the individual Call. Offerors should be alert for any amendments to individual Calls that may permit extensions to the submission date identified in the particular Call or modify terms and conditions of a particular Call.

8.2 Submission Dates and Times. Submission dates and times will be identified in each Call.

White papers WILL NOT BE ACCEPTED after the established due date. There will be no exceptions to the time and date on which responses are due, unless determined otherwise by the Government.

8.3 No Classified Documents. No classified white papers will be accepted.

8.4 No Proposal Submission Authorized Without White Paper Submission. If a Call requests a white paper submission, offerors must submit a white paper that can be evaluated in order to be considered for participation in the submission of proposals. Offerors are not eligible to submit a proposal for any white paper rejected as non-compliant. For more information regarding non-compliant white paper submissions, refer to Section 8.8 below.

8.5 Multiple White Papers. Multiple white papers per Call may be submitted. Each submitted white paper must comply with the terms outlined herein.

8.6 White Paper Format. White papers may include narrative, pictures, figures, tables, and charts in a legible size, and must be accompanied by a one-page quad chart. Format details are:

Paper Size: 8.5-by-11-inch paper.

Margins: 1 inch.

Spacing: Single or double-spaced.

Font: Times New Roman, no smaller than 12 point. Text embedded within graphics or tables in the body of the white paper or the quad chart may not be smaller than 10 point.

Number of Pages: Unless otherwise specified in the Call, no more than twelve single-sided pages consisting of the following shall be submitted:

o A one-page cover page (refer to paragraph 8.7 below for details regarding cover page requirements);

o Ten pages of technical content (refer to paragraph 8.7 below for details regarding technical content requirements); and o A one-page quad chart (refer to paragraph 9.6 below for quad chart format).

WHITE PAPERS EXCEEDING THE DESIGNATED PAGE LIMIT WILL BE REJECTED AS

NON-COMPLIANT AND WILL NOT BE EVALUATED. FOR MORE INFORMATION

REGARDING NON-COMPLIANT WHITE PAPER SUBMISSIONS, REFER TO SECTION

8.8 BELOW.

Proprietary Marking. The offeror is required to appropriately mark any proprietary information contained in any white paper to be submitted in response to any Call issued against this BAA.

Export Control Marking. See Section 12.5.

The white paper submission uploaded to the DHS S&T BAA Portal shall consist of ONE electronic file in portable document format (PDF). The quad chart must be submitted in the same file as the white paper. The file size must be no more than 10 megabytes (MB).

8.7 White Paper Content. White papers shall include, at a minimum, the following:

Cover Page. The cover page shall include the following:

o White Paper Registration Number (assigned when the offeror registers the white paper submission in the DHS S&T BAA Portal; therefore, if submitting more than one white paper, registration must be completed for each submission).

o Call number, i.e., “HSHQDC-??-R-B????”, which will identified in each individual solicitation;

o Title of white paper;

o Name of offeror’s organization and offeror’s administrative and technical points of contact, including name, address, telephone and facsimile numbers, and email addresses. If multiple organizations are participating, identify the above information for each organization;

o Identify whether the offeror (and each organization participating) is a US or foreign owned entity;

o Type Classification as described in paragraph 2.2 above (Type I, Type II, or Type III) that aligns with the proposed technology; and o Signature and title of an authorized representative of the entity submitting the white paper. If multiple organizations are participating, one signature from the principal/leading organization is acceptable.

Quad Chart. A quad chart shall be included and shall be in the format identified in paragraph 9.6 below.

Technical Content. The remaining pages of the white paper shall consist of the following information:

o Provide a description of the basic scientific or technical concepts that comprise the proposed solution to the problem described in the Call specific TA.

o Explain what is unique about the proposed solution and what advantages it might afford compared to other approaches that have been taken in this area. Illustrate the particular scientific, technical, or engineering issues that need to be addressed and resolved to demonstrate feasibility.

o Describe the approach and required resources to test and evaluate the proposed technologies with respect to Call specific TA goals.

o In the technical discussion, the offeror should: discuss how the proposed solution will address program requirements; demonstrate your understanding of the problem; clearly identify all risks and associated mitigation approaches; and present a clear plan and schedule to provide a solution to the problem presented by each Topic Area.

o If offerors desire to use proprietary software or technical data or both as the basis of their proposed approach, in whole or in part, the white paper must 1) clearly identify such software/data and its proposed particular use(s); 2) explain how the Government will be able to reach its goals (including transition) within the proprietary model offered; and 3) provide possible nonproprietary alternatives in any area that might present transition difficulties or increased risk or cost to the Government under the proposed proprietary solution.

o Personnel and Performer Qualifications and Experience. Briefly describe the offeror’s qualifications and experience in similar development efforts. Present the qualifications of the principal technical personnel and any key personnel, who, if a resultant award is made, will be subject to any key personnel clauses included in the resultant award. Describe the extent of your team’s past experience in working with or developing the technologies comprising your solution. For submissions that include multiple organizations, all organizations must be identified. Include a description of what role each organization will play in the project. Identify appropriate technical personnel for each organization and each team member’s past experience in technical areas related to the white paper. In teaming situations, the lead/prime organization must remain the same on both the white paper and, if selected, the proposal.

o Costs, Work, and Schedule: Provide a brief summary of the planned work, costs, and schedule required to execute your project, summarized by major task.

Company to Company Agreement with Noblis, Inc (or successor Systems Engineering and Technical Assistance (SETA) contractor). This Agreement shall be included in accordance with paragraph 11.4 and does not count against the white paper page count.

8.8 Non-compliant White Papers. White papers submitted that do not comply with the white paper submission requirements outlined in this BAA as well as any additional submission requirements outlined in the respective Call under which the white paper is being submitted will result in the white paper being determined non-compliant and rejected without evaluation.

Examples of non-compliant white papers include, but are not limited to:

Total contract value proposed in the white paper is greater than the “Type Classification Ceilings” identified in the respective Call;

Total number of pages submitted does not comply with the page count limitations identified in the respective Call; or

Submission requirements are not met, such as the one page limitation for the cover page and the quad chart (as required by 8.7 above) is exceeded, etc., or the Company to Company Agreement with Noblis, Inc. is not submitted.

9. PROPOSAL SUBMISSION REQUIREMENTS

9.1 Submission Requirements. Submission requirements for proposals shall be in accordance with this announcement unless otherwise amended in the individual Call. Offerors should be alert for any amendments to individual Calls that may permit extensions to the submission date identified in the particular Call or modify terms and conditions of a particular Call.

9.2 Submission Dates and Times. Submission dates and times will be identified in each Call.

Proposals WILL NOT BE ACCEPTED after the established due date. There will be no exceptions to the time and date on which responses are due, unless determined otherwise by the Government.

9.3 No Classified Documents. No classified proposals will be accepted.

9.4 Multiple Proposals. If only proposals (no white papers) have been requested by the individual Call, then multiple proposals may be submitted. When white papers are requested by the individual Call, then offerors must submit a white paper in order to be considered for participation in the submission of proposals. Each submitted proposal must comply with the terms outlined herein.

9.5 Proposal Format.

Proposals will consist of two volumes:

o Volume 1 - Technical Proposal o Volume 2 - Cost Proposal

For each volume, the following format shall apply:

o Paper Size – 8.5-by-11-inch paper.

o Margins – 1 inch.

o Spacing – Single- or double-spaced.

o Font – Times New Roman, 12 point. Text embedded within graphics or tables in the body of the proposal or the quad chart should be legible and not smaller than 10 point.

o Number of Pages: Unless otherwise specified in the Call, page limitations for each volume are as follows:

Volume 1, Technical Proposal: 30 single-sided pages (all parts inclusive) Volume 2, Cost Proposal: No page limitation

PROPOSALS EXCEEDING THE DESIGNATED PAGE LIMIT IDENTIFIED IN EACH

CALL WILL BE REJECTED AS NON-COMPLIANT AND WILL NOT BE EVALUATED.

FOR MORE INFORMATION REGARDIG NON-COMPLIANT PROPOSAL SUBMISSIONS,

REFER TO SECTION 9.7 BELOW.

Proprietary Marking. The offeror is required to appropriately mark any proprietary information contained in any proposal to be submitted in response to any Call issued against this BAA.

Export Control Marking. See Section 12.5.

The proposal submission uploaded to the DHS S&T BAA Portal shall consist of one electronic file for the Technical Volume and one electronic file for the Cost Volume.

Electronic files will be in portable document format (PDF). The quad chart must be submitted in the same file as the Technical Volume. The file size must be no more than

10 MB.

9.6 Proposal Content.

Volume 1: Technical Proposal. Volume 1, Technical Proposal, shall be in the form of a technical volume and a cost proposal overview. Page count limitation for technical proposals will be identified in each Call issued under this BAA. Compliance with the order and content listed below as well as any additional submission requirements identified in the respective Call under which the proposal is being submitted is important to assure thorough and fair evaluation of proposals. The submission of other supporting materials with the proposal is strongly discouraged and, if submitted, will not be reviewed. Non-compliant proposals will be rejected without review. The technical proposal shall include the following:

Cover Page. Provide a one-page cover page. Title the cover page “Volume 1 - Technical Proposal” and also ensure the following information is included:

o Proposal Registration Number (assigned when the offeror registers the proposal submission in the DHS S&T BAA Portal; therefore, if submitting more than one white paper, registration must be completed for each submission).

o Call number, i.e., “HSHQDC-??-R-B????”, which will be identified in each individual solicitation;

o Title of proposal;

o Name of offeror’s organization and offeror’s administrative and technical points of contact, including name, address, telephone and facsimile numbers, and email addresses;

o Whether offeror is US or foreign owned entity;

o Identity of prime offeror and complete list of subcontractors or consultants, if applicable, otherwise indicate that there are no subcontractors or consultants;

o Type Classification as described in paragraph 2.2 above (i.e., Type I, Type II, or Type III) o Duration of effort. Separately identify the base effort and any options;

o Identify understanding and compliance with the below paragraph 12.7, Publication of Research Results. If additional internal approvals are required in order to comply with this requirement, then those approvals are to be obtained PRIOR to submission of any proposal.

o In accordance with FAR 4.1201, prospective offerors for contracts and for OTs involving prototypes shall state the certifications in System for Award Management (SAM) database at https://www.sam.gov have been completed and shall provide the certification validity period; and o The signature and title of an authorized representative of the entity submitting the proposal.

Official Transmittal Letter. Provide a one-page official transmittal letter with authorizing official signature. For the electronic submission, the letter can be scanned into the electronic proposal. The letter of transmittal shall include, at a minimum, the following:

o Whether the proposal has been submitted to a Government agency other than DHS and, if so, specify which agency and the date it was submitted.

o The required disclosure regarding organizational conflict of interest identified in paragraph 12.4 below.

o A statement that the offeror’s proposal is available for award for 180 days beyond the date of proposal submission.

Quad Chart. A quad chart shall be included and, including graphics or tables, will not use any font smaller than 10-point and will be organized as shown in the figure below.

Abstract. Provide a one-page synopsis of the entire proposal, including a listing of total anticipated costs. This page should include the proposal title and offeror name, along with a description of the scientific, technical, engineering, and management approach being proposed to address the goals of the respective BAA Call. It also should describe how the approach is unique, and provide a brief summary of the technology’s anticipated performance relative to the respective BAA Call goals. This section shall be separable (i.e., it will begin on a new page and the following section shall begin on a new page). If the proposal is selected for funding, DHS may post the abstract on the EXD webpages in the dhs.gov domain. Therefore, the abstract should not contain any proprietary information.

Performance Goals. Describe the overall methodology and how it will meet the project goals specified in the respective BAA Call.

Detailed Technical Approach.

o Describe the proposed design and technical issues. Identify the critical technical issues in the design and concept. Outline and address technical challenges inherent in the approach and possible solutions for overcoming potential problems. Demonstrate a deep understanding of the technical challenges and present a plan to achieve the respective BAA Call goals. The offeror should include: discussion on how the proposed solution will address program requirements; demonstrate your understanding of the problem; clearly identify all risks and associated mitigation approaches; and presents a clear plan and schedule to provide a solution to the problem presented by each Topic Area. Provide appropriate measurable milestones (quantification is preferable) at intermediate stages of the project to demonstrate progress, and a plan for achieving the milestones.

o If offerors desire to use proprietary software or technical data or both as the basis of their proposed approach, in whole or in part, 1) clearly identify such software/data and its proposed particular use(s); 2) explain how the Government will be able to reach its goals (including transition) within the proprietary model offered; and 3) provide possible nonproprietary alternatives in any area that might present transition difficulties or increased risk or cost to the Government under the proposed proprietary solution.

Statement of Work (SOW), Schedule, and Milestones. Provide the proposed research tasks, showing each task with major milestones. Include a proposed schedule for the effort (estimated dates of tasks, milestones and deliverables). DHS will likely make severable awards. To support severability, each year of the proposal should be separately defined, and tasks identified must correlate to the tasks identified in the cost proposal submission. The SOW must not include proprietary information. For each defined task/subtask, provide:

o A general description of the objective.

o A detailed description of the approach to be taken to accomplish each defined task/subtask.

o Identification of the primary organization responsible for task execution (prime contractor, subcontractor(s), consultant(s), by name).

o A measurable milestone (e.g., a deliverable, demonstration, or other event/activity that marks task completion).

o A definition of all deliverables (e.g., data, reports, designs, architectures, software, and user documentation) to be provided to the Government resulting from the proposed tasks/subtasks.

Testing and Evaluation. Identify the primary test environment to be used to conduct testing and evaluation, and include a description of the test and evaluation methodology appropriate for the proposal.

Deliverables. Provide a detailed list and description of all deliverables identified in the SOW. Include due dates (i.e., calendar days after the effective date of award, or calendar days after the effective date of award of an option). In addition, and again to support severability, there must be a usable/meaningful deliverable(s) at the end of the first period of performance (base period) and a usable/meaningful deliverable(s) at the end of each additional year of performance (option period) so that should the Government be unable to obtain funds for any option period, the Government can clearly show value for the money expended to date. All deliverables identified must be included in the Assertions Table below.

Management Plan. Provide a brief summary of the management plan, including an explicit description of what role each participant or team member will play in the project.

Facilities. List the location(s) where the work will be performed, and the facilities to be used. Describe any specialized or unique facilities which directly affect the effort.

Government-Furnished Resources. Provide a brief summary of required information and data which must be provided by the Government to support the proposed work, if any.

Resumes for Key Personnel. Provide resumes or curriculum vitae (CVs) for each of the key personnel proposed. A minimum of two key personnel must be identified. Key personnel from subcontractors may be included.

Other DHS Support. Provide a list of any current or pending awards or proposals with DHS that pertain to this work, submitted either as a prime contractor, subcontractor/consultant, or teaming partner.

Past Performance. Fully describe similar efforts on the part of the offeror, to include teammates, currently ongoing and completed, related to technologies sought by the BAA Call. Pertinent efforts can be academic, commercial or Government sponsored, but all sponsors should be identified as explicitly as possible.

Assertion of Data Rights.

o The Assertions Table completed in accordance with this section does not count against the page count for Volume 1 - Technical Proposals.

o It is anticipated that the proposed Assertion of Data Rights will be incorporated in the resultant award instrument. To this end, proposals must include a severable Assertion of Data Rights (i.e., it will begin on a new page and the following section shall begin on a new page) without any proprietary restrictions, which can be removed from the proposal and attached to the contract or agreement award.

After proposal submission, any changes to this information requested by an offeror may cause a proposal to be re-evaluated or deemed not selectable at the Government’s discretion. The format for this section is as follows:

Assertions Table

Identify in the table below each deliverable included in the offeror’s proposal. For each deliverable listed in the below table identify any assertion of restriction on the Government’s use, release or disclosure of technical data or computer software.

Deliverable

Technical Data or Computer Software to be Furnished With Restrictions*

Basis for Assertion**

Asserted Rights Category***

Name of Person Asserting

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. For computer software or computer software documentation identify the software or documentation.

**Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain.

The Government's rights in computer software documentation generally may not be restricted.

For computer software, development refers to the software. Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished at private expense, or for computer software documentation, enter the specific basis for asserting restrictions.

***Enter asserted rights category (e.g., government purpose license rights from a prior contract, limited, restricted, or government purpose rights under this or a prior contract, or specially negotiated licenses).

****Corporation, individual, or other person, as appropriate, or enter “none” when all data or software will be submitted without restrictions.

Completed by:

Signature Date Printed Name and Title

Patents. All offerors must include documentation proving ownership or possession of appropriate licensing rights to all patented inventions to be used for the proposed project.

If a patent application has been filed for an invention, but it includes proprietary information and is not publicly available, an offeror must provide documentation that includes: the patent number, inventor name(s), assignee names (if any), filing date, filing date of any related provisional application, and summary of the patent title, with either:

(1) a representation of invention ownership, or (2) proof of possession of appropriate licensing rights in the invention (i.e., an agreement from the owner of the patent granting license to the offeror).

Company to Company Agreement with Noblis, Inc. (or successor SETA contractor). If white papers were not submitted for the Call, this Agreement shall be included in accordance with paragraph 11.4 and does not count against the proposal page count.

Volume 2: Price/Cost Proposal. Volume 2, Price/Cost Proposal, shall consist of a cover page and two parts, Part 1 and Part 2.

Cover Page. The words “Price/Cost Proposal” should appear on the cover page in addition to the following information:

o Respective BAA Call number;

o DHS S&T Portal Assigned Proposal Number o Title of proposal;

o Name of offeror’s organization and offeror’s administrative and technical points of contact, including name, address, telephone and facsimile numbers, and email addresses;

o Whether offeror is US or foreign owned entity;

o Identity of prime offeror and complete list of subcontractors or consultants, if applicable, otherwise indicate that there are no subcontractors or consultants;

o Type Classification as described in paragraph 2.2 above (i.e., Type I, Type II, or

Type III) o Duration of effort. Separately identify the base effort and any options;

o In accordance with FAR 4.1201, prospective offerors for contracts and for OTs involving prototypes shall state the certifications in System for Award Management (SAM) database at https://www.sam.gov have been completed and shall provide the certification validity period; and o The signature and title of an authorized representative of the entity submitting the proposal.

Part 1. As stated above in paragraph 4.5, submissions must propose the first year of performance as a base period with each additional year as a severable option period. In order for a period of performance to be severable, each period of performance must have a usable/meaningful deliverable(s) that should the Government be unable to obtain funds for any option period, the Government can clearly show value for the money expended to date. Therefore, Part 1 shall consist of a detailed breakdown of all costs by cost category identified by year (12 months) of performance in which it is expected the costs to occur (e.g., base year for only one year of performance; base year and one severable option year period for two years of performance; base year and two severable option year periods for three years of performance). Cost categories include, at a minimum, the following:

Direct Labor. Labor hours and unburdened direct labor rates for each person proposed.

Indirect Costs Breakdown. Fringe Benefits, Overhead, General & Administrative (G&A), Cost of Money, etc.; must show amount and rate for each element.

Travel. Number of trips, destinations, durations, etc. (Travel estimate should include costs for attendance/presentation at an annual one-day Explosives Division Review that is held in the Washington metropolitan area.)

Materials. Materials should be specifically itemized with costs or estimated costs. Where possible, indicate basis of estimate, (e.g., recent purchase of same or similar item, vendor quote, catalog price, engineering estimate, market survey, etc.).

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

Subcontract(s). A cost proposal as detailed as the Offeror’s cost proposal will be required to be submitted by the subcontractor. Costs should be clearly marked as “prime” or “subcontractor” costs. If the subcontractor costs cannot be included with the above detailed cost breakdown, then the prime contractor must stipulate on the detailed cost breakdown that the costs presented only represent those from the prime and the subcontractor’s costs are provided separately as an attachment to an e-mail sent to [location to be identified in each individual Call]. The subject line of the email shall say “Separate Subcontractor Cost Submission – [insert the white paper or proposal number assigned from the DHS S&T BAA Portal.” The body of the email shall contain the following:

The prime entity’s name which should be the same entity that is registered in the DHS S&T BAA Portal;

A POC (name and phone number) from the prime entity; and For each subcontractor proposal attached, include:

The name of the subcontractor for the subcontractor proposal attached; and

A POC (name and phone number) from the subcontractor whose proposal is attached.

The separate subcontractor cost proposal must be as detailed as the offeror’s cost proposal and must be received at the location designated in the individual Call no later than the closing date and time specified by the Call. Note that email transmission time may vary depending on the file size of the attachment(s) included in the email. Therefore, ensure there is adequate time for receipt of the email and any accompanying attachments of the subcontractor(s) cost proposal(s) by the required closing date and time. Acceptance of the email submission is dependent upon the actual date and time the e-mail and any accompanying attachment(s) is RECEIVED at the location designated in the Call. NO SEPARATE

SUBCONTRACTOR COST PROPOSALS RECEIVED WILL BE

ACCEPTED IF RECEIVED AFTER THE CLOSING DATE AND

TIME SPECIFIED IN EACH INDIVIDUAL CALL.

Consultant(s). Provide consultant agreement or other document which verifies the proposed loaded daily/hourly rate.

Fee/Profit. Identify amount and percentage of Fee/Profit, if proposed.

Part 2. Part 2 shall consist of the cost breakdown by task/sub-task using the same task numbers in the Statement of Work. In addition, the task/sub-task breakdown must be identified by year of performance in which it is expected the costs/tasks/sub-tasks to occur (e.g., base year for only one year of performance; base year and one severable option year period for two years of performance; base year and two severable option year periods for three years of performance).

9.7 Non-compliant Proposals. Proposals submitted that do not comply with the proposal submission requirements outlined in this BAA and any additional submission requirements outlined in the Call the proposal is responding to will result in the proposal being determined non-compliant and rejected without evaluation. Examples of non-compliant proposals include, but are not limited to:

Total contract value proposed in the proposal is greater than the “Type Classification Ceilings” identified in the respective Call;

Total number of pages submitted does not comply with the page count limitations identified in the respective Call; or

Submission requirements are not met, such as the one page limitation for the cover page, the transmittal letter, or the quad chart is…