Attachment 1-OBAA Topic-Solicitation No.8-Topic Solicitation.pdf

70RWMD21R00000002 Attachment 1

1 | P a g e

DEPARTMENT OF HOMELAND SECURITY (DHS) COUNTERING WEAPONS

OF MASS DESTRUCTION OPEN BROAD AGENCY ANNOUNCEMENT (CWMD

OBAA) TOPIC SOLICITATION NO. 8: 70RWMD21R00000002

1. Topic Solicitation Number: Topic Solicitation No. 8: 70RWMD21R00000002

2. beta.SAM.gov Solicitation Number: 70RWMD21R00000002 for Topic Solicitation 8 and beta.SAM.gov Solicitation Number: 70RDND19R00000003 for OBAA

3. Topic Solicitation No. 8: 70RWMD21R00000002

Event Dates/Time (Local Eastern Time)

• Notification to Submit Proposals – November 6th, 2020

• Deadline for Submission of Questions – November 16th, 2020, 3:00 PM Eastern Time

• Response to Questions – November 19th , 2020, 3:00 PM Eastern Time

• Pitch Paper Submission Deadline – December 7th, 2020, 3:00 PM Eastern Time

• Pitch Paper Notifications – December 17th, 2020

• Proposal Due Date – January 5th, 2021, 3:00 PM Eastern Time

• Notification of Selection/Non-Selection of Proposals– January 19th, 2021

• Award date (estimated) – February 05th, 2021

There will be no exceptions to the time and date on which responses are due, unless determined otherwise by the Government. Proposals received after the designated closing date/time will not be considered. See 5.3.1 of the OBAA.

Note: This Topic Solicitation will be conducted in accordance with the Two phased Evaluation Process as described under Section 1.6 of the OBAA. This Topic Solicitation is being issued in accordance with the notice and solicitation requirements set forth in FAR 5 for this FAR 35 Research and Development solicitation. The OBAA Solicitation 70RDND19R00000003 was posted on Federal Business Opportunities (FBO.gov) on April 17, 2019. Effective November 12, 2019, FBO.gov is retired, and the OBAA Solicitation 70RDND19R00000003 can now be found on https://beta.sam.gov.

This evaluation process will consist of the solicitation, receipt, and evaluation of both pitch papers and proposals. Under this evaluation, Phase 1 will consist of the solicitation, receipt, and evaluation of the pitch papers from potential performers. Entries in the various sections of the pitch papers should be concise and conform to the specified formatting and word count limitations as indicated in this Topic Solicitation. No formal transmittal letter is required for the Phase 1 responses. Once the pitch paper peer/scientific review process has been completed, potential Offerors will be notified in writing, typically via e-mail, whether the potential Offeror is “encouraged” or “not encouraged” to submit a full proposal.

A down-selection process will then be conducted by DHS. Offerors who submitted Phase 1 pitch papers and were encouraged to submit full proposals will be invited to participate in Phase 2. Phase 2 will consist of the solicitation, receipt, and evaluation of a proposal https://beta.sam.gov/

2 | P a g e limited to 20 pages, excluding the cover sheet, Volume II, and Volume III. Once the proposal peer/scientific review process has been completed, Offerors will be notified in writing, typically via e-mail, that its proposal has either been selected, selected but not funded, or not selected for award.

Offerors not selected for an award may request feedback regarding the peer/scientific review findings of the submitted proposal. A written request to the Contracting Officer must be received within 3 calendar days of notification of non-selection.

4. Topic Solicitation Research & Development Focus Areas:

CWMD.05 – Nuclear Sensing: Technologies to provide cross-cutting improvements to nuclear threat detection through dramatically improved performance or reduced costs when compared to Commercial off the Shelf.

CWMD.07 – Chemical and Biological Detection: Provide increased capability to detect and identify chemical and biological threats in response to emerging operational needs.

4.1. Research Opportunity Description

Title: Chemical, Biological, Radiological, and Nuclear (CBRN) Detection on an Unmanned Ground Vehicle (UGV)

Objective: Rapidly develop and field an Unmanned Ground Vehicle with CBRN sensors for DHS applications.

Technology Readiness Level at Beginning: TRL 5-6 Technology Readiness Level at Conclusion: TRL 7

Background

The U.S. Department of Homeland Security (DHS) is committed to using cutting-edge technologies and scientific talent in its mission to make America safer. In December 2017, the Department of Homeland Security (DHS) established the Countering Weapons of Mass Destruction (CWMD) Office by consolidating the Domestic Nuclear Detection Office (DNDO) and a majority of the Office of Health Affairs (OHA). The mission of CWMD is to counter attempts by terrorists or other threat actors to carry out an attack against the United States or its interests using a weapon of mass destruction. The DHS CWMD Research and Development (R&D) appropriation provides resources necessary to identify, explore, and demonstrate new technologies and capabilities that will help enable the DHS and stakeholders to prevent, protect against, respond to, and mitigate nuclear, chemical, radiological, and biological threats and incidents.

