Attachment_7_-_RAMS-CMA_Maintenance_SOP.pdf

Joint Multinational Readiness Center Operations Group

RAMS Maintenance Standing Operating Procedures (SOP)

TABLE OF CONTENTS

SUBJECT PAGE

DCOG Comments 2

ANNEX 1 Duties and Responsibilities 3

ANNEX 2 JMRC Maintenance Organization and Function 10

ANNEX 3 TAMMS /Report Requirements/Routine Transactions 11

Tab a. STAMIS Operations/Automation Enablers/ (VSATS/CAISI) 16

Tab b. WEBLIDB 24

Tab c. ILAP/Requisition Status 26

Tab d. AEPS (SOUM, PQDR Submissions) 31

ANNEX 4 SAMS-1E Operations 34

ANNEX 5 Class IX Management and Shop Office Operations 38

ANNEX 6 Equipment Readiness Reporting 53

ANNEX 7 Command Maintenance (PMCS) 55

ANNEX 8 Unscheduled Maintenance Operations 59

ANNEX 9 Scheduled Maintenance Services 67

ANNEX 10 NMC Equipment Repair and Evacuation 68

ANNEX 11 Equipment Dispatch Procedures 71

ANNEX 12 Controlled Exchange Policies and Procedures 78

ANNEX 13 Quality Assurance/Quality Control Procedures 79

ANNEX 14 Army Oil Analysis Program Procedures 81

ANNEX 15 TMDE/Calibration Procedures 84

ANNEX 16 Tool Accountability and Control Procedures 87

ANNEX 17 Maintenance Operations 89

Tab a. Communication Maintenance 95

Tab b. Individual and Crew Served Weapon Maintenance 95

Tab c. NBC Equipment Maintenance 98

Tab d. Class II, IV, & VII Equipment Maintenance 100

ANNEX 18 BDAR and Recovery Operations 102

ANNEX 19 Maintenance Training Program 103

Tab a. Drivers and Mechanics Award Program 103

Tab b. Sustainment Training Procedures 106

ANNEX 20 Work Order Management 108

Tab a. Maintenance Priorities 108

ANNEX 21 Equipment Classification/ECOD, ACOD Procedures 110

ANNEX 22 Load Testing Procedures 112

ANNEX 23 Modification Work Order (MWO) Procedures 114

ANNEX 24 Warranty Management Program 117

ANNEX 25 Safety/Hazardous Materials Management 118

ANNEX 26 Motor Pool Security Procedures 126

ANNEX 27 Publication and Forms 127

ANNEX 28 Requisition Status Codes 128

ANNEX 29 Acronyms and Abbreviations 130

ANNEX 30 OC Academy Drivers Traing Program 141

DCOG COMMENTS

ANNEX 1 Duty and Responsibilities

1. PURPOSE: To prescribe maintenance policies, procedures, responsibilities, and guidance for all units assigned to, attached to, or supported by JMRC OPSGRP.

2. MISSION: The mission of the Operations Group (OPSGRP) requires that all equipment is –10/20 standard and is combat-ready at all times.

3. APPLICABILITY: This SOP applies to all Observation Controllers, units and personnel assigned to, attached to, or supported by JMRC Operations Group. This SOP is effective when signed by the OPSGRP Commander and will remain in effect until superseded or rescinded. Any previous editions of OPSGRP Maintenance SOP are hereby rescinded.

4. OBJECTIVES:

Maintain over 90% equipment serviceability with minimum expenditure of time and resources.

Ensure maximum service life of all materiel and equipment.

Attain a state of training and discipline where each Soldier (operator and maintainer) becomes completely knowledgeable of his/her maintenance responsibilities.

Provide procedures for early detection and correction of actual or potential equipment faults at the lowest practical level of maintenance.

Achieve and maintain the highest materiel readiness posture necessary to accomplish assigned missions.

Standardize maintenance activities throughout the OPSGRP.

Make maintenance and maintenance related training a top priority.

5. DEFINITIONS:

Maintenance: Actions taken to sustain or restore materiel to a serviceable condition.

Command Maintenance: A routinely scheduled period of preventive maintenance checks and services (PMCS) devoted to ensuring that all equipment functions and is operationally ready to perform its intended purpose.

Operator Maintenance: PMCS (before operation, during operation, after operation, weekly, monthly) and minor maintenance/repair as prescribed in the applicable TM -10.

Field Level Maintenance: The performance of preventive maintenance services, inspections, adjustments, replacement of designated components and assemblies

IAW the applicable TM –20/30. The performance of mobile, responsive, and one-stop maintenance support includes inspection; troubleshooting; testing; diagnosis;

repair; adjustment; calibration; alignment of components, equipment, and systems; replacement and repair of end items; light body repairs; technical assistance; collection, classification, and recovery services for serviceable and unserviceable materiel; and establishment and operation of battle damage assessment (BDA) teams IAW applicable TM.

6. RESPONSIBILITIES:

(a) OPSGRP Commander:

Establish material readiness goals and priorities.

Develop and implement instructions and procedural guidelines for Observation

Controller Team Commanders’ to ensure compliance with regulations governing maintenance activities.

Render advice to ensure and assist in planning the OPSGRP maintenance program.

Exercise leadership influence (inspections— formal/informal) and command presence during maintenance activities throughout JMRC.

Advise higher headquarters of pertinent aspects of maintenance in the JMRC.

Establish OPSGRP maintenance goals and objectives that ensure optimal use of funds and resources.

Conduct maintenance meetings with commanders and maintenance staff at a prescribed interval.

(b) DCOG (Deputy Commander, Operations Group):

