Attachment 7 OBAA Topic Solicitation No. 8 - Statement of Work.doc

Attachment 7 Topic No.8 Solicitation 70RWMD21R00000002

DEPARTMENT OF HOMELAND SECURITY (DHS)

STATEMENT OF WORK (SOW)

FOR

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

1.0 GENERAL

1.1 Background

The Department of Homeland Security (DHS) Countering Weapons of Mass Destruction Office’s (CWMD) mission is to counter attempts by terrorists or other threat actors to carry out an attack against the United States or its interests using weapons of mass destruction. To achieve these ends, CWMD continually develops and procures weapons of mass destruction (WMD) detection equipment for deployment by DHS and assists state/local/tribal/territorial law enforcement entities, as appropriate, to strengthen detection in various domestic pathways through which global commerce travels.

The Department of Homeland Security’s CWMD Office supports DHS component offices seeks information to understand the current state of unmanned ground vehicles with Chemical, Biological, Radiological/Nuclear and Biological Threat Detection and Identification Sensor Capabilities as they relate to a set of desired characteristics detailed below.

1.2 Scope

The Department of Homeland Security (DHS) has several special mission teams that respond to disasters and other events within the United States. These teams have a strong need for unmanned vehicles that can provide situational awareness, reconnaissance, and remote sensing capabilities; dependent on the situation. 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 developed for its specific missions. The developmental prototype will allow DHS to better assess how to leverage UGVs specifically developed for its mission space.

1.3 OBJECTIVE

This Solicitation is looking to develop an unmanned ground vehicle (UGV) with integrated sensors that can detect CBRN and related materials. The UGV will be utilized by DHS special response teams among the various departments to provide situational awareness, scout unknown areas, and provide intelligence for protection of personnel in hazardous conditions. The UGV will be deployed into a variety of scenarios and situations with the need to be adaptable to the specific conditions. Many of the potential roles 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.

1.4 APPLICABLE DOCUMENTS

The following documents are referenced for basis for this statement and are necessary for the contractor to perform the contract.

Solicitation No. 70RDND19R00000003 DHS CWMD April 17, 2019

Topic Solicitation No. 8 70RWMD21R00000002 DHS CWMD November 6, 2020; all attachments.

1.4.1 COMPLIANCE DOCUMENTS

The following documents provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract:

Topic Solicitation No. 8 70RWMD21R00000002 DHS CWMD November 6, 2020

Attachment 3

Attachment 5

<Offeror please Enter OBAA solicitation number, proposal identification number, and proposal title>

2.0 SPECIFIC REQUIREMENTS/TASKS

Please reference Attachment 3: Unmanned Ground Vehicle System Desired System Description of the solicitation package for desired system description and requirements.

The Phase structure of the tasks below is a requirement for the solicitation.

<The Offeror should update the provided statement of work task structure per their proposal. The provided structure is an example based on the Government’s current plans for the program. The Government understands the diverse nature of a system development; therefore, the Offeror may propose alternative tasks within this Phase structure. Alternative tasks should be provided in a draft statement of work as part of the proposal that be reviewed and approved by the Government during the award process.> Note: Tasks below are labeled by Task Phase.Stage.Task # in the below examples.

2.1 PHASE I, STAGE 1: System Development Planning and Review (3 Weeks) Task 1.1.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 to ancillary devices, changes to the handheld control unit to provide control for integrated components.

NOTE: Tasks 1.1.2 through 1.1.6 are 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. If the task does not include an option A or option B, then the task itself can be considered optional. 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 1.1.2 1.1.2.A: Plan the integration of the Contractor proposed radiation detector; this task includes procurement of the proposed sensor.

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

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

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

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

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

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

Task 1.1.6 Plan the integration of the Contractor 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 the Deliverables Section below

2.2 PHASE I, STAGE 2: System Development (12 Weeks)

The tasks for Phase I, Stage 2 will be the implementation of tasks specified and optioned in Phase I, Stage I. Deviation from the actual plans due to unseen circumstances or the nature of developmental designs is understood and expected. 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. The expected tasks for Phase I, stage 2 are:

Task 1.2.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 1.2.2 1.2.2A: If optioned, develop the radiation sensor package to integrate into the UGV system. This task includes custom programming, fabrication, and testing as needed.

1.2.2.B: 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 1.2.3 1.2.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.

1.2.3.B: 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 1.2.4 1.2.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.

2.2.4.B: 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.

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

Task 1.2.6 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 2.2.7 Delivery of the developed prototype with all sensor packages. This prototype will be ready for field testing. The system will be delivered with all accessories needed to operate a field trial for eight hours continuously as well as meet all of the criteria as specified within the proposal. The delivery will 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 Contractor price includes the complete prototype kit as a single item. Any additional items ordered by the Government will be delivered at the dates provided upon order.

