u.s. army logistics innovation agency unclassified acquisition manager’s guide to cloe/cbm+...

U.S. Army Logistics Innovation Agencyhttps://lia.army.mil

UNCLASSIFIED UNCLASSIFIED

Acquisition Manager’s Guide to CLOE/CBM+

(AMG2CC)And

Dashboard

25 February 2015

AMG2CC Conference


2

Agenda

Background & Staffing Process Staffing Comments, Feedback and Observations AMG2CC Overview Dashboard Overview and Demonstration DASA-APL Path Forward Wrap-Up


3

BACKGROUND


AMG2CC Purpose and Approach

4AMG2CC and Dashboard Facilitate Measurement Of Implementation ProgressAMG2CC and Dashboard Facilitate Measurement Of Implementation Progress

Checklist-driven dashboard tool

The purpose of AMG2CC is to assist Platform-Level PMs to be interoperable with the Logistics Enterprise through the CLOE and to Achieve CBM+ Functionality Provide “how to” guidance to PMs for selecting and implementing CLOE/CBM+ capabilities Support Self–Assessment of CLOE/CBM+ progress via an accompanying dashboard tool

“How to” guidance for implementing CLOE/CBM+

Implementation progress reported at system acquisition reviews


5

AMG2CC Staffing & Trial-Use Period

2015

PM-HBCT

CECOM LRC & PM

ASA(ALT) Vector Check

PM-STRYKER,

JLTV, AMPVPM EE&SS

PM APACHE

Log

TACOM ILSC

2014

AMG2CCAMG2CC AMG2CCRev 1

AMG2CCRev 1

DASA APLGuidance

Memo

ConferenceCoordination

Conference

2013

• Penn State ARL• NAVSEA• USMC


Review - Objectives AMG2CC

How-to, Not A Strategy or Business Case Document

~40 Pages In Main Body, Rest In Appendices

Dashboard Support PM Self-assessment Of CBM+ Topic areas Described In AMG2CC

Staff AMG2CC through Army CLOE/CBM+ stakeholders LIA Conducted Preliminary Staffing With Support From ATEC and The Army Materiel

Command Life-Cycle Management Commands at TACOM, AMCOM and CECOM

ODASA(APL) Promoted staffing Through PEOs/PMs For Trial Use Period

Wrap-Up Conference & Workshop Provide Update to Stakeholders on Staffing Process

Provide Penn State ARL, NAVSEA and USMC Perspectives on RCM and CBM+

Provide ODASA (APL) Path Forward for AMG2CC and Dashboards

6


7

Update Selection of Lead Organization for Army CBM+ Store & Forward (SaF)

Implementation Lead Organization: PEO EIS / PD-AMIS; Supporting Organizations: CASCOM, HQ AMC,

G-4/LIA, TACOM/AMCOM/CECOM LCMCs, CERDEC

Recent CBM+ Activities AMC CBM+ 5 Year Plan CASCOM CBM+ CONOPS CBM+ SaF Problem Statement CBM+ SaF Course of Action Analysis and Recommendations

Continuing Efforts Army Integrated Logistics Architecture (AILA) CERDEC CBM+ Communication Systems Architecture (CCSA) Common CBM+ Architecture (CCA)

Governance Army CBM+ Executive Steering Committee (ACSC) – In addition to AMC G-3/4; G-44(M) and

CASCOM Chief of Ordnance added as Co-Chairs HQDA Business Process Council and Army Business Council


8

Comment Summary, Feedback & Observations


9

Current Status: Comments To-Date# Organization # Comments

1 ASA(ALT) ASA(ALT), Director of Policy & Staff 28

2

LIA (CLOE)

CLOE 26

3 AILA (Govt & contractor teams) 30

PNNL 114

5 HQ AMCHQ, AMC CBM+ Systems Engineering IPT 31

6 ATEC IPS Evaluator, Mounted Systems 57 PEO Soldier 298

PM

PM-ABCT (VHMS) (CPC) 29

9 PM-GCV ILS 8

PM-ABCT Govt 1810

11 JNN 712 JLTV 6

13 CERDEC CERDEC CBM+ 25

14 UNIVERSITY PSU ARL 5

TOTAL COMMENTS 258

Twelve Organizations

Fourteen Reviewing

Teams

258 Comments


10

Feedback1. Positives

a) All Stakeholders Liked The Concept Of The Dashboard.

b) No Stakeholder Disagreed With The Use Of The Dashboard Compliance Gauge In The SQC.

2. Negativesa) None; The 262 Written Comments Received Were All Constructive

Criticisms.

3. Principal Change Recommendationsa) Stakeholders Suggested Scoring Criteria Changes for Dashboard

Categories For Platform Software And Platform COMM


11

Observations3. Surprises

a) Most PM Log Divisions Are Not Familiar With DODAF - They Have To Search To Find DODAF Expertise (PD-MBTS /VHMS Is The Exception).

