Attachment 0006 Sample Tasks.pdf

UNCLASSIFIED

UNCLASSIFIED

RFP: W56HZV-22-R-0003

Attachment 0006 – Sample Tasks

Sample Task 1: TITLE: Ground Vehicle Robotics

1. SUBMISSION REQUIREMENTS: In response to this sample task, the offeror shall submit all of the following:

1.1 Technical Narrative: The offeror shall provide a detailed technical approach to execute the sample tasks below within the 48-month period of performance. The offeror shall describe its methodologies used to analyze the tasks and its rationale supporting the chosen approach to demonstrate its understanding of the project requirements. The narrative shall discuss project management planning, risk identification and management, and a potential technical solution approach and integration approach, and teaming approach with suppliers and stakeholders to satisfy the tasks identified in section 3. The technical solution approach narrative is limited to 20 pages, not including the title page and index/table of contents as required per Section L paragraph 3(a) and 3(b). Offerors are cautioned that the Government will not review any pages beyond the 20 pages.

1.2 Work Breakdown Structure (WBS): The offeror shall provide a WBS at Level 3 for the sample task as described below. The WBS shall be provided in accordance with DOD MIL-STD-881E (Work Breakdown Structures for Defense Material Items).

1.2.1 Basis of Estimate (BOE): The BOE shall apply labor categories and hours to the WBS work elements required to complete the sample task requirements as proposed.

The offeror shall use the labor categories as defined in Attachment 0002. The BOE shall not include any rates or cost information. The offeror shall provide its rationale for the number of hours for each proposed labor category in the BOE. The rationale shall provide sufficient information for the Government to understand how the labor hours were developed. The number of hours estimated for the sample task BOE will not be evaluated for cost. Offerors are not limited to the number of hours defined per each labor category as stated in Attachment 0008 and may estimate more or less hours in any one category as necessary to execute the proposed approach. Attachment 0008 hours are defined to ensure proper and consistent composition of the composite labor rate across offerors. ENSURE YOUR BOE CORRESPONDS AND TRACES BACK TO YOUR PROPOSED TECHNICAL APPROACH. The WBS including BOE is limited to 20 pages.

1.3 Project Work Schedule: The offeror shall provide a detailed project work schedule in MS Project 2010 detailing the tasks and schedule for executing the requirements below. The project work schedule is limited to 6 pages.

2. DESCRIPTION OF EFFORT:

2.1 REFERENCE: C.4.1, C.4.2, C.4.3, C.4.4, C.4.5, C.4.6, C.4.7, C.4.8, C.4.10, C.4.13, and C.4.15

UNCLASSIFIED

2.2 BACKGROUND: The US Army is developing technologies for robotic and autonomous ground vehicle systems as well as test and evaluation procedures. These technologies will be teamed with Army formations and support all combat warfighting functions, such as close combat, reconnaissance, targeting and acquisition. The Army desires new technologies to achieve Technology Readiness Level (TRL) 6 by the end of FY28. Achieving this goal will allow these new technologies to be considered in the next major program of record. Core to achieving this goal is the integration of new technologies with amenable data rights for third party upgrade and advancement into existing Government owned products.

2.3 OBJECTIVE: To develop and integrate technologies to enable autonomous ground system capabilities to assimilate with Army formations and support all combat warfighting functions (close combat, reconnaissance, targeting and acquisition), develop Manned/Unmanned Teaming (MUM-T) Behaviors using the Soldier-in-the-loop, develop the Soldier Machine Interfaces to intuitively interact and control robotic systems, and develop the methods and protocols to operate and assess these systems safely.

2.4 PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE:

2.4.1 The period of performance for this sample task shall be 48 months from the date of award.

2.4.2 The primary place of performance for this sample task shall be the contractor’s facility.

2.5 GOVERNMENT FURNISHED EQUIPMENT:

2.5.1 It shall be assumed that the Government will provide the following items for the execution of this sample task and all Government Furnished Equipment (GFE) shall be returned to the Government at the end of the task:

a. All tactical military platforms inherent to integration

