Future Combat Systems FCS Home Boeing Home Integrated Defense Systems FCS Home Boeing Home SAIC Phantom Works home

16 Ton Class Manned Ground Vehicle

BIA Number: 15000

Pricing Information
The LSI anticipates a funding level of approximately $775,000 for each contract award(s) resulting from this BIA.

Detailed Description of Effort and Task
The Future Combat System (FCS) manned ground vehicle plan is for a family of approximately fifteen different combat vehicles based on a common platform that is compatible with transporting and fielding in a combat ready configuration on a C-130 military air transport without a transportation waiver restriction (except the NLOS, BLOS, and mortar vehicle which are expected to exceed the nominal 16 short ton weight). This limits the combat ready weight of each vehicle. Each vehicle is distinct when equipped and assembled with a unique mission module system consisting of a combination of carrier and/or ordnance systems. All components will be based on an open system architecture and facilitate block upgrades spiral development throughout the life of the vehicle.

This Statement of Work (SOW) is applicable for system level integration of the 16 ton class FCS manned ground vehicles in Table I. We are requesting proposals for the period of performance October 7 through December 20, 2002, for the integrated vehicle design refinement to a level to support an early PDR in SDD, the subsystem design interface work required to integrate these vehicles, and the associated system level specification development support for developing the specifications.

The integrator is responsible for integrating both the common subsystems and the unique mission subsystems that is required for each of the vehicles defined in Table I. The integrator will provide support in the development of the vehicle level specifications by the LSI. The integrator will be responsible for the subsystem specifications, common and unique. The vehicle integrator will provide draft/legacy subsystem specifications for review. Potential common subsystems reside in the following areas; chassis-hull, mobility system, ECS/TMS/NBC systems, survivability systems, vetronics, warfighter machine interface, AutoNav, communication system, and the sensors.

Key factors to be considered for integrating each vehicle system include C-130 deployability and weight control, reliability, maintainability, and supportability. Design features that reduce logistics footprint and improve operability will also improve cost benefit.

Weight is a critical design attribute that will make the vehicles capable components of the FCS system of systems architecture. We are interested in a description of the weight allocation, tracking, and mitigation plan for meeting the weight requirement for each concept. We are interested in any weight reductions that have been introduced, applied, or can be applied to meet performance and weight goals.

Low Life-Cycle-Cost is important to making FCS successful. That makes maintainability, supportability and reliability attributes also vital points of interest to us. Extended operation without re-supply, cross platform part commonality, and reduced logistics footprint are additional points of interest. Please provide a description of your plan to exceed legacy attributes and characteristics at the major system/subsystem level in these areas with cost savings in mind.

TABLE I - Unique Vehicle Mission Module Subsystems and Attributes
 
Vehicle System
Attributes and Technology
T1 LOS/BLOS Vehicle Combat vehicle with 105-120mm cannon with LOS/BLOS capability. Also included is a Self Protection Weapon.
T2 NLOS Cannon Vehicle Combat vehicle with 120-155mm cannon with NLOS capability. This system incorporates technologies that include CARGO rounds and smart submunitions, and Fire and Forget Seeker technology. Also included is a Self Protection Weapon.
T3 NLOS Mortar Vehicle Combat vehicle with 120mm mortar gun with NLOS capability. Also included is a Self Protection Weapon.
T4 Missiles Vehicle Combat vehicle carries missiles-in-a-box configuration that minimizes reloading time and effort. The Missile system provides BLOS precision guided missiles and loitering munitions. Also included is a Self Protection Weapon.
T5 Armored Personnel Carrier Transports a full 9-man infantry squad including their associated gear and 2 soldier crew. Also included is a Self Protection Weapon.
T6 Control Vehicle (CV) Provides 4 soldier workstation, 1 driver and 1 commander. Used for control of UGV's andUAV's. Also included is a Self Protection Weapon.
T7 Command and Control (C2) Vehicle Provides 4 soldier workstation, 1 driver and 1 commander. Provides the connection among the Force and communication on the move. Also included is a Self Protection Weapon.
T8 Re-supply Vehicle General-purpose vehicle with embedded semi-autonomy provides operation as a follower. Crew size consists of 1 driver and 1 commander. Also included is a Self Protection Weapon.
T9 Reconnaissance, Surveillance, and Target Acquisition (RSTA) Vehicle Integrates RSTA suite of 5-meter mast, thermal imagers (LWIR and MWIR), day/night TV camera, 10 km+ laser range finder, Ka band radar, and 360 deg. all elevation azimuth. Provides 2 soldier workstation, 1 driver and 1 commander. Also included is a Self Protection Weapon.
T10 155 mm Re-supply Vehicle Provides automated re-supply to the 155-mm NLOS vehicle; re-supplied with palletized ammunition: Crew size consists of 1 driver and 1 commander. Also included is a Self Protection Weapon.
T11 Recovery Vehicle Provides towing and recovery assistance. Crew size consists of 1 driver and 1 commander. Also included is a Self Protection Weapon.
T12 Medical Vehicle Vehicle provides evacuation and/or medical treatment. Provides 1 injured station, 1 driver and 1 commander.
T13 Bridge Vehicle Equipped to lay bridge.
T14 Mobility/Countermobility Vehicle Equipped to breach and lay minefields, can be operated semi-autonomously; mission package includes a scraper, flail, and Mongoose. Vehicle has semi-autonomous capability. Also included is a Self Protection Weapon.
T15 SUAV Launcher Carrier Vehicle Transports a pod of 32 SUAV's and the launching system. Crew size consists of 1 driver and 1 commander.