Serve as the Senior OPSGRP materiel readiness officer.

Supervise preparation and execution of the OPSGRP maintenance programs.

Serve as the principal advisor to the OPSGRP Commander in maintenance matters.

Review instructions issued by the staff to ensure conformity with established maintenance policy.

Review periodic and special maintenance reports submitted to higher headquarters for accuracy.

Evaluate the maintenance program.

Make recommendations to the commander regarding adjustments to the maintenance program.

(c) OPSGRP Command Sergeant Major:

Enforce Command Maintenance periods.

Ensure that Observation Controller Team NCOIC’s and supervisors are present during Command Maintenance periods.

Advise the OPSGRP Commander on maintenance personnel gains, loses, strengths, and weaknesses.

Validate motor pool areas and motor pool facility compliance through frequent announced and unannounced inspections and leadership presence.

Identify maintenance weaknesses, make corrections though the NCO support channel, and advise the OPSGRP Commander as needed.

(d) OPSGRP S4:

Reconcile Tables of Distribution and Allowances (TDA) with property book to ensure that equipment shortages are on order.

Reconcile AMSS authorization file with property book for reporting accuracy.

Publish procedures for equipment receipt/disposal.

Allocate and monitor funds for expendable and non expendable parts and supplies in support of the maintenance effort.

Report changes in equipment authorizations to the maintenance officer and

Observation Controller Team Commanders for AMSS update.

(e) Observation Controller Commanders 07/04 and Maintenance Representatives:

Organize and implement an effective operator maintenance program for all Team assigned equipment.

Ensure that all assigned equipment (vehicles, radios, night vision devices, and navigation equipment) is maintained to -10/20 standard IAW DA PAM 750-8, AR

750-1, applicable TM, and this SOP.

Implement Team Maintenance Policy.

Ensure all assigned equipment (vehicles, radios, night vision devices, and navigation equipment) is loaded in the SAMS-1E system.

Ensure all operators are assigned for each piece of equipment.

Ensure Command Maintenance and services are scheduled on training calendar and are properly conducted.

Ensure leaders are thoroughly familiar with PMCS procedures and documentation, and follow up on tasks required through all logistic systems.

Maintain and enforce command and leadership presence during Command

Maintenance periods.

Ensure that the OPSGRP Executive Officer and Maintenance Section are notified any time an item becomes Non-Mission-Capable.

(f) Observation Controller Team 02:

Enforce OPSGRP Maintenance policies IAW SOP.

Identify weekly areas of interest for Command Maintenance within the

Observation Controller Team in-line with the OPSGRP maintenance objectives.

(g) Company Commander (HHC):

Supervises, plans, and reviews periodic and special reports, pertaining to assigned equipment, submitted to higher headquarters.

Conduct analysis on maintenance issues relating to HHC equipment not belonging to the Observation Controller Teams.

Recommends changes to the maintenance program for HHC equipment not belonging to Observation Controller Teams.

Ensures proper operator PMCS of assigned equipment.

(h) Company First Sergeant (HHC):

Enforce maximum participation during Command Maintenance.

Enforce Company maintenance standards.

Identify maintenance personnel shortcomings to the OPSGRP Command Sergeant

Major for possible re-alignment across the JMRC OPSGRP.

(i) Senior Automotive Maintenance Officer (CMA/MDH SAMO):

Scrub the AHO-026 report daily, and ensure its accuracy.

Interact with item managers as needed to expedite critical requisitions.

Provide guidance and mentorship to the OPSGRP Maintenance

Officer/Technician and NCOIC.

Responsible for the Overall Automotive Maintenance Program in the OPSGRP.

Review the OPSGRP NMC report daily for completeness and accuracy.

Ensure that field level maintenance procedures and programs conform to current regulations and directives.

Coordinate automotive maintenance matters with adjacent units as required.

Monitor scheduled maintenance services for the automotive fleet and monitor completion.

Monitor quality control inspections and analyze equipment deficiencies and failures.

(j) OPSGRP Maintenance Officer/Technician:

Provide a candid and forthright assessment of the OPSGRP maintenance posture to the OPSGRP Commander, DCOG and OPSGRP S-4 daily.

Make recommendations for controlled exchange in order to sustain readiness and ensure mission accomplishment.

Work closely with item managers to expedite special purpose and hard to get parts for the OPSGRP.

Provide mentorship, guidance, and technical assistance to the other technicians in the OPSGRP to ensure that the OPSGRP is postured to execute its mission.

Assist adjacent units in solving technical problems in maintenance and supply.

Monitor all field level maintenance operations.

Plan, organize, and coordinate unit maintenance activities for the OPSGRP.

Ensure that field level maintenance procedures and programs conform to current regulations and directives.

Maintain the OPSGRP Maintenance SOP.

Manage the Repair Parts Local Purchase Program and Class IX repair parts.

Monitor the completion of scheduled services across the OPSGRP.

Develop and maintain maintenance certification programs for Soldiers and local national employees within the maintenance section.

(k) OPSGRP Motor Sergeant:

Supervise automotive maintenance operations.

Supervise scheduled maintenance services and troubleshooting.

Organize and supervise the automotive maintenance team including the preparation of work sheets and charts assigning daily work to maintenance personnel.

Supervise the quality control procedures.

Supervise the training of maintenance personnel.

Recommend changes to the current maintenance policy to the Automotive

Maintenance Officer/Technician and the OPSGRP Senior Automotive

Maintenance Officer.

Keep the Automotive Maintenance Technician informed of daily training and workload issues.

Responsible for overall cleanliness and efficiency of the Motor Pool