Priority needs of DHS’s operational components drive CWMD's R&D investments. CWMD looks for the following types of solutions within the chemical, biological, radiological, and nuclear mission space:

3 | P a g e

• Over the horizon, future innovations that will transform the way homeland security operators accomplish their missions.

• Near-term capabilities that will solve current operational challenges and meet the Department's R&D needs.

• New applications of technologies to respond to emerging threats to the homeland.

As the threat of terrorism evolves, DHS intends to assess a wide spectrum of potential technologies that can enhance its capabilities.

The Department of Homeland Security (DHS) has several special mission teams that respond to disasters and other heightened security events within the United States. These teams have a strong need for unmanned vehicles that can provide situational awareness, reconnaissance, and remote sensing capabilities. Currently DHS operates a small fleet of unmanned ground vehicles and sensor packages developed for specific Department of Defense missions. DHS is interested in developing and prototyping an unmanned ground vehicle specifically designed for its specific missions. The developmental prototype will allow DHS to better assess how to leverage UGVs specifically developed for its mission space.

Description

This Topic Solicitation is looking to develop an unmanned ground vehicle (UGV) with an integrated array of sensors that can detect CBRN and related materials. The UGV will be utilized by DHS special mission teams among various DHS Components to provide situational awareness, scout unknown areas, provide protection of personnel in hazardous conditions and aid in the detection and identification of CBRN/WMD threats and hazards.

The UGV will be deployed into a variety of scenarios and situations with the need to adapt to unknown conditions. Many of the potential uses for the UGV will require it to wirelessly stream back video and sensor data to provide critical information to the DHS components in the field.

This solicitation is envisioned to be a spiral development effort that will occur in three phases. Phase One will be focused on the Offeror developing an integrated CBRN UGV for DHS operational needs; providing a prototype integrated package consisting of a remotely-controlled ground vehicle, manipulative arm, sensors, and ancillary devices.

Phase Two will consist of continuing to develop the prototype by addressing any observed operational issues or deficiencies during Phase One. Phase Three will develop expanded capabilities by integrating additional sensors onto the system. Phases Two and Three will be optional; dependent upon system success in the previous phase, government funding availability, and government need.

The initial phase focuses on the integration of three (3) to four (4) key CBRN sensor types and a manipulative arm into/onto the base ground vehicle. The Government is interested in the potential of commercial sensor assemblies that can meet DHS’ CBRN detection needs.

However, the Government is also requesting that Offerors provide contract options to allow for the integration of Government Furnished Equipment (GFE) sensor packages. As such, Phase One will be costed with two options for each of the three sensor types requested.

4 | P a g e

For each phase of the development, the Government will conduct field trials of the developed, functional prototype with DHS Operational Components. These field trials will provide hands-on evaluation experience and data that will be reported to both CWMD and the Offeror. To support this part of each phase, the offeror will be asked to supply in-person system familiarization training and materials to end users, reach back support, and onsite maintenance support. Additional testing by CWMD is planned after the field trials to evaluate system ruggedness and long-term sensor capabilities.

The optional second phase will require the Offeror to propose on improving the system to correct system deficiencies and/or implement recommended improvements identified during the phase one field trials. After improvements have been made, the system will again be deployed for field trials with operational DHS components.

The optional third phase will require the Offeror to propose on developing and integrating additional sensors onto the existing UGV system. These additional sensors may be additional GFE sensors, or commercial sensors identified by the Offeror that meet DHS’ desired capabilities.

Phase Structure

Offerors must follow the below spiral development phase structure approach. There will be no exceptions. All work must be conducted in coordination with CWMD Rapid Capabilities Division (RCD). Deliverables are specific by phase and stage. At a minimum, all offerors should anticipate a kick-off meeting at the start of each phase with periodic reporting required throughout each. The Offeror will be required to maintain a configuration bill of materials during the program, including both hardware and software for the prototype that can be requested ad-hoc by the government as needed. All recurring reporting formats will be determined with the Government before the first reporting period.

All single event reports shall use a Government provided template. The specific technical deliverables are identified by phase and stage below. Note the phases provide example tasks that the Offeror may restructure in their statement of work (SOW) and price sheet.

Phase I, Stage 1 - System Development Planning and Review (Duration = 3 Weeks, Not to Exceed $100,000): After kick-off, the Offeror will develop a comprehensive plan for development of a working prototype including the overall system architecture to support sensor integration. This plan will be provided to the Government for review, revision and agreement before the start of stage II.

Tasks:

Phase I, Stage 1 will have the following expected base task:

Task 1: Create a plan for developing the underlying system architecture including software and hardware to allow for specified component integration. This planning task should include planning for integration or improvements to provide a manipulative arm, changes

5 | P a g e to ancillary devices, changes to the handheld control unit to provide control for integrated components.