Task 1
Coordinate the major system level requirements and define major Interface Control Documents (ICD) with LSI. A Platform architecture shall be developed for each variant that defines the internal relationships among subsystem components as well as the relationships between to the C4ISR architecture. Initial system requirements, architecture and assumptions will be provided at the start of the contract. On going trade studies and refinement of the Operational Requirements Document (ORD) may require updates to initial requirements and/or vehicle systems defined in Table I.

Task 2
Refine the concept design from the Concept Technology Development (CTD) phase 1 to a level that will support an early PDR (to be announced later) during the SDD phase. This may include some refinement of existing completed trade study work from phase 1 CTD. Define vehicle-to-subsystem-to-subsystem interfaces to a level to demonstrate major transport element routing.

Provide top-level description of the major vehicle subsystems. Descriptions shall include schematics/block diagrams, top-level performance characteristics, growth potential to support spiral upgrades, weight, RAM-D, cost, etc.

Provide rationale used to arrive at system/subsystem design requirements.

Provide assessments or compliance with these requirements and architecture definitions provided by the LSI.

Task 3
Provide 3D CAD Envelope Models and 2D Layouts of the system general arrangement locating the major system elements sufficient to define subsystem-to-vehicle interfaces. The choice is for 3D CAD Envelope Model datasets to be either PRO/Engineer version 2001 or CATIA V4. If not available in either of these CAD formats a STEP format file shall submitted. 2D layouts to be contractor CAD dataset format and one 36" wide paper plot. Provide simulation model of system performance to support vehicle performance simulation assessments.

  • EASY5 or MATLAB/Simulink for system level analyses
  • DADS or equivalent at a minimum COTS software for multi-body dynamic analysis (DADS is preferred).

Task 4
Provide subsystem commonality plan that maximizes commonality across all vehicle systems. Plan shall include at a minimum: proposed common subsystem(s) for each vehicle system listed in Table I. Also, for each vehicle in Table I, provide the following for each common subsystem: (1) ROM vehicle non-recurring and recurring cost delta (+/-$), (2) ROM vehicle weight delta (+/-lbs) and (3) any other potential pro/cons (i.e. maintenance, survivability, mobility, etc.). Provide functional schematics depicting the integration of common subsystems and mission unique subsystems for each vehicle system in Table I. Provide ROM vehicle subsystem requirements for: heating /cooling, power (electrical, hydraulic, pneumatic), and durability and reliability predictions.

Task 5
Support the development and creation of vehicle-to-C4ISR, vehicle-to-supportability, and vehicle-to-training ICDs..

Task 6
Provide preliminary SDD program plan, based on LSI provided key milestones, to include at a minimum: preliminary system element development/verification plan (i.e., describe a top-level plan for vehicle testing that would correlate predictions of subsystem, and a fully integrated vehicle), preliminary system manufacturing plan, long lead items list, program critical path, preliminary subsystem/vehicle system level test plan, plan to get to early PDR, and program risk issues. Submit a candidate Work Breakdown Structure (WBS) for SDD. This WBS shall also delineate common versus system unique hardware and software components.

