CWMD-BOTAA_CWMD BOTAA-24-01.docx

ARMY CONTRACTING COMMAND

ABERDEEN PROVING GROUND

EDGEWOOD CONTRACTING DIVISION

BROAD OTHER TRANSACTION AUTHORITY ANNOUNCEMENT (BOTAA) SUPPORTING OTHER TRANSACTION AUTHORITY AGREEMENTS FOR PROTOTYPE DEVELOPMENT EFFORTS FOR THE JOINT PROGRAM EXECUTIVE OFFICE FOR CHEMICAL BIOLOGICAL RADIOLOGICAL AND NUCLEAR DEFENSE (JPEO-CBRND) –

COMBATING WEAPONS OF MASS DESTRUCTION (CWMD)

CWMD BOTAA-24-01

W911SR-24-R-CWMD

Table of Contents

1. INTRODUCTION:

The Joint Program Executive Office for Chemical, Biological, Radiological, and Nuclear Defense (JPEO-CBRND), a component of the U.S. Department of Defense’s Chemical and Biological Defense Program, protects the entire Joint Force– Army, Navy, Air Force, Marines, Coast Guard, and First Responders– through the advanced development of CBRN defense capabilities.

JPEO-CBRND is organized into four Joint Project Management Offices (JPMO) and two Joint Project Lead Offices (JPLO), each responsible for specific commodity areas as described further in Section IV below, and the JPEO-CBRND website at https://www.jpeocbrnd.osd.mil/. Three JPMs and one JPL provide oversight for the portfolios covered under this BOTAA: JPM CBRN Protection, JPM CBRN Sensors, JPM CBRN Special Operations Forces, and JPL CBRN Integration.

Under the authority of 10 USC 4022, JPEO-CBRND seeks to award funding through Other Transaction Authority agreements (OTAs or Agreements) for prototype and follow-on production projects within JPEO-CBRND Areas of Interest, identified in Section IV.B. JPEO-CBRND is interested in efforts directed toward the development of enabling technologies that speed up the advanced development process.

Proposals are sought from all eligible sources as specified herein, including educational institutions, nonprofit organizations, and private industry. This Announcement provides general information, proposal preparation instructions, evaluation and selection criteria, and award administration information.

BOTAA Award Process Overview:

· Offerors may submit preproposals against any area of interest listed in Section IV. (Note: Guidelines for the requirements of a preproposal are listed in Section III B 1.)

· Preproposals are reviewed by the requiring office of the Government.

· If there is interest, the Government may reply with a Request for Full Proposal (RFFP) within 60-90 days. (Note: The Guidelines for all required information needed for a full proposal is explained in Section III B 2.)

· The offeror will prepare and submit the full proposal in accordance with the RFFP, generally set at 30 days for submission.

· Once received, the Government will evaluate the proposal.

· Discussions among the parties, whether verbally or in writing, may occur as appropriate.

· Subject to approvals and successful discussions, the Government may send an agreement to the offeror.

· Additional discussions may occur as necessary.

· Awards, if any, will be made after evaluation and selection of a successful proposal. (Note: Awards are dependent upon the availability of funds.)

The Government may issue separate Requests for Project Proposals (RPPs) under this BOTAA for additional areas of interest or specific prototype needs. Unless otherwise stated in a particular RPP, responses to RPPs issued under this BOTAA will follow the same process described above for review and selection.

Detailed instructions on submitting responses to this BOTAA or RPPs issued under this BOTAA can be found in Part III Section B of this document.

1.

DEFINITIONS

ACCEPTABLE ACCOUNTING SYSTEMS REQUIREMENTS: Whenever an OT is awarded as an expenditure (cost) type agreement the accounting system must be capable of identifying direct costs to the agreements and equitably allocating indirect costs. The OT should typically utilize the company’s existing accounting system and include cost principles and / or Cost Accounting Standards (CAS) only when a business unit is performing other work subject to these requirements. See 48 CFR 9903.201-1(b) for exemptions.

