DRAFT BAA 25S5000.pdf

<DATE>

IRREGULAR WARFARE TECHNICAL SUPPORT DIRECTORATE (IWTSD)

BROAD AGENCY ANNOUNCEMENT (BAA) 25S5000

Due Date for Receipt of Phase 1 Submissions:

No Later Than <DATE> All submissions are due by 3:00 p.m. U.S. Eastern Time (ET) on the above date

Advanced Analytics (AA)

Advanced Development (AD) Chemical, Biological, Radiological, Nuclear, and Explosives (CBRNE)

Expeditionary Force Protection (EFP) Explosive Ordnance Disposal and Explosive Operations (EOD-EXO)

Human Performance and Training (HPT) Influence and Information Capabilities (I2C) Protection, Survivability, and Recovery (PSR)

Surveillance, Collection, and Operations Support (SCOS) Tactical Offensive Support (TOS)

The Broad Agency Announcement Information Delivery System (BIDS) is the system in which all submissions and communications will flow. Communications outside of BIDS may result in expulsion from the competition.

TABLE OF CONTENTS

1. INTRODUCTION

1.1. APPROACH

1.1.1 Type of Proposals

1.1.2. Cost Type Contracts

1.2. SMALL BUSINESS SET ASIDE

1.3. LIMITATION OF FUNDS

1.4. TECHNICAL EVALUATION SUPPORT

1.5. BAA PACKAGE DOWNLOAD

1.6. BAA CONTRACTUAL AND TECHNICAL QUESTIONS

1.7. BIDS WEBSITE HELP REQUESTS

2. GENERAL INFORMATION

2.1. ELIGIBILITY

2.1.1. Who is eligible?

2.1.2. Federally Funded Research and Development Centers

2.1.3. Research Development and Engineering Centers (RDECs)

2.2. PROCUREMENT INTEGRITY, STANDARDS OF CONDUCT, ETHICAL CONSIDERATIONS

2.3. REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR

EQUIPMENT

2.4. RESTRICTIVE MARKINGS ON PROPOSALS

2.5. SUBMISSION HANDLING/RIGHTS IN TECHNICAL DATA AND COMPUTER SOFTWARE/PATENT RIGHTS

2.5.1. Procurement Integrity

2.5.2. Submission Information and FOIA

2.5.3. Rights in Technical Data and Computer Software

2.5.4. Patents

2.6. PRODUCT AND DELIVERABLE REQUIREMENTS

2.7. DISTRIBUTION/RELEASE LIMITATIONS

2.8. SUBCONTRACTING

2.9. ANIMAL OR HUMAN TESTING COMPLIANCE

2.9.1. Animal Testing

2.9.2. Human Subjects Testing

2.10. SUBMISSION DOCUMENT LANGUAGE

2.11. RISK MANAGEMENT FRAMEWORK

3. PROPOSAL PREPARATION

3.1. BAA INFORMATION DELIVERY SYSTEM (BIDS)

3.1.1. Submitter Registration

3.1.2. User Accounts and Password Resets

3.1.3. Registration and Account Help

3.1.4. Document Identifier

3.1.4.1. Constructing Document Identifiers

3.1.4.2. Creating Vendor Internal Tracking (VIT) Numbers

3.2. BIDS SECURITY AND ACCESS CONTROL

3.3. SUBMISSION CHANGES

3.4. SPECIAL HANDLING PROCEDURES FOR CLASSIFIED INFORMATION

3.5. PHASE 1 SUBMISSIONS

3.5.1. Phase 1 Due Date and Time

3.5.2. Electronic File Format

3.5.3. Quad Chart and Addendum Content

3.5.3.1. Header Information

3.5.3.2. Top Left Quadrant, Graphical Depiction

3.5.3.3. Top Right Quadrant, Operational and Performance Capabilities

3.5.3.4. Bottom Left Quadrant, Technical Approach

3.5.3.5. Bottom Right Quadrant, Cost, and Schedule

3.5.3.6. Addendum

3.5.4. Phase 1 Notification to Offeror

3.5.5. Phase 1 Status and Inquiries

3.6. PHASE 2 WHITE PAPER SUBMISSIONS

3.6.1. Phase 2 Due Date and Time

3.6.2. Electronic File Format

3.6.3. Phase 2 Document Upload

3.6.4. White Paper Content

3.6.4.1. Cover Page

3.6.4.2. Technical Approach

3.6.4.3. Tasks and Deliverables

3.6.4.4. Schedule

3.6.4.5. Cost

3.6.4.6. Intellectual Property, Technical Data, and Software

3.6.4.6.1. Patents and Patent Applications

3.6.4.6.2. Rights in Technical Data and Software

3.6.4.7. Transition from Prototype to Production

3.6.4.8. Organizational Capability Statement

3.6.5. Phase 2 Status and Inquiries

3.6.6. Phase 2 Notifications to Offeror

3.7. PHASE 3 FULL PROPOSAL SUBMISSIONS

3.7.1. Phase 3 Due Date and Time

3.7.2. Electronic File Format

3.7.3. Phase 3 Document Upload

3.7.4. Full Proposal Components

3.7.5. Technical Proposal Content

3.7.5.1. Table of Contents

3.7.5.2. Abstract

3.7.5.3. Executive Summary

3.7.5.4. Technical Approach

3.7.5.5. Project Plan

3.7.5.5.1. Phases

3.7.5.5.2. Tasks Within a Phase

3.7.5.5.3. Products and Deliverables

