SECC2 short PWS_revised.pdf

PERFORMANCE WORK STATEMENT (PWS)

Sensored Soldier On-Soldier Systems Sensing

1.0 Mission Objective

Ground Soldier Technology Workflow, Integration, and eXperience, and GS-TWIX effort develops ground Soldier-centric information technology across the hardware, software, network, and data spectrum as well as integrates same to optimize the ground Soldier’s ability to shoot, move and communicate according to the Army Modernization Priorities.

GS-TWIX will impact multiple DEVCOM Soldier Center efforts and collaborations including Sensored Soldier, Nett Warrior, Integrated Visual Augmentation System (IVAS), Soldier Integration Facility (SIF), Joint Program Executive Office (JPEO) Chemical Biological Radiological and Nuclear Defense (CBRND), OUSD Research and Engineering (R&E) 5G Tactical Applications for Small Units in Distributed Operations

(5GTA-SUDO).

2.0 General Requirements

The GS-TWIX effort in FY22 to FY25 will focus on equipment, systems, software, network, and data flow throughout the Soldier workflow as it relates to ground Soldier systems to address optimization in warfighter functions such as lethality, maneuver, communications, logistics, and protection.

2.1 Scope

GS-TWIX specifically seeks to design, develop, and analyze solutions associated with small unit ground Soldier systems and devices as they impact Soldier sub-systems integration, Soldier workflow, and Soldier experience. Historically, Small Unit systems were electronic in nature. Currently, Small Unit systems span the mechanical, electrical, software, network, and data engineering spectrum. Furthermore, the operational space for these solutions is also diverse covering warfighter functions spanning lethality, maneuver, communications, logistics, and protection.

2.2 Place of Performance

Work shall be performed mainly at contractor facility with bi-weekly progress discussions and demonstrations over A365/MSTeams or similar VTC platform and quarterly in-person integration and demonstration events at DEVCOM Soldier Center or similar location.

2.3 Period of Performance (Approximate, based on contract award date)

Base Year with 3 Options

2.4 Recognized / Government Holidays

Work shall not be required on the following Federal holidays unless specifically identified in a Requirement.

• New Year’s Day

• Martin Luther King Jr. Birthday

• Presidents Day

• Memorial Day

• Juneteenth Day

• Independence Day

• Labor Day

• Columbus Day

• Veterans Day

• Thanksgiving Day

• Christmas

2.5 Travel / Temporary Duty

Travel charges shall be authorized in advance. Contractor travel charges shall be invoiced in accordance with the current volume of the Government Joint Travel Regulations (JTR). Contractors will not be reimbursed for travel within a 50-mile radius of their primary work location. Fee/profit on travel is not authorized and shall not be reimbursed under the terms of the resultant contract for both prime and subcontractors.

The contractor shall be required to travel in performance of this contract. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. Estimated travel as described below is required as part of contract performance.

Location # of Days # of Trips # of Persons per Trip Sensored Soldier DEVCOM Soldier Center Natick, MA 01760

4 4 per year 16 for 4 years 2

Nett Warrior Ft Belvoir, VA 4 4 per year

16 for 4 years 2

IVAS

Ft Belvoir, VA 4 4 per year

16 for 4 years 2

Location # of Days # of Trips # of Persons per Trip

SIF

Ft Belvoir, VA 4 4 per year

16 for 4 years 2

CBRND

Ft Belvoir, VA 4 4 per year

16 for 4 years 2

OUSD R&E 5GTA SUDO

Ft Bragg, NC 4 6 per year

24 for 4 years 3

OUSD R&E 5GTA SUDO

Ft Belvoir, VA 3 2 per year

8 for 4 years 3

OUSD R&E 5GTA SUDO

Ft Benning, GA 3 2 per year

8 for 4 years 3

OUSD R&E 5GTA SUDO

NTC Ft Irwin, CA 21 1 per year

4 for 4 years 3

2.6 Government - Contractor Relationships

a. The Government and the contractor understand and agree that the services to be delivered under this contract by the contractor to the Government are non-personal services and the parties recognize and agree that no employer-employee or master-servant relationships exist or will exist under the contract between the Government and the contractor and/or between the Government and the contractor's employees. It is therefore in the best interest of the Government to afford the parties a full and complete understanding of their respective obligations.

b. Contractor personnel under this contract shall not:

(1) be placed in a position where they are appointed or employed by a Federal Officer, or are under the supervision, direction, or evaluation of a Federal Officer, Military or Civilian.

(2) be placed in a staff or policy making position.

(3) be placed in a position of command, supervision, administration or control over DA Military or Civilian personnel, or personnel of other contractors, or become a part of the Government organization.

(4) be used for the purpose of avoiding manpower ceilings or other personnel rules and regulations of DA or the Civil Service Commission.

(5) be used in administration or supervision of military procurement activities.

c. Employee Relationships

(1) The services to be performed under this contract do not require the contractor or its employees to exercise personal judgment and discretion on behalf of the Government, but rather the contractor's employees will act and exercise personal judgment and discretion on behalf of the contractor.

