BCIS Initial Draft MFP
20 June 98

1.1 PURPOSE. This first draft Materiel Fielding Plan (MFP) is published to serve as a planning document for the fielding and sustainment of the Battlefield Combat Identification System (BCIS). This MFP is written in accordance with (IAW) AR 700-142, Materiel Release, Fielding, and Transfer, and DA PAM 700-142, Instructions for Materiel Release, Fielding, and Transfer. The BCIS initial draft MFP applies to all active US Army FORSCOM elements responsible for planning and supporting this system before, during and after deployment to the field. It is intended for this document to serve as a comprehensive planning document for all logistical support details necessary for successful fielding of BCIS (AN/VSX-4 and AN/VSC-9) to the FORSCOM units at Ft. Hood, TX and specifically for the 4th Infantry Division (-).

1.2 DATA.

1.2.1 Data Sources. The data contained in this first draft MFP is limited to information available at the time of publication. The information was obtained from the following data sources:

1.2.2 Limits of Data. There are no known restrictive or limiting qualifications that apply to any data covered by this plan.

1.3 AGREEMENTS. A Materiel Fielding Agreement (MFA) establishes the administrative and logistical support relationship between FORSCOM, TRADOC and PM CI for the fielding of the BCIS total package. The MFA will be negotiated between representatives of these organizations and incorporated in the final MFP as a record of agreement in Appendix 9-1.

1.4 FIELDING AND LOGISTIC SUPPORT CONCEPT.

1.4.1 Fielding Concept. BCIS fielding concept is that of a Total Package Fielding (TPF) Category I, Level 2 System as outlined in AR 700-142. The TPF supply project code is not yet available, but will be indicated in the final MFP.

1.4.2 Maintenance and Supply Concept. BCIS will be supported through normal maintenance and supply channels except that the depot maintenance actions are anticipated to be accomplished by the BCIS prime contractor. All technical publications will reflect a two-level maintenance concept: Unit Level (UL) and Depot Level. The UL maintenance tasks are limited to system troubleshooting, identification of malfunctioning Line Replaceable Units (LRUs) using Built-In-Test (BIT) for the two major components, and replacing failed LRUs with spares. Failed LRUs (reparable components) will be turned-in to the Electronic Sustainment Support Center (ESSC) for return to the contractor depot for repair. The unit will requisition a new replacement LRU as well as any consumable components in accordance with Army standards. The initial spares stockage on the Authorized Stockage List (ASL) will be determined by Automated Requirements Computation Standard Initial Provisioning (ARCSIP). Replenishment spares on the ASL will be stocked according to demand.

1.4.3 Contractor Logistic Support. The contractor (TRW, Redondo Beach, CA) is anticipated to be the depot repair activity for the life of the system due to organic depot technology limitations and capabilities. The depot decision resulting from a Depot Maintenance Interservice (DMI) Study has not been rendered at this time, but is expected prior to the next MFP update. Contractor teams will install and checkout BCIs interoperability with each vehicle at the fielding location prior to BCIS handoff.