3.7.5.6. Master Schedule

3.7.5.7. Government Furnished Equipment

3.7.5.8. Project Risks and Mitigation

3.7.5.9. Organizational Capability Statement

3.7.5.10. Organizational Resources

3.7.5.11. Intellectual Property, Technical Data, and Software

3.7.5.11.1. Patents and Patent Applications

3.7.5.11.2. Rights in Technical Data

3.7.5.12. Transition from Prototype to Production

3.7.5.12.1. Transition Strategy

3.7.5.12.2. Transition Approach

3.7.5.12.3. Test and Evaluation

3.7.5.12.4. Operational Support

3.7.5.13. Human Subjects and Animal Testing

3.7.5.14. Environmental Impact

3.7.5.15. Classification and Security

3.7.5.16. Subcontracting Plan

3.7.6. Cost Proposal

3.7.6.1. Cost Narrative

3.7.6.1.1. Table of Contents

3.7.6.1.2. Direct Labor Costs

3.7.6.1.3. Indirect Costs

3.7.6.1.4. Other Direct Costs

3.7.6.1.5. Government Furnished or Contractor Acquired Equipment

3.7.6.1.6. Profit or Fee

3.7.6.1.7. Competitive Methods

3.7.6.1.8. Established Catalog or Market Prices/Prices Set by Law or Regulation

3.7.6.1.9. Royalties

3.7.6.2. Facilities Capital Cost of Money

3.7.6.3. Other Funding Sources

3.7.6.4. Additional Information/Documents

3.7.7. Phase 3 Notifications to Offerors

3.7.8. Phase 3 Protests

3.7.9. Phase 3 Status and Inquiries

3.8. CLARIFICATION REQUESTS

3.9. INSTRUCTIONS FOR OFFEROR “NO-BID” AND SUBMISSION WITHDRAWAL

4. PROPOSAL EVALUATION

4.1. EVALUATION CRITERIA

4.1.1. Basic Requirement

4.1.2. Technical Performance

4.1.3. Cost

4.1.4. Schedule

4.1.5. Contractor Past Performance

5. TECHNOLOGY DEVELOPMENT REQUIREMENTS AND OBJECTIVES

5.1. ADVANCED ANALYTICS (AA)

5.2. ADVANCED DEVELOPMENT (AD)

5.3. CHEMICAL, BIOLOGICAL, RADIOLOGICAL, NUCLEAR, AND EXPLOSIVES (CBRNE)

5.4. EXPEDITIONARY FORCE PROTECTION

5.5. EXPLOSIVE ORDNANCE DISPOSAL AND EXPLOSIVE OPERATIONS (EOD-EXO)

5.6. HUMAN PERFORMANCE AND TRAINING (HPT)

5.7. INFLUENCE AND INFORMATION CAPABILITIES (I2C)

5.8. PROTECTION, SURVIVABILITY, AND RECOVERY (PSR)

5.9. SURVEILLANCE, COLLECTION, AND OPERATIONS SUPPORT (SCOS)

5.10. TACTICAL OFFENSIVE SUPPORT (TOS)

1. INTRODUCTION.

This is an Irregular Warfare Technical Support Directorate (IWTSD) Broad Agency Announcement (BAA) issued under the provisions of paragraph 6.102(d)(2)(i) of the Federal Acquisition Regulation (FAR) to provide for the competitive selection of research proposals.

Contracts based on responses to this BAA are considered to be the result of full and open competition and in full compliance with the provisions of Public Law (PL) 98-369 Section 2701, “The Competition in Contracting Act.” Awards for submissions under this BAA are planned for Fiscal Year (FY) 2026. No contract awards will be made until appropriated funds are available from which payment for contract purposes can be made.

[NOTE: Persons submitting proposals are advised that only the Contracting Officer can obligate the Government to any agreement involving expenditure of Government funds.]

1.1. Approach.

A three-phased proposal selection process will be used for this BAA to minimize cost and effort for prospective offerors:

• Phase 1 will consist of the solicitation, receipt, and evaluation of a one-page Quad Chart and a one-page addendum.

• Phase 2 will consist of the solicitation, receipt, and evaluation of a White Paper and applies to only those submissions that have been accepted in Phase 1.

• Phase 3 will consist of the solicitation, receipt, and evaluation of a Full Proposal and applies to only those submissions that have been accepted in Phase 2. Based on the priority of critical requirements and the availability of funding, Phase 1 submissions can be selected for Phase 3 without a Phase 2 submission.

Clarifications to White Papers and Full Proposals may be requested.

1.1.1 Type of Proposals.

Firm-fixed-price proposals are preferred for all requirements published in this BAA.

1.1.2. Cost Type Contracts.

Offerors interested in cost type contracts (to include Cost Plus Fixed Fee options) must have an accounting system determined adequate by Defense Contract Auditing Agency/ Defense Contract Management Agency (reference FAR 16.301-3(a)(3)). If no determination has been made, please contact BIDSHelp@iwtsd.gov for further guidance.

1.2. Small Business Set Aside.

The Government encourages nonprofit organizations, educational institutions, small businesses, small disadvantaged business (SDB) concerns, Service-Disabled Veteran-Owned Small Businesses (SDVOSBs), Historically Black Colleges and Universities (HBCU), Minority Institutions (MI), women-owned businesses, and Historically Underutilized Business zone enterprises as well as large businesses and Government laboratories to submit research proposals mailto:BIDSHelp@iwtsd.gov for consideration and/or to join others in submitting proposals; however, no portion of the BAA will be set aside for these special entities because of the impracticality of reserving discrete or severable areas of research and development (R&D) in any specific requirement area.