b. All specific platforms and sensors.

C. All common use developed software already integrated to the specific platforms required for general operation of the systems.

3. SPECIFIC TASKS:

3.1 Improve human-robot interactions by introducing technology which improves the effectiveness of the robot as a tool for the human to complete the mission. Improve the manner for which the operator is able to maintain situational awareness in a cluttered environment, manage interruptions based on user attention or current task, and communicate system reasoning to improve trust between the user and robot in various

UNCLASSIFIED

environments.

3.2 Add and detect context during a mission to dictate aggressiveness of motion controls while maintaining safety constraints for man in the loop as well as determining safety of operation for multiple systems containing combinations of manned and unmanned systems in simultaneous operations within the battlespace.

3.3 Design, Develop, Deliver, and evaluate Robotic behaviors such as overwatch (positioning to provide cover for another asset), shield (placing the UGV between the warfighter and a threat), and push/block (offensive maneuver to block an opponent threat using direct contact or path interference from the UGV).

UNCLASSIFIED

Sample Task 2: Software Engineering Support for Real-time, Mission and Safety Critical Ground Systems Embedded Software submit all of the following:

1.1 Technical Approach Narrative: The offeror shall provide a detailed technical approach to execute the sample tasks below within the 48-month period of performance. The offeror shall describe its methodologies used to analyze the tasks and its rationale supporting the chosen approach to demonstrate its understanding of the project requirements. The narrative shall discuss project management planning, risk identification and management, and a potential technical solution approach and integration approach, and teaming approach with suppliers and stakeholders to satisfy the tasks identified in section 3. The technical solution approach narrative is limited to 20 pages, not including the title page and index/table of contents as required per Section L paragraph 3(a) and 3(b). Offerors are cautioned that the Government will not review any pages beyond the 20 pages.

1.2 Work Breakdown Structure (WBS): The offeror shall provide a WBS at Level 3 for the sample task as described below. The WBS shall be provided in accordance with DOD MIL-STD-881E (Work Breakdown Structures for Defense Material Items).

1.2.1 Basis of Estimate (BOE): The BOE shall apply labor categories and hours to the WBS work elements required to complete the sample task requirements as proposed.

The offeror shall use the labor categories as defined in Attachment 0002. The BOE shall not include any rates or cost information. The offeror shall provide its rationale for the number of hours for each proposed labor category in the BOE. The rationale shall provide sufficient information for the Government to understand how the labor hours were developed. The number of hours estimated for the sample task BOE will not be evaluated for cost. Offerors are not limited to the number of hours defined per each labor category as stated in Attachment 0008 and may estimate more or less hours in any one category as necessary to execute the proposed approach. Attachment 0008 hours are defined to ensure proper and consistent composition of the composite labor rate across offerors. ENSURE YOUR BOE CORRESPONDS AND TRACES BACK TO YOUR PROPOSED TECHNICAL APPROACH. The WBS including BOE is limited to 20 pages.

1.3 Project Work Schedule: The offeror shall provide a detailed project work schedule in MS Project 2010 detailing the tasks and schedule for executing the requirements below.

The project work schedule is limited to 6 pages.

2.1 REFERENCE: C.3.3, C.3.4, C.3.8, C.4.1, C.4.6, C.4.7, C.4.8, C.4.9, C.4.12, C.4.13, C.4.14, C.4.16, C.4.18, C.4.20, C.6.2, C.6.3, C.6.4, C.6.5, C.6.6, C.6.7, C.6.8, C.6.12, C.6.13, C.6.14, C.6.15, and C.6.17

UNCLASSIFIED

2.2 BACKGROUND: The Ground Vehicle Systems Center (GVSC) Software Engineering Center (SEC) mission includes providing software engineering support for combat and tactical platforms throughout the lifecycle of the platforms. These activities focused on developing, testing, integrating, validating and sustaining military applications, systems and operating environments. Examples of these systems are:

Active Protection Systems, Embedded Systems, Vehicle Electronic Architectures, Manned and unmanned Robotic Systems, Human/Machine Interfaces, and Electronic Control Systems. To this end the SEC must apply mature life cycle software engineering processes and tools to provide services to support these programs. The SEC maintains and runs facilities to perform software development and defect correction for ground vehicle systems, and in addition supports ground vehicle weapon system PEOs and PMs in identifying additional support capability requirements.

2.3 OBJECTIVE: To develop the software engineering support capability to be utilized for the development, testing, integration, and validation of new technologies to current and future military ground systems.

2.4 PERIOD OF PERFORMANCE/PLACE OF PERFORMANCE:

2.4.1 The period of performance for this sample task shall be 48 months from the date of award.

2.4.2 The primary place of performance for this sample task shall be the Government’s facility at Ground Vehicle Systems Center in Warren, MI.

2.5 GOVERNMENT FURNISHED EQUIPMENT:

2.5.1 It shall be assumed that the Government will provide the following items for the

a. All Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) Capability Set components to be integrated using the software architecture including radios, internet controllers, WIN-T, Tactical Radios, FBCB2, Blue Force Tracking, displays, computing hardware and sensors.

3.1 The contractor shall develop an open-systems, modular, adaptable, agile, maintainable standard software architecture applicable for military ground vehicles that provide the ease of integration of current and future electronics subsystems and minimize changes required to port to other military ground systems.

3.2 The contractor shall develop Application Programmer's Interfaces (APIs) and implement standard sets of services for the compliant software architecture.

UNCLASSIFIED

3.3 The contractor shall integrate Government-furnished Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) components using the software architecture, API, and services developed above into a Bradley A3.

3.4 The contractor shall support the development, integration, test and sustainment of software products managed by the SEC. Support elements include:

a. Infrastructure and Laboratory

b. Cyber Security Engineering and Assurance

c. Product/Process Quality Assurance

d. Defect Containment

e. Process Engineering and Control

f. Configuration Management

g. Product Transition Planning

h. Product Support – Documentation, Replication, Distribution, Installation, and Training

i. Data/Knowledge Management

UNCLASSIFIED

Sample Task #3 TITLE: Enhanced Vetronics Architecture Development submit the following:

1.1 Technical Narrative: The offeror shall provide a detailed technical approach to execute the sample tasks below within the 72-month period of performance. The offeror shall describe its methodologies used to analyze the tasks and its rationale supporting the chosen approach to demonstrate its understanding of the project requirements. The narrative shall discuss project management planning, risk identification and management, and a potential technical solution approach and integration approach, and teaming approach with suppliers and stakeholders to satisfy the tasks identified in section 3. The technical solution approach narrative is limited to 20 pages, not including the title page and index/table of contents as required per Section L paragraph 3(a) and 3(b). Offerors are cautioned that the Government will not review any pages beyond the 20 pages.

1.2 Work Breakdown Structure (WBS): The offeror shall provide a WBS at Level 3 for the sample task as described below. The WBS shall be provided in accordance with DOD MIL-STD-881E (Work Breakdown Structures for Defense Material Items).

1.2.1 Basis of Estimate (BOE): The BOE shall apply labor categories and hours to the WBS work elements required to complete the sample task requirements as proposed.

The offeror shall use the labor categories as defined in Attachment 0002. The BOE shall not include any rates or cost information. The offeror shall provide its rationale for the number of hours for each proposed labor category in the BOE. The rationale shall provide sufficient information for the Government to understand how the labor hours were developed. The number of hours estimated for the sample task BOE will not be evaluated for cost. Offerors are not limited to the number of hours defined per each labor category as stated in Attachment 0008 and may estimate more or less hours in any one category as necessary to execute the proposed approach. Attachment 0008 hours are defined to ensure proper and consistent labor rates across offerors. ENSURE

YOUR BOE CORRESPONDS AND TRACES BACK TO YOUR PROPOSED

TECHNICAL APPROACH. The WBS including BOE is limited to 20 pages.

1.3 Project Work Schedule: The offeror shall provide a detailed project work schedule in MS Project 2016 detailing the tasks and schedule for executing the requirements below.

The project work schedule is limited to 6 pages.