Deliverables:

· Deliverables for Phase I, Stage 2 can be found in the Deliverables Section below

2.3 PHASE I, STAGE III: Acceptance Testing and Field Trials (26 Weeks)

The Contractor will provide the following tasks during field trials per the contract tasks will either be by monthly funded contract or on an ad-hoc basis Task 1.3.1 Ad-hoc: Provide 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 familiarization training noted under Phase I, part 2. This will be at a single location for each instance.

Task 1.3.2 Monthly basis: 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. The basis assumes 20 days per month at 6 hours of reach back support via the following phone number: xxx-xxx-xxxx or email address xxxxxxxxxxx. Field maintenance will include all parts and labor to maintain the single prototype system in the field.

Task 1.3.3 Monthly basis: Provide onsite maintenance support at the field trial or evaluation site to correct any system issues that needs technician or engineer support that cannot be supplied over the phone or by video conference. Field technicians will be dispatched to conduct field repairs at one of the following locations upon Government agreement. Engineering support will be supplied via the deployed field technician. The Contractor will respond to having a technician on site within 48 hours of determining that the issue noted requires field maintenance.

Task 1.3.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 1.3.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.

Deliverables:

· Deliverables for Phase I, Stage 3 can be found in the Deliverables Section below 2.4 PHASE II, STAGE 1 (Optional): Planning of Developmental Updates to System (12 weeks)

After Phase II kick-off, the Government and vendor 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 Contractor to assist in their proposal process.

Task 2.1.1 Plan development of updates to the existing prototype UGV.

Deliverables:

· Deliverables for Phase II, Stage I can be found in the Deliverables Section below 2.5 PHASE II, STAGE 2 (Optional) –Developmental Updates to System (18 weeks)

After agreement on the second phase development design with the Government, the Contractor will develop a working prototype of the UGV, integrating all agreed to changes within the existing prototype. During this period the Contractor 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 Contractor should be recorded and transmitted to the Government. The Contractor should also develop an updated familiarization packet to be provided during stage 3 to the operational components.

Task 2.2.1 Tasks will be based on updated statement of work for Phase II based on the requested updates.

Deliverables:

· Deliverables for Phase II, Stage I can be found in the Deliverables Section below 2.6 PHASE II, STAGE 3 (Optional): Updated System Field Testing (Current estimate 26 weeks)

The Contractor will provide the following tasks during field trials per the contract tasks will either be by monthly funded contract or on an ad-hoc basis Task 2.3.1 Ad-hoc: Provide 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 familiarization training noted under Phase I, part 2. This will be at a single location for each instance.

Task 2.3.2 Monthly basis: 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. The basis assumes 20 days per month at 6 hours of reach back support via the following phone number: :xxx-xxx-xxxx or email address xxxxxxxxxxx. Field maintenance will include all parts and labor to maintain the single prototype system in the field.

Task 2.3.3 Monthly basis: Provide onsite maintenance support at the field trial or evaluation site to correct any system issues that needs technician or engineer support that cannot be supplied over the phone or by video conference. Field technicians will be dispatched to conduct field repairs at one of the following locations upon Government agreement. Engineering support will be supplied via the deployed field technician. The Contractor will respond to having a technician on site within 48 hours of determining that the issue noted requires field maintenance.

Task 2.3.4 Monthly Basis: 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 2.3.5 Ad-Hoc: 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.

2.6 PHASE III (Optional) –Operational Deployment Optimization (6 Months)

Phase III will encompass development of additional sensor package(s) and integration to provide additional capabilities for the prototype UGV. These capabilities will be based on commercial and GFE components that are currently in development and prototyping.

Task 3.1.1 (Optional) The Contractor will integrate the agreed, with the Government, Gas/Vapor Chemical Identification sensor to the prototype UGV system. The sensor may be Contractor procured or provided as GFE by the Government.

Task 3.1.2 (Optional) The Contractor will integrate the agreed, with the Government, Solid/Liquid Chemical Identification sensor to the prototype UGV system. The sensor may be Contractor procured or provided as GFE by the Government.

Task 3.1.3 (Optional) The Contractor will integrate the agreed, with the Government, Bio-Threat sensor provided as GFE, to the prototype UGV system. The sensor may be Contractor procured or provide as GFE by the Government.

Task 3.1.4 (Optional) The Contractor will integrate the agreed, with the Government, Advanced observation to the prototype UGV system. The sensor may be Contractor procured or provide as GFE by the Government.

Task 3.2.2 (Optional) Provide 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 familiarization training noted under Phase I, part 2. This will be at a single location for each instance.

Task 3.2.2 (Optional) 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. The basis assumes 20 days per month at 6 hours of reach back support via the following phone number: :xxx-xxx-xxxx or email address xxxxxxxxxxx. Field maintenance will include all parts and labor to maintain the single prototype system in the field.