Stage 1 will have the following optional tasks; it is intended that the Government will fund either option A or option B of each specified task to develop the full sensor suite for the UGV. Each task includes the planning for the development of software and hardware and any testing that may be needed. The goal of each optional task is to develop a plan for creating a sensor assembly that can integrate with the ground vehicle and the planned system architecture. Note that some tasks require procurement of the base sensor package from commercial sources while other tasks are to incorporate GFE provided sensor packages. Basic specifications for the GFE components are provided in Attachment 5.

Task 2A: Plan the integration of the Offeror proposed radiation detector; this task includes procurement of the proposed sensor.

Task 2B: Plan the integration of a GFE supplied radiation detector; for this optional task the Government will provide the sensor package.

Task 3A: Plan the integration of the Offeror proposed Base Chemical Sensor (BCS); this task includes procurement of the proposed sensor.

Task 3B: Plan the integration of the Government specified Base Chemical Sensor; this task includes procurement of the Government specified base chemical sensor;

Task 4A: Plan the integration of the Offeror proposed Chemical Warfare Agent (CWA) sensor; this task includes procurement of the proposed sensor.

Task 4B: Plan the integration of a GFE supplied CWA sensor; for this optional task the Government will provide the sensor.

Task 5A: Plan the integration of the Offeror proposed oxygen sensor; if this capability is provided by one of the other sensors optioned above, this task will not be optioned.

Task 6A: Plan the integration of the Offeror proposed ambient air thermal sensor; if this capability is provided by one of the other sensors optioned above, this task will not be optioned.

Deliverables:

• Deliverables for Phase I, Stage 1 can be found in Section 5

Phase I, Stage 2 - System Development (Duration = 12 Weeks): After agreement on the preliminary design with the Government, the Offeror will develop a working prototype of the CBRN UGV, integrating both the proposed manipulative arm as well as the requested sensors per the contract and preliminary design reviews. During this period, the Offeror will provide biweekly status reports to the Government and hold biweekly meetings with

6 | P a g e

Government representatives. When completed and tested, the developed prototype with sensors, accessories, support equipment, and consumables will be delivered to the Government for acceptance testing. The Offeror shall also develop a system familiarization plan and packet to be provided during stage 3 to the operational components.

Tasks:

The tasks for Phase I, Stage 2 will be the implementation of tasks specified and optioned and agreed to in Phase I, Stage I. Deviation from the actual plans due to unforeseen circumstances or the nature of developmental designs is understood and expected. Deviations should be approved by the Government. Deviations from the original plans and concepts should be recorded both in the biweekly reports as well as being incorporated into the final design package due to the Government on completion of this Phase. A synopsis of the expected tasks for Phase I, stage 2 are:

Task 1: Developing the system architecture, including software and hardware, to allow for specified component integration of the UGV system. This includes custom programming, fabrication, and testing. This task also includes incorporating and testing the optioned sensor packages, listed below, into the UGV system. Note that the sensor packages are to be flexible such that the UGV can have multiple configurations with different arrays of sensors sent into the field.

Task 2A: If optioned, develop the radiation sensor package to integrate into the UGV system. This task includes custom programming, fabrication, and testing as needed.

Task 2B: If optioned, develop the radiation sensor package, based on the GFE sensor, to integrate into the UGV system. This task includes custom programming, fabrication, and testing as needed.

Task 3A: If optioned, develop the Base Chemical Sensor (BCS) package to integrate into the UGV system; This task includes custom programming, fabrication, and testing as needed.

Task 3B: If optioned, develop the Base Chemical Sensor (BCS) package, based on the Government specified sensor, to integrate into the UGV system; this task includes custom programming, fabrication, and testing as needed.

Task 4A: If optioned, develop the Chemical Warfare Agent sensor package to integrate into the UGV system; this task includes custom programming, fabrication, and testing as needed.

Task 4B: If optioned, develop the Chemical Warfare Agent sensor package, based on the GFE sensor, to integrate into the UGV system; this task includes custom programming, fabrication, and testing as needed.

7 | P a g e

Task 5A: If optioned, develop the oxygen sensor package to integrate into the UGV system; this task includes custom programming, fabrication, and testing as needed.

Task 6A: If optioned, develop the ambient air thermal sensor package to integrate into the UGV system; this task includes custom programming, fabrication, and testing as needed.

Task 8: Delivery of the developed prototype with all sensors. This prototype should be fully integrated and ready for field testing. The system should be delivered with all accessories needed to operate continuously in field trials for up to eight hours as well as meet all the criteria as specified within the proposal. This should include batteries, extra batteries, battery chargers, handheld controller, base stations, and other ancillary items.

The system should also be delivered with at least one consumables kit as specified. The Offeror should price out the complete prototype kit as a single item but also provide additional items as accessories to allow for the Government to procure spare parts in some situations during Phase I, Stage 3.

• Deliverables for Phase I, Stage 2 can be found in section 5

Phase I, Stage 3 – Field Trials (Duration = approximately 26 Weeks): This stage will be primarily conducted by the Government with the Offeror providing key tasks such as:

system familiarization, system reach back and maintenance support; these are listed below as tasks. As part of the taskings the Offeror will provide a biweekly reach back and maintenance report to the Government during this stage. The Offeror will also maintain a configuration record of the system. Stage 3 will incorporate the following events that are to be scheduled after contract award, note that some of these events and locations may change during the program execution due to DHS Component needs and should be considered notional:

• Event 1: Acceptance Testing (2 Weeks) The system will be evaluated by the Government to ensure that it is operating properly, that sensors are providing data, and that it can be reliably sent to DHS Operational Components without issue.

• Event 2: Field Trial A (approx. 6 Weeks) The system will be shipped to an appropriate location per the DHS operational component conducting the trials. The system will then go through a system familiarization course with team members of the operational component. After the system familiarization course, the operational component team will conduct a one-month field trial based on their own application of use cases and demonstrations to determine how the system meets their operational needs, any identifiable issues with the system, and any suggested improvements. CWMD RCD will be responsible for capturing this information from the operational component team members. The system will then be checked out, additional consumables may be ordered, and the system will be shipped to the next event.

8 | P a g e

• Event 3: Field Trial B (Approx. 6 Weeks) Event 3 will be structured identically to Event 2, only changing the operational component conducting the trials and potentially the venue of the trials per the operational component.

• Event 4: Field Trial C (Approx. 6 weeks) Event 4 will be structured identically to Events 2 and 3, only change the operational component conducting the trials, and potentially the venue of the trials per the operational component.

• Event 5: Post Deployment Evaluation (Approx. 3 to 5 weeks) Event 5 will evaluate the system’s robustness and survivability over the past twenty weeks of field trials.

This event will also include evaluating the system against both specific ground vehicle capabilities as well as verify that the sensors maintain their base capabilities as specified.

It is anticipated that CWMD will consolidate data from all the events and provide an out-briefing to stakeholders, to include the Offeror, regarding capabilities found, issues identified, and improvements suggested.

Tasks:

During Phase I, Stage 3 the following tasks will need to be supplied by the Offeror during the events listed above:

Task 1: Provide an in-person system familiarization course to the operational component team and/or test team members (up to 30 individuals) to enable them to operate the system per the familiarization training noted under Phase I, Stage 2 deliverables.

Task 2: Provide reach back support to the operational component team and/or test team members to enable them to identify issues with the system. Reach back support will be the first step in addressing issues or malfunctions with the system in the field. Reach back support should be available via phone and e-mail. Required hours will be determined based on the events ongoing in the field but should be generally planned for availability on weekdays eight hours a day during each of the events listed above.

Task 3: Provide maintenance support that is deployed to the field trial sites as needed; such as to correct any system issues that requires technician, or engineer, support that cannot be supplied over the phone or by video conference. Field maintenance should not incorporate time to prepare and ship the system into the field. All repairs should be completed in the field as approved by the Government, to minimize down time for the operational component’s time. The support is intended for this to be a service call type maintenance with appropriate personnel deploying to the test site as needed rather than being present to provide immediate support. The expectation is that maintenance personnel can be on-site within 48 hours of determining, with the Government, that field repair is needed. Per this task the Offeror should note any changes made to the Bill of Materials (including software) even when replacing like part for like part and to maintain a current record of both hardware and software in the field.

9 | P a g e

Task 4: Provide software updates and revisions. These updates and/or revisions should be provided when the system is unable to operate in the field per the capabilities that were to be developed per the contract. With such updates, both the Bill of Materials and software release notes shall be updated.

Task 5: Provide additional consumables as needed. The contract should be structured to allow order of additional consumables as needed between or during events.

These consumables should be available and deliverable within 1 week of being ordered by the Government.

• Deliverables for Phase I, Stage 3 can be found in section 5

(Optional) Phase II, Stage 1 - Planning of Developmental Updates to System (Duration 12 weeks): After Phase II kick-off, the government and Offeror will review data from Phase I, Stage 3 to propose additional system development efforts, or redevelopment, to address priority issues identified. This may include changes of sensors or components, or new software builds. It is anticipated that the government will provide a list of prioritized changes to the Offeror to assist in their proposal process.

Tasks: Plan development of updates to the existing prototype UGV.

• Deliverables for Phase II, Stage 1 can be found in section 5 below.

(Optional) Phase II, Stage 2 (Duration approximately 18 Weeks): After agreement on the second phase development design with the Government, the Offeror will develop a working prototype of the UGV, integrating all agreed to changes within the existing prototype. During this period the Offeror will provide biweekly status reports to the Government and hold biweekly meetings with Government representatives. When completed and tested, the developed prototype with accessories, support equipment, and consumables will be delivered for acceptance testing by the Government. Developmental tests conducted during this time by the Offeror should be recorded and transmitted to the Government. The Offeror should also develop an updated familiarization packet to be provided during stage 3 to the operational components.

Tasks: Will be based on an updated statement of work for Phase II based on the requested and approved updates.