(l) OPSGRP Shop Foreman:

Supervise Soldiers work activities.

Supervise daily safety and quality control operations.

Perform QA/QC inspections on completed equipment services and repairs.

Update work log throughout the day & keeps technician and motor sergeant informed of job status.

Notify supported Observation Controller Maintenance Representatives of issues

(equipment ready for pickup, etc.).

Coordinate flow of jobs into and out of shop.

(m) Quality Assurance/Quality Control Inspector (QA/QC) Inspector:

Perform technical inspections prior to accepting and upon completion of major assembly jobs to ensure quality standards are met.

Perform QA/QC inspections prior to equipment dispatch.

Conduct initial QA/QC inspection of vehicles going into equipment service.

Conduct QA/QC upon completion of equipment services.

(o) Equipment Records/Parts Shop Office Supervisor:

Provide a daily NMC report daily.

Plan the daily activities of the Equipment Records/Parts Specialists.

Ensure that all STAMIS transactions occur on time.

(p) Equipment Records and Parts Specialist:

Maintain equipment records and verify entries according to DA Pam 750-8 and

SAMS-1E User Manual.

Prepare forms and reports for higher headquarters according to DA Pam 750-8 and local SOPs.

Serve as equipment dispatcher and validates that each operator is properly licensed in SAMS-1E prior to dispatch.

Maintain 100% accountability of the unit PLL and bench/shop stock.

Request, receive, store and issue repair parts and class IX supplies.

Update records as required.

(q) OPSGRP Recovery Vehicle Supervisor:

Ensure recovery vehicle operators are continually trained on perishable skills.

Ensure that all safety measures are followed during recovery operations.

(r) Recovery Vehicle Operator:

Perform operator, organizational maintenance, and scheduled maintenance of recovery equipment.

Recover inoperative, disabled, damaged, mired or abandoned material from its current position and returned it to the maintenance facility for repair.

Ensure rigging, lifting and towing is conducted properly and in a safety manner before moving equipment.

(s) Signal Maintenance Supervisor:

Supervise communications maintenance operations.

Organize and supervise the communications equipment maintenance including the preparation of work sheets and charts assigning daily work to maintenance personnel.

Supervise quality control procedures.

Supervise training of signal maintenance personnel.

Recommend changes to current maintenance policies to the OPSGRP maintenance officer.

(t) Equipment Operator:

Operate the equipment IAW –10 TM’s. Additionally observe for any safety violation before, during, and after operation of equipment.

Perform operator level maintenance checks and services and properly annotate discrepancies on DA Form 5988E.

Performs lubrication maintenance as required in the equipment lubrication order

(LO).

Assist maintenance personnel during unscheduled and scheduled maintenance.

Install operator level class IX repair parts for assigned equipment.

Ensure equipment is fully-mission-capable before operation.

ANNEX 2 JMRC Maintenance Organization and Function

1. PURPOSE: To establish the maintenance architecture for the JMRC OPSGRP maintenance section.

2. GENERAL: Maintenance in the OPSGRP is a commander’s program. The OPSGRP

Commander is overall responsible for the materiel posture of the OPSGRP. With such a unique mission and with limited resources we have leveraged civilian employees to work hand in hand with our military members. The Observation Controller 04/07’s are directly responsible to the OPSGRP Commander on all maintenance matters. Team 04/07’s accomplish their maintenance tasks through the OPSGRP Maintenance Section.

3. PROCEDURES: All Observation Controller equipment involved in the JMRC

OPSGRP is supported by the OPSGRP RAMS maintenance section located at Bldg. 300 and/or Consolidated Maintenance Activity motor pool Bldg. 536.

RAMS

Shop

Office

O/C Recovery

MDH

OPSGRP Maintenance Architecture Structure

OPSGRP CDR

DCOG

S4

Automotive

Unscheduled Maint

SVC

Team

COMM

Team

Welding g Shop

COMMEL SAMS

Supply

TRP

Const

Shop 1 Shop 2 Shop 3

ANNEX 3 TAMMS/Report Requirements/Routine Transactions

1. PURPOSE: To establish procedures and policy to manage the Army Maintenance

Management System records and files.

2. GENERAL: The Army Maintenance Management System (TAMMS) is the management of records set up in categories of operational records, maintenance records, and historical records. TAMMS is the system used to schedule daily maintenance operations and forecast maintenance operations plans.

3. POLICY AND PROCEDURES:

The following Maintenance Management Records are maintained in accordance with the

Standard Army Maintenance System Enhance (SAMS-E), Maintenance Management

Update (DA PAM 750-8), and local regulations:

1) Equipment Data Files: Add Equipment: (NOTE: Equipment can't be added if equipment national stock number on the REV file or in equipment catalog is not input in your system.)

2) Weapon System Data: All equipment that is part of a system IAW AR 700-138 is placed in this file. (NOTE: Ensure that the main system is entered in first before sub-system).

3) Administrative Data: All administrative data is input (i.e., odometer reading and cumulative, dispatching, AC, equipment class code, fuel type, key number, equipment license number, warranty expiration date, year manufactured, operator license number, dispatching destination, and official user's name and phone number).

4) Services Data: Organizational services are scheduled IAW -20 Technical Manuals and -12 Lubrication Orders.

5) Component Data: Components enrolled in the Army Oil Analysis Program

(AOAP) (engines, transmission, and hydraulics). See DA Pam 750-8, para 2-5, for required equipment and system.

6) Equipment Management - Add: This allows the SAMS-E operator (TAMMS

Clerk) to update or change data within the equipment files.