(2) Rules, regulations, directions, and requirements which are issued by command authorities under their responsibility for good order, administration, and security are applicable to all personnel who enter any Government installation, or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control which is inconsistent with a non-personal services contract.

2.7 Identification of Contractor Employees

a. All contractor employees shall be identified as such by wearing badges at all times while performing work at Government facilities and when performing work for the Government under the scope of specific contract at other installations or non-government sites to include attendance at meetings, seminars, etc. The badges may be either affixed to clothing or be displayed from a chain or other mechanism worn around the neck. Badges must include contractor's company name and employee's name. No other items may be placed on the badge.

b. Contractor workspace shall ensure that Federal employees and the public know that they are not Federal employees.

c. Contractor employees shall initially identify themselves by name and company affiliation when answering the telephone, presenting briefings, conducting or attending meetings/seminars or any other situations where their contractor status is not obvious.

d. Official contractor correspondence (written, facsimile, and email display) shall include their company name and any other documents or reports produced by contractors are identified as contractor products or contractor participation is disclosed.

2.8 Non-Personal Services

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks under the contract. Such contractor employees shall be accountable solely to the Contractor who, in turn is responsible to the Government. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.

2.9 Inherently Governmental Functions

The Contractor shall not provide inherently governmental functions as defined in FAR

2.101 under this contract.

3.0 Specific Tasks

The contractor shall execute the Specific Task areas defined in this section.

3.1 Sensored Soldier ($1M)

3.2 Nett Warrior/GS ($3M)

3.4 Ground Soldier Systems Integration (SIF) ($1M)

3.5 CBRND Integration with Ground Soldier Systems ($2M)

3.6 OUSD 5G TAS ($8M)

3.1 Task 1: Sensored Soldier

The goal of Sensored Soldier is to enhanced Multi Domain Operations (MDO) through mission information integration. This task has three sub-tasks that shall provide an interconnected tool suite of actionable decision tools by the end of FY25. First, the Leader Planning & Decision Tools sub-task shall guide Small Unit leaders in the maneuver planning for optimal Soldier physiological, equipment electrical power, network health, and protection using remote sensing drones. Second, the Soldier Equipment Sensing and Integration sub-task Shall provide Soldier Sub-system operational usage status to Small Unit leaders and provide equipment status sensing across the Squad workflow. Lastly, the Remote Sensing and Integration sub-task shall provide hardware, software, network, and data components that provide a Small Unit with a standoff capability to sense threats, maneuver, and communicate same to Small Unit leaders This sub-task shall 1) integrate remote sensing systems and sub-systems,

2) optimize user experience of remote squad sensing components, 3) optimize remote sensing MDO across the Small Unit workflow. Sensored Soldier tasks will transition to Nett Warrior, IVAS, or other Ground Soldier Systems Program of Record (PoR)

3.2 Task 2: Nett Warrior and Ground Soldier System

The contractor shall provide comprehensive and wide-ranging support to the PdM GSS for evolving, maturing, and maintaining NW V3.X system in the areas of software engineering, system engineering, cybersecurity, system architecture, and integration.

The Contractor, in conjunction with the PdM GSS NW SETA contractor, shall ensure the work has a migration path to the NW program record and/or NW Future Initiatives, if the capability needs time to mature. If the Contractor and PdM GSS NW SETA contractor have divergent views on how to ensure a successful transition to the NW program of record of these requirements or how work is divided between both parties, then the Contractor shall promptly notify PdM GSS (GSS Tech Director / NW Chief Engineer) so any required Government clarification / direction can be provided to both parties. The Contractor shall develop solutions that allows application developers to store and distribute information in their own data format. However, the contractor shall leverage server services already provided by the larger TAK ecosystem rather than developing their own server system.

3.3 Task 3: Ground Soldier Systems Integration

The contractor shall provide technical services for CCDC SC, IVAS, and other government agencies in areas of advanced concepts for information portrayal, sub-system integration, and data analytics: Similar to the IVAS-Soldier Integration Facility (SIF), CCDC SC Mission Information Team requires the development of information portrayal system that interacts with project objectives, project tasks, and both lab and field experimentation operations that includes Nett Warrior-based Soldier worn sensors, ATAK-platoon based sensors, and NW & ATAK web based sensors.

3.4 Task 4: CBRND Integration with Ground Soldier Systems:

The Joint Program Executive Office for Chemical, Biological, Radiological, and Nuclear Defense (JPEO-CBRND) seeks to design, prototype, test, and document promising wearable capabilities integrated into a single system. The wearables system includes the following components: assistive automation capabilities; wearable, subcutaneous, and implantable devices; cyber secure and scalable wired and wireless architectures;