1.3. Limitation of Funds.

The Government intends to incrementally fund Cost Reimbursement contracts awarded from this BAA as provided by FAR 52.232-22, “Limitation of Funds.” Most contracts awarded are anticipated to be 12 to 24 months in duration and at times may include additional 6 to12 month option(s). To facilitate incremental funding, submissions shall include the cost and schedule by a task-phased structure with clear exit criteria and shall be inclusive of all work to complete the effort including any options. It is anticipated that the entire effort will be negotiated with the initial contract award.

[NOTE: Based upon the availability of funding, the Government may have to partially fund Fixed Price contracts in accordance with DFARS 252.232-7007, “Limitation of Government’s Obligation.” In such cases, milestone payments will need to be a part of the full proposal.

Applicability of this issue will be stated in the email asking for a Phase 3 proposal.]

1.4. Technical Evaluation Support.

It is the intent of this office to use contractor support personnel in the review, evaluation, and administration of all submissions for this BAA. All contractor support personnel will have access to proprietary data and shall certify that they: (1) will not disclose any information pertaining to this solicitation including any submissions, the identity of any submitters, or any other information relative to this BAA; and (2) have no financial interest in any submissions evaluated, reviewed, and administered. Submissions and information received in response to this BAA constitutes permission to disclose that proposal data to certified evaluators under these conditions.

1.5. BAA Package Download.

This BAA Package can be downloaded electronically in its entirety from IWTSD BAA Information Delivery System (BIDS), https://bids.iwtsd.gov/, under Resources. Registration is not required to download the BAA package; however, BIDS registration is required to upload a response to the BAA.

1.6. BAA Contractual and Technical Questions.

All contractual and technical questions regarding this BAA, including the published requirements and instructions, must be posted via either the BAA and Requirement Questions features, accessible from the BIDS homepage via Have a Question?, or emailed to BIDSHelp@iwtsd.gov. No other office personnel will acknowledge, forward, or respond to any inquiries received in any manner concerning the BAA. All questions must be received no later than 14 days after the release of the final BAA. Contractual questions and answers will be posted periodically under BAA and Requirement Questions. Offerors are encouraged to periodically review BAA Questions, accessible from the BIDS homepage via Have a Question?.

1.7. BIDS Website Help Requests.

For technical help using BIDS, submit questions to BIDSHelp@iwtsd.gov or by using the button https://bids.iwtsd.gov/ https://bids.iwtsd.gov/ https://bids.iwtsd.gov/Help/DisplayHelpIndex mailto:BIDSHelp@iwtsd.gov https://bids.iwtsd.gov/ https://bids.iwtsd.gov/Help/DisplayHelpIndex located under Have a Question?. Include a valid email address, your BIDS username, and a detailed description of the question or concern in the comments block. To assure adequate time to resolve any technical issues encountered, vendors should register and submit early. Technical issues reported to the Help Desk less than 1 hour before the BAA closing date and time will not be considered for extensions. Vendors may revise a submission up to the BAA's closing date and time. BIDS provides other valuable resources, such as Doing Business with the Government.

Reference documents noted in this BAA, such as the Quad Chart Sample and IWTSD Cost Proposal Template, are available for download under Resources on the homepage menu bar.

A list of BIDS FAQs can be found in the Have a Question? section of BIDS.

2. GENERAL INFORMATION.

This section includes information applicable to all awards under this BAA.

2.1. Eligibility.

To be eligible for contract award, a responsible offeror must meet certain minimum standards pertaining to financial solvency and resources, ability to comply with the performance schedule, prior record of satisfactory performance, integrity, organization, experience, operational controls, technical skills, facilities, and equipment. See FAR 9.104.

• All offerors must be registered in the System for Award Management (SAM) database prior to award at https://sam.gov/.

Other helpful information is provided under Doing Business with the Government on the BIDS homepage.

2.1.1. Who is eligible?

All private companies, educational institutions, non-profit organizations both large and small are able and encouraged to submit to the IWTSD BAA.

2.1.2. Federally Funded Research and Development Centers.

Only DOD-Sponsored Federally Funded Research and Development Centers (FFRDCs) can compete with commercial sector Vendor submissions and will be evaluated using the normal BAA process. For further information, reference DFARS 235.017-1.

2.1.3. Research Development and Engineering Centers (RDECs).

DOD Research Development and Engineering Centers (RDEC)s)/Labs, e.g., Naval Research Lab (NRL) may submit to the IWTSD BAA. Submissions from RDECs/DOD Labs will be evaluated only after all commercial sector vendor and DOD-Sponsored FFRDC submissions have been evaluated and determined that such submissions did not meet the BAA requirement.

IWTSD will inform the RDECs through a BIDS notification at the time of submitter registration that RDEC submissions will be reviewed last in the process, i.e., after all https://bids.iwstd.gov/Help/DisplayHelpIndex https://bids.iwtsd.gov/ https://bids.iwtsd.gov/Help/DisplayHelpIndex https://bids.iwstd.gov/ file://srvr-fs-03/shared/Living%20Documents/2022%20Industry%20Day/Make%20these%20changes%20to%20next%20front%20matter.msg https://sam.gov/ https://bids.iwtsd.gov/ commercial sector vendor and DOD Sponsored FFRDC submissions are reviewed and determined that none meet the BAA requirement. RDECs/DOD Labs will also be informed of this condition during registration in the BIDS system.