7) Equipment Management - Delete: Allows operator to delete all files on any one

Admin number.

8) AdHoc Query: Has five main fuctions:

a. To create/add new AdHoc Queries

b. To update/modify existing Queries

c. To delete/purge existing Queries

d. To read/view existing Queries

e. To quickly locate existing Queries

4. Equipment Dispatch Control Log:

(a) Is automatically purged the first of every month.

(b) SAMS-E operator (TAMMS Clerk) prints a dispatch control log the last working day of each week. OPSGRP maintenance officer will review and notify OC

Teams of any overdue dispatches.

(c) Maintain on hand (Filed) until next purge or in case of accident until investigation is complete.

(d) SAMS-E operator updates the dispatch control log once the dispatch is returned.

5. Equipment Maintenance and Inspection Worksheet (DA Form 5988-E):

(a) SAMS-E Operator (TAMMS Clerk) will print this maintenance form when:

Equipment is dispatched

During scheduled service (print out an operator’s monthly inspection and organizational level inspection).

Command Maintenance: (Print and/or Post on shared drive all Equipment

Maintenance and inspection Worksheets the last working day of the week).

(b) Kept on hand (Filed) until SAMS-E has been update with current information. If a deadline fault has been annotated on the 5988-E then it must be kept on hand until the deadline deficiency is corrected. If used to perform a service then it must be kept on hand until the next serviced is performed.

6. Equipment Admin Number Management: This allows the SAMS-E Operator

(TAMMS Clerk) to add, change, or delete a fault. Equipment Maintenance and

Inspection Worksheet is updated when all corrective actions are taken by operators, supervisors, and maintenance personnel and all repair parts are ordered.

7. Parts Received Not Installed:

(a) SAMS-E Operator (TAMMS Clerk) updates and print parts received not installed listing on the last workday of the week and give it to the OPSGRP maintenance officer by 1500 hrs.

(b) Last working day of the week, the maintenance representatives and the maintenance officer reviews listing to plan and install repair parts on assigned equipment during the next maintenance opportunity. Also reviewed are parts awaiting additional parts to be installed.

(c) When equipment supervisor or maintenance personnel remove parts, parts received not installed list is initialed.

(d) Parts Received Not Installed list is updated, when parts are installed and the maintenance faults record is updated. Parts Received Not Installed list and

Equipment Maintenance and Inspection Worksheet should match and be updated at the same time.

(e) Parts received not installed listing is kept on file for one week.

8. Non-Mission Capable Report: List of non-mission capable equipment.

(a) SAMS-E Operator (TAMMS Clerk) will print out daily deadline report prior to

1400 hours. The maintenance officer will review, update, and submit any changes to the Senior Automotive Maintenance Officer by 1500 hrs daily.

(b) NMC reports are kept on hand (Filed) for 90 days.

9. The DA Form 2408-4 are maintained on all weapons systems listed in Annex E of DA

PAM 750-8 and DA PAM 750-3. Personnel accountable for weapons will maintain these records on their weapons systems.

10. DA Form 2408-9 (Acceptance): Is maintained IAW Maintenance Management

Update (DA Pam 750-8). The maintenance officer will verify acceptance of DA Form

2408-9 with assigned equipment quarterly.

11. Service Schedule: This process will provide a printed service schedule by Admin number, NSN, or date range.

(a) SAMS-E Operator (TAMMS Clerk) will produce schedule by date with 10% tolerance allowed, up to three months ahead of schedule.

(b) OPSGRP maintenance officer will review monthly scheduled service to plan maintenance operations with training schedule.

(c) Services Performed: This process is to input data when service are completed and update service files.

12. Maintenance Request Register: File of organizational work order numbers of maintenance request forwarded to direct support.

(a) SAMS-E Operator (TAMMS Clerk) will print register daily after receiving data from SAMS-1 box.

(b) BMT/BMS will review register daily for status and to update files.

(c) Are filed for one (1) year.

13. Maintenance Request (DA Form 5990-E):

(a) To request maintenance action from direct support unit. This maintenance request process can be printed by Admin number.

(b) Print maintenance request to direct support is in two copies. (NOTE: Unit will run a SAMS transaction diskette or BLAST transaction with each maintenance request).

(c) Maintenance requests that are open are filed until the work request is closed. At which time it is moved to the closed work order request file for 90 days.

14. Operators Qualification Records: The SAMS-E Operator (TAMMS Clerk) will not update and make entries in the Operator's qualification records from all information included in the Drivers Training Program. All corrections or updates will be made by the

OC Drivers Training Academy.

15. Maintenance Management Files: OPSGRP Maintenance Officer and SAMS-E

Operators will maintain files IAW DA Pam 25-200-2, and AR 700-138.

16. Oil Analysis Request: SAMS-E Operator (TAMMS Clerk) will generate upon request or AOAP Coordinator.

(a) Component Data File Printout: This list all components enrolled into AOAP. If applicable the maintenance officer will print this file monthly upon receipt of

AOAP Lab printout and will compare the data on both printouts ensuring it is identical.

17. Document Control Register (DCR): This report may be printed out by Admin

Number, All Open Records, All Records, Inactive Records, Document Number, All High

Priority Request, NMCS (01-03) High Priority request, NIIN, or by Range of Document

Numbers.

(a) The DCR is a critical asset in maintenance management. It is commonly used to show current status of parts, whether they have been received or not.

(b) Used to complete customer reconciliation’s (Recons) from local SSA.

(c) Inactive DCR is the only DCR that must be kept on file. It must be filed for two

(2) years.

