LOGISTICS SYSTEMS ARCHITECTURE FOR ACTIVE ARMY, RESERVES, AND AMC

DAAS

CCSSIMMC

AMI

SARSS-Gateway

SARSS-2AC/B(CMMC)

SARSS-2AD(DMMC)

SARSS-1(SSA)

ULLS(Unit)

ULLS(Unit)

SARSS-1(INSTALLATION

DOL)

SAMS(DSU)

SAMS(DSU/GSU)

ICP(DLA, GSA,

et al)

AMCISS(AMCINST)

SDS(MAINTDEPOT)

TAV

STARFIARS-MOD

STANFINS

DSS(DIST

DEPOT)

DFAS

RASFIARS

SOMARDS

Interfund BillNAMI

F02, F08, F09

ILAP

ILAP

Legend Financial Systems

Supply Systems

Management Reporting System (ILAP)

Management Reporting System (TAV)

Other Systems

AMCRETAIL

ARMYRETAIL

Wholesale

AFMIS

FAS

IFS

TAMMIS

PRISM

Shortcomings

• Multiple points of sale• Multiple levels of

ownership• Multiple levels of

financial accounting• Limited asset visibility• Redundant Inventories• Limited redistribution• Variable credit• Non standard business

practices• Sub-optimized

requirements determination

Changes

System Architecture Circa 2000

ACIIPS

OCTOBER 2000 SYSTEMS ARCHITECTURE FOR ACTIVE ARMY, RESERVES, AND AMC (Before SSF)

DAAS

CCSS AMI

SARSS-Gateway

SARSS-2AC/B(CMMC)

SARSS-2AD(DMMC)

SARSS-1(SSA)

ULLS(Unit)

ULLS(Unit)

SARSS-1(INSTALLATION

DOL)

SAMS(DSU)

SAMS(DSU/GSU)

ICP(DLA, GSA,

et al)

AMCISS(AMCINST)

SDS(MAINTDEPOT)

TAV

ISB

STANFINS

DSS(DIST

DEPOT)

DFAS

SOMARDS

Interfund BillNAMI

F02, F08, F09

ILAP

ILAP

Legend Financial Systems

Supply Systems

Management Reporting System (ILAP)

Management Reporting System (TAV)

Other Systems

ARMYRETAIL

AFMIS

FAS

IFS

TAMMIS

PRISM

Changes

System Architecture Circa 2000

ACIIPS

JUNE 2003 SYSTEMS ARCHITECTURE FOR ACTIVE ARMY, RESERVES, AND AMC (After SSF MS 3)

SPBS-R

IMMC

DAAS

CCSS AMI

SARSS-Gateway

SARSS-2AC/B(CMMC)

SARSS-1(SSA)

ULLS(Unit)

ULLS(Unit)

SARSS-1(INSTALLATION

DOL)

SAMS(DSU)

SAMS(DSU/GSU)

ICP(DLA, GSA,

et al)

AMCISS(AMCINST)

SDS(MAINTDEPOT)

TAV

ISB

STANFINS

DSS(DIST

DEPOT)

DFAS

SOMARDS

Interfund BillNAMI

F02, F08, F09

ILAP

Legend Financial Systems

Supply Systems

Management Reporting System (ILAP)

Management Reporting System (TAV)

Other Systems

ARMYRETAIL

AFMIS

FAS

IFS

TAMMIS

PRISM

Changes

System Architecture Circa 2000

ACIIPS

PBUSE

IMMC

Current System Architecture (November 2007)Note: There is one instance of LMP fielded at CECOM

and one custom fielding of GCSS-Army (PBUSE)

Legacy Systems Replacement

LMP will replace:Commodity Command Standard System (CCSS)Standard Depot System (SDS)

GCSS-Army will replace: Unit Level Logistics System (ULLS)Standard Army Maintenance System (SAMS)Standard Army Ammunition System (SAAS)Standard Army Retail Supply System (SARSS)Standard Property Book System - Redesign (SPBS-R)Integrated Logistics Analysis Program (ILAP)

GFEBS will replace:Standard Financial System (STANFINS)Standard Operation Maintenance Army Research and Development System (SOMARDS)

GCSS-Army

SAMMS

Arm

y N

at’l

Sust

ainm

ent

Nat

'l(D

LA

)

Nat

iona

lSu

stai

ning

Bas

e GCSS-JointJoin

tO

SD

LIDB

CCSSSDS

Army Evolution

LMP ERP

CSSCS

FBCB2

CSS

Maneuver

BSM ERP

Sin

gle

Arm

y Lo

gist

ics

Ent

erpr

ise

PLM +