Task 3.2.3 (Optional) Provide onsite maintenance support at the field trial or evaluation site to correct any system issues that needs technician or engineer support that cannot be supplied over the phone or by video conference. Field technicians will be dispatched to conduct field repairs at one of the following locations upon Government agreement. Engineering support will be supplied via the deployed field technician. The Contractor will respond to having a technician on site within 48 hours of determining that the issue noted requires field maintenance.

Task 3.2.4 (Optional) 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:

· Deliverables for Phase III can be found in the Deliverables Section below

3.0 CONTRACTOR PERSONNEL

3.1 QUALIFIED PERSONEL

The Contractor shall provide qualified personnel to perform all work specified in this SOW.

3.2 CONTINUITY OF SUPPORT

The Contractor shall ensure that the contractually required level of support for this requirement is always maintained. The Contractor shall ensure that all contract delivery schedule is maintained and that personnel are working per the schedule. If for any reason the Contractor effort levels are not, cannot, be maintained due to vacation, leave, appointments, etc., and replacement personnel will not be available, the Contractor shall provide e-mail notification to the Contracting Officer’s Representative (COR) prior to employee absence.

3.3 KEY PERSONEL

Before replacing any individual designated as Key by the Government, the Contractor shall notify the Contracting Officer no less than 15 business days in advance, submit written justification for replacement, and provide the name and qualifications of any proposed substitute(s). All proposed substitutes shall possess qualifications equal to or superior to those of the Key person being replaced, unless otherwise approved by the Contracting Officer. The Contractor shall not replace Key Contractor personnel without approval from the Contracting Officer. The following Contractor personnel are designated as Key for this requirement. Note: The Government may designate additional Contractor personnel as Key at the time of award.

· Principle Investigator/Technical Lead

3.4 PROJECT MANAGER

The Contractor shall provide a Project Manager who shall be responsible for all Contractor work performed under this SOW. The Project Manager shall be a single point of contact for the Contracting Officer and the COR. It is anticipated that the Project Manager shall be one of the senior level employees provided by the Contractor for this work effort. The name of the Project Manager, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the Project Manager, shall be provided to the Government as part of the Contractor's proposal. The Project Manager is further designated as Key by the Government. During any absence of the Project Manager, only one alternate shall have full authority to act for the Contractor on all matters relating to work performed under this contract. The Project Manager and all designated alternates shall be able to read, write, speak and understand English. Additionally, the Contractor shall not replace the Project Manager without prior approval from the Contracting Officer.

3.4.1 The Project Manager shall be available to the COR via telephone between the hours of 0800 and 1600 EST, Monday through Friday, and shall respond to a request for discussion or resolution of technical problems.

4.0 OTHER APPLICABLE CONDITIONS

Contractor shall note any applicable conditions that the Government should be aware of.

4.1 SECURITY

Contractor access to unclassified, but Security Sensitive Information may be required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination.

4.2 Period of Performance

The period of performance for this contract is a 10 month, 1 week base period with two option periods as follows:

Base Period/Phase1:

10 months, 1 week

Option Period One/Phase 2:

14 months

Option Period Two/Phase 3:

9 months

4.3 PLACE OF PERFORMANCE

The primary place of performance will be the Contractor’s facilities. During the system field trials, the Contractor will provide onsite training and support at the selected field locations within CONUS.

4.4 Travel

Contractor travel shall be required to support this requirement. All travel required by the Government outside the local commuting area(s) will not be reimbursed. All costs associated with Contractor travel shall be planned for and included in the Contractor’s Statement of Work under the appropriate CLINs that would require travel.

4.5 POST AWARD/KICK-OFF MEETING

The Contractor shall attend a Post Award/Kick-off meeting with the Contracting Officer and the COR no later than 10 business days after the date of award. The purpose of the Post Award/Kick-off meeting, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this contract and review the Contractor's draft project plan. The Post Award Conference will be held at the Government’s facility or via teleconference.

4.6 PROGRESS REPORTS AND PERFORMANCE REVIEWS

Biweekly Progress Report (BR)

The OBAA requirement for the regular 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

· Schedule status

· 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

Performance Reviews will be held every six months after the start of Phase 1 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 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 and Phase II 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:

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

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

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

4.7 PROGRESS MEETINGS

After agreement on the preliminary design with the Government in Phase 1, Stage 1, the Contractor will develop a working prototype of the UGV, integrating both the proposed manipulative arm as well as the requested sensor package(s) per the contract and preliminary design reviews. During this period, the Contractor will provide biweekly status reports to the Government and hold biweekly meetings with Government representatives. Briefing materials will be prepared for these discussions in accordance with a Government provided template. These meetings will take place at either the Government’s or Contractor’s facilities, or other location as mutually agreed to by both parties, or via teleconference.

