Downloaded from https://www.everyspec.com (6) MFA. b. The SLAMIS is the Web-based application (located at http://www.slamis.army.pentagon.mil) that is used to manage selected new, modified, and displaced (cascaded) materiel systems having a resource impact on GC. The Web site contains or links to the following plans and lists as they become available: (1) BOIP. (2) Incremental change package. (3) Management decision package (MDEP). (4) Modernization path. (5) Master force file. (6) Unit identification code (UIC) and DOD activity address code (DODAAC) cross-reference. (7) Transportability reference file. (8) MOS file. (9) TOE file. (10) Organizational assessment checklist. (11) SS.
(12) System Training Plan. (13) MFP. (14) Weapon system operating and support cost files. c. Fielding requirements need to be identified as early as possible in the system planning documents to allow for adequate budgetary lead time. 5–3. Memorandum of notification The PM initiates the formal materiel fielding process by providing a MON to each GC and installation garrison at least 240 days before the LRIP/production contract for a developmental materiel system is awarded (see DA Pam 700–142, app D, for fielding milestones). The MON will be forwarded to the GC and installation garrison at least 170 days prior to product availability and will— a. State the intention to field a system. b.
Provide specific fielding MSs. c. Briefly describe the system and its intended uses. The MON will also indicate if it replaces a materiel system now in use. If so, it will indicate whether the replaced system will be transferred under normal excess procedures or whether directed redistribution, normal equipment transfer, or displaced equipment fielding (DEF) is appropriate (see chap 6 for materiel transfer and DEF guidance). d. Identify the types of units to receive the materiel and provide the best cost estimate available for the logistics resource impact on the GC. (The AMRD cost data will be used, if available, as the basis for these estimates.) e.
Identify the applicable ESOH documentation including, but not limited to, the National Environmental Policy Act documentation and the Programmatic Environment, Safety, and Occupational Health Evaluation. f. Be accompanied by a draft MFP. (If an MFP is not necessary, the rationale will be provided, and the GC will be requested to concur and an MFA can be attached for signature or comment. GC concurrence is required to waive the requirement for an MFP.) g. Provide the preliminary distribution plan, based on the current BOIP and common TOE update (CTU), if available, to the GC and state that an MSP is required.
(The MON will request identification of units nominated for initial fielding and a distribution plan if an MFP/MSP is not required.) h. Provide PM POCs and request GC POCs. i. Request GC comment on the MON, MFP, and schedules. j. Ensure that force integrators get fielding schedules to the GCs. k. Be prepared for each GC (similar to 5–4 b ). 5–4. Materiel fielding plan The PM, in coordination with the supportability integrated process team members, GC, and HQDA will prepare the MFP for each new materiel system having a significant support impact on the GC. a.
The MFP will be posted to the TAFS Web site (https://aeps.ria.army.mil), and all involved organizations will be provided a copy or be notified that it is available on the TAFS Web site. b. All MFPs will be kept current and complete and provide information on security classification guides, to include the status, if one is available, for any of the systems new to the command. The point of contact, name, telephone number, and mailing address for each applicable security classification guide will be listed. c. All MFPs will provide information on the physical, informational, and operational security requirements of all equipment in the fielding.
Classified information will be included in a classified annex and referenced in the appropriate sections of the MFP. 26 AR 700–142 • 26 March 2008