AGENCY: Agency means any of the military departments or defense agencies with authority to award OTAs for prototype projects.

AGREEMENTS OFFICER: An Agreements Officer has authority to enter into, administer, or terminate OTs for prototype projects and make related determinations and findings.

DEVELOPMENT: The systematic use of scientific and technical knowledge in the design, development, testing, or evaluation of potential new products, processes, or services to meet specific performance requirements or objectives. It includes the functions of design engineering, prototyping, and engineering testing. Advanced development consists of activities that plan, produce and deliver information outputs (documents, data, and records) from discovery through prototype delivery. The general phases of the lifecycle are Research, Material Solution Analysis, Technology Maturation & Risk Reduction, Engineering & Manufacturing Development, Production and Deployment.

ENABLING TECHNOLOGIES: Technologies that are not countermeasure products or systems themselves but facilitate or accelerate the development of countermeasure products or systems. Examples of enabling technologies include combinatorial chemistry, visualization technologies, chemical and biological sensing technologies, robotics technologies, permeable and non-permeable materials technologies, decontamination technologies, and other product development tools.

IMPROVED LOGISTICS TRACKING: Technologies which facilitate tracking and monitoring individual product items throughout shipping, storage, delivery to, and use by the end user (factory to foxhole). Examples include technologies which facilitate or simplify supply chain management and/or shelf life extension, such as Item Unique Identification (IUID), and Radio-Frequency Identification (RFID).

NON-TRADITIONAL DEFENSE CONTRACTOR: In accordance with 10 USC 2302(9) this is an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense for the procurement or transaction, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section.

OTHER TRANSACTIONS FOR PROTOTYPES: The Department has authority Title 10 USC 4022 to award “other transactions” (OTs) in certain circumstances for prototype projects that are directly relevant to enhancing the mission effectiveness of military personnel and the supporting platforms, systems, components, or materials proposed to be acquired or developed by the Department of Defense, or to improvement of platforms, systems, components, or materials in use by the Armed Forces. Agreements issued under this authority are acquisition instruments that generally are not required to comply with the Federal Acquisition Regulation (FAR), its supplements, or laws limited in their applicability to procurement contracts.

PROTOTYPE PROJECTS: A prototype project can generally be described as a preliminary pilot, test, evaluation, demonstration, or agile development activity used to evaluate the technical or manufacturing feasibility or military utility of a particular technology, process, concept, end item, effect, or other discrete feature. Prototype projects may include systems, subsystems, components, materials, methodology, technology, or processes. By way of illustration, a prototype project may involve: a proof of concept; a pilot; a novel application of commercial technologies for defense purposes; a creation, design, development, demonstration of technical or operational utility; or combinations of the foregoing, related to a prototype. The quantity should generally be limited to that needed to prove technical or manufacturing feasibility or evaluate military utility.

III. OTHER TRANSACTIONS FOR PROTOTYPES:

A. GENERAL INFORMATION

The award of Prototype OTAs shall be for the development of prototypes in accordance with 10 USC 4022 for prototype projects that are directly relevant to enhancing the mission effectiveness of military personnel and the supporting platforms, systems, components, or materials proposed to be acquired or developed by the Department of Defense, or to improvement of platforms, systems, components, or materials in use by the Armed Forces.

The resultant award of any OTA using the procedures of this BOTAA are NOT made or issued under the provisions of the Competition in Contracting Act of 1984 (P.L. 98-369), FAR Part 6 or any other FAR based regulation. However, the information provided in this BOTAA is intended to ensure competitive procedures are used to the maximum extent practicable when entering into agreements to carry out these prototype projects.

Only a warranted Agreements Officer may obligate the U.S. Government to the expenditure of funds for awards under this Announcement. The Government shall not be liable to pay for any work unless authorized in writing by a warranted Agreements Officer.

The U.S. Government does not fund preparation of proposals or support work efforts or tasks that are inferred from discussions with technical project officers. The Offeror will not be reimbursed for any costs incurred prior to the effective date of the project agreement.