• Deliverables for Phase II, Stage 2 can be found in section 5

10 | P a g e

(Optional) Phase II, Stage 3 – Field Trials (Duration = approximately 26 Weeks): This stage will be primarily conducted by the Government with the Offeror providing key tasks such as: system familiarization, system reach back and maintenance support; these are listed below as tasks. As part of the taskings the Offeror will provide a biweekly reach back and maintenance report to the Government during this stage. The Offeror will also maintain a configuration record of the system. Phase II, Stage 3 will incorporate events much like occurred in Phase I, Stage 3 but may include a different number of events or change the time structure of those events; depending on funding available and Government needs.

It is anticipated that CWMD will consolidate data from all of the events and provide an out-briefing to stakeholders, to include the Offeror, respecting capabilities found, issues identified, and improvements suggested.

Tasks:

During Phase II, Stage 3 the following tasks will need to be supplied by the Offeror during the events listed above:

Task 1: Provide a system familiarization to the operational component team and/or test team members (up to 30 individuals) to enable them to operate the system per the systems familiarization noted under Phase I, Stage 2 deliverables.

Task 2: Provide reach back support to the operational component team and/or test team members to enable them to identify issues with the system. Reach back support will be the first step in addressing issues or malfunctions with the system in the field.

Task 3: Provide maintenance support that is deployed to the field trial sites as needed; such as to correct any system issues that requires technician, or engineer, support that cannot be supplied over the phone or by video conference. Field maintenance should not incorporate time to prepare and ship the system into the field. All repairs should be completed in the field as approved by the Government, to minimize down time for the operational component’s time. The support is intended for this to be a service call type maintenance with appropriate personnel deploying to the test site as needed rather than being present to provide immediate support. The expectation is that maintenance personnel can be on-site within 48 hours of determining, with the Government, that field repair is needed. Per this task the Offeror should note any changes made to the Bill of Materials (including software) even when replacing like part for like part and to maintain a current record of both hardware and software in the field.

Task 4: Provide software updates and revisions. These updates and/or revisions should be provided when the system is unable to operate in the field per the capabilities that were to be developed per the contract. With such updates, both the Bill of Materials and software release notes shall be updated.

Task 5: Provide additional consumables as needed. The contract should be structured to allow order of additional consumables as needed between events. These should be available and deliverable within 1 week of being ordered by the Government.

11 | P a g e

(Optional) Phase III, Operational Deployment Optimization (Duration = 9 months):

Integration of additional sensors to provide additional capabilities for the prototype UGV.

These capabilities will be based on commercial and GFE components.

(Optional) Phase III, Stage 1 Complete the integration of the requested sensors as determined per the Government. The integration should include both software and hardware updates, any custom fabrication required. For each task the offeror can propose alternative sensors equivalent or better than the currently specified sensors noted.

Tasks;

The anticipated tasks under Phase III, Stage 1 are to integrate new sensors. These sensors should each be able to be plug and play and meet all integration requirements previously agreed to:

Task 1: (Optional): Integrate a Gas/Vapor Chemical Identification sensor that is equivalent, or better, then a custom MX 908 with appropriate attachments.

Task 2 (Optional): Integrate a Solid/Liquid Chemical Identification sensor that is equivalent, or better, then a Pendar 10x onto the manipulator arm to allow for it to be directed at specific samples providing visual guidance to properly target the material at a distance.

Task 3 (Optional): Integrate a Bio-Threat sensor that is equivalent, or better, than a

FLIR IBAC-1.

Task 4 (Optional): Integrate an observation sensor that is capable of viewing over obstacles taller than the UGV system in low profile to minimize detection while observing an area; extending the observation sensors only over the obstacle while the rest of the system remains out of sight.

(Optional) Phase III, Stage 2 This phase will support testing of the new sensor packages in an operational environment.

Tasks:

Task 1: Provide a system familiarization to the operational component team and/or test team members (up to 30 individuals) to enable them to operate the system per the systems familiarization noted under Phase I, Stage 2 deliverables.

Task 2: Provide reach back support to the operational component team and/or test team members to enable them to identify issues with the system. Reach back support will be the first step in addressing issues or malfunctions with the system in the field.

12 | P a g e

Task 3: Provide maintenance support that is deployed to the field trial sites as needed; such as to correct any system issues that requires technician, or engineer, support that cannot be supplied over the phone or by video conference. Field maintenance should not incorporate time to prepare and ship the system into the field. All repairs should be completed in the field as approved by the Government, to minimize down time for the operational component’s time. The support is intended for this to be a service call type maintenance with appropriate personnel deploying to the test site as needed rather than being present to provide immediate support. The expectation is that maintenance personnel can be on-site within 48 hours of determining, with the Government, that field repair is needed. Per this task the Offeror should note any changes made to the Bill of Materials (including software) even when replacing like part for like part and to maintain a current record of both hardware and software in the field.