4.8 GENERAL REPORT REQUIREMENTS

The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with DHS workstations (Windows 7 and Microsoft Office Applications).

4.9 INTELLECTUAL PROPERTY

If the Contractor’s proposal is selected for funding, the Contracting Officer will contact the apparent awardee so confirm that the apparent awardee has submitted all assertions in accordance with FAR clause 52.227‐20. The assertions must be identified, and assertion of use, release, or disclosure must be provided for the government’s review and acceptance. Contracts cannot be awarded until assertions have been approved. This section will include text capturing the approved assertions information. Assertions are to be included as part of the proposal.

4.10 PROTECTION OF INFORMATION

Contractor access to proprietary information is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the law and Government policy and regulation.

Contractor access to proprietary information is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive But Unclassified (For Official Use Only) Information. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6).

6.0 GOVERNMENT FURNISHED RESOURCES

The Government will provide the following property to the Contractor for work required under this contract:

<This list will be updated once the Government has decided on the options selected per the proposal> The Contractor shall use Government furnished property, equipment and supplies only for the performance of work under this contract and shall be responsible for returning all Government furnished facilities, property, and equipment in good working condition, subject to normal wear and tear. The Government will provide all necessary information, data and documents to the Contractor for work required under this contract.

The Government will provide copies of the references cited in SOW 1.4 at the Post Award Conference.

The Contractor shall use Government furnished information, data and documents only for the performance of work under this contract and shall be responsible for returning all Government furnished information, data and documents to the Government at the end of the performance period. The Contractor shall not release Government furnished information, data and documents to outside parties without the prior and explicit consent of the Contracting Officer.

7.0 CONTRACTOR FURNISHED PROPERTY

The Contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract, except for the Government Furnished Resources specified in SOW 2.0 and SOW 6.0.

8.0 GOVERNMENT ACCEPTANCE PERIOD

The COR will review deliverables prior to acceptance and provide the contractor with an e-mail that provides documented reasons for non-acceptance. If the deliverable is acceptable, the COR will send an e-mail to the Contractor notifying it that the deliverable has been accepted.

The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor may have an opportunity to correct the rejected deliverable and return it per delivery instructions.

The government has five (5) business days to review deliverables, request changes, clarifications, or communicate acceptance to the contractor

The contractor has five (5) business days to address changes and/or provide clarification.

Absent any comments from the government after the initial five (5) day review period, the deliverables are to be considered accepted.

9.0 DELIVERABLESA

The Contractor will consider items in BOLD as having mandatory due dates. Items in italics are deliverables or events that must be reviewed and/or approved by the COR prior to proceeding to next deliverable or event in this SOW.

All deliverables shall be sent in accordance with the table to the Contracting Officer (CO) and Contracting Officer’s Representative (COR) identified in the contract Terms & Conditions. All financial and management reports shall be sent electronically to the COR, CO, and any Contract Specialist (CS) at the addresses listed in the contract Terms & Conditions.

All physical item deliveries, such as the prototype UGV, sensors, accessories, etc. shall be checked and verified by a representative of the Program Management Office (PMO) reporting to the PM, COR and Contracting Officer on the status of the delivered items. For items requiring acceptance testing, the Government will withhold 20% of the task price/cost of the item until accepted.

9.1 Additional Details The following information is provided as additional details for deliverables provided above.

· Item 15: A fully integrated prototype CBRN UGV system tested and ready for field trials including:

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

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

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

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

· The handheld controller with additional hardware and/or software integrated and tested to operate the ground vehicle, manipulative arm, and attached sensors

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

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

· Item 16: Final design package including:

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

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

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

· Item 23: A preliminary design package for the updated system including:

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

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

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

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

· An accounting on the costs of the design effort including time, materials, and fees.

10.0 POINTS OF CONTACT

<<Insert performer’s name>> Points of Contact (POCs) are as follows:

· Technical POC(s) – <<provide name, address, e-mail, phone for Principle Investigator and Project Manager>>

· Financial POC(s) – <<provide name, address, e-mail, phone for business POC>> <<Insert performer’s name>> may change the individual designated as a POC upon notice to the COR and CO of such change.

The DHS POCs are as follows:

· Contracting Officer Jonathan Igwebeuze

Countering Weapons of Mass Destruction (CWMD) Office

U.S. Department of Homeland Security

202-447-0139 jonathan.igwebueze@hq.dhs.gov

· Contracting Officer’s Representative Marissa Giles Countering Weapons of Mass Destruction (CWMD) Office

U.S. Department of Homeland Security

202-254-7615 marissa.giles@hq.dhs.gov

· Resource Manager Cory Biram Countering Weapons of Mass Destruction (CWMD) Office

U.S. Department of Homeland Security

202-603-8990 cory.biram@hq.dhs.gov DHS CWMD may change the individual designated as a POC upon notice.