There are certain post-employment restrictions on former Federal officers and employees as defined in 18 USC 207. If an offeror believes a post-employment restriction or conflict of interest exists, notification should be sent to the Agreements Officer prior to initiating efforts on a full proposal.

The U.S. Government may engage advisory and assistance services from contractors (“Support Contractors”) in the review of pre-proposals and proposals. All Support Contractors have executed Non-Disclosure Agreements with their employer per the terms of their contracts with the Government, protecting confidential or sensitive information, intellectual property, third party information, and company inventions. In addition, the receiving agency requires persons receiving any pre-proposal or proposal information to certify non-disclosure and personal financial interest prior to viewing any government or third-party information. Offerors submitting proprietary information in their pre-proposals and proposals may seek to further protect their information from unauthorized use or disclosure by executing a non-disclosure agreement with the Support Contractor company for as long as it remains proprietary and refrain from using the information for any purpose other than that for which it was furnished. Prior to submitting pre-proposals, Offerors may contact the Agreements Officer for information about Support Contractors that may be involved in the pre-proposal evaluation process and to facilitate execution of any additional agreement. Offerors must provide any such additional agreements to the Agreements Officer. JPEO-CBRND obtains written agreements from all evaluators that information in the pre-proposal or proposal will only be used for evaluation purposes and will not be further disclosed. Proposals for funded projects will be subject to public release under the Freedom of Information Act (FOIA) to the extent that they are incorporated into an award document; proposals that are not selected for funding will not be subject to public release.

The FOIA (5 USC 552) provides a statutory basis for public access to official U.S. Government records. “Records” are defined to include documentation received by the U.S. Government in connection with the transaction of public business. Certain types of information submitted to the Government in a process having the potential for award of an OT are exempt from disclosure requirements of 5 USC 552 (the Freedom of Information Act-FOIA) for a period of five (5) years from the date the Government receives the information. The types of information listed above may continue to be exempted, in whole or in part, from disclosure after the expiration of the five (5) year period if it falls within an exemption to the FOIA such as trade secrets and commercial or financial information obtained from a person and privileged or confidential. Offerors should mark business plans and technical information that are to be protected for five years from FOIA disclosure with a legend identifying the documents as being submitted on a confidential basis.

The Government is prohibited from soliciting and awarding actions to contractors that have engaged or are suspected to have engaged in criminal, fraudulent, or seriously improper conduct.

Prospective contractors shall complete electronic annual representations and certifications at www.SAM.gov. By submission of an offer, the Offeror acknowledges the requirement that prospective awardees MUST be registered in the System for Award Management (SAM) database prior to submitting an invoice and through final payment of any OTA or Agreement resulting from this BOTAA. Offerors that are not registered should consider applying for registration prior to submission of their preproposal. To remain registered in the SAM database after the initial registration, the Offeror is required to review and update on an annual basis from the date of initial registration (or subsequent updates) its information in the SAM database to ensure it is current, accurate, and complete.

To facilitate communication on both technical and administrative matters relating to this Announcement, a single email address may be used for all communication with the JPEO-CBRND. Please send all technical and administrative questions and inquiries to usarmy.apg.acc.mbx.jpeo-cbrnd-botaa@army.mil.

B. SUBMISSION PROCEDURES:

The announcement of the current interests will be posted on the Contract Opportunities section of the SAM website (https://sam.gov). No Classified Information is to appear in any of the proposal types discussed herein.

Generally, this announcement is continuously open. Preliminary proposals (preproposals) may be submitted and will be evaluated for the general requirements of this BOTAA at any time throughout the year. RPPs in regard to specific areas of interest of types of prototypes may be issued with a specific cut-off date for response.

The availability of funds may limit the ability of the U.S. Government to make awards in specific areas, nevertheless preproposals are sought under this BOTAA for the Areas of Interest referenced above. See Section IV of this announcement for details.

This BOTAA is considered a competitive process. Preproposals will be submitted as detailed below. Those preproposals that are deemed to have merit may be invited to submit a full proposal. The Government will evaluate the proposals against the criteria in this announcement. The Government may engage in discussions to include during the development of the full proposal. Preproposals shall be evaluated for merit based on: (i) technical feasibility based proposed plans, methods, techniques, and procedures with no duplication of the project being worked elsewhere; (ii) a reasonable project schedule; (iii) direct relevance to enhancing the mission effectiveness of personnel of the Department of Defense or improving platforms, systems, components, or materials proposed to be acquired or developed by the Department of Defense, or to improvement of platforms, systems, components, or materials in use by the armed forces; (iv) the TRL/MRL level the technology; (v)projects that demonstrate an innovative approach with clear, valid, and logical objectives; (vi) facilities; and (vi) the proposed costs.

1. PREPROPOSALS: Preproposals should be no longer than eleven (11) pages and include a description of the relevant technology including: supporting data, the scope of the proposed effort (including a high-level Work Breakdown Structure (WBS)), and a description of the proposer’s research, development, manufacturing, past performance, or other special qualifications. The preproposal should indicate at which Technology Readiness Level/Material Readiness Level (TRL/MRL) level the proposed product will be at per the descriptions found in Attachment A0001. The preproposal should also include an anticipated cost for the efforts described in the preproposal, defined in milestones based on each fiscal year. Preproposals shall be submitted to the following email address: usarmy.apg.acc.mbx.jpeo-cbrnd-botaa@army.mil. If any of the required information is missing, the preproposal may not be considered.

Brochures or other descriptions of general organizational or individual capabilities will not be accepted as a preproposal. All preproposals will be assigned an identification number, and an email will acknowledge receipt of a preproposal. Usually, the Project Manager of the submitting organization should receive a decision letter or email regarding the preproposal within 60-90 days of submission.

GENERAL FORMATTING GUIDELINES: Preproposals and proposals under this BOTAA shall be submitted electronically. All submissions must be clear, legible, and conform to the following general formatting guidelines:

1. Elaborate proposals with high-gloss paper, vivid colors, detailed artwork, or other embellishments are unnecessary and not desired.

2. Paper: Pages shall be 8.5 x 11 inches, single sided, with each page numbered “X of Y pages.”

3. Margins: Minimum of 1 inch on all sides.

4. Type Font: 12-point Times New Roman, single spaced.

5. Acronyms: Spell out all acronyms the first time they are used. One page of the proposal body is allocated to spell out acronyms, abbreviations, and symbols.

6. Language: English.

7. Electronic file format: PDF, compatible with Adobe Acrobat Reader v. 11.0. File size less than 20 MB.

2. FULL PROPOSALS: If a preproposal submitted in response to this BOTAA is accepted by the U.S. Government, a Request for Full Proposal (RFFP) will be sent to the organization submitting the preproposal. The following is general guidance as to the scope of the full proposal for an Agreement.

Note that page limits are considered ceilings and do not denote a required number of pages.

FULL PROPOSAL GUIDELINES:

a. Cover Page (1 page) “Proposal for Prototype OTA”:

1. BOTAA number

2. Name of Lead Organization submitting proposal including Commercial and Government Entity code (CAGE) and Data Universal Number (DUNS).

3. Type of business, selected among the following categories: “Large Business,” “Small Disadvantaged Business,” “Other Small Business,” “HBCU,” “MI,” “Other Educational,” or “Other Nonprofit.”

4. Contractor’s reference number (if any)

5. Proposal Title

6. Technical point of contact to include salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), and electronic mail address (if available)

7. Administrative point of contact to include salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), and electronic mail address (if available)

8. Date proposal was submitted.

b. Technical Section (20 pages)

1. Acronyms, Abbreviations, and Symbols

2. Project objective. Describe the prototype and what will be accomplished if the U.S. Government funds the proposal. Describe how it fulfills an area of interest described by this Announcement.

