|
4.10.1.3.4. Training Missile Emulator (TME) |
The TME consists of software embedded in each missile launcher which provides the capability of simulating RF missile operations. The TME can replicate the functioning of four RF missiles on each launcher. The TME will replicate the missile's launch mode selection processing, target acquisition/target tracking functions, and missile BIT routines. Each AH-64D will have the embedded training capability of the TME. |
|
4.10.1.3.5. Interactive Computer Based Training (ICBT) |
Interactive Courseware (ICW) will be developed to support both institutional and unit training. A prime consideration for the ICW is that it must be useable on existing hardware (normally a standard IBM PC) currently used at both the institution and the unit. Service schools and field units will use the ICBT to support academic training and sustain systems knowledge. Dynamic graphics and student-computer interactivity will provide increased training effectiveness. These systems will also incorporate audio, video, real time simulation, and hyper-text into a single highly interactive source. |
|
4.10.1.3.6. Airframe, Engine, and Drivetrain, Systems Trainer (AEDST-L6) |
The AEDST-L6 is a full-size replication of the AH-64D with removable components. Its primary purpose is to support the training of critical Apache Longbow airframe repairer (MOS 67R) remove-and-install tasks and skills. It has functional modularity which permits simultaneous task training of airframe, engine, drive, brakes, landing gear, utility, fuel, environmental control, and drivetrain/flight control systems. |
|
4.10.1.3.7. Multiplex, Avionics, Visionics, Weapons, and Electrical Systems Trainer (MAVWEST-L7) |
The MAVWEST-L7 consists of a full-size replication of the AH-64D with functional subsystems and a separate Instructor/Operator Station (I/OS). The primary purpose of the MAVWEST-L7 is to support the training of the Apache Armament/Electrical/Avionics repairers (MOS 68Y). Its functional subsystems include the FCR, TADS, Pilot Night Vision Sensor (PNVS), IHADSS, Area Weapon System (AWS), Point Target Weapons System (PTWS), and 2.75" Folding Fin Aerial Rocket (FFAR) delivery system. Using the "fault-insertion" capability of the Instructor/Operator Station, the MAVWEST-L7 enables the instructor to further develop students’ skills and knowledge in weapons and electrical systems troubleshooting as well as fault isolation techniques. |
|
4.10.1.4 Training Equipment |
When operator and maintainer training occurs at Mesa, AZ, some of the gaining unit aircraft may be used in the conduct of this training. Unit aircraft will be made available to the unit by E-Date. Training equipment is shown in Appendix T. |
|
4.10.2 Other Training Requirements Not Previously Mentioned |
No new training facility requirement has been identified. One of the goals of this training program is to limit training facility requirements to those already in existence to support the AH-64A program. A surge of training may occur during the lengthy transition time from a 100% AH-64A fleet to a 100% |
|
4.11 Computer Resources Support |
Computer Resources Support includes both embedded (operational flight software) mission critical computer resources as well as computer resources for training devices and TMDE. The Apache Attack Helicopter Computer Resources Management Team (CRMT) manages support for all computer resources. The CRMT is comprised of government, outside support contractor personnel, and government supporting agencies such as AMCOM, CECOM, and Picatinney Arsenal. The CRMT provides on-site technical representatives at both the aircraft prime contractor’s facility and at the FCR prime contractor facility. The CRMT is responsible to execute all computer resources management functions. |
|
4.11.1 Computer Resources Requirements |
The AH-64D Apache Longbow has a software intensive multiplexed bus System Architecture using 32-Bit processing technology and ADA programming language. Included within the major processing center is the AH-64D FCR which is coupled with the on-board computer resources to form a complex set of integrated computer software. All computer resources were developed under MIL-STD-2167A as Computer Software Configuration Items (CSCIs). All software has been documented during the development phase using a tailored MIL-STD-2167A approach. For the production program phase, the MIL-STD-2167A approach was discarded in favor of a streamlined and commercialized acquisition approach. This new approach does not disturb what was already accomplished during development. All existing documentation is retained as developed under the Military Standards, and all software remains to be categorized as Computer Software Configuration Items as originally developed. However, new computer resources utilize a commercial practice set of documentation that was created using CRMT developed commercialized standards. These commercial standards assure that new software is developed, tested and documented, with supportability being a key goal. As part of the acquisition streamlining process, military standard type Formal Qualification Tests and Functional and Configuration Audits for new software modifications or enhancements are not used during the production phase (although these were performed as part of the development phase). For the production phase both "block updates" and contract modification type changes are permitted. In any case, a Software Baseline Verification Test (SBVT) and a Software Baseline Verification Test Review (SBVTR) are conducted for software change or group of changes prior to software release. The SBVT is similar to the MIL-STD-2167A Functional Qualification Test in that the Software Test Descriptions are executed to test each function in the Software Requirements Specification. The SBVTR is a review of the SBVT test results to disposition noted problems and assign corrective action to any deficiencies found during the SBVT. Software changes are defined either by block updates (annually or semi-annually) or contractual modifications such as Engineering Change Proposals (ECP). Because the block update changes do not require ECP action, the Apache CRMT has created a contractual requirement stating that a Software Engineering Change Fact Paper (SECFP) be prepared and delivered in accordance with instructions defined in a CRMT-developed Data Item Description (DID) before the software change can be released. The SECFP provide such information as: purpose and nature of the change; any associated System Problem Reports (SPR), why the change is being made, identification of critical components affected; impact on software metrics such as memory and processing throughput. SECFPs normally assume a 30 day response time, however, urgent SECFPs are processed within 5 government working days utilizing quick internet capabilities. |
|
4.11.2 Software ILS Requirements |
Support requirements for computer resources consist of managing and controlling fielded software, analyzing and correcting field problems, maintaining documentation, development of new software, and maintaining the capability to quickly respond to field problems and new requirements. |
|
4.11.3 Post Deployment Software Support |
In the acquisition streamlining process support of all computer resources is the contractual responsibility of the prime contractor. Where previously, a major weapon system would utilize a government owned life cycle software support facility, the Apache Longbow computer resources are supported by a Contractor Software Support Facility (CSSF), commonly know as a Life Cycle Software Support Environment (LCSSE). The requirements for CSSF are defined in the contract and include all the equipment and personnel necessary to fully support fielded computer resources. Both the airframe prime contractor and the FCR prime contractor are contractually required to maintain a CSSF with specific capabilities. The CSSF is capable of interfacing the entire the entire Apache Longbow software suite from a modular, subsystem and total system aspects. For the aircraft and the FCR on-board software, upgrades can be accomplished in the field with the use of a portable PC by connecting directly into the software intensive hardware. Software programs are burned into Electrical Erasable Programmable Read Only Memory (EEPROMS), making it relatively easy to upload new versions without removing the Line Replaceable Unit from the aircraft. Upgrades will be accomplished only by the prime contractor by way of his field representatives. All software upgrades are accompanied by a change in name plate to identify the software version. In addition, the software version is embedded into the actual software so that it can be identified anytime on the crew display screens. All such memory modules identifies the software version it contains which can also be viewed on the cockpit displays. To protect against adverse business events, a Government-owned Software Support Facility Library (GSSFL) has been contractually created at the prime contractor’s facility. The purpose of the GSSFL is to store an exact duplicate of all drawings, parts lists, maintenance and operating procedures, definitions of hardware and software, etc. that includes everything needed to permit the government to duplicate exactly the contractor’s CSSF and to maintain and operate it independent of the contractor. The GSSFL is relatively inexpensive, but provides the government protection to assure that the Apache Longbow computer resources can be fully supported in any event. The GSSFL is contractually deliverable and, therefore, provides the government with the option to compete software support if ever it became necessary or economical to do so. |
|
4.11.4 Computer Resources Life Cycle Management Plan (CRLCMP) |
Computer Resources management is accomplished by the Project Manager’s CRMT. The CRMT is responsible for ensuring that the computer resources developed, tested, fielded, documented, configuration managed and supported in an effective and timely manner. Acquisition streamlining has resulted in the establishment of the CRMT, which maintains a close working relationship with the prime contractors as well as other associated contractors. To provide a direct working link between the contractors and the Apache PMO, the CRMT employs an on-site (at the contractor’s plant) Computer Resources Technical Representative (CRTR) at both the airframe contractor and the FCR contractor. To enhance mutual decision making, Integrated Product Teams are established when necessary to assure that a decision is a coordinated and agreed to event among government and contractor personnel. In addition, the CRMT hosts contractually scheduled Software Technical Interface/Interchange Meeting (STIM) with the prime contractors. The STIMs are conducted in accordance with an agreed to agenda and always include a report of current software metrics, identification of problem areas, and a discussion of all on-going projects. During the Apache Longbow development effort, the STIMs and the CRTRs proved to be an effective means of direct communication between the PMO and the contractor thereby creating an atmosphere to accomplish tasks quickly, economically and effectively. |
|
4.11.5 Acquisition, Test, and Evaluation |
The testing of computer resources will follow the procedures outlined in the TEMP and supporting test documentation. AMCOM will evaluate system failures or additional requirements as identified by the AAH PMO during the developmental phases preceding fielding. The contractor is responsible for correcting the failures and performing additional testing. The following process encompasses hardware and software deficiency procedures: |
1. TRADOC identifies new requirement or upgraded capability and provides that information to the AAH PMO. 2. Test Deficiency or design deficiency manifests itself through analysis and evaluation, design reviews, Specification Change Notices, SECFP, ECP or contract modification. 3. During the test phase, Test Incident Reports (TIR) are prepared by the test activity. TIRs are forwarded to the AMCOM System Engineer; comments and recommended corrective actions are forwarded to the PMO or test sponsor who initiates the corrective action. The System Engineer establishes the receipt, control, and assignment of responsibility for corrective action on TIRs. 4. The System Engineer coordinates with the AMCOM functionals to determine the extent and impact of all TIRs and reports results to the AAH PMO. 5. PMO determines necessity and method of implementing change; e.g., Pre-planned product Improvement (P³I), ECP, change to existing contracts. Changes will be limited to those considered absolutely essential for safe and effective system performance. 6. PMO monitors prime contractor to ensure performance range is |
|
5.1 Reporting Requirements |
Fielded AH-64D aircraft and the LBHMMS will be subject to the Army readiness reporting system governed by AR 220-1, Unit Status Reporting; AR 700-138, Army Logistics Readiness and Sustainability; and DA PAM 738-751, Functional Users Manual for the Army Maintenance Management System - Aviation (TAMMS-A). DA DCSLOG is developing readiness reporting procedures and requirements for the AH-64D and the FCR/RFI. Until those procedures are published, units will be informed how to report during the NMIB. |
|
5.2.1 Pacing Item |
The AH-64D and FCR will be reported as a pacing item on DA form 2715, Unit Status Report Worksheet, in accordance with AR-220-1. Not applicable for the LBHMMS. MACOMs and units will be briefed proper procedures during the NMIB. |
|
5.2.2 AR 220-1 or AR 700-138 Reportable |
a. The AH-64D and FCR are also reportable under the provisions of AR 700-138 and DA PAM 738-751. b. Each gaining command is required to submit the completed AMC Form 2410-R, Availability of Logistic Support Elements, 30 days after FUE. The MFT will provide the AMC Form 2410-R and will assist in preparation when requested by the gaining command. The completed questionnaire will be submitted to: |
Executive Director USAMC Logistics Support Activity ATTN: AMXLS-A Redstone Arsenal, AL 35898-7466 |
|
|
In addition, one copy of the questionnaire will be provided to: Project Manager Apache Attack Helicopter ATTN: SFAE-AV-AAH-L Bldg 5681 Redstone Arsenal, AL 35898 c. Disposition of DA Form 2410 (Component Removal and Repair/ Overhaul Record) for the AH-64D will be as follows: (1) Upon component removal, copy #1 will be sent to: Commander AMCOM ATTN: AMSAM-MMC-RE-FD Bldg 5309 Redstone Arsenal, AL 35898 |
|
(2) Upon completion of repair of the component, copy #2 will be sent to AMCOM as in (1) above. (3) Upon reinstallation of the component, copy #3 will be sent to AMCOM as in (1). (DA Form 2410 is a three copy, four section form) The LBHMMS is reportable under the provisions of AR 700-138. |
|
|
5.2.3 Equipment Readiness Code (ERC) |
The AH-64D, FCR, and LBHMMS are currently planned as ERC A items. All three fall into the Primary Weapons and Equipment category. If their ERC changes, units will be notified |
|
6.1.1 AH-64D |
Data collection on the AH-64D will center around the Longbow’s Maintenance Data Recorder (MDR) and the Unit Level Logistics System-Aviation (ULLS-A). The MDR is a memory storage device capable of storing hundreds of fault indications, exceedances, and cautions/warnings for several missions before requiring downloading of the data by maintenance personnel. The MDR will read this data off the aircraft’s 1553 bus. Maintenance personnel will then download the stored data into the Soldier’s Portable On-System Repair Tool (SPORT). The SPORT also hosts the Interactive Electronic Technical Manuals (IETMs). A software module will process the data downloaded from the MDR into a format that will be compatible with the SPORT and launch the IETMs. The maintenance unit can then use the data in conjunction with the ULLS-A. |
|
The ULLS-A will employ laptop computers assigned to the Longbow aircraft. The laptops will contain automated maintenance management forms as well as forms for flight information, aircraft readiness data, and supply information. The data collected from the ULLS-A and the MDR will have many uses. It will provide the operational and maintenance information needed to assess how well the aircraft is performing in its operating environment. The data will also provide the necessary inputs to Operating and Support (O & S) cost studies, and will highlight candidates for reliability improvement and cost reduction initiatives. The ULLS-A information will also drive manpower and provisioning studies and will ensure sufficient input data for extensive modeling and simulation efforts. The failure trend data will provide feedback for improving maintenance troubleshooting procedures. The planned upgrade to ULLS-A is the Integrated Combat Service Support System (ICS3). In short, ICS3 will allow the unit to manage the aircraft in a largely paperless environment, while providing the data needed to determine how well the aircraft performs in its mission environment. The transition from ULLS-A to ICS3 is expected to begin during FY 99. |
|
|
6.1.2 LBHMMS |
The same information above applies to the LBHMMS. |
|
6.1.3 FCR/RFI |
The same information above applies to the FCR/RFI. |
|
7.1 Support Required for Materiel Fielding Teams (MFTs) |
The MFTs will be responsible for coordinating and planning for fielding and on-site logistic support. The teams will consist of Government personnel and contractor representatives. Per Section 3.5 of this MFP, visits will be coordinated prior to fielding the first AH-64D Apache Longbow at a given site. The following must be considered prior to MFT visits: Security Clearances Billeting Transportation Communications (Telephone, Mail) Office Space Supplies Miscellaneous |
|
7.2 Support Required from the Gaining MACOM |
The following is required of the gaining MACOM: Labor: N/A Facilities: ICS Window facilities per Section 4.8. Utilities: Electrical utilities to support Facilities for ICS Windows. Fuel: N/A Equipment: N/A Reports: Post Fielding Report per AR 700-142 |
|
8.1 Purpose |
This MFP provides guidance to user and support activities for orderly deployment of the AH-64D and LBHMMS and their associated support systems. It is a living document and is, therefore, subject to periodic review and updates as more data becomes available or if information changes significantly. |
|
8.2 First Unit Equipped |
The 1st Attack Helicopter Battalion-227th Aviation Regiment, 1st Cavalry Division, Ft. Hood, TX, is scheduled to receive the first AH-64Ds and LBHMMSs in July 1998. |
|
8.2.1 Other Equipment Issues |
Exact fielding quantities of AH-64D Apache Longbow peculiar support equipment will be furnished to FORSCOM units in TOE and RPSTL quantities sufficient to support TOE aircraft and projected flying hour programs. Fort Hood, TX, is programmed to be the AH-64D fielding location for all AH-64D aircraft. FORSCOM units will train IAW the 21st Cavalry Brigade AH-64D training plan. |
|
8.3 Major Accomplishments |
EUTE training completed FY 90. PAE training completed March 1993. PPQT training completed June 1994. Logistic Demonstration, completed June 1994. Long-lead contract award, December 1994. FDTE, completed December 1994. IOTE, completed March 1995. First AH-64A aircraft inducted into the re-manufacture program at Boeing-Mesa in November 1995. Multi-year contract award for the first 232 production aircraft signed in August 1996. The signed FCR MY contract is expected by the end of Nov 97. |
|
8.4 Open Issues |
The following issues were raised as potential trouble spots. Actions are underway to resolve these issues.
The schedule of ICS personnel to support fielding at Ft. Hood follows: -- Three ICS window personnel, one supply and two technical representatives (Boeing and Lockheed): 3 March 98 -- C-5A arrival of the first six aircraft and two contractor supplemental maintenance personnel: 7 April 98 -- Two additional supplemental maintenance personnel: 4 May 98 -- Two more supplemental maintenance personnel: 1 June 98
|
|
9.1 Agreements |
Appendix A. FORSCOM Materiel Fielding Agreement (MFA). Appendix B. Memorandum Of Agreement (MOA) Between PEO AV, PEO Tactical Missiles, ODCSOPS, ODCSLOG, AMC and its MSCs, FORSCOM, and TRADOC. Subject: Processing of AH-64A Aircraft for Entry into the AH-64D Apache Longbow Program, signed into effect 16 Oct 97. |
|
9.2 Key Correspondence |
Appendix C. Environmental Impact Assessment. Appendix D. Statement of Airworthiness Qualification. |
|
9.3 Associated Plans |
Appendix E. FORSCOM Mission Support Plans. Appendix F. New Equipment Training Plan. This is also available electronically to all MSCs. |
|
9.4 Fielding and Gaining Command Checklist |
Appendix G. These timelines depict the activities necessary to field the AH-64D and associated systems, broken down by responsible parties, and lead through to unit operational capability at home station. |
|
9.5 Personnel Support Plan |
Appendix H. This plan, from DCSPER, explains their support for fielding the Apache Longbow system. |
|
9.6 Warranties |
Appendix I. Boeing-Mesa (Aircraft) extract attached. |
|
9.7 Components Of End Items (COEI) List |
Appendix J. Aircraft Inventory Master Guide DA Form 2408-17 extracts. Appendix K. Avionics and ASE Listing extracts. |
|
9.8 Basic Issue Items (BII) Lists. |
Not applicable. |
|
9.9 Additional Authorization List |
Not applicable. |
|
9.10 Transportability Analyses and Approval |
Appendix M. |
|
9.11 Technical Manuals |
The TMs for the AH-64D Apache Longbow are to be presented in the IETM format as discussed in Section 4.7. Initial issue equipment manuals will be delivered with the aircraft per normal aircraft publications delivery procedures and are not attached as an appendix to this MFP. Updates to paper manuals will be provided through pinpoint distribution or DA 17 requisition. |
|
9.12 Related MFPs |
Appendix N. Longbow Hellfire Modular Missile System (LBHMMS) Materiel Fielding Plan (MFP). May 1994. DELETED as an appendix and its contents incorporated throughout this document. |
|
9.13 Data Collection Concept Paper |
Appendix O. |
|
9.14 PGSE Descriptions |
Appendix P. |
|
9.15 DCSOPS AH-64D Fielding Schedule |
Appendix Q. |
|
9.16 ASL |
Appendix R. Listing of D-unique and FCR spares for the ICS windows and proposed LBHMMS ASL items that will be part of the LSP. |
|
9.17 Classified Information |
Appendix S. Not required. |
|
9.18 Training Device Information |
Appendix T. |