and visualization and decision support tools. The contractor shall provide sub-systems that advance the human integration and current technology for lightweight, integrated wearable systems; Soldier integrated displays and body-worn systems that enhance the Soldier survivability, and situational awareness on the battlefield. Special interest areas include unique human systems integration of data and power systems, miniaturization, increased durability and reliability, and components having low power as well as new power solutions that meet Soldier-portable system requirements for survivability and situational understanding. Specific examples of body- worn system capabilities include:

data devices, integrated electronic modules, inter- connections in fabrics, wearable battery technologies, combat identification, tactical engagement simulation capability, system voice control, State-of-the-Art unique interfaces, haptics, neuro-physiological, and physiological/medical sensors and data management, Soldier integration of individual/team weapon system sensors and controls.

3.5 TASK 5: 5G Tactical Applications for Small Units in Distributed Operations

(5GTA-SUDO)

The goal of 5GTA-SUDO is to demonstrate the operational impact of a 5G bandwidth improvement to the Integrated Tactical Network (ITN). This task shall develop and demonstrate in an operationally relevant environment, at the Battalion & Company echelon level, multiple ground Soldier tactical applications. Tactical applications shall include 96 hour out load, sensitive site exploitation, sensor to shooter Full Motion Video (FMV) applications, edge device management, ITN multi-network/Primary, Alternative, Contingency, and Emergency (PACE)) router, image product distribution, robotic systems integration and other 5G-based applications. All applications shall be integrated with the software code base and hardware system for either Nett Warrior or

IVAS.

4.0 Special Requirements

This section describes the special requirements for this effort. The following sub-sections provide details of various considerations on this effort.

4.1 Safety/OSHA Requirements

The contractor shall be in compliance with applicable state and federal safety standards. Special safety requirements will be identified in the individual tasks, when required. Contractor must ensure that they are in compliance with all applicable OSHA standards.

4.2 Contractor Furnished Items and Responsibilities

The Contractor shall furnish all personnel, facilities, equipment and supplies unless otherwise provided by the Government. Contractor shall propose resources to address requirements for this contract.

4.3 Government Furnished Property and Services

GFI: The government will provide access to ATAK software, ATAK application program interfaces (API) and other software integration documentation.

4.4 Quality Assurance Surveillance Plan (QASP)

The Government shall monitor the Contractors performance under this contract accordance with the Governments QASP.

4.5 Performance Requirement Summary (PRS)

Government will ensure that contract performance conforms to specified requirements by including a Performance Requirements Summary (PRS) in this contract that outlines the basis upon which the performance requirements will be measured.

5.0 Document Reporting Requirements and Deliverables

5.1. Report Covers

The cover of each document produced by the contractor must contain, as a minimum, the information listed below:

a) Contractor name and business address

b) Contract Number

c) Date of report

d) Period covered by report

5.2 Contents of Monthly Reports

The content of each monthly report produced by the contractor must contain, as a minimum, the information listed below:

a) Budget table that tracks monthly dollars billed, cumulative dollars billed, dollars remaining, and percentage of total dollars remaining for each GFEBS funding source.

b) Man-hours expended by discipline for the reporting period, and cumulatively during the contract, as well as the number of employees who performed on the contract during the reporting period, noting if any of the performers are new employees.

c) Description of progress made during period reported, including problem areas encountered, and recommendations, if any for subsequent solution beyond the scope of this contract

d) Trips and significant results

5.3 Deliverables

CDRL # Deliverable Title PWS

Reference Due

A001 Monthly Status Report A002 Technical Report A003 Reports A004 Source Code A005 Final Report

Application Software with Unlimited Government Rights (Source code and executable code).

Technical data with Unlimited Government Rights (architecture documentation, block diagrams, and user guide).

PM IVAS Transition plan documentation.

6.0 Points of Contact

Contracting Officer’s Representative (COR)

Steve Lui

FCDD-SCD-ESM

DEVCOM Soldier Center – Mission Information Team steven.j.lui.civ@army.mil

7.0 Applicable Documents

a. The following documents form a part of the PWS.

MIL-HDBK-4704 Designing and Developing Maintainable Products and Systems

8.0 Security

8.1. Classified access is required for performance of the contract.

9.0 Operational Security (OPSEC)

Security Clearance and Storage

The Contractor shall be required to receive and generate classified material and store classified hardware at its facility. The Contractor is authorized to use the Defense Technical Information Center (DTIC). The Contractor is required to obtain COMSEC and Defense Courier Service (DCS) accounts. This contract has OPSEC requirements in addition to requirements of the NISPOM. Classified Automated Information System (AIS) processing at the SECRET level shall be required at the Contractor facility. These classified systems will be stand-alone systems and shall be accredited IAW the NISPOM prior to the start of processing. All Contractors under this contract shall have at least an Interim Secret clearance prior to the start date of the efforts associated with PWS.

Facility Clearance.

The Contractor shall establish a Top Secret (TS) facility clearance with SECRET safeguarding requirements. The Contractor may require access to COMSEC information, Non-Sensitive Compartmented Information (SCI), NATO information, Foreign Government Information, and For Official Use Only (FOUO) information.