3. Background data. Include, for example, data supporting early development, testing, manufacturing capabilities, current capability or state of development, the validity of models used to test and evaluate the technology, and Offeror compliance with applicable policies and standards as appropriate.

4. Proposed technical approach. Describe, in a comprehensive manner, the technical approach proposed to accomplish the project objective. Describe the proposed technical approach in sufficient detail so that the U.S. Government may determine that the proposed approach is of acceptable risk.

5. The proposal shall indicate the current TRL/MRL of the proposed prototype in accordance with Attachment A0001.

c. Project Management Section (20 pages).

1. Statement of Work (SOW). The Offeror shall submit a statement of work that formally captures and defines the work activities, deliverables, and timeline, for the prime contractor and any subcontractors, necessary to execute performance or development of the prototype. The SOW should include detailed requirements with standard regulatory and governance terms and conditions to sufficiently conceptually overlap with the agreement.

2. WBS and WBS dictionary. The offeror shall submit a WBS and use extended WBS elements as needed to define the agreement scope and to accurately describe the proposed effort. The WBS should correlate with the SOW and Agreement Line Items (ALINs).

3. Integrated Master Schedule (IMS). (Optional) The IMS should document the critical path, major milestones, tasks/activities, duration, lead/lag/slack time, and schedule relationships. The IMS should be directly traceable to the SOW, ALINs, and the WBS. The IMS is intended to be used as a tool for day-to-day tracking of the program/project. Tasks/activities should roll-up to increasingly higher summary levels. All tasks/activities in the IMS should be logically linked together showing predecessor/successor relationships. The tasks/activities should be sufficient to account for the entire program/project under agreement. Dates delineated in the IMS would become legally binding, and will be adjusted accordingly, based on actual award date. The IMS should be submitted electronically in “Read Only” format that shows all formulas and links for review. The data file shall be in the Microsoft Project latest version format.

4. Project Management Approach. The approach to managing and integrating the various aspects of the required work shall be described in sufficient detail so that the U.S. Government may assess associated risks. The Offeror shall identify significant milestones, decision points, and the processes that will be used to evaluate program status and progress. The Offeror shall include a description of any functional oversight. The Offeror shall present mechanisms for interactions/communications between Program Management and the U.S. Government, to include how processes will be updated (e.g., managing and interfacing with key Subcontractors and the U.S. Government). The Offeror shall include a description of management relationships or techniques that will be used to supplement day-to-day processes and procedures.

5. Risk Management Plan. The Offeror shall identify potential risks and describe the implementation of an integrated and proactive risk management plan as part of an overall management scheme (e.g., risk planning, risk assessment, risk handling, risk monitoring and documentation). The risk management plan shall discuss integrated methods for identifying, analyzing, prioritizing, and tracking risk drivers and include plans for adequate resources for risk mitigation. The Offeror shall describe tools or methodologies used in the integrated risk management and risk assessment processes.

d. Past Performance Section (10 pages).

Information shall be provided for all proposed first-tier subcontractors with whom the Offeror is teaming as well as the Offeror. The Offeror shall list ongoing and previous U.S. Government and commercial contracts held during the past three years, which are relevant and demonstrate ability to perform the effort required by the proposal. The Offeror shall explain the relevance of previous efforts with respect to the effort described in the proposal. The Government may send Past Performance questionnaires to Reference(s) listed. For that reason, the offeror must provide current contact information for all references listed in this section, to include: POC name, address, phone number, fax number and email address. Offerors shall provide notification to the Government pertaining to all contracts with commercial or Government entities that have been terminated for default in whole or in part, for any reason, during the past two years.

e. Budget Section.