18. Excess Management Report: Used by maintenance personnel to track excess repair parts. It is a complete listing of Shop Stock and non-stock records for a DODAAC that have an excess quantity on hand.

19. Financial Transaction Report: Provides a listing of Financial Transactions showing the daily expenditures.

(a) Must be signed by the Commander or designated representative and filed for two

(2) years.

20. Commander’s Exception Report: Provides for a selected DODAAC a listing of high priority and/or high value items.

(a) Company Commander must sign and initial all high priority and all high dollar items over $500.00.

(b) Must be filed for two (2) years.

21. AMSS: This is used to capture accurate readiness of the unit’s equipment. There are various reports such as the Projection Report, Roll-up by UIC or EIC, which can be used by leaders to effectively manage the readiness rates of all reportable equipment assigned to a unit.

(a) Projection Report: Used to project FMC rates to the end of the report period using the current status of the equipment.

(b) Roll Up By UIC/EIC: Provides information of accumulated NMC time by UIC or

EIC.

(c) Summary Report: Provides FMC/NMC computations for all reportable, substitutes, in lieu of, and exempt items. This report will give your PERRY

(Percentage of On Hand Equipment Mission Capable/OR Rate) and PIEMC

(Percentage of Pacing Items on Hand Mission Capable).

(d) End of Report Period is run on the 16th of each month.

(e) Hard copy and disk that are created from End of Report are filed for 6 months.

ANNEX 3 TAMMS/Tab a. STAMIS Operations/Automation Enablers

1. PURPOSE: To identify Logistic Automation Systems and Enablers available to JMRC

OPRGRP personnel and to assign responsibilities to the key personnel in maintenance.

2. GENERAL: The Army has been using automated information systems for years. Most of these systems were developed prior to the establishment of the world-wide-web and as a result, were developed by functional organizations meeting previously manual systemic needs. While improvements in the interoperability of these systems has been improved upon over time, most of these early systems are still largely independent a do not interface well with other Combat Service Support systems (CSS).

3. VSAT (Very Small Aperture Terminal): A satellite communications system that gives a forward-deployed combat service support (CSS) units communications capabilities equal to those used in garrison. The system, CSS Very Small Aperture Terminal (VSAT), can be operational within an hour of a unit's arrival in the theater.

(a) Description: Is a two-way satellite ground station with a dish antenna that is smaller than 3-meters. VSAT data rates typically range from narrowband up to 4

Mbit/s. VSATs access satellites in geosynchronous orbit to relay data from small remote earth stations (terminals) to other terminals (in mesh configurations) or master earth station "hubs" (in star configurations).

(b) Use: VSAT, when used in connection with the Multi-Media Communications

System and the CSS Automated Information Systems Interface, provides worldwide voice, video, and data communications capability for forward operating bases. With this system, CSS units can share documents, process requisitions, conduct online meetings, send and receive text messages, and use the system as a short-range telephone. The system acts as a combat multiplier by increasing operational readiness while reducing the downtime of combat systems.

4. Combat Service Support Automated Information System Interface (CAISI):

(a) Description: The CAISI allows combat service support (CSS) automation devices to network within support areas and to electronically exchange information via tactical or commercial communications. CSS satellite communications

(SATCOM) provide an easy-to-use, transportable commercial SATCOM link to extend broadband information exchange to anywhere in the world, and provide full integration in the Global Information Grid (GIG).

(b) Use: CAISI is a deployable wireless LAN infrastructure that can link up to 40 tents, vans, or shelters in a deployed seven-square kilometer area. It includes FIPS

140-approved encryption (Federal Information Processing Standards security requirements) for sensitive but unclassified (SBU) traffic. CSS SATCOM uses commercial off-the-shelf auto-pointing remote satellite terminal hardware repackaged in fly-away transit cases. CSS SATCOM is totally Internet protocol

(IP)-based and connected to the Army’s Land War Net and DOD GIG. CAISI and

CSS SATCOM are operated by combat service support personnel. CAISI can also serve as a hub in conjunction with the VSAT to increase available ports.

5. Army Battlefield Command System (ABCS): Links automation assets, communications media, and operational facilities to support commanders and their staffs in collecting and analyzing information, developing plans and orders, and monitoring the tactical battlefield, while simultaneously planning future operations.

DESCRIPTION AND SPECIFICATIONS –

(a) Description: Army Battle Command System (ABCS) is the Army’s component of the Global Command and Control System (GCCS). It is a complex system of systems that provides the mechanism to receive and transmit information among the joint forces. The ABCS consists of subsystems for the battlefield functional areas (BFA), each of which supports and provides information to other systems, and provides situational awareness of the battlefield. By integrating the ABCS components through the Joint Common Database (JCDB), the common tactical picture can be viewed at any workstation, to the operator’s specific requirements.

In addition, ABCS subsystems provide an array of specialized capabilities and applications for commanders of diverse units at all levels.

(b) Use: In regards to our mission we would utilize the Combat Service Support –

Combat Service Support Command System (CSSCS): An automated system for logistical, medical, financial, and personnel support to assist decision-making and the battle planning process.

6. Global Command and Control System (GCCS):

(a) Description: GCCS is an automated information system designed to support deliberate and crisis planning with the use of an integrated set of analytic tools and flexible data transfer capability. It is the mid-term implementation of the

Command, Control, Computers, Communications and Intelligence for the Warrior

(C4IFTW) concept, which fulfills a requirement for a capability to move a U.S.

fighting force on the globe at anytime and to provide it with information and direction to complete its mission. GCCS provides a fused picture of the battle space within a modern C4 system capable of meeting Warfighter needs into the

