W911SR-24-9-RAPID RPP W911SR-RAPID Final_11APR2023x.pdf

Edgewood Contracting Division, Fort Detrick

Request for Project Proposal

W911SR-24-R-RAPID

Agency: Department of the Army Office: Army Contracting Command, Edgewood Contracting Division Location: Fort Detrick, MD, USA Program Office: JPEO CBRND Enabling Biotechnologies (JPEO-CBRND-EB) RPP Number: W911SR-24-R-RAPID Date Issued: 11 Apr 2024 Proposals Due: 1 May 2024 NLT 1400 EST

1. In accordance with Section III.F of announcement CBRND BAA 22-01, the Government is hereby requesting formal submission of preproposals intended to execute a formal agreement under 10 USC 4022(b), Other Transaction Authority (OTA) for the prototype project described below. Upon receipt of a preproposal submitted in response to this RPP, the next steps are as follows:

• The Government will evaluate the preproposal.

• Discussions among the parties, whether verbally or in writing, will occur as appropriate.

• The Government may request a full proposal from the offeror(s).

• Additional discussions may occur as necessary.

• Award(s) may be made after evaluation and selection of a successful proposal.

(Note: Awards are dependent upon the availability of funds.)

3. This competitive Request for Project Proposal (RPP) is issued to request project proposals in compliance with 10 USC 4022 and is being issued for planning purposes only. It is not to be construed as a commitment by the Government to award an agreement, nor will the Government pay for the information solicited. This RPP is for the requirement described in Attachment 1, Statement of Objectives (SOO).

4. Recognizing the difficulty in coordinating a whole of government response to the SARS-CoV- 2 pandemic, JPEO-CBRND-EB realized current medical countermeasure (MCM) development timelines are not rapid enough to effectively prevent infectious disease outbreaks, thereby impeding warfighter readiness. By leveraging the lessons learned and best practices from the response to the SARS-CoV-2 pandemic and the USG experience in developing an anti-SARS- CoV-2 therapeutic, the JPEO-CBRND-EB seeks to design and develop a readily accessible information warehouse and sharing system (the RAPID Database or data management solution).

Collectively, these components of RAPID will work synergistically to provide the Chemical and Biological Defense Program (CBDP) decision makers information for determining portfolio investment strategies and give Combatant Commands (CCMDs) knowledge of and access to safe and effective, developmental prophylactics and therapeutics that can be advanced and fielded in response to credible intelligence or chemical/biological event. Any award resulting from this RPP may be issued as an agreement under the authority of 10 USC 4022, with the expectation of a prototype testing event followed by final prototype development of the successful prototype.

Follow on the purchase of quantities necessary for fielding and sustainment are considered.

A. GENERAL INFORMATION:

5. The Government will review and evaluate the submitted preproposals which may result in a selection of one or more to consider for an award. The Agreements Officer may issue a request for full proposal (RFFP) from the selected preproposal(s) considered for funding. The Government may issue an agreement for an award based on the proposal submission or may require submission of additional details. The award of prototype agreements shall be for the development of prototypes in accordance with 10 U.S.C. 4022 for projects that are 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 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. Only a warranted Agreements Officer may obligate the U.S. Government to the expenditure of funds for awards under this Announcement.

6. Evaluation will be performed by JPEO-CBRND personnel, other Federal Agency Representatives or combinations thereof to enable the selection of the best preproposal submission, and/or subsequent full proposal submission. After evaluation and selection, an award will be made to the successful offeror(s). Subsequent 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 requirements.

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 (POC) 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 may 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.

7. Conceptual approach of acquisition is to potentially award to one or more performer(s) to develop a prototype data management system. The developed prototype(s) will be field tested at a relevant military exercise to be determined, to obtain real world feedback from potential future users, followed by a second technical evaluation and down selection of the best system to complete the final development and delivery of the completed prototype.

8. 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 any agreement. There are certain post-employment restrictions on former Federal officers and employees as defined in 18 USC 207 and FAR 3.104-4(c). 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.