1. Proposals submitted in response to a specific RPP or RFFPs may be submitted on a Fixed Milestone or Expenditure basis. Fixed Milestones allow the Offeror to submit pricing based on the completion and delivery of performance milestones. Expenditure based OTA’s allow the Offeror to submit invoices and receive payment on the actual costs incurred. Invoices for expenditure based shall be no more frequent than monthly. If during evaluation, or at any time prior to award, the Government determines that Offeror’s proposed type of budget is not suitable for the effort, the parties will negotiate a change in the arrangement. If a change to the type of budget proposed is required, revised budget information aligning to the type of arrangement agreed upon will be provided by the Offeror to the Government.

2. Offeror’s submitting a Fixed Milestone payment arrangement shall propose the milestone schedule and a price for each milestone. Each milestone price should correspond to a meaningful and verifiable point of the Prototype development. Offerors shall submit adequate information to substantiate and justify the proposed prices. At any given time up to the point of award, the Government may request pricing information from Offeror to assist in the Government’s evaluation of the Milestone pricing.

3. If the Offeror’s proposal is submitted as Expenditure based in response to this Announcement or an RPP, all cost information shall be submitted on a separate Budget Proposal in a “Read Only” Microsoft Excel file, showing all formulas and links. The depth and breadth of the budget information shall be determined based on the complexity of the requirement. Instructions for submission shall be provided in the RFFP.

f. Security Requirements.

Although not to be evaluated, the Offeror shall identify existing, or describe capability of obtaining, personnel/facilities security clearances. DoD security management and handling requirements outlined in regulations such as DoD 5200.1-R and DoD 5400.7-R apply OTs for prototypes.

g. Key personnel qualifications.

The proposal shall include a Curriculum Vitae (CV) and bibliographic data for the Program Manager and other Key Personnel detailing their qualifications to perform the work. If the Offeror does not presently employ Personnel in the positions identified as Key, the Offeror shall present a description of the terms of the commitment(s). The Offeror shall provide technical, regulatory, and management staffing plans, specifically addressing vacancies and maintaining Key Personnel. The Offeror shall also provide the CVs and/or resumes and list proposed duties of key subcontractor personnel and consultants (if any) who are proposed for this effort. The Offeror shall describe the overall proposed labor hours and labor categories relating to the performance of the SOW of Key Personnel.

h. Subcontractor Management.

The Offeror shall propose a subcontracting management approach to include analysis of subcontractor selection (i.e. list selection criteria), choice of subcontract types, and the plan for incentivizing contractors and assuring subcontractors meet cost, schedule, and performance requirements. The Offeror shall describe how subcontract competition will be sought, promoted, and sustained throughout the course of the cost reimbursement component of the acquisition, identify any known barriers to increasing subcontract competition and how to overcome any such barriers. The offeror shall provide the subcontractor business size status in accordance with the current Small Business guidelines and NAICS. Prior to Agreement execution, the Offeror shall submit with its proposal the first-tier subcontractors’ letter(s) of consent allowing the Government to disclose the subcontractors’ past performance to the Offeror during negotiations.

i. Company Financial Statements.

Offerors shall provide copies of their annual financial statements for the last three years.

j. Reports / Meetings / Knowledge Dissemination:

Reports are necessary for continuation of funding. Each request for full proposal will state the necessary reports that will be required. The Offeror must price all reports and deliverables.

k. Miscellaneous:

Any other documentation that may be requested by the U.S. Government in a Request for Project Proposals (RPP).

C. EVALUATION FACTORS FOR PROTOTYPE AGREEMENTS:

Proposals may be submitted in response to this Announcement or separate RPPs for particular requirements.

Full proposals will be evaluated by JPEO-CBRND personnel, other Federal Agency Representatives, outside subject matter experts in the technology area, or combinations thereof. At a minimum, the following will be considerations during the evaluation (in no particular order):

1. Technical Merit: The proposed plans, methods, techniques, and procedures must be feasible, clear, valid, adequately referenced, and state-of-the-art. The proposed schedule must be reasonable. Literature searches are recommended for documenting the strengths of the proposed project.

2. Military and Program Relevance: Projects must be directly relevant to enhancing the mission effectiveness of personnel of the Department of Defense or improving platforms, systems, components, or materials proposed to be acquired or developed by the Department of Defense, or to improvement of platforms, systems, components, or materials in use by the armed forces.