21st century. GCCS incorporates the core planning assessment tools required by combatant commanders and their subordinate joint force commanders and meets the readiness support requirements of the Services. GCCS has replaced the

World-wide Military Command and Control System (WWMCCS) and is the system of record. Functionality and operational improvements are fielded/distributed in the form of version releases.

7. Combat Service Support Command System (CSSCS):

(a) Description: The Combat Service Support Control System (CSSCS) is a decision-support system that assists commanders and their staff in planning and executing

CSS operations. The CSSCS will rapidly collect, store, analyze, and disseminate critical logistics, medical, financial, and personnel information. Currently, CSS commanders and staffs manually gather, correlate, and analyze volumes of technical data from the existing Standard Army Management Information

Systems (STAMIS) and the Army Tactical Command and Control System. The

CSSCS extracts summary information from the STAMIS; accepts input from other elements of the CSS community; and exchanges information with other automated systems to evaluate CSS information about the force-level commander’s tactical courses of actions. The CSSCS is the combat service support component of the Army Battle Command System (ABCS). The CSSCS is organic to CSS units and headquarters staffs, within the maneuver brigades, separate brigades, armored cavalry regiments, divisions, corps, and echelons above corps. The CSSCS is comprised of computer units, common operating environment software, and CSSCS-unique software. The CSSCS is deployable in a tabletop configuration, with or without storage/transit cases, and can also be housed in the family of Standardized Integrated Command Post Systems (SICPS).

While the current sources of CSS data are the STAMIS systems and manual entry, the future data sources are automated links to FBCB2 & GCSS-A.

(b) Use: Provide timely situational awareness and force projection information to determine capability of supporting current operations and sustaining future operations as a key logistical enabler for the Army Vision.

8. Standard Army Management Information Systems (STAMIS):

(a) Unit Level Logistics System (ULLS)

(b) Standard Army Maintenance System (SAMS)

(c) Standard Army Ammunition System (SAAS)

(d) Standard Army Retail Supply System (SARSS)

(e) Standard Property Book System - Redesigned (SPBS-R)

(f) Standard Installation Division Personnel Information System (SIDPERS)

(g) Theater Army Medical Management Information System (TAMMIS)

(h) DA Movement Management System-Redesigned (DAMMS-R)

(i) Transportation Coordinators Automated C2 Information System (TCACCIS)

(j) Transportation Coordinators Automated Information for Movement System

(TCAIMS)

9. Standard Army Maintenance System Enhance (SAMS-E): SAMS-E is located at any unit that has an organizational maintenance facility. It automates vehicle dispatching, PLL management, and TAMMS. SAMS-E interfaces with SARSS-1, SAMS-1, IVIS, vehicle sensors, and PBUSE. The AIT Interrogator is connected directly to the SAMS-E.

SAMS-E is linked to the wholesale supply system through OSC.

10. Standard Army Maintenance System (SAM):

(a) SAMS-1 is an automated maintenance management system used at the direct support (DS) Maintenance Company and FSC found in the separate brigade, division, corps, and echelons above corps and the general support (GS)

Maintenance Company at echelons above corps. The system automates work order registration and document registers. It automates inventory control and reorder of shop and bench stock as well as automating work order parts and requisitioning. It produces pre-formatted and ad hoc reports and allows extensive on line inquiry. SAMS provides the capability for automated processing of DS/GS maintenance shop production functions, maintenance control work orders and key supply functions previously performed manually. Requisitions are prepared automatically and automatic status is received from SARSS-1. It also provides completed work order data to the LOGSA for equipment performance and other analyses. SAMS-1 automates maintenance documentation and information gathering and transmittal; provides management of work orders and work order tasks; allows transfer of repair parts and/or dues-in between work orders and shop stock; accounts for direct, indirect, and non-productive man-hours; simplifies and standardizes the collection and use of maintenance data; improves readiness management and visibility by providing equipment status and asset data; raises the quality and accuracy of performance, cost, backlog, man-hour, and parts data through improved maintenance management. SAMS-1 operates on commercial off the shelf hardware with a Master server/workstation and a Remote workstation. The server and the remote form a local area network (LAN). The server is the central computer, responsible for managing the LAN. In addition to managing the LAN, the server is a workstation. SAMS-1 has interfaces with the following systems:

Standard Army Maintenance System Enhance – (SAMS-1E)

Standard Army Maintenance System (SAMS-2)

Standard Army Maintenance System –Installation /Table of Distribution and

Allowance (SAMS-I/TDA)

Standard Army Retail Supply System (SARSS-1)

SARSS Gateway

(a) SAMS-2 is an automated maintenance management system used at the main support battalion (MSB), the forward support battalion (FSB) in the division, and the materiel office of functional maintenance battalions and support groups in the corps and echelons above corps (EAC). It is also used at the material management center (MMC) and in the division support command (DISCOM); corps support command (COSCOM), and the theater Army area command (TAACOM). SAMS-

2 is used by the field commands to collect and store equipment performance and maintenance operations data. This is used to determine guidance to be given to their subordinate maintenance units. SAMS-2 provides the capability of monitoring equipment non-mission capable status and controlling and coordinating maintenance actions and repair parts utilization to maximize equipment availability. SAMS-2 receives and processes maintenance data to meet information requirements of the manager and to fulfill reporting requirements to customers, higher SAMS-2 sites, and the wholesale maintenance level. Data can be accessed instantly to fulfill management’s needs in controlling, coordinating, reporting, analysis and review. SAMS-2 maintains equipment status by line number and unit within the command; maintains a record of critical repair parts and maintenance problem areas; provides visibility of backlog and planned repair requirements; provides maintenance performance and cost evaluation tools.