2.1 REFERENCE: C.3.3, C.3.4, C.3.5, C.4.1, C.4.2, C.4.3, C.4.4, C.4.5, C.4.6, C.4.7, C.4.8, C.4.10, C.4.12, C.4.13, C.4.15, C.4.16, C.4.17, C.5.1, C.5.2, C.5.3, C.6.2, C.6.3, C.6.4, C.6.5, C.6.6, C.6.7, C.6.8, C.6.16, C.6.17.

2.2 BACKGROUND: The US Army is developing technologies to demonstrate a common military standard open architecture for ground combat vehicles to manage data, video, UNCLASSIFIED and power systems to enable future combat vehicle capabilities such as advanced protection, optionally-manned control, electrification capabilities, target recognition, 3rd Gen FLIR, lethality and in-vehicle networked systems for its next new vehicle or modernization program. These technologies will reduce weight in addition to increasing performance of the targeted military ground vehicle. The Army desires new technologies to achieve Technology Readiness Level (TRL) 6 by the end of FY29. Achieving this goal will allow these new technologies to be considered in the next major program of record.

2.3 OBJECTIVE: To provide a Modular Open System Approach (MOSA) architecture (data and power system design) and vehicle integration expertise to Ground Vehicle System Center (GVSC) to develop, integrate, test, and validate a next generation data and power system design. These designs will be integrated and tested on a Paladin M109A7 utilizing a 72kW Integrated Starter Generator (ISG) to provide MIL-PRF- GCS600A electrical power and deliver a minimum of 20kW of 28VDC MIL-STD-1275F electrical power to mission equipment in order to achieve the following capabilities:

Platform to platform communication, driving under armor with video, ability to show situational awareness data from multiple vehicles, slew to cue of weapons and sensors, interchangeable crew station functionality between the driver, commander, and gunner, Time Sensitive Networking (TSN) ethernet communications, electrical power management, and secure software download capability.

2.4 PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE:

2.4.1 The period of performance for this sample task shall be assumed to be 72 months from the date of award.

2.4.2 The primary place of performance for this sample task shall be assumed to be at the contractor’s facility.

2.5 GOVERNMENT FURNISHED EQUIPMENT:

2.5.1 It shall be assumed that the Government will provide the following items for the

a. One M109A7 Paladin Self-Propelled Howitzer platform

b. One 210kW High Voltage Power Controller & 20kW unidirectional DC/DC converter

3.1 The contractor shall develop an architecture identifying what standards (commercial, military, and other) it considered and which are actually used.

3.2 The contractor shall develop and integrate an open, modular, & scalable high voltage power system design utilizing Silicon Carbide (SiC) on a M109A7 Self Propelled Howitzer for demonstration at TRL6 as defined by the Defense Acquisition Guidebook

UNCLASSIFIED

3.3 The contractor shall develop and integrate a MOSA compliant in-vehicle data system design which implements the capabilities referenced in section 2.3 of this sample task on a M109A7 Self Propelled Howitzer for demonstration at TRL6.

3.4 The contractor shall develop and set up a deliverable System Integration Laboratory (SIL) at the contractor facility to support the software/systems development for the next generation power and data system. The SIL must be capable of being delivered to the USG at the end of the period of performance.

3.5 Two Engineering Evaluation Tests (assumed to be two weeks in duration) and one Soldier Operational Experiment (assumed to be four weeks in duration) shall be planned for this effort at Camp Grayling Joint Maneuver Training Center to test whether the fully integrated data and power systems on the M109A7 Self Propelled Howitzer can demonstrate the capabilities described in Section 3.2 and 3.3. The contractor shall develop and execute a test plan to conduct engineering and operational evaluations, collect subsystem performance data and vehicle performance data, and analyze the data collected to deliver a final assessment report. Test incident reports and test reports shall be provided for each test or experiment.

3.6 The contractor shall measure data throughput to support evaluation of the network systems. The contractor shall measure electrical power system efficiencies in the evaluation of the power system. The contractor shall conduct these measurements during the testing and operational experiment events in Section 3.5.