Mission: Implement an enterprise solution to execute tactical CSS as

an integral component of the SALE

CURRENT FUTURE

ULLS-AULLS-GSAMS-1

SAMS-I/TDA

SPBS-RULLS-S4PBUSE

SARSS-1SARSS-2AD (partial)

SAAS-MOD ATP/DAO

Cur

rent

STA

MIS

(Tac

tical

)

ILAP / JLWISAMS-2

SARSS-2AD(partialSARSS-2AC(partial)SARSS-GW(partial)

SARSS-2ADSARSS-2AC/BSARSS-GW

SAAS-MMC ASP

FMTP

WIN-T

via

Arm

yTa

ctic

alA

rmy

C2

FLE

FCS / DoDAF (Department of Defense Architecture Framework) Systems(Hi Side)

GCSS-Army Guiding Principles• Enable CS/CSS Transformation• Support the Objective Force• Enterprise-wide integration• Web based (DRID 54) • Employ Industry Best Practices• Employ COTS Software • Enable Distribution Based Log• Integrate CSS & C2 • Drive CSS Re-engineering• Avoid custom techniques & code

Ext

erna

l SA

LE In

terfa

ces

via

PLM

+

Web Browser Access- Any Authorized User- One Picture / One Enterprise

... for about 135,000 Users

GC

SS-A

rmy

Dev

elop

men

t

FUNCTION

BCS3

Maint

Property

SupplySupport

Ammo

LogMgmt

MMCIntegration

Chg in TechApproach

PLM+ External Interfaces• Blueprinting will include the following interfaces which have been

identified in the JROC ORD

TMIP

GCSS-Army

LMP DIMHRS

TC-AIMS II

LIDB

MC4MTS

EAI / XI Tool

EAI / XI Tool

TMDE

GCSS-MCATLASS II+

LAAWS

LMP

OTHER

BCS3CSSCS

BSM

STAMIS

FBCB2CC/JTF

TAMIS-R

DFAS

WARS-NT

TAMMIS/DMLSS

FMTP

Joint SystemARMY SystemDoD System

Legend

GUARD

FCSLDSS

PLM+ will use SAP’s XI Component of

NetWeaver to interface with the legacy systems as

confirmed during blueprinting.

PLM

+PLM

+

8

Common Logistics Operating Environment (CLOE)

Establishing Logistics

InteroperabilityCurrent Future

Army Joint

Vision: To Enable The Army To Operate In A Fully Integrated Joint Logistics Environment That Fuses Information, Technology And Anticipatory Logistics Processes That Soldiers Trust

To Provide The Right Support At The Right Time And In The Right Place

Mission: To Create A Common Logistics Operating Environment That Provides Domain Wide Visibility, Supports Unity Of Effort, And Enables Rapid, Precise

Response Across The Full Range Of Military Operations

Tactical

Platform Enablers

Strategic

Operational

Platform/Soldier

Crew DisplayData Bus

Data BaseReasoner

Maintenance Aid

Sensors

IETMs

AIT/SIMSerialized Item

STAMISGCSS-A Interface

ERP

Antenna

ED/EP

CBM+ Is an Integral component of a CLOE…

CLOE AILA and Emerging Logistics Systems

The Army’s Common Logistics Operating Environment (CLOE) initiative aims to synchronize logistics concepts, organizations, and processes, as well as the latest generation of technologies, into a single operational and technical architecture for the force structure of the future. CLOE’s vision is an integrated logistics architecture that fuses information, logistics processes, and platform-embedded, sensor-based technologies to support tactical, operational, and strategic sustainment.

The CLOE strategy allows the Army to transition to a unit-centric focus for specific units of action (UA) and their supporting unit of employment (UE). CLOE sets common data standards, specifications, and protocols necessary to integrate platform, information, and C3 technologies for use in the Objective Force logistics sustainment. CLOE capabilities represent a unique blend of embedded command, control and communications (EC3) interfaces and equipment configurations designed to integrate platform-level equipment and consumable status information with the Army’s logistics enterprise environment. The AILA is a major initiative of the CLOE Program. It is the Deputy Chief of Staff, G-4’s overarching logistics architecture developed in accordance with DoD Architecture Framework.

The AILA consists of the integration of TRADOC’s validated Operational Views (OVs), CIO/G-6 published Technical Views (TVs), and SASG and PM developed System Views (SVs). The architecture is capabilities-based and addresses modularity and transformation. The OVs for version 1.1 of the AILA were validated by TRADOC, and TVs were approved by CIO/G-6 and published in the DoD Information Systems Registry. AILA V 1.3 (which includes V1.2) is scheduled for validation in the Jun 07 timeframe.