b) Most PMs We Talked To Do Not Implement RCM. They Do Implement Reliability Programs.

4. Principal Improvement Suggestionsa) Incorporate Dashboard Scoring Criteria In The Body Of The AMG2CC.

b) Have A CLOE-CBM+ Acquisition SOW Template In The AMC2CC for New Programs.

c) Need Tighter Synchronization Between CAPDEV and MATDEV WRT Army RCM Policy

12

AMG2CC Discussion


13

AMG2CC Topics Introduction, Scope CBM+ Concepts and Platform Examples

Tactical Wheeled Vehicles (MRAP & FMTV) Fighting Vehicles (Abrams, Stryker) Aircraft (AH-64) C4ISR (SICPS w/TQG)

CLOE/CBM+ Implementation Assessment Topics (6) RCM DODAF Architecture Standards and the CLOE STDV-1 CLOE/CBM+ Hardware and Software Infrastructure CBM+ Data Categories, Routing and Formatting Platform Communication Capabilities


AMG2CC Topics Dashboard

Reliability - Centered Maintenance (RCM)

2 CLOE/CBM+ DODAF Architecture

3 Data Standards

4

Network Communications

5

CBM+ Hardware & Software

6

CBM+ Data Categories

1

Each Topic Addresses:1. Concept2. Policy3. Standards4. Checklist

14

Dashboard

Cites Weapon System Examples

of Hardware & Software

Implementation

Cites Weapon System Examples

of Hardware & Software

Implementation


15

Army Platform Examples of CBM+ Imple-

mentation

Acft C4ISR

MRAP FMTV StrykerPM-HBCT(VHMS)

AH-64DSICPS

w/TQG1

Type Application

SAE J1708 & SAE J1587 XSAE J1939 X X X X (Pilot)Mil-Std-1553 Avionics, Turret, Weapons X XCAN Bus Consumables, weaponsEthernet C4ISR X X X

Component Source or Requirement

Drive Train COTS / RCM / Pilot X (COTS) X (COTS) X (COTS) X (RAM) X (RCM) X (Pilot)Consumables X X X X (Pilot)Weapon Systems X X XAvionics / Vetronics X XHigh-Failure X XHigh-Cost X XMission Critical X X

Dedicated X X (MSPU)2

Shared XNone X X

Type Application

Satellite ITV X (MTS3) X (MTS)Radio (SINCGARS/EPLRS) C2 (FBCB2 / JBC-P) X X X XWI-Fi CBM data Xfr X (pilot)

Type Application

Digital LogBook Interface to Log IT X (ACN4)

IETMTroubleshooting, Repair, PMCS

X X

VHMS / HUMS Health Management X (VHMS) X X (HUMS) X (Pilot)CM / AIT Config Mgmt X X

Type ApplicationJDMS5 or JTDI msg and file management

Message, interface and data file management

X (Pilot) X (JDMS) X (JTDI) X (Pilot)

Hull / Drive Train / GenSets /

ExamplesTWV

Digital Platform BackboneData Bus

Sensor Grid

RAM or RCM-determined for CBM

FV

Embedded SoftwareApplication Software

Embedded Communications

Embedded ComputingComputer, System health

Systems Software

16

DASHBOARD OVERVIEW


17

Dashboard(s)

There Are Two Dashboards Dashboard 1

A Worksheet-style Dashboard With The Checklists For Five Of The Six CLOE-CBM+ Compliance Topic Areas In The AMG2CC, Which Is Used To Build The Second Dashboard

Dashboard 2 A Dashboard Without The Checklists, Adding RCM Status (Completing the 6

CLOE-CBM+ Topic Areas)

Why Have Two Dashboards? Cleaner Presentation of CLOE/CBM+ Implementation Topics Without Clutter

on the GUI.


18

What The Dashboard(s) Are The Dashboards Are Adobe Flash Objects, Created Using A Software Program

Called SAP Dashboard. As Flash Objects, They Can Be Embedded License-free In Microsoft Office Applications, Such As Word And PowerPoint, And Adobe PDF Documents.

The Dashboards Present The Six Implementation Topics In The Form Of Gauges That Give A Sense Of Implementation Progress And Status.

Each Of The Six Topics Are Summed Into One Master Status Gauge


1Platform Worksheet

2Master Assessment

3Black-bezel Gauge Readings on Left are Transferred to Right

4RCM Status Acts as a “Throttle” on the Master Gauge

1Outer Black-bezel Gauges Readings are Determined by Input Mechanisms

2Inner Black-bezel Gauges Sum The Outer Gauges

The Dashboards19


20

Product Support Strategy Metrics Data

Sustainment Schedule O&S Data

MS B MS C IOC FRP FOC Sustainment

BCA

LCSP

CLS Start

Depot Standup

LRIP Contract Award

Blended Partnership Startup

PBL Recompete