a. Technology Readiness Level/Material Readiness Level (TRL/MRL): The technology proposed shall indicate at which TRL/MRL level the technology is at currently. See attached for a full description of the TRL/MRL levels.

b. Project Objectives: The stated objectives must be clear, valid and logical. Projects that demonstrate an innovative approach are desired.

c. Support of other U.S. Government requirements. The proposal will be evaluated for alignment with, and ensure no unnecessary duplication of, JPEO-CBRND or other DoD requirements.

d. Key Personnel Qualifications: Document the qualifications, capabilities and experience of the proposed Project Manager and other key personnel in sufficient details to demonstrate that the proposed staff has the knowledge and skills to achieve the proposed objectives.

e. Facilities: Describe the proposed facilities and equipment, or unique combinations of these, in detail to demonstrate that the organization has, or may access, the necessary facilities required for the accomplishing the proposed objectives.

f. Budget/Cost: The budget must reflect the actual needs of the proposed work and be fully justified so that the U.S. Government can evaluate and determine the cost to be realistic as well as fair and reasonable and commensurate with the complexity and nature of the work proposed.

g. Best value: Award will be made to that Offeror whose proposal offers the best overall value to the Government based on an integrated assessment of the non-cost and cost related factors.

h. Past Performance: Documented satisfactory performance record. In the case of an offeror without a record of relevant past performance or for whom information on past performance is not available, the offeror may not be evaluated favorably or unfavorably on past performance.

Note: The Government reserves the right to amend the identified criteria or add additional criteria for consideration during evaluation of full proposals.

D. SELECTION FOR AWARD OF PROTOTYPE AGREEMENTS:

Any proposal received may be negotiated. After Government evaluation and selection, an award will be made to the successful offeror(s). Awards depend upon the availability of funds and fulfillment of requirements and priorities determined to exist at the time of award. In some cases, funding priorities may change as certain scientific tasks are addressed and new mission assignments arise. Award may also be dependent upon demonstration by the offeror that they have adequately addressed the following requirements, if applicable to the efforts being proposed:

a. Facility Safety Plan.

b. Certificate of Environmental Compliance.

c. All required Representations and Certifications are completed and on file.

E. AWARD ADMINISTRATION:

1. ELIGIBILITY:

To receive an award, at least one of the following conditions must be met:

· There is at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent in the prototype project.

· All significant participants in the transaction other than the Federal Government are small businesses or nontraditional defense contractors.

· At least one third of the total cost of the prototype project is to be paid out of funds provided by sources other than the Federal Government.

· The Senior Procurement Executive for the agency determines in writing that exceptional circumstances justify the use of a transaction that provides for innovative business arrangements or structures that would not be feasible or appropriate under a contract or would provide an opportunity to expand the defense supply base in a manner that would not be practical or feasible under a contract.

2. PAYMENT: Payment process and terms will be set forth in any resultant agreement.

3. AUDITS AND COST PRINCIPLES:

a. Agreements will require that adequate records be maintained to account for federal funds received and cost-sharing, if any.

b. Section 801 of the National Defense Authorization Act for Fiscal Year 2000 establishes a requirement that an OT for a prototype project that provides for payments in a total amount in excess of $5,000,000 include a clause that provides Comptroller General access to records. Because this is a mandatory requirement that has a substantial impact on the public, the Interim Rule implementing this law was published in the Federal Register, became effective July 5, 2000, is codified in Part 3 of Section 32 of the Code of Federal Regulations, Subtitle A, Chapter I, and is attached as Appendix 4. Section 804 of the Floyd D. Spence National Defense Authorization Act for Fiscal Year 2001 provides clarification that limits access in certain situations.

F. In accordance with 10 U.S.C 4022, subsection (f), Follow-on Production Contracts or Transactions. —(1) A transaction entered into under this BOTAA for a prototype project may provide for the award of a follow-on production contract or transaction to the participants in the transaction. A transaction includes all individual prototype subprojects awarded under the transaction to a consortium of United States industry and academic institutions.

