Attachment_0005_-_SAMPLE_TASKS_(10-MAR-2016).pdf

UNCLASSIFIED: Distribution Statement A. Approved For Public Release: Distribution Unlimited

RFP: W56HZV-16-R-0064

Attachment 0005 – Sample Tasks

UNCLASSIFIED

Sample Task 1: TITLE: Ground Vehicle Robotics Main Battle System (MBS)

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, technical development and integration approach, and teaming arrangements. The technical 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-881C (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 0008. 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.2, C.4.3, C.4.4, C.4.5, C.4.6, C.4.7, C.4.8, C.4.10, and C.4.15

RFP: W56HZV-16-R-0064 UNCLASSIFIED

2.2 BACKGROUND: The US Army is developing technologies for a new vehicle system. These technologies will increase transportability and performance of the targeted military ground vehicle system. The Army desires new technologies to achieve Technology Readiness Level (TRL) 6 by the end of FY21. Achieving this goal will allow these new technologies to be considered in the next major program of record. Ground Vehicle Robotics (GVR) is working to provide an open Warfighter-Machine Interface and Advanced Autonomy system enabling state-of-the-art capabilities for manned and unmanned system teaming that supports the current combat and tactical vehicle fleet at TRL 6 in FY21.

2.3 OBJECTIVE: To develop, integrate, and test technologies for Manned and Unmanned Teaming concept that will demonstrate increased capability in comparison to a traditional Main Battle Tank with 4-man crew. The Main Battle System (MBS) concept consists of one manned command and control (C2) vehicle with a 4-man crew, and two armed unmanned ground vehicle systems. The manned vehicle system will have crew stations for the driver and the commander utilizing the TARDEC Warfighter-Machine Interface (WMI), local 360 degree Situational Awareness (360SA), Degraded Visual Environment (DVE) and Indirect Vision Driving (IVD) technologies, and two additional crew stations that will be occupied by the commander of each unmanned system. The unmanned systems are fully autonomous and can drive in formation acting as the wingman for the manned system. Armed with a 105mm-120mm weapon, each unmanned system commander can utilize the onboard sensors to search for and designate enemy targets.

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. Stryker Infantry Carrier Vehicle (ICV) equipped with two advanced crew stations (driver and commander).

3. SPECIFIC TASKS:

3.1 The contractor shall develop and integrate intelligent agent software, algorithms, and technologies into each of the manned and unmanned systems to enable increased Soldier performance, proper crew workload balancing, and effective task automations.

3.2 The contractor shall develop appropriate WMI graphical user interface designs for 360 situational awareness, indirect vision driving, and control of the unmanned systems.

3.3 The contractor shall develop and integrate advanced sensors, mobility algorithms, and drive-by-wire vehicle actuation to enable fully autonomous operation and intelligent teaming behaviors of the unmanned ground vehicle systems.

3.4 The contractor shall provide appropriate personnel (technical, logistical and administrative) to ensure successful execution and completion of test events. Contractor shall be responsible for diagnosing and troubleshooting technical issues, providing briefing materials, serving as technical expert representatives for exchanges during customer interactions, and providing personnel to facilitate test activities. Test events include one Warfighter Experiment (assumed to be three weeks in duration), and two Engineering Evaluation Tests (assumed to be two weeks in duration each) whose objective is to demonstrate technology maturity. Warfighter Experiments will consist of soldiers conducting battlefield scenarios utilizing prototype vehicle(s) that demonstrate advanced technical capabilities, and may include a mixture of real and virtual friendly and enemy vehicles, to assess integral future battle command concepts.

Sample Task 2: Software Engineering Support for Real-time, Mission and Safety Critical Ground Systems Embedded Software

1. SUBMISSION REQUIREMENTS: In response to this sample task, the offeror shall 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 24-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, technical activities and considerations, quality assurance practices, Information Assurance and security considerations, teaming arrangements. The technical 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-881C (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 0008. 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.6, C.4.7, C.4.8, C.4.9, C.4.12, C.4.13, C.4.14, C.4.16, C.4.17, C.4.18, C.4.19, C.4.20, C.4.21, C.6

2.2 BACKGROUND: The TARDEC Software Engineering Center (SEC) mission includes providing software engineering support to several Army Research and Development (R&D) Programs. These R&D programs are focused on developing, maturing, demonstrating and transitioning new technologies for military applications and operating environments. Examples of these systems are: Active Protection Systems, Vehicle Electronic Architectures, 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, integration, demonstration and transition of new technologies to current and future military ground systems. Time and mission critical software functions will be enabled by smart, modular, adaptable, cyber-secure, safe, and reliable architectural designs which provide the soldier new or enhanced capabilities. Software architectures will optimize size, weight, power, cooling, and cost (SWAPC2) impacts and provide necessary vehicle functions and services that reduce soldier load and increase mission effectiveness using minimal computing resources.

2.4 PERIOD OF PERFORMANCE/PLACE OF PERFORMANCE:

2.4.1 The period of performance for this sample task shall be 24 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 TARDEC 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 a VICTORY compliant 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 VICTORY compliant software architecture.

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 MRAP All-Terrain Vehicle (M-ATV).

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

3.5 The contractor shall exhibit software development and management maturity by applying best practices as defined by the Software Engineering Institutes (SEI) Capability Maturity Model Integrated (CMMI) and IEEE/EIA 12207-2008 or equivalent.

Sample Task # 3 TITLE: VEA Mobile Demonstrator System Development and Integration

1. SUBMISSION REQUIREMENTS: In response to this sample task, the offeror shall submit 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, technical development and integration approach, information assurance considerations, and teaming arrangements. The technical 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-881C (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 0008. 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.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.13, C.4.15, C.4.17, C.4.19, C.4.20, C.4.21, C.5.2, 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.16.

2.2 BACKGROUND:

The US Army is developing technologies 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 FY19. Achieving this goal will allow these new technologies to be considered in the next major program of record. Vehicle Electronics and Architectures (VEA) is working to provide an open, vehicle data & power architecture and system implementation enabling modularity & capability enhancements at TRL 6 in FY19.

2.3 OBJECTIVE:

To provide a standards based open architecture (open, modular, scalable data system design; open, modular, scalable power system design) and vehicle integration expertise to TARDEC’s VEA to develop, integrate, test, and validate a next generation data and power system design. These designs will be integrated and tested on a Stryker Vehicle utilizing a 120kW Integrated Starter Generator (ISG) to provide MIL-PRF-GCS600A electrical power and deliver a minimum of 30kW of 28VDC MIL-STD-1275E electrical power to mission equipment in order to allow for interchangeable crew station functionality between the driver, commander, and squad leader.

2.4 PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE:

2.4.1 The period of performance for this sample task shall be assumed to be 48 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 Stryker Double V-Hull (DVH) Infantry Carrier Vehicle (ICV), non-Engineering Change Proposal (ECP) configuration

b. One Stryker C7 power pack with 120kW ISG & 35kW electric propulsion fan

3.1 The contractor shall propose an approach for developing an architecture utilizing standards (commercial, military, and other) where appropriate.

3.2 The contractor shall develop and integrate an open, modular, & scalable high voltage power system design utilizing Silicon Carbide (SiC) on a Stryker Combat Vehicle for demonstration at TRL6.

3.3 The contractor shall develop and integrate an open, modular, & scalable in-vehicle data system design which allows for interchangeable crew station functionality between the driver, commander, and squad leader on a Stryker Combat Vehicle for demonstration at TRL6.

3.4 The contractor shall develop a System Integration Laboratory to support the software/systems development for the next generation power and data system.

3.5 Two Engineering Evaluation Tests (assumed to be two weeks in duration) and one Soldier Operational Experiment (assumed to be three weeks in duration) shall be planned for this effort at Camp Grayling Joint Maneuver Training Center to test the fully integrated data and power systems on the Stryker vehicle. The contractor shall develop a test plan to conduct engineering and operational evaluations, collect subsystem performance data, and vehicle performance data; analyze the data collected. Test incident reports and test reports shall be provided for each test or experiment.

3.6 The contractor shall develop an approach to measure data throughput to support evaluation of the network system. The contractor shall develop an approach to measure electrical power system efficiencies in the evaluation of the power system.