Avionics PBL

PBL Recompete

Sustainment Approach Current (initial CLS covering total system)

Future (sub-system based PBL contracts)

Issues Shortfall in O&M funding in FYDP

Reliability and availability estimates are below goals

LCSP requires update before DAB

Resolution POM request for O&M restoration submitted

Reliability improvement plan with clear RAM goals up for final signature

LCSP in draft

BCA BCA BCA

Cost ElementAntecedent

CostABC Original

BaselineABC Current

Cost

1.0 Unit-Level Manpower 3.952 5.144 5.750

2.0 Unit Operations 6.052 6.851 6.852

3.0 Maintenance 0.739 0.605 0.688

4.0 Sustaining Support 2.298 2.401 2.401

5.0 Continuing System Improvements 0.129 0.025 0.035

6.0 Indirect Support 1.846 1.925 1.956

Total 15.046 16.951 17.682

Cost based on average annual cost per squadron

Total O&S Costs Antecedent ABC

Base Year $M 102,995.2 184,011.9

Then Year $M 245,665.3 395,147.2

SAMPLE PROGRAM: “ABC”

Today

Date:

MetricAntecedent

ActualOriginal

GoalCurrent

Goal

Current Estimate/

Actual

Materiel Availability 76% 80% 77% 71%

Materiel Reliability 37 hrs 50 hrs 50.5 hrs 48 hrs

Ownership Cost 245.6B 385.5B 395.1B 395.1B

Mean Down Time 12 hrs 20 hrs 18 hrs 15 hrs

CLOE/CBM+ Compliance Assessment

Sustainment Quad Chart with CLOE/CBM+ Implementation Assessment


PM Self-Assessment Example

21


22

PM ABCT (VHMS) Platform Self-Assessment


Dashboard Operation(Separate Demonstrations)

23


CCA Discussion

24CCA: Common CBM+ Architecture


What is the CCA? WHAT: The CCA Is An Integrated Architecture Description

Which Describes The CBM+ Infrastructure For End-to-End CBM+ Capabilities And Contains Metrics For Analysis.

WHY: Solutions For Achieving CBM+ capabilities for A MATDEV Will Vary. However, The Infrastructure Which Those Solutions Utilize Is Common Across The Army.

25


Value of the CCA• Reduces Risk

• Provides a Common Approved Infrastructure Verified and Validated by ASA(ALT) and TRADOC

• Ensures Alignment to the CLOE• Ensures Interoperability with LOGSA and the

CCBMDW

• Reduces Cost and Schedule • Single Integrated Communication Solution vs

Multiple• Shortens Development timelines• Promotes Data Re-Use• Eliminates Redundant Efforts

• Provides Architecture Analysis• Capability to perform SoS Interoperability Analysis• Network Performance & IA Analysis• Supports and Leverages Technology Insertion• Supports Effective Decision Making

• Support Compliancy to Army and DoD• AILA Integrated Achieved through the CCA• Supports All PM efforts in CLOE Compliance (AMG2CC)• Compliant with: CJCSI 6212.01F, AR 70-1, AR 750-1, DoDI

4151.22, etc.

PM B

PM C PM A

Data

Function

Services

Standards

Common Standards

Common Services

Function Specifics

Data Specifics

Redundant Efforts Common Infrastructure

Vs


27

What is at the Core of the CCA?• End-to-End “Common” CBM+ Infrastructure

encompassing Information and Network Systems• 26 DoDAF v2.02 Compliant Views• 50 Key Systems (Information and Transmission)• 35+ Platform Placeholders include ground, air and

C4ISR platforms.• 300,000+ Data Attributes organized to provide

efficient analysis with minimal effort to support effective decision making

Data

Attributes


28

Integration Process

• The AMG2CC identifies at a high level how to integrate with the CCA.

• The CCA Integration Plan v1.0 is comprised of the following topic areas (Appendix C of the AMG2CC):

– Integration Methodology– Pre-Integration Check List– Purpose & Scope Consistency– Integration Boundaries– Architectural Effectiveness Measurement– Integration Methods– IV&V Process– Transition to Integrating Stakeholder (PM / LCMC)


29


30

Path Forward


31

DASA APL Path Forward

Sustainment Quad Chart Sustainment Quad Chart Is Preferred Approach for CLOE-CBM+

Implementation Progress Reporting Institutionalize in Army Policy (e.g., AR 700-127)

Continuing AMG2CC Support (TBD) DASA (APL) LIA ATEC HQ AMC

Institutionalizing AMG2CC and Dashboard DA PAM proposal


32

Discussion

u.s. army logistics innovation agency unclassified acquisition manager’s guide to cloe/cbm+...

Documents

cbm saf implementation

cbm functionality

cerdec cbm initiative

army cloecbm stakeholderslia

purpose of amg2cc

cloecbm amg2ccand dashboard

army business council

preliminary staffing