9. The Freedom of Information Act (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 (e.g. a proposal, proposal abstract, and supporting documents; a business plan submitted on a confidential basis; and technical information submitted on a confidential basis) submitted to the Government in a process having the potential for award of an OT are exempt from disclosure requirements of 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.

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

11. Prospective awardees shall complete electronic annual representations and certifications at https://beta.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 contract resulting from this RPP. Offerors that are not registered should consider applying for registration immediately upon receipt of this solicitation. 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.

12. Data submitted that is proprietary and/or otherwise cannot be disclosed to the public for any purpose, , shall be appropriately marked.

13. Questions regarding this announcement may be submitted by email to usarmy.detrick.dod-jpeo-cbrnd.mbx.baa@army.mil within 7 business days prior to the closing date.

14. In accordance with 10 U.S.C. § 4022(f), the Government may award a follow-on production contract or Other Transaction (OT) for any OT awarded under this BAA if: (1) that participant in the OT, or a recognized successor in interest to the OT, successfully completed the entire prototype project provided for in the OT, as modified; and (2) the OT provides for the award of a follow-on production contract or OT to the participant, or a recognized successor in interest to the OT. This requirement does not include follow-on production.

15. Proposals, brochures or other descriptions of general organizational or individual capabilities will not be accepted as a preproposal. An email will acknowledge receipt of a proposal.

Generally, the Project Manager of the submitting organization should receive a decision letter or email upon completion of the evaluation and determination.

16. Administration: The Government will retain comments and information received in response to this RPP. Do not use Government security classification markings. All written responses must be received by the due date. Submission must be identified with a Subject Line of Responding Organization and RPP Title. Material that is advertisement only in nature is not desired. Late submissions will not be considered.

17. Eligibility: The Awardee must be eligible for an Other Transaction Authority for Prototype Agreement in accordance with 10 USC § 4022(d), meeting one of the following conditions:

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

(B) All significant participants in the transaction other than the Federal Government are small businesses (including small businesses participating in a program described under section 9 of the Small Business Act (15 U.S.C. 638)) or nontraditional defense contractors.

(C) 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.

(D) 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.

( A non-traditional defense contractor is defined as “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 the full coverage under the cost accounting standards prescribed pursuant to Section 1502 of title 41 and the regulations implementing such section”.

Offerors must document within their submission their eligibility.

18. Requirements: See Attachment 1, Statement of Objectives (SOO).

19. Submissions: Preproposals must be limited to eleven pages (not including cover sheet) 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 must also include an anticipated rough order of magnitude (ROM) cost for the efforts described in the preproposal, including a table demonstrating high level breakdown of the elements of cost for consideration (labor, hours, materials, ODC’s, other costs, indirects and fee) based on fiscal year. Preproposals shall be submitted in accordance with CBRND-BAA-22-01 Section VIII “Other Transaction Agreements” Subsection 11 “Submission Procedures” to below listed mailboxes only:

usarmy.detrick.dod-jpeo-cbrnd.mbx.baa@army.mil Scott.i.hoffman2.civ@army.mil Mea.n,johnson.civ@army.mil Late submissions will not be considered.

20. EVALUATION FACTORS: The following factors will be considered during evaluation (in no particular order):

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

ii. Military and Program Relevance: Projects must support the development of medical CBRN countermeasures, to include Countermeasure Prototypes, Special Projects, and Developmental Initiatives Supporting Medical CBRN Countermeasures and Enabling Technologies. Proposals should address an outstanding requirement and balance or reduce programmatic risk of the current DoD countermeasure development program.

iii. Funds Availability: JPL EB must have funds available to support the proposed work.

JPL EB funds are for purposes of warfare defense against JCS validated CBRN warfare threats.

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

https://sam.gov/opp/f2d01f5a6c444e32af543e9519a0805f/view mailto:usarmy.detrick.dod-jpeo-cbrnd.mbx.baa@army.mil mailto:Scott.i.hoffman2.civ@army.mil

v. Support of other U.S. Government requirements. The proposal will be evaluated for alignment with, and unnecessary duplication of, other DoD requirements and the medical CBRN Medical Countermeasure development efforts of the Department of Health and Human Services, the Department of Veterans Affairs, or the Department of Homeland Security.

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

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

viii. 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 fair and reasonable and commensurate with the complexity and nature of the work proposed.

ix. Best value: Contract 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.

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

21. SELECTION FOR AWARD: Subject to availability of funds, if agreeable terms are reached after evaluation of the proposal and negotiations, an award will be made.

ATTACHMENT 1

STATEMENT OF OBJECTIVES

DESCRIPTION/OBJECTIVE OF THE PROJECT: The Joint Program Executive Office for Chemical, Biological, Radiological, and Nuclear Defense, Enabling Biotechnologies (JPEO- CBRND-EB), develops, manufactures and delivers safe and effective Medical Countermeasures (MCMs) for preparedness, prevention, protection, response, and recovery from CBRN threats.

Today’s chemical and biological threat landscape is diverse, dynamic, and regionally distinct.

Agile and flexible defense systems are required to provide Combatant Commands (CCMDs) and other stakeholders throughout the Chemical and Biological Defense Program (CBDP) with actionable information regarding MCM availability at the speed of relevance.

The Rapid Access to Products in Development (RAPID) program is an integrated defense system composed of both physical MCM storage and fielding capabilities and a readily accessible information warehouse and sharing system (the RAPID data management solution or data system). The RAPID data system will identify and incorporate diverse data sets, curate and categorize the data, enable contextualized analysis of the integrated body of information, and provide a diverse set of stakeholders with actionable information necessary to make complex, resource-driven, and mission-focused decisions about continued development and/or fielding of MCMs.

The RAPID System is not intended to be used for biosurveillance (e.g., tracking outputs from fielded ChemBio detection platforms). Physical storage and fielding of MCMs are outside the scope of worked outlined below.

Throughout this RPP, “data system” is being used as a generic term to describe any form of data management solution that allows data identification, extraction, translation, loading, organization, storage, relational linking, analysis, retrieval, and visualization. Data can be structured, semi-structured or unstructured with centralized or decentralized storage using relational or multi-dimensional design schema.

STATEMENT OF OBJECTIVES (SOO):

Prototype Project Objective

Complex data and information related to CBRN MCMs will be stored and organized in the RAPID Data system so that it is intuitively accessible by a variety of stakeholders and end users.

The Data system is intended to provide actionable information to assist (1) JPEO- and CBDP-level decision makers when determining portfolio investment strategies and/or rapid response adjustments based on changing circumstances and (2) CCMD-level decision makers when evaluating a RAPID MCM for potential administration or for potential rapid deployment to enable fielding to US warfighters. The RAPID Data system will organize developmental MCMs using a Tier-based schema (See Table 1), with Tier 1 encompassing products early in development and Tier 3 designating MCMs with successfully completed Phase 1 clinical studies and an inventory of available doses. When queried by CBRN threat type, the data system needs to return, at a minimum, a list of potential MCMs along with their characteristics, tier data packages, availability, and developmental stage. A dashboard view will allow end users to easily view MCM coverage across individual and families of biological and chemical threats. Multiple user types are envisioned, including but not limited to JPL EB MCM Subject Matter Experts, CBDP stakeholders, CCMD Medical and CBRN leaders and planners, MCM Developers (e.g., pharmaceutical company representatives), US Government Interagency Partners, US-based non-government Partners, and International Partners. Data/information access rights will differ for each user type.

JPEO-CBRND-EB is seeking an interactive data management solution that enables (including but not limited to):

• Flexible integration of multiple data types from multiple sources without loss of context or meaning.

• Semi or fully automated identification and retrieval of new relevant information in accessible data sources as close to real time as possible.

• Efficient curation, validation, categorization, and integration of new data into the existing knowledge base.

• Streamlined access to a top-level information regarding information and availability of MCMs against specific threat of interest to inform decision regarding potential use

• Streamlined access to in-depth information regarding individual threats, and individual MCMs for use of this information in other EB efforts

• Efficient review of threat space coverage with existing MCMs at different levels of maturity, to include an interactive and user-friendly visualization of threat space coverage.

• Gap assessment to inform decision making process for threat prioritization

Table 1

Tier RAPID Tier Description*

Tier

Product discovery is complete, basic and/or preliminary efficacy data is available, developability data, small scale manufacturing initiated, assays developed, Tier

Cell banks available, preclinical studies complete, clinical supply available, Investigational New Drug (IND) ready

Tier

Demonstrated initial product safety, fielding plan is in place, 5-10k doses staged

*Data contained within each Tier subject to change

Performance Objectives (required results)

Project Objectives

The primary objective of this effort is to develop a RAPID data management solution to enable stakeholders to make data-driven decisions about fielding and/or accelerating development of MCMs. The targeted objectives include:

1. The RAPID data management solution will be composed of chemical and biological weapons threat and relevant medical countermeasure product data, including products that are in development.

2. The data management solution must be accessible to a broad array of stakeholders using USG systems, including NIPR, SIPR, and JWICS. The contractor must provide appropriately cleared personnel and be able to support implementation and maintenance on those systems.

3. The Offeror will be responsible for creating and incorporating current information relevant for development of novel MCMs against DoD-relevant chemical and biological threats (e.g., cell receptors, pathogenicity, LD50, endemic range, animal models, etc.). This generally does not include intelligence community analysis of threat space, though links to those analyses may be required.

4. The Offeror will facilitate the collection and processing of relevant and current medical countermeasure data, including searching existing literature and databases for candidates, working with DoD and USG performers to provide correctly formatted input/data regarding ongoing or former MCM development efforts. Relevant data sources are likely to include unstructured, semi-structured, and structured data sets.

5. The Offeror will provide an advanced visualization mechanism for threat-space coverage that enables intuitive understanding of countermeasure coverage, maturity and gaps.

6. The Offeror will ensure compliance with all relevant regulations and maintain an appropriately aggressive cybersecurity posture.

7. The Offeror will acquire inputs from the user community and adjust interfaces to maximize the utility of the data system. In addition, the Offeror will provide any necessary educational materials/trainings.

8. The data system may be implemented in iterations (e.g., via agile development), with full system accessibility within 2 years of agreement award.

9. The database and all associated materials and documentation may be tech transferred if necessary to maintain the system.

10. The government intends to make multiple awards (subject to available funding) for an approximate 12-month proof-of-concept demonstration system development and implementation on NIPR, with down-selection to a single follow-on award of options for further development and extension to classified systems. The scope of demonstration will be refined in collaboration with awardees during the first quarter of performance, but in general it will include full implementation of a minimal viable product encompassing at least 10 threat families and 15 developmental products as part of a targeted Q4 FY25 military exercise. Preproposals should clearly identify the division of costs from the proof-of-concept phase and final prototype completion.

Table 2. Non-inclusive list of additional RAPID System Performance Characteristics

# Component Description Metric(s) 1 Stand-Alone

System

• Flexibility in testing requirements.

• Provide the USG the option of bringing infrastructure entirely in-house.

• Interoperability with the Global Information

Grid

• Implemented on an approved DOD Cloud

Service (e.g. C Army or Platform-One) in accordance with all US army And U.S.

Government current/relevant cyber and information security regulations

• To the extent possible, design using software to be hardware-agnostic to mitigate system

• Continuity of Operations Plan

• Transition Plan to USG

• Image a USG computer with appropriate software and provide the same query to external and internal systems to compare result times and responses obsolescence or dependence on proprietary technologies.

2 Web-Based Graphical User Interface

• Widget-based or modular tools to allow customization of user interface based on access level, permissions, and/or user preferences.

• Broadly accessible and intuitive interface

• End User Feedback or Survey

• Validate compliance with Information and Communication Technology Section 508 Standards and other relevant USG guidelines/requirements.

Validation can be performed by a third-party vendor.

3 User Access Control with Multiple User Roles

• Required User Roles (not all inclusive):

• RAPID Program

• OCSURG

• JPEO/DASD Leadership

• Industry/Academia

• FHP

• Other USG Partners

• Customization of permissions for each role by an authenticated user

• Require user signoff/authentication on any action that impacts resource allocation/disbursement

• Execute Performance Qualification (PQ) to demonstrate that users can only execute allowed actions/access.

• Ensuring user-based access is secured in accordance with DoD Development, Security, and Operations (DEVSECOPS) standards (e.g., two-factor or non-CAC and CAC-enabled authentication)

4 User Activity Audit Trail and Analytics

• Create audit trail of user actions (for security, decision justification, and data system utilization analytics)

• Demonstrate that audit trail steps can replicate results (e.g., demonstrating equivalent end-state of a data system image prior to audited actions).

5 User Workflow Setting Persistence

• User can log in and begin where they left off

• Customizable, user-friendly dashboard where users define what they want displayed on their front page

• Access interface from different networks and confirm user preferences are captured and ported

6 User-Specific Notifications

• Users are provided notifications based on user type and user preferences; for example, RAPID team users are notified when a product goes to clinical trial

• Salient information types are tagged, which then triggers notification of selected users when the attribute changes

• Lag between system updates and user notifications

7 Ability to Initiate Actions within Data system Interface

• For example, a stakeholder can click “more info” for a product, which will then trigger a process flow on the back end to deliver additional information

• User can perform actions such as tagging and/or bookmarking items, send to other users, and other actions

• Allowable actions are permission-based as defined by user role.

• Demonstrate actions perform desired outcome and are only accessible to appropriate permission holders.

8 Mechanism for Customer Feature Requests Post-Fielding

• Feature may be implemented outside of the system

• Requests go to a decision making authority to assess priority, possibly informed by technical support for feasibility and ease of implementation.

• Can leverage existing ticket submission/tracking systems, including COTS.

9 Frameworks for Classified Options

• Include CUI and Secret options, with hooks for

TS/SCI

• Data system will be implemented and maintained by the performer across multiple security classification levels, to include CUI, Secret, and possibly TS/SCI

• Numerous systems have been developed that straddle classification designations.

Borrow classification and cybersecurity functionality assessment metrics from other programs.

10 Coverage for at least 10 Threats and 15 Products

• Threats and products to be determined by the government

• Tier reports for products will be government furnished information, but threat information should be provided by performer

• Confirm there is adequate SME support to fulfill the task

• Evaluation of coverage depth

11 Integration with an Internal Surveillance System

• Weekly update from the system triggers standardized report to users in an automated way about which MCMs are available for a threat

• Weekly report

12 Data system Query Ability for a Specific Threat with RAPID Product Match

• Multiple user types with different dashboards and views

• Speed and quality of data returned

• Option to do multiparameter Boolean/filter searches against data system

13 Ongoing Ability to Ingest Data from Multiple Sources and Clean, Transform, Store, and Provide Data to Users

• Includes structured and unstructured data types

• Includes text and non-text data formats (such as images or vector-based graphics)

• Converting and integrating an existing Excel-and MATLAB-based analytical framework into an open source programming language

• Needs to be resilient and extensible to respond to evolving needs

• Capable of supporting both automated updates and SME-enabled review/approval prior to integration

• Interoperability with other systems/applications through the exchange of data and visualizations

• Accuracy and fidelity of data post transformation

• Provide list of relevant authoritative data sources for threat and MCM information on priority list given to them, and methods for data ingestion from those sources.

• Lag time between data source and data system

• For each data archetype, construct test dataset where every element is queried and compared against original content.

14 Provide Stakeholders with All Necessary Information to Assess and Authorize Product User in U.S. Military Population

• Detail user stories: user stories will shape the dashboard and reports

• Each user type will need a dashboard and ability to generate reports.

• Resilient and extensible reporting to respond to evolving needs.

• Ability to export reports and data.

• Dashboard/Report accurately reflects data system content

• Dashboard/Report updates when data system updates.

• Report satisfies stakeholder needs

Project Management Objectives

It is anticipated that the offeror will be required to submit a number of documents to capture the progression of the project, post-award. Requirements may include, but are not limited to the following:

A001 Quality Agreement Upon agreement award, the offeror will provide a draft Quality Agreement within 10 calendar days after award. The Government will respond with comments or acceptance 10 calendar days following receipt of the draft Quality Agreement. The final agreement with incorporated changes shall be submitted 5 calendar days after receipt of Government comments. The Government will provide written acceptance. The offeror will submit via e-mail in Microsoft Office format to the Government representatives listed in the RPP.

A002 Meeting/Teleconference Minutes The offeror shall host and manage regularly scheduled integrated product team (IPT) meetings and provide meeting agendas no later than 2 days prior to the meeting and meeting minutes within 3 calendar days after all meetings/teleconferences conducted with JPEO-CBRND-EB.

Frequency depends on number of meetings and teleconferences.

A003 Monthly Progress Report The Monthly Progress Report shall contain regular status updates of all Intellectual Property (IP) license(s) related to the effort, in order to ensure that all license(s) are in good standing as the project progresses. In the event of any change in IP license(s) status or potentially imminent change in status, the offeror shall immediately contact the Agreements Officer (AO), Agreements Officer’s Representative (AOR) and, by telephone or e-mail communication.

The Monthly Progress Report shall contain the technical progress made during the previous month, a wireframe (visual diagrams) of system architectures, and the updated integrated master schedule (IMS) in Microsoft Project format. The schedule update shall include the explanation for any changes in the schedule, as well as drivers for the change, as applicable. The report will also address any concerns that would impact the performance, schedule, or cost planned for the effort. The offeror shall report using risk matrix format, to include risk mitigation strategies.

Submission shall be 15 calendar days after the end of each month of performance. The Government will have 10 calendar days to respond to the report with any comments, and the offeror will have an additional 5 calendar days to revise the deliverable or respond to those comments.

These reports will be used by the Government to assess both technical and schedule performance and will serve as milestones to allow invoicing for work executed to date.

A004 Annual Report The annual report shall narrate a complete summary of the project execution and associated results obtained, to include project results and accomplishments, issues encountered and recommended solutions. The report shall also address tasks that were not completed, reasons for non-completion, and a plan to accomplish the tasks or alternative approach to accomplish project goals, and as needed, an updated Statement of Work (SOW).

Submission shall occur within 15 calendar days of the anniversary date of award per annum. The Government will have 30 calendar days to respond to the report with any comments, and the offeror will have an additional 10 calendar days to revise the deliverable or respond to those comments.

A005 Final Report A Final Report shall be prepared at the end of the effort. A final report shall be provided whether any or all of the project Stages are completed. This report takes the place of the last annual report due (a financial report is still required). The report shall narrate a complete summary of the project execution and associated results obtained. The narration will include outstanding problems and their potential solutions, and problems solved during the course of the year(s), along with the solution to the solved problems. The report shall demonstrate how the prototype was advanced.

The offeror shall submit a Draft Final Report by the 30th calendar day following the end of the project period of performance. The Government shall provide comments to the offeror by the 30th calendar day following receipt of the offeror’s Draft Final Report. The offeror shall submit the Final Report on the 30th calendar day after receipt of Government comments.

A006 Master Government Property – Physical Inventory During performance of the agreement, the offeror may purchase material or equipment using Government funds [Contractor Acquired Property (CAP)] if approved by the AO and/or AOR.

The offeror shall perform, record, and disclose physical inventory results of all CAP in the offeror's possession.

A007 Patents – Reporting of Subject Inventions In accordance with the terms and conditions of the agreement.

A008 Expenditure Forecast The offeror shall submit the first expenditure forecast within 30 calendar days after award. An updated forecast shall be submitted within 15 calendar days of any agreement modifications that change the period of performance or the cost of the agreement. The monthly expenditure forecast submission shall include analysis of the cost drivers for Estimate to Complete changes, if any, from the previous month’s projection. All submissions must be provided in Excel format, including all formulas.

The expenditure forecast shall be submitted 15 calendar days from the start of each month and shall include both the monthly planned accrual and the cumulative total.

A009 Miscellaneous Data Submissions Required submissions include but are not limited to, Point Papers, Briefings, Transition of the system to USG plan and Technical Presentations and Publications.

A010 Work Breakdown Structure (WBS) The offeror shall provide a four-level WBS with costs and schedule (top level is program, level 2 is Stage, level 3 are major tasks, level 4 are subordinate tasks). For the lowest task level, the offeror shall provide a breakdown for labor, material, and other indirect costs.

The WBS shall be updated annually or 30 calendar days after a SOW modification. Government review/approval is 15 calendar days after receipt of first submittal. The offeror shall provide changes to the draft within 10 calendar days of such request. The offeror shall provide the final document within 10 calendar days after approval of changes is received from the Government.

A011 Integrated Master Schedule (IMS) The offeror shall provide within 15 calendar days after agreement award, an IMS in Microsoft Project format. Any updates to the IMS shall be included in the monthly progress reports. Any event that impacts the critical path by more than 30 days shall result in an off-cycle IMS update.

Submission shall be 15 calendar days after the end of each month of performance. The Government will have 10 calendar days to respond to the report with any comments, and the offeror will have an additional 5 calendar days to revise the deliverable or respond to those comments.

Operational Constraints/Limitations/Restrictions: Not Applicable

PERIOD AND PLACE OF PERFORMANCE: The anticipated Period of Performance for this effort is up to 1 year from date of award. Specific dates to be negotiated. It is anticipated that the primary place of performance will be the contractors’ facilities, however this aspect can be negotiated as part of each Offerors’ submission.

DELIVERABLES: The contractor will be required to provide a number of deliverables throughout the course of this project, categorized as either Data or Prototype.

DATA DELIVERABLES: Data deliverables include meeting minutes, financial reports, technical progress reports, annual reports, property inventory, patents and invention reports, technical data packages, forecasts, WBS, IMS, TPP, and any other data necessary to document the product development. In addition, there will be collection, curation, and storage of the data in the Government-issued data format for future transfer to the Government.

Note: Technical data deliverables described herein shall be delivered to the Government with a minimum of Government Purpose Rights.

Table 3 Milestone Delivery Table Milestone Date from Project Start User Stories 2 Months User Interface 3 Months to Mockup

6 Months to Operational Demo Architecture and Framework for

MVP

4 Months

Access Controls and Audit Trail 6 Months Architecture and Framework for System

9 Months

RAPID participation at Military Exercise TBD

Approx 12 Months

Delivery of final RAPID System to

USG

Approx 15 Months

*Dates are prospective, updates to be made based upon offeror proposed solution.

SPECIAL REQUIREMENTS:

Export Control: In accordance with applicable laws and regulations.

Security and Classified Data: NOTE: Security Clearances are not required for access to unclassified data.

Security Clearances. Personnel performing on this SOO shall obtain a Secret, Top Secret in accordance with the DD 254, Contract Security Classification Specification. The Contractor must possess or obtain a facility security clearance at the level of Secret, Top Secret prior to contract award. The Contractor shall register and request security clearances through the National Industrial Security Program Central Access Information Security System (NCAISS) (https://www.dss.mil/is/ncaiss/). Contractor personnel shall have appropriate clearances prior to contract award unless otherwise approved in writing by the Contracting Officer (CO). If subcontractors are utilized in performance of a classified contract, the Prime Contractor shall create a Subcontract DD 254 in the National Industrial Security Program Contract Classification System (NCCS). The Prime Contractor shall ensure that any teaming partners or subcontractors have the appropriate security clearances prior to contract award.

FAR 52.204-2, (a) may be included in a resulting agreement. This clause applies to the extent that this contract involves access to information classified "Confidential," "Secret," or "Top Secret." (b) The Contractor shall comply with (1) the Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (32 CFAR Part 117), and

(2) any revisions to that manual, notice of which has been furnished to the Contractor. (c) If, after the date of this contract, the security classification or security requirements under this contract are changed by the Government, and if the changes cause an increase or decrease in security costs or otherwise affect any other term or condition of this contract, the contract shall be subject to an equitable adjustment as if the changes were directed under the Changes clause of this contract. (d) The Contractor agrees to insert terms that conform substantially to the language of this clause, including this paragraph (d) but excluding any reference to the Changes clause of this contract, in all subcontracts under this contract that involve access to classified information.

A SF 312 Non-Disclosure Agreement (NDA) initiated by the company’s Facility Security Officer (FSO) is required for each of the Contractor’s personnel.

Security Manager Appointment. The Contractor shall appoint a security manager. The security manager shall provide employees with training required by DOD 5200.1-R, Information Security Program Regulation. The Contractor will also provide initial and follow-on training to Contractor personnel who work in Army controlled/restricted areas.

Listing of Employees & Clearance Documentation. The Contractor shall maintain a current listing of employees. Within 10 calendar days of contract award, the Contractor shall provide the Contracting Officer’s Representative (COR) a list with the names, location of performance and clearance requirements of all company employees assigned to this effort. The list shall be validated and signed by the company Facility Security Officer (FSO). An updated listing shall be provided when an employee's status or information changes.

Controlled/Restricted Areas. The awardee shall be compliant with all applicable security procedures for access/entry/control/restrictions of areas where awardee personnel will work

Physical Security. The Contractor shall safeguard all Government property and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each workday, all Government facilities, equipment, and materials shall be secured.

All contractor personnel shall conform to all Department of Army, Department of Defense, and US Government policies and procedures relating to workplace security and safety at all times.

The contactor shall report security and safety violations immediately to the Contracting Officer’s Representative (COR)/Contract Manager. Lost Government-issued security badges must be reported immediately to the COR/Contract Manager or appropriate security POC. The contractor shall be responsible for securing all Government owned hardware, software, and the facilities that contractor personnel will be using. The following personal items are prohibited inside classified workspaces at all times: cell phones/ Blackberries, portable USB memory drives, other portable USB devices, external hard drives, cameras, MP3 players, scanning devices, digital flash cards/disks, personal laptop computers, camera/USB watches and wireless transmitters.

Additional Security Requirements: This effort requires access to classified Government information at U.S. Government facilities. Physical, personnel, information, and operational security measures are part of the security specifications as outlined in the DD Form 254 and the contractor shall comply in accordance with DIAM 50-5 and other Government security regulations, manuals, and directives.

Pass and Identification Items. The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.

Comply with HSPD-12 Personal Identity Verification (PIV) issuance requirements, known as the Common Access Card (CAC). Be responsible for obtaining CAC or PIV ready status prior to contract start.

Retrieving Identification Media. The Contractor shall retrieve all identification media, including vehicle passes from employees who depart for any reason before the contract expires, e.g., terminated for cause, retirement, etc.

Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their contractor-owned vehicle or privately-owned vehicle while on all Army installations.

Controlled Unclassified Information (CUI). The Contractor shall comply with Department of Defense (DoD) Instruction 5200.48 “Controlled Unclassified Information (CUI) DoD 5400.48, Controlled Unclassified Information requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding CUI material.

Reporting Requirements. Contractor personnel shall report to an appropriate authority any information, or circumstances of which they are aware of, which may pose a threat to the security of DOD personnel, Contractor personnel, resources, and classified or unclassified defense information.

Key Control/Access Badge Control. The Contractor shall establish and implement methods of making sure all keys/badges issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. The Contractor shall not duplicate any keys issued by the Government.

Government Furnished Equipment (GFE). The Contractor shall establish and implement procedures to ensure all GFE to include laptops and other data processing devices, issued to the Contractor by the Government are not lost or misplaced, are not used by unauthorized persons or are not subject to unauthorized external devices. The Contractor shall immediately report to the COR any occurrences of lost GFE within two (2) hours of discovery of occurrence. If GFE is lost, the Contractor may be required, upon written direction of the CO, to replace the equipment at no additional cost to the Government. The Government may replace the equipment and deduct the cost of such from the monthly payment due the Contractor.

Information System Security. The Contractor shall implement Information System (IS) security protections and ensure the protections are appropriate to the confidentiality, integrity, and https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF availability needs of the Government. Establish appropriate administrative, technical, and physical safeguards to protect any and all nonpublic Government data.

Risk Management Framework (RMF). All Information Systems (IS), Platform Information Technology (PIT) and Information Technology (IT) Services or Products under this requirement, that receive, transmit, store, or process nonpublic government data must be accredited in accordance with Department of Defense (DOD) Instruction (DoDI) 1510.01, Risk Management Framework (RMF) for DoD Information Technology (IT) and comply with annual Federal Information Security Management Act (FISMA) security control testing. IS and PIT systems must be categorized in accordance with Committee on National Security Systems Instruction (CNSSI) 1253, implement a corresponding set of security controls from the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, and use assessment procedures from NIST SP 800-53A with additional DoD-specific assignment values, overlays, implementation guidance, and assessment procedures as required.

All systems subject to RMF must present evidence of authorization in the System Security Plan (SSP), Security Assessment Report (SAR), Plan of Action and Milestones (POA&M), and authorization decision document; or show that the system has a DoD Risk Management Framework (RMF) or equivalent DoD Component PIT system accreditation decision that is current within 3 years. Evidence of FISMA compliance must be presented in the form of a POA&M.