SAMS-2 provides Maintenance and Management information to each level of command from the user to the division or corps, wholesale and DA levels.

SAMS-2 collects, stores, and retrieves maintenance information from SAMS-1 sites, and allows managers to coordinate maintenance workloads. SAMS-2 passes significant maintenance and supply information to higher commands for the purpose of maintenance engineering and readiness reporting. SAMS-2 has interfaces with the following systems:

Standard Army Maintenance System Enhance – (SAMS-1E)

Standard Army Maintenance System (SAMS-1)

Standard Army Maintenance System (SAMS-2)

Standard Army Maintenance System (SAMS-I/TDA)

LOGSA

Combat Service Support Control System (CSSCS)

11. Standard Army Retail Supply System (SARSS): Standard Army Retail Supply

System: SARSS is the primary automation system for supply units operating in the

Brigade and Division areas. It processes customer requests from ULLS, Standard Army

Maintenance System (SAMS) and Standard Property Book System-Redesign (SPBS-R).

SARSS maintains stock record balances and reports them to the higher echelon SARSS systems. SARRS functions are:

Financial management

Asset visibility

Redistribution/referral

Accountable records

12. Global Combat Support System – Army (GCSS-A): Existing CSS information management and operations systems are focused mainly on vertical information flows within a stovepipe structure. Current automation systems, where available, operate at single locations with no interface or non-real time interoperability among other systems.

Communications is generally reduced to the use of “sneaker net” – the passing of floppy diskettes. A key issue identified in the Total Distribution Action Plan after Operation

Desert Storm was the “lack of a multifunctional STAMIS using a common shared relational database.” For these and other reasons, the Chief of Staff of the Army (CSA) has identified logistics automation as one of the Army’s top three programs. To that end, he has called for a Revolution in Military Logistics.

(a) Description: GCSS-Army is being designed to support Army CSS including the functions of manning, arming, fixing, fueling, moving, and sustaining. The system will establish interfaces with other CSS automated systems in order that users can maximize the amount of information available with the minimum amount of data entry. It is a commercial off the shelf (COTS) hardware solution, using the

Windows NT operating system, and programmed using Oracle Design. GCSS-

Army is following a three-tier developmental strategy: Tier 1 – Initial Operational

Capability (Integration and Modernization). In this tier, an initial operational capability (IOC) is developed through incremental integration and modernization of current tactical logistics STAMIS. The principal ones to be integrated include

ULLS, SARSS, SPBS, SAAS, and SAMS. The products of this integration are the six GCSS-Army modules listed below:

(b) Supply/Property: will integrate supply operations and property accountability in units.

(c) Maintenance: integrates ground, aviation, and water equipment maintenance operations at all levels.

(d) Ammunition Supply Point integrates Class V management and operations at

ASPs.

(e) Supply Support Activity integrates supply management and operations at the

SSAs.

(f) Integrated Materiel Management integrates supply, property, ammunition, and maintenance management in the MMC.

(g) Management that will integrate all the above information, as well as data exchange with other CSS Joint automated systems.

All components of GCSS-Army must communicate flexibly. The system is designed to take advantage of all available methods of communications including tactical packet networks, circuit switch networks, wireless networks, defense information switching network, telephone networks, and strategic communications capabilities. Sneaker net is used only as necessary to transfer information on removable media. The initial focus is on Logistics Modernization (LOG MOD), which is intended to privatize the functions of the current wholesale SDS, and CCSS automated systems. Full Operational Capability

(joint Integration). This tier will implement all required interfaces with automated systems in the joint community, national sustaining base, and applicable allied systems.

Access is available to CSS data sources and complete interoperability is achieved when operating in the open system environment. This capability will provide a seamless, integrated, modular, interactive, and interoperable CSS automated system for the total

Army.

ANNEX 3 TAMMS/Tab b. WebLIDB

1. PURPOSE: To identify WebLIDB capabilities available to personnel assigned to, attached to, or supported by the JMRC OPSGRP.

2. GENERAL: WebLIDB is a true web-based application that provides customer-focused reports utilizing the Internet Explorer web browser. Like commercial web sites, WebLIDB provides instantaneous query results and quick response times for larger reports. WebLIDB supports the Army’s key mission areas of transformation, readiness, sustainment and asset management/visibility of major weapon systems. It serves as the backbone of the Army’s logistics support hub through integration with the GCSS-A and the LMP. WebLIDB is fully Windows-compliant, which means reports and graphics can be exported to your favorite office automation software such as Microsoft Word, Excel, PowerPoint, Access, and more.

(a) Additional capabilities include:

Access to ETMs directly from the Publications Selection module or the ETM

Search module.

Generation of multiple reports during the same session without waiting for the first report to complete.

Automatic (unattended) report generation using the Scheduled Reports features.

3. ACCESS: WebLIDB can be accessed through the LOGSA Home Page or through the

WebLOG site. Customers who do not have an LIDB login ID or password must complete a LOGSA SAR. (Enter LIDB/WebLIDB in the Request LOGSA Data/Service block.)

4. LIDB is an application that provides all customers with near real-time, accurate, logistics information.

(a) LIDB Overview: In 1993, the USAMC LOGSA was formed by the consolidation of the AMC SRAs. These agencies provided logistics support to organizations at all levels of the Army, DOD, and other military services. The systems developed and maintained independently within the SRAs continue to be maintained independently within LOGSA. LIDB is being developed to integrate these separate systems into a single data base accessible through a single application.