Provide system/subsystem element analyses/data to support LSI/Govt risk assessment analyses necessary to ensure that FCS embodies acceptable affordable risk going into SDD.

Task 7
The integrator will provide support in the development of the vehicle level specifications by the LSI for each of the vehicles in table 1. The integrator will provide draft (legacy acceptable if applicable to FCS) subsystem specifications, common and unique for each of the vehicles.

Task 8
Define armored chassis hull design definition capable of meeting or exceeding the structural, ballistic, mine blast, & external attachment performance and ICD requirements provided by the LSI within the platform weight and dimensional requirements. Advanced lightweight performance and synergistic solutions are encouraged. Support refinement to the subsystem performance and interface requirements. Provide system attribute sensitivity (i.e., weight, volume, threat capability, structural capability) to potential growth in performance requirements as specified by the LSI. Provide structural concepts for attachment of additional external armor of other external items. The chassis hull is not limited to a monocoque design.

Task 9
Provide a fabrication concept that addresses building and assembling the chassis hull components to performance requirements provided by the LSI and in sufficient detail to support manufacturing plan development, including tooling concepts, materials selections, quality assurance procedures, and processing technologies. Provide structural concepts for attachment of additional external armor of other external items. Provide preliminary repair/maintenance concepts associated with structure/armor design.

Task 10
Provide open architecture mobility subsystem hardware/software design definition that supports block upgrades spiral development. The mobility subsystem comprises the engine, energy storage, drive train, steering, suspension, running gear and associated control and power electronics. Design definition shall include functional schematics, simulation models, and system metrics (weight, power, cooling, volume, RAM-D, etc.)

Task 11
Develop a Vetronics system architecture for each variant which maximizes commonality across the variant family of vehicles and defines the internal relationships among Vetronics components as well as the relationships between the Vetronics and the rest of the system and the C4ISR architecture.

Meeting Support
Weekly telecons to review schedule status, accomplishments, significant findings/conclusions/recommendations, integration issues, etc.
Telecons to start 1 wk after contract award and continue each week till contract end. (Note: Not required the week of Initial and Final Coordination Meeting)
Initial Spec/ICD Development & Coordination Meeting - 11/19/02-11/20/02
Final Spec/ICD Development & Coordination Meeting - 12/18/02-12/19/02

Schedule Milestones
Subcontract Start Date - 10/7/02
Subcontract Completion Date - 12/20/02

Deliverables/ Data Requirements
(Note: Deliverables/Data to be provided in contractor format.)
Delivery Date (On dock at LSI)
  1. Issues/concerns with initial system requirements, architecture and assumptions.
  2. Top (potential) integration issues.
  3. Top system risk areas
10/14/02
  1. Initial report that includes status results from tasks 1, 2, 4, 6, 8, 9, 10, and 11.
  2. Draft system specification inputs, subsystem specifications, and ICD inputs, task 5 ,7
  3. CAD models from task 3.
 11/01/02
  1. Final report that includes status results from tasks 1, 2, 4, 6, 8, 9, 10,and 11.
  2. System specification, subsystem specifications, and ICD inputs, task 5, and 7.
  3. CAD models from task 3.
 12/06/02

Evaluation Criteria
Supplier proposal will be evaluated in each of the broad categories listed below. Each category is allocated a maximum page count for consideration. Each category must be addressed by the proposal. The sub-bullets are intended to provide insight into the key areas of interest for each category. Proposal submittals shall address these areas as well as others that demonstrate significant category expertise that demonstrate capability to execute the statement of work.

Technical Approach (25-page (75,000-character) limit)

  • Approach to platform design commonality
  • Approach to developing concepts into preliminary design with evolving requirements
  • Approach to assess technology readiness for integration into platform design
  • Approach to spiral upgrade development and implementation

Understanding of the Technical Challenges (5-page (15,000-character) limit)

  • Identification of top technology challenges
  • Identification of top integration challenges
  • Identification of top supportability challenges
  • Plan and processes for execution of the above statement of work.

Key Program Challenge Mitigation Plans (5-page (15,000-character) limit)

  • Mitigation plan to address identified technology, integration, and supportability challenges.
  • Risk management approach/process
  • Weight management approach/process