If an RDEC's/DOD Lab’s submission meets the BAA requirement and all other commercial sector vendor/DOD-Sponsored FFRDC submissions have been exhausted (i.e., post non-select), correspondence with the RDEC will occur directly (Government to Government) to establish a statement of work, deliverables, and MIPR/Work Order to commence the project.

2.2. Procurement Integrity, Standards of Conduct, Ethical Considerations.

Certain post-employment restrictions on former federal officers and employees exist including special Government employees (Section 207 of Title 18, United States Code (U.S.C.)). If a prospective offeror believes that a conflict of interest exists, the offeror should make this known to the Contracting Officer for resolution before time and effort are expended in preparing a proposal.

2.3. Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment.

FAR provision 52.204-24 applies to all BAA requirements. The full text of FAR provision 52.204-24 is below.

52.204-24 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment (Nov 2021)

The Offeror shall not complete the representation at paragraph (d)(1) of this provision if the Offeror has represented that it "does not provide covered telecommunications equipment or services as a part of its offered products or services to the Government in the performance of any contract, subcontract, or other contractual instrument" in paragraph (c)(1) in the provision at 52.204-26, Covered Telecommunications Equipment or Services— Representation, or in paragraph (v)(2)(i) of the provision at 52.212-3, Offeror Representations and Certifications-Commercial Products or Commercial Services. The Offeror shall not complete the representation in paragraph (d)(2) of this provision if the Offeror has represented that it "does not use covered telecommunications equipment or services, or any equipment, system, or service that uses covered telecommunications equipment or services" in paragraph (c)(2) of the provision at 52.204-26, or in paragraph (v)(2)(ii) of the provision at 52.212-3.

(a) Definitions. As used in this provision—

Backhaul, covered telecommunications equipment or services, critical technology, interconnection arrangements, reasonable inquiry, roaming, and substantial or essential component have the meanings provided in the clause 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment.

(b) Prohibition. (1) Section 889(a)(1)(A) of the John S. McCain National Defense

Authorization Act for Fiscal Year 2019 (Pub. L. 115-232) prohibits the head of an executive agency on or after August 13, 2019, from procuring or obtaining, or extending or renewing a contract to procure or obtain, any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system. Nothing in the prohibition shall be construed to—

(i) Prohibit the head of an executive agency from procuring with an entity to provide a service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or

(ii) Cover telecommunications equipment that cannot route or redirect user data traffic or cannot permit visibility into any user data or packets that such equipment transmits or otherwise handles.

(2) Section 889(a)(1)(B) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232) prohibits the head of an executive agency on or after August 13, 2020, from entering into a contract or extending or renewing a contract with an entity that uses any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system. This prohibition applies to the use of covered telecommunications equipment or services, regardless of whether that use is in performance of work under a Federal contract. Nothing in the prohibition shall be construed to—

(i) Prohibit the head of an executive agency from procuring with an entity to provide a service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or

(ii) Cover telecommunications equipment that cannot route or redirect user data traffic or cannot permit visibility into any user data or packets that such equipment transmits or otherwise handles.