The development approach includes the use of COTS client server technologies.

(b) LIDB integrates and replaces the following databases:

(c) EOPDB (d) CBS-X (e) ACLDB (AMDF & SB 700 20)

(f) WOLF (g) FDB (h) UIT

(i) CDDB (j) REQVAL (k) MIDR

(l) DODAAF (m) DAMPC (n) Army Master RIC javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this) javascript:kadovTextPopup(this)

(o) Field data sources are received continuously and the LIDB is updated as follows:

RIDB (daily)

Supply Demands (three times per day)

Maintenance (three times per day)

Major Item Assets (three times per day)

ADM (bi-monthly)

Force Data (two times per week)

ACLDB (three times per day)

Usage Data (daily)

5. Technical Support:

If you have questions about the installation or operation of WebLIDB, contact LOGSA as follows:

For software and WebLIDB technical support, call the LOGSA Help Desk:

OCONUS DSN: 312-645-7716

CONUS DSN: 645-7716

Toll Free: 1-866-211-3367

Commercial: 256-955-7716

Email: helpdesk@logsa.army.mil

For functional support, contact the LOGSA Hotline:

Phone: 1-800-878-2869

DSN: 645-0499

Commercial: 256-955-0499 http://www.logsa.army.mil

Mail: USAMC LOGSA

Redstone Arsenal, AL 35898-7466

For logistics data/application assistance, contact the Logistics Quick Reaction Team through the LOG911 assistance system at:

https://weblog.logsa.army.mil/log911/index.cfm email: logart@logsa.army.mil mailto:helpdesk@logsa.redstone.army.mil

ANNEX 3 TAMMS/Tab c. ILAP/Requisition Status

1. PURPOSE: To identify ILAP capabilities available to personnel assigned to, attached to, or supported by JMRC OPSGRP.

2. GENERAL: The Integrated Logistics Analysis Program (ILAP) is an evolving application that integrates information from the different STAMISs and provides logisticians and resource managers with a user-friendly, relational database. ILAP draws information from the supply, maintenance and financial areas (at local, regional and national levels) and converts the information into a manageable database with predetermined reports. These reports allow multiple users access to information that provides logisticians instant access to current, integrated and timely information. In order to understand ILAP, you must first understand the requisitioning, maintenance and financial databases that feed into ILAP.

(a) Figure 1 shows the information flow through a divisional unit. This same structure can be applied to a nondivisional unit with a little modification. At the lowest level, the company, requests are processed through the Property Book Unit

Supply Enhanced (PBUSE) and the Unit Level Logistics System-Ground or

Aviation (ULLS-G or A) or Standard Army Maintenance System (SAMS-1E).

Supply personnel routinely process Class II (general supplies), Class III(P)

(packaged petroleum, oils and lubricants), and Class IV (construction and barrier materiel) requests through ULLS-S4 to their direct support unit’s (DSU’s)

Standard Army Retail Supply System (SARSS-1) site. Maintenance personnel also process Class IX (repair parts) requests through SAMS-1E/ULLS-G to their supporting DSU’s SARSS-1 site as well as maintenance data through the supporting Standard Army Maintenance System (SAMS-1) site. At the same time the company is requesting parts and classes of supply, the company also is receiving status back from the supporting SARSS-1 and SAMS-1 sites.

(b) At the supporting maintenance site, requests are processed through SAMS-1 into

SARSS-1. The division property book office orders through the Standard Property

Book System-Redesigned (SPBS-R) and routes the request through its servicing

SARSS-1 site. From all of the SARSS-1 sites across the division, information flows through the division materiel management center’s (DMMC’s) SARSS-2A site, through the corps’ SARSS-2AC/B system and then into the Defense

Automated Addressing System (DAAS). DAAS routes the data to the appropriate

National Inventory Control Point (NICP).

(c) DAAS routes the information into three financial systems. They are the Standard

Army Financial Inventory Accounting and Reporting System (STARFIARS), the

Standard Financial System (STANFINS), and the database Commitment and

Accounting System (dCAS). STARFIARS is managed and owned at the installation level as the primary accounting system generating, recording and reporting interfund transactions. STARFIARS also processes supply and equipment data for STANFINS transactions. STARFIARS inputs information to and receives information from STANFINS. STANFINS is managed by the

Defense Finance and Accounting Service (DFAS) and processes all financial data throughout the Department of Defense. Finally, dCAS, also owned by DFAS, is the commitment ledger system that records and manages current fiscal year committed funds and funding data. ILAP captures and integrates information from these three financial programs and processes the data into a helpful, manageable format.

Figure 2 illustrates all of the programs, to include the financial and logistics automated systems that feed into ILAP at the division level. The data has been forwarded to the appropriate levels, necessary actions taken, records established, and status posted. Copies of many files from these STAMISs feed into ILAP. ILAP takes that data and manipulates it into a relational database that logisticians and resource managers can use to analyze information from a single report to accomplish the same mission that used to require analyzing the information from several reports or STAMISs.

3. ILAP Users:

(a) At division level, the comptroller inputs the financial data from dCAS into ILAP as well as unit quarterly/annual targets. The comptroller then manages the division’s budget through queries aimed at checking individual unit and DSU budgets, authorized stockage lists (ASLs) budgets, roll-ups by accounting process code (APC) or Department of Defense Activity Address Code (DODAAC), due-ins and due-outs, and high-dollar reviews.

(b) G4 uses ILAP for fleet readiness trends and general planning purposes.

(c) DMMC, maintenance managers can check Request Order Numbers (RONs) and

Document Order Numbers (DONs), status of document numbers, national…