The Army is transforming in numerous ways

By Jason Robertson,2014-04-20 19:21
7 views 0
The Army is transforming in numerous ways


Headquarters, Department of the Army

    ODCS, Army G-4, DALO-SMM

    500 Army Pentagon

    Washington, DC 20310-0500

    The Army is transforming the way it conducts maintenance in numerous ways. Most pronounced in this transformation is the Army’s move toward a two-level maintenance

    force structure. Using critical enablers and modern maintenance processes that will allow us to connect the logistician to an integrated, enterprise-wide logistics system, this approach makes us more effective in our ability to rapidly repair platforms by seamlessly collecting critical platform information that can be used to support holistic lifecycle support.

    The fundamental starting point for this transformation is on the platform, and centered on a set of principles termed condition-based maintenance. A number of technology enablers will be digitally integrated on-platform to create an embedded health management capability. The capability includes embedded diagnostics and prognostics, interactive technical manuals, automatic identification technology and unique identification devices, automated logbook, digital preventive maintenance checks and services, an integrated data bus, a platform health management reasoner, seamless ties to the command and control system, and automated status reporting. This set of capabilities incorporates the Condition Based Maintenance Plus (CBM+) initiatives from the Office of the Secretary of Defense. These capabilities are being managed collectively to develop and describe a single logistics operational environment under the Common Logistics Operating Environment (CLOE) program.

    The goal of the CLOE effort is to provide combatant commanders with higher equipment availability using fewer, more capable resources. What ties together the Army’s ability to achieve this more responsive process is the shift from preventive and reactive maintenance processes to condition-based and proactive analytical maintenance processes. Key to the future of Army logistics is the ability to provide the combat commander with relevant, maintenance-based force readiness information at every level. The Army has recognized the potential benefits of these new capabilities and programmed a significant manpower reduction for the Army out-year maintenance workforce. There are companion benefits for other logistics disciplines as the Army


    moves from the current structure of supply echelons to streamlined condensed supply echelons that will substantially reduce the deployment footprint for future operations.

    The Army’s CBM+ implementation plan has several areas designed to ensure successful implementation. First, CBM+ is being incorporated into Army policy regulations that will enable change, lead to a change to related doctrine (tactics, techniques, and procedures), implementation of integrated maintenance processes, and support the funding and fielding of key required enablers that provide the capabilities to allow the implementation of new business processes. The Army is taking the following steps to achieve the end state.

Policy revisions (completed or in work):

    AR 70-1 Army Acquisition Policy

    AR 750-1 Army Materiel Maintenance Policy (March 2005)

    AR 750-43 Test Measurement and Diagnostics Equipment Policy and Program (May 2004)

    TRADOC PAM 71-9 Requirements Determination

    Common Logistics Operating Environment Policy (September 2003)

Requirements documents under continuous review:

    Capabilities development and production documents (CDD and CPD respectively) Enterprise and business process mapping and blueprinting (TLDD and CLOE have already been successfully aligned with the SALE architecture. FCS initiatives are in the process of being aligned. End to End business processes including branches and sequels are being refined.)

Enablers in work or under development:

    Enterprise Resource Planning (ERP) based Single Army Logistics Enterprise Interactive electronic technical manuals (IETMs) (PM LIS, LOGSA)

    Embedded diagnostics (ED) (PM TMDE, and platform PMs)

    Common prognostics and health management (PHM) (PM TMDE)


    Automatic identification technology/serialized item management (AIT/SIM) (Army) Tactical logistics data digitization (TLDD) (PM LIS)

Processes or supporting efforts:

    CLOE Configuration Control Board (AMCOM SED)

    CLOE Systems Integration Laboratory (LTA)

    CLOE simulation and modeling (LTA)

    CLOE business case analysis (LTA)

    Army Maintenance Transformation (AMT) Plan


    National Maintenance Management (AMC)

    Second, the Army envisions that CBM+ will revolve around the construction of a data-centric, platform-based operating environment within the Army Logistics Enterprise that monitors critical maintenance data elements, uses platform-based processors to generate platform-level health management of components and critical systems, and analyzes the data using advanced algorithms. These efforts will use physics of failure for each system and will focus engineering efforts to merge traditional areas (such as system, reliability, design, and controls) to rethink the way we design, build, and support future systems with new dynamic maintenance programs.

    The Army will use the Logistics Transformation Agency (LTA) to synchronize the process and platform configuration control for early implementation of the architecture, and add further enabling technologies as they are developed. This allows the Army to ensure that technology works harmoniously to build future logistics business processes that allow us to institute a CBM+ environment. LTA, in conjunction with the Department of the Army Logistics Enterprise Integrator (DALEI), will develop common data standards, specifications, and protocols that will be used, tested, and updated to ensure the seamless flow of platform-level data to populate the Army Logistics Enterprise information system. What differentiates this approach from other ERP implementations


    is the use of the platform as the basic data source and essential building block for developing all combat requirements in the near future. The platform will track and report the status of consumables, such as ammunition, fuel, food, water, and spares; manage its own health and that of its crew; and interact with the crew, command, and logistician seamlessly to move critical information through both the Army’s command, control, and

    communications system and the logistics enterprise. CLOE is designed to support modularity at its root and allow the automation of logistic status reports. The implementation of the CLOE program increases operational availability through the use of Interactive electronic Technical Manuals (IETMs), embedded diagnostics and prognostics (ED/EP), platform health management (PHM), automatic identification technologies (AIT) and serialized item management (SIM) that will work in harmony to identify and describe damaged or defective components. Item repair can then be accomplished in accordance with the combatant commanders’ priorities and support resources allocated based on mission need. CLOE will also support the movement of data that allows wholesale-level fleet trending, configuration management, and failure analysis to allow Army adjustments to maintenance programs based on service needs as required.

    Version 1.0 of the CLOE operational architecture is being devised for the Stryker brigade combat teams. The environment design is deliberately modular and easily upgraded as each new application is introduced. Current plans call for the architecture to be systematically expanded to include other systems, such as aviation, soldier systems, and the Future Combat System. CLOE will expand, over time, to adopt other new functional capabilities as they become available

    The CLOE operational architecture view is the starting point for systems and technical architecture views that will eventually apply to all Army platforms and systems. The strategy calls for CLOE enablers to be incorporated into designated systems as a part of reset, new system design, or modification programs. Because CLOE affects all Army platforms and logistics enterprise system, and is dependent on system-specific build or modification schedules and standards, the pace of implementation will be affected by


    both affordability considerations and the rate at which new systems are introduced over time. For this reason, the coordinated update of the policy, doctrine, and requirements documents, outlined above, is critical to ensure the Army remains oriented on the CLOE objective, even as future timelines for system-specific implementations are adjusted.

    For the present, the objective of CBM+ is to achieve a common logistics operating environment over the course of the next decade. The CLOE environment directly supports efforts to achieve the Army’s integrated logistics enterprise and to enable joint force interoperability and interdependency, sense-and-respond logistics, network-centric warfare for logistics, and a fully modernized and transformed sustainment environment for the future that supports multifunctional, expeditionary, combined-arms units on a distributed, non-linear battlefield.


Report this document

For any questions or suggestions please email