(2) A follow-on production contract or transaction provided for in a transaction under paragraph (1) may be awarded to the participants in the transaction without the use of competitive procedures, notwithstanding the requirements of chapter 221 of this title and even if explicit notification was not listed within the request for proposal for the transaction if—

(A) competitive procedures were used for the selection of parties for participation in the transaction; and

(B) the participants in the transaction successfully completed the prototype project provided for in the transaction.

G.

IV. JPEO-CBRND AREAS OF INTEREST:

A. MISSION AREAS:

1) CBRNE counter-proliferation, nonproliferation, and defense equipment.

2) Installation and force protection.

3) Command, Control, Communications, Computers, Intelligence, Surveillance, and Rconnaissance (C4ISR) systems for WMD detection, localization, identification, and tracking and CBRNE response operations.

4) Technologies that support the Find, Fix, Finish, Exploit, Analyze, and Disseminate (F3EAD) process.

5) Preparing for and combatting improvised threats and the improvised explosive device network.

6) WMD precursor, agent, and device defeat or neutralization.

7) Ensuring nuclear deterrence.

8) Manned and unmanned platforms capable of supporting CWMD operations.

9) Technologies that enhance the effectiveness of forces that are tasked to conduct CWMD operations.

10) Software and Artificial Intelligence (AI) platform technology to achieve CBRN Defense integration, interoperability, and interdependence across all warfighting domains and functions.

11) Other operations related to the CWMD mission.

Included are the following Modernization Focus Areas:

1) Flexible, Scalable, and Interoperable Threat Agnostic Detection

2) Threat Characterization and Hazard Modeling

3) Artificial Intelligence and Machine Learning

4) Wearable Sensors

5) CBRN Information Nested with Joint All-Domain Command and Control

6) Unobtrusive Individual Protection

7) Biothreat Containment and Aeromedical Evacuation to Assure Continuity of Operations

8) Quick and Effective Decontamination to Contain and Neutralize Spread

JPEO-CBRND may also issue a separate RPP issued under this BOTAA for additional areas of interest.

B.

JPEO-CBRND OFFICE RESPONSIBILITIES:

1. Joint Project Manager (JPM) CBRN PROTECTION develops, fields and sustains CBRN protection and mitigation capabilities for the warfighter and the Nation. They develop next-generation physical protection capabilities, like masks and suits, that reduce physiological burden and enhance protection against emerging threats. JPM CBRN Protection also develops contamination mitigation technologies, including decontamination systems, to significantly decrease the time and materials required to decontaminate personnel and equipment.

2. JPM CBRN SENSORS develops, fields, and sustains CBRN sensors, reconnaissance systems, and mobile laboratory capabilities. They provide integrated early warning by bringing together the products in their portfolio along with robotics and autonomous systems, decision support tools, machine learning and artificial intelligence to provide situational awareness and understanding of CBRN threats.

3. JPM CBRN SPECIAL OPERATIONS FORCES (SOF) rapidly acquires and equips Special Operations and Special Purpose Forces with critical CBRN defense equipment necessary for mission success. Their focus is to further develop crucial technologies necessary for survival and unimpeded operations in denied CBRN environments. These technologies are transitioned to other Programs of Record as appropriate to enhance the capability of the Joint Force.

4. Joint Project Lead (JPL) CBRN INTENGRATION is responsible for the total lifecycle of enterprise information technology systems and provides enterprise wide CBRN threat warning and reporting, hazard prediction, and decision support capabilities for the collection, analysis, and dissemination of CBRN defense information. These capabilities provide commanders with more complete situational understanding of all the threats in the battlespace by integrating CBRN defense systems with traditional defense systems.

1. ATTACHMENTS AND APPENDICES:

ATTACHMENT 0001 Manufacturing Readiness Level Deskbook V2, May 2011