(c) Procedures. The Offeror shall review the list of excluded parties in the System for Award Management (SAM) (https://www.sam.gov) for entities excluded from receiving federal awards for "covered telecommunications equipment or services".

(d) Representation. The Offeror represents that—

(1) It □ will, □ will not provide covered telecommunications equipment or services to the Government in the performance of any contract, subcontract or other contractual instrument resulting from this solicitation. The Offeror shall provide the additional disclosure information required at paragraph (e)(1) of this section if the Offeror responds "will" in paragraph (d)(1) of this section; and

(2) After conducting a reasonable inquiry, for purposes of this representation, the Offeror represents that—

It □ does, □ does not use covered telecommunications equipment or services, or use any equipment, system, or service that uses covered telecommunications equipment or services.

The Offeror shall provide the additional disclosure information required at paragraph (e)(2) of this section if the Offeror responds "does" in paragraph (d)(2) of this section.

(e) Disclosures. (1) Disclosure for the representation in paragraph (d)(1) of this provision. If the Offeror has responded "will" in the representation in paragraph (d)(1) of this provision, the Offeror shall provide the following information as part of the offer:

(i) For covered equipment—

(A) The entity that produced the covered telecommunications equipment (include entity name, unique entity identifier, CAGE code, and whether the entity was the original equipment manufacturer (OEM) or a distributor, if known);

(B) A description of all covered telecommunications equipment offered (include brand;

model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); and

(C) Explanation of the proposed use of covered telecommunications equipment and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(1) of this provision.

(ii) For covered services—

(A) If the service is related to item maintenance: A description of all covered telecommunications services offered (include on the item being maintained: Brand; model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); or

(B) If not associated with maintenance, the Product Service Code (PSC) of the service being provided; and explanation of the proposed use of covered telecommunications services and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(1) of this provision.

(2) Disclosure for the representation in paragraph (d)(2) of this provision. If the Offeror has responded "does" in the representation in paragraph (d)(2) of this provision, the Offeror shall provide the following information as part of the offer:

(i) For covered equipment—

(A) The entity that produced the covered telecommunications equipment (include entity name, unique entity identifier, CAGE code, and whether the entity was the OEM or a distributor, if known);

(B) A description of all covered telecommunications equipment offered (include brand;

model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); and

(C) Explanation of the proposed use of covered telecommunications equipment and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(2) of this provision.

(ii) For covered services—

(A) If the service is related to item maintenance: A description of all covered telecommunications services offered (include on the item being maintained: Brand; model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); or

(B) If not associated with maintenance, the PSC of the service being provided; and explanation of the proposed use of covered telecommunications services and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(2) of this provision.

(End of provision)

2.4. Restrictive Markings on Proposals.

All proposals should clearly indicate content disclosure limitations. Submissions can be marked as “Proprietary” or words to that effect; however, markings such as “Company Confidential” or other phrases that could be confused with national security classifications shall not be used. All paragraphs that contain proprietary information must be clearly marked. The Contracting Officer may challenge proprietary markings if they are not substantiated.

2.5. Submission Handling/Rights in Technical Data and Computer Software/Patent Rights.

2.5.1. Procurement Integrity.

The Government shall comply with FAR 3.104 in its treatment of information submitted in response to this BAA solicitation and marked with the individual’s or company’s legend.

2.5.2. Submission Information and FOIA.

Records or data bearing a restrictive legend can be included in the proposal. However, the offeror is cautioned that portions of the proposal are subject to release under the terms of the Freedom of Information Act (FOIA), 5 U.S.C. § 552, as amended. In accordance with FOIA regulations, the offeror will be afforded the opportunity to comment on, or object to, the release of proposal information.

2.5.3. Rights in Technical Data and Computer Software.

Rights in technical data and computer software and software documentation provided in the proposal are treated in accordance with the Department of Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7016, “Rights in Bid and

Proposal Information.” Rights in technical data, and computer software and computer software documentation in the resultant contract shall be in accordance with DFARS 252.227-7013 (regarding technical data) and DFARS Section 252.227-7014 (regarding computer software and software documentation). Both clauses (DFARS sections 252.227-7013 and 252.227-7014) will be included in any non-commercial contract exceeding the simplified acquisition threshold. Table 1 contains these and related clauses that may be included in the contract.

Table 1. Contract Clauses DFARS Title

252.227-7013 Rights in Technical Data – Noncommercial Items 252.227-7014 Rights in Noncommercial Computer Software and

Noncommercial Computer Software Documentation 252.227-7016 Rights in Bid and Proposal Information 252.227-7017 Identification and Assertion of Use, Release, or Disclosure

Restrictions 252.227-7019 Validation of Asserted Restrictions - Computer Software 252.227-7025 Limitations on the Use or Disclosure of Government-

Furnished Information Marked with Restrictive 252.227-7027 Deferred Ordering of Technical Data or Computer

252.227-7028 Technical Data or Computer Software Previously Delivered to the Government

252.227-7030 Technical Data - Withholding of Payment 252.227-7037 Validation of Restrictive Markings on Technical Data

2.5.4. Patents.

Patents in existence and patent applications pending at the time of the proposal, which relate to the proposed effort, shall be identified in the White Paper and Full Proposal in accordance with the clauses above.

2.6. Product and Deliverable Requirements.

All proposal phases shall include the costs for products and data deliverable requirements.

Minimum data (report) requirements include Monthly Status Reports (MSRs), meeting minutes and a Final Technical Report even if the research is to be continued under a follow-on contract or contract option. MSRs document program, technical, and financial status. The Final Technical Report summarizes the project and associated tasks at the conclusion of each contract. Include MSRs, the Final Technical Report, and any products and deliverables specific to the performance of the proposed effort (e.g., system specification). The Government will provide the offeror with a full listing of data deliverables (i.e., Contract Data Requirements List) in the request for Phase 3 Full Proposal. Additional products and deliverables could include prototype hardware, software, or systems; test plans; test and technical reports; technical data; specifications;

requirements documents; computer programs or software; user manuals; drawings; or other products and data. The number, types, and preparation instructions for products and deliverables will be specified in the contract.

2.7. Distribution/Release Limitations.

The offeror should be aware that all resulting contracts or other awards will contain release limitations for all data resulting from the effort in accordance with DFARS 252.204-7000. This includes products, data, information, and services to be performed. The contractor shall protect all data and information from disclosure, and shall not release any data or information by any method of dissemination without prior Government approval.

2.8. Subcontracting.

Pursuant to Section 8(d) of the Small Business Act (15 U.S.C. § 637(d)), it is the policy of the Government to enable small business and small disadvantaged business concerns to be considered fairly as subcontractors to contractors performing work or rendering services as prime contractors or subcontractors under Government contracts, and to assure that prime contractors and subcontractors carry out this policy.

2.9. Animal or Human Testing Compliance.

The contractor shall comply with all laws and regulations governing the use of animals or human subjects in research projects. Information regarding compliance requirements for using humans and animals in testing is also available on BIDS under Resources.

2.9.1. Animal Testing.

Any contract resulting from this BAA that potentially involves the testing of animals shall include the following language:

Any contractor performing research on warm blooded vertebrate animals shall comply with the Laboratory Animal Welfare Act of 1966, as amended, 7 U.S.C. §§ 2131 - 2159, and the regulations promulgated thereunder by the Secretary of Agriculture in 9 C.F.R. Parts 1 through 4, pertaining to the care, handling, and treatment of vertebrate animals held or used for research, teaching, or other activities supported by Federal contract awards. In addition, the contractor shall comply with the provisions of Department of Defense Instruction (DODI) 3216.01, as implemented by SECNAVINST 3900.38C, and DFARS 252.235-7002, “Animal Welfare,” which is incorporated into this contract.

2.9.2. Human Subjects Testing.

Any contract resulting from this BAA that potentially involves the use of human subjects in the research or study shall include the following language:

The contractor shall comply with all regulations promulgated by the Office of the Secretary of Defense in 32 C.F.R. Part 219, pertaining to the protection of human subjects. In addition, the contractor shall comply with the provisions of DODI 3216.02 and DFARS clause 252.235-7004. If human subjects are to be used at any time during the project, the contractor shall have a Federal assurance that is acceptable to IWTSD before involving human subjects. Additionally, the protocol shall be approved by a Federally-assured Institutional Review Board (IRB) office named in the institution’s assurance. The contractor shall prepare these documents and shall ensure that they are on file with IWTSD prior to the start of research involving human subjects. Collaborators with the contractor, to include IRBs, shall also comply with regulations to protect human subjects for both classified and unclassified research. The contractor shall report all changes in the protocol or consent form to the IWTSD Contracting Officer’s Representative as they occur. Release of initial and follow-up funding will be contingent upon initial and continuing reviews, and to other IRB and component requirements.

2.10. Submission Document Language.

All submission documents must be in English.

2.11. Risk Management Framework.

The DOD requires all solutions that use information technology to follow current best practices for maintaining cybersecurity. Standards and compliance apply even if the solution is a component of a larger system. Information technology systems must be compliant with the DOD Risk Management Framework as described in DOD Instruction 8500.01. Compliance with this instruction ensures all projects account for information security from requirements gathering to implementation, maintenance and continuous monitoring.

3. PROPOSAL PREPARATION.

This section provides information and instructions for the preparation and submission of all phases under this BAA. All submissions must meet these requirements including format, content, and structure, and must include all specified information to avoid disqualification, submission rejection, or delays in evaluation.

3.1. BAA Information Delivery System (BIDS).

BIDS at https://bids.iwtsd.gov/ is used: (1) to provide public access to the BAA package; (2) to collect all unclassified submissions; and (3) to collect placeholder records for all classified submissions. BIDS also provides submission progress tracking, evaluation comment collection, and results notification back to the submitter.

3.1.1. Submitter Registration.

A BIDS submitter registration is required to respond to this BAA. Registrations should reflect the offeror’s contracting or business authority. The username, created by the offeror, must be unique and is used for BIDS log in and submission tracking. Registration acceptance for submitters is automatic, but takes several seconds to be recognized by BIDS. A success email will be sent to indicate that the username and account are accepted.

BIDS now requires the use of Multifactor Authentication (MFA). All accounts require the download and configuration of the Okta Verify application on the cell phone they wish to associate with a given account. Potential submitters are advised to complete this step as soon as possible as Registrations not completed at least 1 hour before the BAA's closing date and time will not be considered for extensions. Directions explaining how to do this are available on the Vendor QuickCard and on the BIDS Resources page. BIDS is email dependent and uses the registration email as the single point of contact (POC) for all notifications associated with the BAA. This email address should be monitored frequently during the BAA process for the notices. Submitters should periodically check status in their account, not receiving a notification email does not constitute grounds to appeal an evaluation decision. Spam blockers and other email security software may cause a notification email to be rejected; check your account. Email addresses included in the submissions or any other data field in BIDS will not be used for contact and notification purposes.

3.1.2. User Accounts and Password Resets.

Registration account information such as the POC, email, and password can be updated after log in. The “Forgot your password?” link on the BIDS login page allows registered users with a valid username to automatically reset a password. The system will verify the account username and email and then send a new password to that email.

3.1.3. Registration and Account Help.

BIDS help requests can be emailed to BIDS administrators at BIDSHelp@iwtsd.gov or submitted via the button located on the Have a Question? page.

3.1.4. Document Identifier.

The offeror shall include the document identifier in the header of each submission.

Document identifiers must match the BIDS submission record and should be constructed before upload to BIDS.

3.1.4.1. Constructing Document Identifiers.

Document identifiers, auto-generated in part by BIDS, are based on Subgroup, the requirement number, the username, and a Vendor Internal Tracking (VIT) number. The underlined portion of the sample shown in Table 2 depicts the segment automatically formed by BIDS.

Table 2. Sample Document Identifier and Components Definition

CBRNE-1112-ABCCORP-10703JT-QC

From Sample Document Identifier Component CBRNE subgroup designation - from BAA 1112 requirement number - from BAA ABCCORP username - from BIDS registration

10703JT-QC

VIT number - any alphanumeric combination (with no special characters or spaces) created by the submitter for (submitter) tracking purposes along with the document type suffix

3.1.4.2. Creating Vendor Internal Tracking (VIT) Numbers.

VIT numbers are unique identifiers created by submitters and entered in the submission record during the upload process. VIT numbers can be any alphanumeric combination (no special characters or spaces) chosen by the submitter plus a suffix indicating the document type. BIDS enforces unique VIT numbers and will not allow the submission record to be saved if the VIT number has already been used. Table 3 provides sample VIT numbering formats for each https://bids.iwtsd.gov/Help/DisplayHelpIndex document type.

Table 3. Sample VIT Numbers for an Accepted Submission Document Type Auto-generated by BIDS VIT# Quad Chart +1-page addendum

CBRNE-1112-ABCORP 10703JT-QC

White Paper CBRNE-1112-ABCORP 10703JT-WP Full Proposal CBRNE-1112-ABCORP 10703JT-FP

Offerors uploading more than one submission to the same requirement shall create unique identifiers by adding a numbered sequence to the document type suffix. Table 4 offers sample VIT number formats for multiple submissions to the same requirement.

Table 4. Sample VIT Numbers for Multiple Submissions to the Same Requirement Submission # Auto-generated by

BIDS

VIT# Sample 1 VIT#

Sample 2* Submission 1 CBRNE-1112-

10703JT-QC1 QC1

Submission 2 CBRNE-1112-

10703JT-QC2 QC2

Submission 3 CBRNE-1112-

10703JT-QC3 QC3

* NOTE: If the submitter does not require an internal tracking number, use the document type designation.

3.2. BIDS Security and Access Control.

All data uploaded to BIDS is secure from public view and download. All submissions will be considered proprietary/source selection sensitive and protected accordingly. The documents can only be reviewed by the registrant and authorized Government and contractor representatives with no conflict of interest.

3.3. Submission Changes.

Changes to uploaded submissions are permitted up to the closing date and time. If a modification is required, update the original file in the source application and save. Convert to an acceptable format (detailed below) if applicable. In BIDS, open the submission record under Previously Uploaded Proposals. Only submissions with the Update Proposal status can be modified.

Changes can be made after clicking on the submission link. Click on the trash icon to delete the old file. Use Choose File to select the revised document. Click Save Proposal to save the changes. Documents cannot be edited online through the BIDS interface. File names must contain no spaces or special characters. Ensure the file size does not exceed the prescribed limits.

To completely remove a submission from consideration, select Delete Proposal. Changes after the submission due date and time are not permitted.

3.4. Special Handling Procedures for Classified Information.

If a submission contains classified information, the offeror must first create a placeholder record in BIDS with an unclassified cover page attachment. Identify in the placeholder document that the submission cannot be uploaded due to classification and include the method of delivery

(hand-carried, secure mail, etc.) as well as the tracking number, if applicable. The BIDS Document Identifier must be clearly identified on the mailed document(s). Classified responses (up to SECRET) must be appropriately and clearly marked (including all paragraphs and pages containing the subject data), packaged, and shipped in accordance with classified material handling procedures and security regulations pertaining to the level of classification for that document. To obtain mailing instructions for classified submissions, email:

BIDSHelp@iwtsd.gov.

Classified submissions must be received by the applicable due date and time. Classification in no way eliminates the offeror’s requirement to comply with all BAA instructions.

3.5. Phase 1 Submissions.

Offerors shall prepare and upload a one-page Quad Chart and a one-page addendum in response to Phase 1 of this BAA. All pages shall be 8 ½ by 11 inches. Use Times New Roman font size 10 point or greater. Single spacing is preferred for the addendum. If more than two pages (i.e., the Quad Chart plus the addendum) are submitted, only the first two pages will be evaluated. Phase 1 submissions do not require a cover page.

3.5.1. Phase 1 Due Date and Time.

All unclassified Quad Charts must be received electronically through BIDS no later than 1500 (3:00 p.m.) U.S. Eastern Time on the date specified on the cover of this document.

Likewise, classified submissions must be received by the same due date and time.

Offerors must create a placeholder record in BIDS with an unclassified cover page attachment. Refer to section 3.4 of this BAA for instructions on classified submissions.

BIDS does not allow proposals to be uploaded or placeholders for classified submissions to be created after the closing date and time. Any proposal, regardless of classification, submitted by any other means, or that is late, will not be considered by the Government.

Avoid the last minute rush; submit early.

3.5.2. Electronic File Format.

The Quad Chart and addendum shall be submitted in a single file. This file must be in Portable Document Format (.pdf). Adobe Acrobat and MS Word can generate such files. The document must be print-capable, without a password, and no larger than 1024 KB. File names cannot contain spaces or special characters. Apple users must ensure the entire file name and path are free of spaces and special characters.

Submissions that cannot be opened, viewed, or printed will not be considered.

[NOTE: ZIP files and other application formats, such as Microsoft Office (.docx or .pptx) are NOT acceptable.]

3.5.3. Quad Chart and Addendum Content.

A Quad Chart conveys the essence of the proposed solution for a single requirement.

When preparing a submission, the offeror shall ensure that the specific criteria of the requirement are addressed, the solution is clear, and can be accomplished with the proposed technology, cost, and schedule. The Quad Chart includes a document header and four quadrants. The Quad Chart format and sample are provided on BIDS under

Resources.

3.5.3.1. Header Information.

Header information shall include the BAA number, the Document Identifier, and the Proposal Title. The date and company name should be included along with the appropriate document markings.

3.5.3.2. Top Left Quadrant, Graphical Depiction.

The top left quadrant is a graphical depiction, photograph, or artist’s concept of the proposed solution or prototype. Include labels or brief descriptive text as needed for clarification. Ideally, this will convey the prototype concept, use, capability, and any relevant size or weight relationships based on the published requirement.

3.5.3.3. Top Right Quadrant, Operational and Performance Capabilities.

The top right quadrant contains the operational and performance capabilities summary. Describe any basic, new, or enhanced capabilities the system will provide to meet the published requirement. In bullet form, list key aspects of performance, capability, operational use, relevant software or hardware specifications, and planned interface and/or compatibility.

3.5.3.4. Bottom Left Quadrant, Technical Approach.

The bottom left quadrant contains the proposed technical approach. Specifically, describe the technology involved, how it will be used to solve the problem, actions done to date, and any related ongoing efforts. Briefly describe the tasks to be performed for each phase. A bulleted list is acceptable.

3.5.3.5. Bottom Right Quadrant, Cost, and Schedule.

The bottom right quadrant contains the Rough Order of Magnitude (ROM) and Schedule, Products and Deliverables, and Corporate Contact Information.

Vendors shall also note the type of contract proposed (e.g., FFP, CPFF, etc.).

ROM and Schedule shall be proposed by phase and include the cost, period of performance (POP), and exit criteria for each phase. A total cost and POP that combines all phases, all applicable data requirements and minimum data report requirements (e.g., MSR, meeting minutes, Final Technical Report, etc.) shall also be included. Products and Deliverables shall include, by phase, a list of all prototype hardware and software along with the required data as described in “Product and Deliverable Requirements” in section 2.6. of this document.

Corporate contact information shall include the submitter’s company name, POC, phone number, and email address. Include any significant teaming partner (contact information) relevant to the evaluation.

[NOTE: The contact information in the BIDS registration is used for all notices and contact purposes.]

3.5.3.6. Addendum

The offeror shall use the addendum to describe the technical solution in greater detail.

3.5.4. Phase 1 Notification to Offeror.

The Government will notify the offeror when a submission has been accepted or rejected.

Notification of acceptance with a request to submit the next phase document will be emailed to the offeror’s contracting authority as entered in the BIDS registration and will indicate the next submission type, clarification requests, and due date and time. Likewise, rejection notifications will be emailed to the address provided in the BIDS registration.

Debriefings for Phase 1 submissions will not be conducted due to the nature of BAAs.

In general, submissions are not considered for further review when they do not meet the basic requirement, are too costly, or do not fit the mission. All Phase 1 submissions are evaluated in accordance with Section 4, Proposal Evaluation, of this BAA.

3.5.5. Phase 1 Status and Inquiries.

Phase 1 is complete when all submissions have been accepted or rejected in accordance with this BAA. Inquiries outside of the BIDS system (e.g., phone, email, etc.) concerning the status of Phase 1 submissions will not be accepted. After BIDS log on, submitters are able to check the status of their submission(s) under Previously Uploaded Proposals.

3.6. Phase 2 White Paper Submissions.

Offerors shall prepare and upload a White Paper with no more than twelve (12) pages plus a cover page in response to Phase 2 of this BAA. The cover page template is provided at the BIDS website under Resources. The cover page is excluded from the White Paper page count. All submission pages shall be 8 ½ by 11 inches, double-spaced with Times New Roman font no smaller than 10 point; all margins shall be one inch. Each page of the submission shall contain the document identifier in the document header. If the White Paper contains more than 12 pages including tables, charts, and figures, only the first 12 pages will be evaluated.

3.6.1. Phase 2 Due Date and Time.

All unclassified White Papers must be received electronically through BIDS no later than the due date and time specified in the Phase 1 Quad Chart acceptance email. Likewise, classified submissions must be received by the same due date and time; offerors must create a placeholder record in BIDS with an unclassified cover page attachment. Refer to section 3.4 of this BAA for instructions on classified submissions. BIDS does not allow proposals to be uploaded or placeholders for classified submissions to be created after the due date and time. Any proposal, regardless of classification, submitted by any other means, or that is late, will not be considered by the Government.

3.6.2. Electronic File Format.

The White Paper shall be submitted in a single file. This file must be in Portable Document Format (.pdf). Adobe Acrobat and MS Word can generate such files. The document must be print-capable, without password, and no larger than 2048 KB. File names cannot contain spaces or special characters. Apple users must ensure the entire file name and path are free of spaces and special characters. Submissions that cannot be opened, viewed, or printed will not be considered.

[NOTE: ZIP files and other application formats, such as Microsoft Office (.docx or .pptx) are NOT acceptable.]

3.6.3. Phase 2 Document Upload.

To upload a next phase document, use the link back to BIDS provided in the acceptance email, or log in to BIDS and navigate to Requested Proposals to open the accepted record. Review the checklist then click Create Proposal and follow the instructions.

3.6.4. White Paper Content.

White Papers shall provide a description of the technical approach, the specific tasks and deliverables by phase, schedule and cost estimate by phase, intellectual property and government rights, transition planning for production, and a capability statement. The offeror shall incorporate all clarification data requests from the acceptance email into the submission. Indicate clarification entries by footnote and reference the requested item(s) in the footer area. The following White Paper sections and details are required.

3.6.4.1. Cover Page.

A cover page template is provided BIDS under Resources. The cover page includes necessary contractual information including the offeror’s contracting POC (name, telephone number, email address, facsimile number, mailing address) and business information such as your Unique Entity ID issued by the sam.gov website. Include the proposed contract type, total cost, and the duration of all phases/tasks. The cover page is excluded from the page count.

3.6.4.2. Technical Approach.

Describe the proposed solution relative to the requirement. Focus content on operational capabilities required to address the problem, the underlying theory that supports the operational capability, and suggested concept of operations.

Identify end users that could be interested in the proposed solution and describe how the solution will be a benefit. Include drawings, diagrams, charts, and tables needed to explain the effort. Describe if, and where, the proposed technology/solution has been, or is being used. Identify sponsoring agency and funding resources; or if none, so state.

3.6.4.3. Tasks and Deliverables.

Identify the proposed tasks by phase in the order of occurrence. A phase must have clear exit criteria to serve as a “go” or “no-go” decision point to proceed to the next phase. Identify work that will be performed by other organizations or agencies. Identify anticipated technical risks along with planned mitigation efforts.