Revised: 8/23/02

Vehicle Electronics (Vetronics)

BIA Number: 15714

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 vetronics system is a common subsystem for all FCS manned ground vehicles. The Vetronics comprise vehicle health monitoring sensors, computational elements, databuses, backplanes, chassis, data distribution networks, network interfaces, storage devices and related software products, and driving/navigation sensors, Note: Controls , displays, autonomous navigation, and other human-computer interfaces are covered by a separate BIA. Consideration should be given to the following standards: VRA, JTA-A, and other open systems standards.

All components will be based on an open system architecture and facilitate block upgrades / spiral development throughout the life of the vehicle.

Initial subsystem requirements and architecture will be provided at the start of the contract. Multiple awards are expected

While the vetronics system is conceived as a "Common" system, it will have potential variants across different vehicle applications and missions. This BIA is meant to deal with the common, or core, vetronics. The variants will be dealt with in the vehicle or mission specific WBS.

Task 1
Define subsystem hardware/software design of meeting the performance and interface requirements provided by the LSI. Support refinement to the subsystem performance and interface requirements.

Task 2
Provide subsystem level functional schematics

Task 3
Provide 3D CAD Envelope Models and 2D layouts of Envelope Models/Layouts of the preferred subsystem arrangement for the major subsystem elements sufficient to define subsystem-to-vehicle interfaces and to show compliance with interface requirements. Provide 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 be submitted. 2D layouts to be contractor CAD dataset format and one 36" wide paper plot.

Task 4
Review applicable standards (existing and emerging) and make recommendations.

Task 5
Provide ROM Subsystem-Level Reliability Assessment

Task 6
Provide preliminary repair/maintenance concepts associated with system/subsystem design.

Task 7
Provide description of the critical subsystem failure modes.

Task 8
Provide SDD Test and Evaluation roadmap for the subsystem elements necessary to validated simulation models and verify system performance and RAM-D requirements.

Task 9
Provide subsystem attribute sensitivity (i.e., weight, volume, power, cooling) to potential growth in subsystem performance requirements as specified by the LSI.

Task 10
Provide a fabrication concept that addresses building and assembling the vetronics subsystem components in sufficient detail to support manufacturing plan development.

Task 11
Offeror shall support SDD WBS development.

Meeting Support

1. Weekly Telecons to report Schedule Status, Accomplishments, Significant Findings/Conclusions/Recommendations, Problems with mitigation plans, integration issues needing resolution, etc.
2. Three 2 day meetings held in Seattle

Schedule Milestones
Subcontract Start Date - 10/7/02
Initial Coordination Meeting - 10/7/02
Interim Coordination Meeting - 10/31/02
Interim Coordination Meeting - 11/2912/02/02
Subcontract Completion Date - 12/16/02

Data Requirements
Initial input - 10/31/02
Final input - 11/2912/02/02
Revised Input - 12/16/02

Deliverables

10/14/02

1. Issues/concerns with initial subsystem requirements and interfaces provided by the LSI
2. Top (potential) integration issues that need resolution with vehicle integrators
3. Top subsystem risk areas

10/21/02

1. Initial hardware/software functional schematics. A Vetronics systems architecture shall be developed for each variant that defines the internal relationships among Vetronics components as well as the relationships between the Vetronics and the rest of the system and the Vetronics and C4ISR architecture.
2. A Vetronics Product-based WBS shall be developed for each system variant. This WBS shall also delineate common versus system unique hardware and software components.

10/31/02

1. Initial subsystem report which includes results from tasks 1, 2, 3, 4, and 9.
2. CAD models from task

11/22/02

1. Issues/concerns with updated subsystem requirements and ICD provided by the LSI
2. Top (potential) integration issues
3. Subsystem risk areas update

11/2912/02/02

1. Final subsystem report which includes status results from tasks 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10.
2. CAD models from task 3.

12/16/02

Revised subsystem report which includes status results from tasks 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10.

CAD models from task 3.

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 design into platform concept
• Approach to developing concepts into preliminary design with evolving requirements
• Approach to multi-platform design commonality
• Approach to assess technology readiness for integration into platform subsystem design
• 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