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

Autonomous Navigation Subsystem

BIA Number: 15350.2

Pricing Information
The Program anticipates a funding level of up to $95,000 for the contract award(s) resulting from this BIA.

Detailed Description of Effort and Tasks
The Autonomous Navigation Subsystem (ANS) consists of sensors, software and interfaces that perform land navigation, perception, world modeling, behavior generation and command generation functions to provide a semi-autonomous mobility capability for the 6 ton Armed Reconnaissance Vehicle (ARV) Unmanned Ground Vehicle (UGV), 16 ton Manned Ground Vehicle (MGV), and possibly a 1-2 ton Mule UGV. As a goal, the ANS will utilize common computing, communication and GPS/INS infrastructure defined by the LSI.

The work effort under this SOW includes preparation of draft performance specifications and interface documentation for the ANS subsystem and LSI-defined platform interfaces, and preparation of ANS concepts and ROM cost models that address the draft requirements.

Task 1
Prepare and maintain ANS design concept that meets performance requirements described in draft specifications and interface documentation. Provide models (CAD, functional) and analyses that substantiate subsystem performance predictions and address requirements for location of sensors.

Task 2
Prepare ANS interface documentation that supports integration with LSI-directed common subsystems/components and vehicles. LSI will provide subsystem/component and vehicle interface requirements and guidance at contract award.

Task 3
Prepare a draft ANS specification. LSI will provide preliminary ANS performance requirements and specification guidance at contract award.

Task 4
Analyze LSI-prepared final draft ANS specification and provide comments at Final Review. LSI will provide final ANS draft specification two weeks after In-Process Review.

Task 5
Provide ROM cost models for SDD and production. LSI will provide SDD planning and guidance at contract award.

Task 6
Provide preliminary Systems Development and Demonstration (SDD) program plan to include at a minimum: preliminary system manufacturing plan, long lead items list, program critical path, preliminary subsystem/vehicle system level test plan, and program risk issues.

Task 7
Offeror shall support SDD WBS development.

Schedule and duration of on-site support - No on-site support other than reviews

Number, duration(s) and location(s) of meetings -
Kickoff Telecon (1/2 day)
In-Process Review (2 days), Huntsville, AL
Final Review (2 days), Huntsville, AL

Schedule Milestones
Subcontract Start Date - 10/9/02
Subcontract Completion Date - 12/20/02
Initial Coordination Meeting - 10/9/02 - 10/11/02 (Kickoff Telecon)
Interim Coordination Meeting - 10/28/02 - 11/8/02 (In-Process Review)
Final Coordination Meeting - 12/4/02 - 12/13/02 (Final Review)

Data Requirements
Initial input - IPR 10/28/02
Final input - FR 12/4/02 - 12/13/02

Deliverables
Draft ANS Performance Specification: IPR
Draft ANS Interface Documentation: IPR
ROM Cost Models: FR
Analyses and Performance Predictions

Report: Initial IPR, Final FR
CAD Models: Initial IPR, Final FR
Functional Models: Initial IPR, Final FR

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 (6-page (18,000-character) limit):

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

Understanding of the Technical Challenges (3-page (9,000-character) limit)

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

Key Program Challenge Mitigation Plans (3-page (9,000-character) limit)

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