Task 4: Provide software updates and revisions. These updates and/or revisions should be provided when the system is unable to operate in the field per the capabilities that were to be developed per the contract. With such updates, both the Bill of Materials and software release notes shall be updated.

• Deliverables for Phase III can be found in section 5

5. Deliverables:

Minimum Deliverables are broken out by Phase below.

Phase I Minimum Deliverables

Monthly Progress Report (MR) – Phase I

The requirement for the monthly progress report will be met by the biweekly reports specified in Stages 2 and 3 during Phase I, providing the following information as noted in each stage. In general, the biweekly report shall provide:

• Summary of the previous period activities

• Progress achieved against any inch stones and/or milestones

• Activities by task

• A summary of any technical challenges or risks and risk mitigation strategies (as needed)

• A summary of planned activities for the upcoming period

• Any additional information requested by the CWMD PM

Performance Reviews - Phase I

Performance Reviews will be held every six months after the start of stage 3. The need for a performance review will be met by an initial kick off meeting at the beginning of the project, the design review at end of Stage 1, and a test readiness meeting at the end of Stage

13 | P a g e

2. For general PR Phase I briefings will be comprehensive in nature and must include, where appropriate:

• Conceptual Overview

• Accomplishments & Highlights

• Key Challenges / Issues to Address

• Remaining Issues

• Effort for next quarter / phase / year (as appropriate) presentation slides

Detailed technical and programmatic discussion for last quarter (as long as required)

• Accomplishments: Plan vs Actual, per Task activities

• Technical issues: risks and mitigation strategy

• Plans to complete Phase

• Any additional information required by the CWMD PM.

End of Phase Performance Evaluation & Report - Phase I

The end of Phase I and Phase II will conclude with a submission of materials in lieu of the End of Phase Report. The materials provided will be part of a performance evaluation that will be the basis for determining continued funding for the follow-on phase. The End of Phase report. The materials to be submitted shall include:

• A summary of the Technical progress achieved

• A summary of the technical challenges and risks

• If follow on work is proposed, updates to the project plan, milestones, schedule, statement of work, and cost breakdown for the next phase.

• Lessons learned

• A synopsis of all reach back and field maintenance activities completed

• A final Bill of Materials (as specified above)

• Final software release notes

• Final set of Software licenses

• Draft familiarization package

• Draft operator manual

• Final design package including:

o Final drawings and design notes regarding the system, including all fabrication drawings and full detail of all software interfaces developed and used to connect the integrated subsystems.

o Software architecture layout(s) showing both software components in relation to each other as well as data flows between components.

o Drawings and details of all commercial products utilized as sensor or other major components.

• Updated Statement of Work for Phase II anticipated work.

• Additional items requested by PM

Phase II Deliverables

Monthly Progress Report (MR)

14 | P a g e

Please follow the guidance provided in sections 8.8 and 8.9 of the OBAA.

Performance Reviews

Please follow the guidance provided in sections 8.8 and 8.9 of the OBAA.

End of Phase Performance Evaluation & Report

Please follow the guidance provided above for Phase I delivery of this item.

Phase III Deliverables Please follow the guidance provided in sections 8.8 and 8.9 of the OBAA for all minimum required deliverables.

Additional Deliverables The following Deliverables for the Topic Solicitation are those additional to those defined in the OBAA per section 8.8. They are:

Phase 1 Stage 1 Deliverables:

• A preliminary design package for the complete system including:

o Drawings and preliminary hardware layouts for the ground vehicle and supporting system components to include an analysis on the anticipated capabilities of the designed UGV.

o A conceptual design for the system architecture detailing software to be developed, interfaces utilized, power management, and data transfer.

o A conceptual design for the user interface providing mockup of all GUIs to be utilized, controls provided, preliminary command trees and data flows.

o A schedule showing proposed milestones and inch stones and their anticipated completion dates.

• A list of system development risks and their possible consequences.

• A design review meeting with the Government to review the proposed system, answer Government questions on the proposed system, and receive concurrence on the design to enter stage 2.

Phase 1 Stage 2 Deliverables:

• Biweekly progress reports, two pages or less in length, providing development status including: milestones and inch stones achieved, issues that have occurred and are outstanding, issues that have occurred and been addressed.

• Videos of Offeror developmental testing, both as links to online servers and a complete set of videos provided on either a CD, portable USB drive, or memory card upon completion of stage II.

• A fully integrated prototype CBRN UGV system tested and ready for field trials including:

o The ground vehicle with all additional fixed integration hardware and software installed and tested.

o The manipulative arm with all additional fixed integration hardware and software installed and tested.

15 | P a g e o All sensors with all additional integration hardware and software installed and tested.

o All accessories required to meet the capabilities as described in the proposal and/or preliminary design.

o The handheld controller with additional hardware and/or software integrated and tested to operate the ground vehicle, manipulative arm, and attached sensors o Any additional equipment needed to operate the system in the field for up to eight hours such as base stations, extra batteries, battery chargers, etc.

o Any consumables needed to return the system to operation from minor mishaps or expected operational wear and tear. The consumables should include one version of each common tool needed to install/remove the arm and sensors or the consumables themselves. The consumables and tools should be provided in a case, or other divided packaging, allowing for easy inventory. The consumables package should also include a base inventory so that replenishment can be completed as needed.

• A Bill of Materials (Due on system delivery) including both hardware and software components including software version numbers for both developed and provisioned software.

• Software release notes (Due on system delivery) for all developed software.

• Software licenses (Due on system delivery) for all developed and provisioned software.

o All provisioned software must be provided with a license valid for 2+ years from the date of system delivery.

o All software developed for this effort should, at a minimum, have a

Government use license in perpetuity.

• Draft system familiarization package (Due on system delivery). The package shall be designed to train component personnel how to familiarize other operational component personnel with, at a minimum, how to: Operate the system; Navigate the system; Operate the manipulative arm; Attach and detach components, accessories, and sensors; Find and interpret all sensor data; Change sensor modes, components, etc. to change sensor functionality as designed. Additionally, the familiarization package should include how to replace any provided consumables in the field.

• Draft operator manual (Due on system delivery) to include written, detailed guidance and reference on operating system, using all controls, identification of all data being provided, how to change out accessories, how to change out manipulative arm, how to change out sensors. The operator manual shall cover in a clearly written format all items detailed under the familiarization package.

o The operator manual may be a hardcopy format of the familiarization package that is tabulated, incorporates a table of contents and subject index for easy reference in the field.

• Final design package (due 90 days after system acceptance) including:

o Final drawings and design notes regarding the system, including all fabrication drawings and full detail of all software interfaces developed and used to connect the integrated subsystems.

16 | P a g e o Software architecture layout(s) showing both software components in relation to each other as well as data flows between components.

o Drawings and details of all commercial products utilized as sensor or other major components.

Phase I, Stage 3 Deliverables:

• A biweekly report on all reach back and maintenance support activities that occurred.

o The report should include the date and time of a reach back support request and its resolution or escalation o The report should include the date and time of all maintenance activities, its current status, and planned, or achieved resolution o The report should note any components, including software, replaced or re-installed during this period.

o All reach back and maintenance support activities should be indexed to allow comparison between reports.

• A biweekly meeting with the Government to discuss system progress and any outstanding issues in the field.

• A final maintenance report (Due 6 weeks after end of Event 5) detailing all reach back and maintenance activities that occurred during Phase I, Stage 3 activities

• A final configuration report (Due 6 weeks after end of Event 5) detailing the final system configuration and all changes made to the system configuration (Bill of Materials) and software releases.

• System familiarization training at the times and locations agreed to with the Government to support the DHS components

• Updated software per Task 4 to be delivered either with automated installation tools or such that the Offeror provides personnel to install the software patches and updates in the field.

(Optional) Phase II, Stage 1 Deliverables:

• A preliminary design package for the updated system including:

o Drawings and preliminary hardware layouts for the ground vehicle and supporting system components including an analysis on the anticipated capabilities of the designed UGV; these should indicate changes proposed to be made to the previous system either by mark up or highlighting.

o A conceptual design for the system architecture detailing software to be developed, interfaces utilized, power management, and data transfer.; these should indicate changes proposed to be made to the previous system either by mark up or highlighting.

o A conceptual design for the user interface providing mockup of all GUIs to be utilized, controls provided, preliminary command trees and data flows;

these should indicate changes proposed to be made to the previous system by highlighting or comparison.

o A schedule showing proposed milestones and inch stones and their anticipated completion dates and estimated costs.

17 | P a g e o An accounting on the costs of the design effort including time, materials, and fees.

• A list of system development risks and their possible consequence.

• A design review meeting with the Government to review the proposed system redevelopment, answer Government questions on the proposed system redevelopment, and receive concurrence on the design to enter stage 2.

(Optional) Phase II, Stage 2 Deliverables:

• Monthly progress reports providing development status including: milestones and inch stones achieved, issues that have occurred and are outstanding, issues that have occurred and been addressed and costs incurred.

• Videos of Offeror developmental testing both as links to online servers and a complete set of videos provided on either a CD, USB drive, or memory card upon completion of stage II.

• A prototype UGV system tested and ready for field trials including:

o The ground vehicle with all additional integration hardware and software installed and tested.

o The manipulative arm with all additional integration hardware and software installed and tested.

o All sensors with all additional integration hardware and software installed and tested.

o All accessories required to meet the capabilities as described in the proposal and/or preliminary design.

o The handheld controller with additional hardware and/or software integrated and tested to operate the ground vehicle, manipulative arm, and attached sensor package(s) o Any additional equipment needed to operate the system in the field for eight hours such as base stations, extra batteries, battery chargers, etc.

o Any consumables needed to return the system to operation from minor mishaps or expected operational wear and tear. The consumables should include one version of each common tool needed to install/remove the arm and or sensor packages or the consumables themselves. The consumables and tools should be provided in a case, or other divided packaging, allowing for easy inventory. The consumables package should also include a base inventory so that replenishment can be completed as needed.

• A Bill of Materials (Due on system delivery) including both hardware and software components including software version numbers for both developed and provisioned software.

• Software release notes (Due on system delivery) for all developed software.

• Software licenses (Due on system delivery) for all developed and provisioned software.

o All provisioned software must be provided with a license good for 2+ years from the date of system delivery.

o All software developed for this effort should, at a minimum, have a

Government use license in perpetuity.

18 | P a g e

• Draft system familiarization package (Due on system delivery) The package should be designed to familiarize operational component personnel with how to: Operate the system; Navigate the system; Operate the manipulative arm; Attach and detach components, accessories, and sensors; Find and interpret all sensor data, and change sensor modes, components, etc. to change sensor functionality as designed.

Also, the familiarization package should include how to replace any provided consumables in the field.

• Draft operator manual (Due on system delivery) to include written, detailed guidance and reference on operating system, using all controls, all data being provided, how to change out accessories, how to change out manipulative arm, how to change out sensors. The operator manual shall cover all items detailed under the familiarization package in a clear written format.

o The operator manual may be a written/hardcopy format of the familiarization package that is tabulated, incorporates a table of contents and subject index for easy reference in the field.

• Final design package (due 90 days after system acceptance) including:

o Final drawings and design notes regarding the system, including all fabrication drawings and full detail of all software interfaces developed and used to connect the integrated subsystems.

o Software architecture layout(s) showing both software components in relation to each other as well as data flows between components.

o Drawings and details of all commercial products utilized as sensor or other major components.

(Optional) Phase III Deliverables:

• Integrated sensors

• UGV system and/or components updated to integrate and incorporate the prototype sensors

• Finalized design package for the updated sensors

• Monthly reports on integration progress per section 8.9 of the OBAA.

• Updated familiarization package from Phase II for the UGV, covering new sensor capabilities added.

• Updated operator manual from Phase II for the UGV, covering new sensor capabilities added.

The government requests unlimited government rights for all software and algorithms developed under this topic.

6. Number of Selections: CWMD expects to make up to one award using its FY 2020 funds.

7. Anticipated Ceiling: Although subject to appropriations and funds availability, it is anticipated that no more than $350,000 of Fiscal Year (FY) 2020 funds will be available for a resultant award for this OBAA Topic Solicitation for Phase I. For planning purposes, the overall ceiling should not exceed $750,000 over a five-year period for this award.

19 | P a g e

The Government will reserve the right to incrementally fund any resultant CLINS awarded from this OBAA Topic as provided by the FAR 52.232-22, “Limitation of Funds.”

8. Anticipated Award Type:

The Government is planning on awarding a multiple type contract to enable the best flexibility in achieving the program goals. The following CLIN structure and award type anticipated are as follows:

CLIN 0001 System Planning (Phase I, Stage 1) is anticipated to be firm fixed price CLIN 0002 System Development and Construction (Phase II, Stage 2) is anticipated to be firm fixed price CLIN 0003 Accessories and System Components is anticipated to be firm fixed price for three years CLIN 0004 Support and Maintenance is anticipated to be firm fixed price for three years.

CLIN 0005 (Phase II, Phase III) is anticipated to be cost plus fixed fee based on the labor rates quoted.

9. Anticipated Award Dates: The 2nd Quarter of Fiscal Year 2021 is when the government anticipates making a resultant award for this Topic Solicitation. However, the award date may vary based on the quality of the Proposals received and the availability of funds.

10. Pitch Papers: Pitch papers must be submitted on or before the deadline listed in the Topic Solicitation in accordance with section 5.2.1 of the OBAA. Guidelines regarding the format and content of the pitch paper and review process are provided below

10.1. Format and Content of Pitch Paper:

A pitch paper is a single electronic file in PDF format, viewable by Microsoft Windows-10 compatible machines. The individual pitch paper file size must be no more than 5 MB. Pitch papers shall not exceed two pages (standard size: 8.5” by 11”) using 1” margins and 12-point fonts or larger for text and 9-point fonts or larger for pictures, figures, tables and charts.

The pitch paper shall contain the following information in the following order:

• Cover Sheet (See attachment C in the OBAA for format, not included in two-page limit)

• A Quad Chart (See attachment 2 in this Topic Solicitation for format, included in the two-page limit)

• One page summary capturing information not included in the Quad Chart or Cover

Sheet abstract to include:

o System architecture (No more than half of a single page): Describe the proposed integrated unit system architecture covering the following key points o How system will communicate with the sensors o How system will provide sensor data to the operator o How system will provide power and control commands to the sensors

• Ground Vehicle Video Demonstration (No more than half a single page):

20 | P a g e o An illustration or picture of the platform indicate the location of the payload weight.

o Provide a URL address/link to one demonstration video of the ground vehicle completing each task listed below, or a single…