presentation slides
TRANSCRIPT
1A Warrior’s Approach to Business Architecture
A Warriors Guide to Business Architecture
This Presentation is NOT endorsed or supported by any Government organization. The views, ideas and concepts are solely and exclusively those of the presenter and do NOT represent any official or unofficial policy.
Saving Money and Supporting the Warfighter
2A Warrior’s Approach to Business Architecture
Purpose of Brief
To provide an update about Army efforts to develop and use enterprise architectures and
service oriented architectures (SOA).
This presentation is Unclassified and will focus on the “Business” side of the Army.
3A Warrior’s Approach to Business Architecture
Enterprise Information Environment Mission Area (EIEMA)DoD Lead: DoD CIO/ASD(NII) | Army Lead: CIO/G-6
Governance
Business Mission Area (BMA)DoD Lead: USD(C) | Army Lead: USA
Ac
qu
isit
ion
Ow
ner:
US
D(A
T&
L) |
Arm
y Le
ad:
AS
A(A
LT)
Fin
an
cia
l M
an
ag
em
en
tO
wne
r: U
SD
(C)
| Arm
y Le
ad:
AS
A(F
M&
C)
Hu
man
Res
ou
rce
Man
agem
ent
Ow
ner:
US
D(P
&R
) | A
rmy
Lead
: A
SA
(MR
&A
)
Lo
gis
tic
sO
wne
r: U
SD
(L&
MR
) | A
rmy
Lead
: A
SA
(ALT
)
Ins
tall
ati
on
s &
En
vir
on
me
nt
Ow
ner:
US
D(A
T&
L) |
Arm
y Le
ad:
AS
A(I
&E
)
Civ
il W
ork
sA
rmy
Ow
ner:
A
SA
(CW
)
Governance
Warfighting Mission Area (WMA)DoD Lead: CJCS | Army Lead: G-3/5/7
Ba
ttle
sp
ac
e A
wa
ren
es
sO
wne
r: V
. D
ir In
tel,
J-2,
JS
| A
rmy
Lead
: G
-2
Bat
tles
pac
e C
om
mu
nic
atio
ns
Ow
ner:
V.
Dir.
C4,
J-6
, JS
| A
rmy
Lead
: G
-6
Fo
cu
se
d L
og
isti
cs
Ow
ner:
V.
Dir.
Log
., J
-4,
JS |
Arm
y Le
ad:
G-4
Pro
tec
tio
nO
wne
r: D
ep. D
ir F
P, J
-4, J
S |
Arm
y Le
ad: G
-8
Fo
rce
Ap
pli
ca
tio
nO
wne
r: D
ep.
Dir
JWC
S,
JS |
Arm
y Le
ad:
G-8
Information AssuranceDomain
Owner: Director, Information Assurance | Army Lead: CIO/G-6
Communications
Owner: D, Wireless | Army Lead: CIO/G-6
Computing InfrastructureOwner: D, Architecture
& Interoperability | Army Lead: CIO/G-6
Core Enterprise Services
Owner: D, Information Management |
Army Lead: CIO/G-6
Governance
National Intelligence Mission Area
DoD Lead: USD(I) | Army Lead: G-2
Governance
In Work
In Work
Governance
National Intelligence Technical Infrastructure
Mission Area (NITMA)
Owner: ICSIS | Army Lead: In Work
Draft Army Alignment with GIG ES Governance
4 Mission Areas: - 15 Domains - 9 Domain Owners
DoD and Army Governance Structure
4A Warrior’s Approach to Business Architecture
Purpose of Army BEA Effort
Ensure the Army “To-Be” Business Enterprise fully supports a Modular, Expeditionary Army● Joint Interoperability
● Decrease the In-Theater Sustainment Footprint
● Make Army Sustainment More Cost-Effective
● Ensure Required Army Programs meet IOC Goals
Compliance
● Defense Authorization & Appropriation Acts● Clinger-Cohen Act and other Congressional Guidance● USD(AT&L), USD(C) and other DoD Requirements● Executive Orders and other (i.e. OMB) guidance
5A Warrior’s Approach to Business Architecture
BEA & EIE MUST Align to WMA WMA requirements must be fed into the mission area architectures for the BMA and EIE MA to ensure business systems are fully aligned to the operational needs of the Army.
Proc
urem
ent
Dispo
sition
Gar
riso
n St
orag
e
& T
rans
port
atio
n
Dep
ot
Mai
nten
ance
Hum
an
Resou
rces
Des
ign
&
Dev
elop
men
t
Plan
ning
, Bud
geting
IT In
fras
truc
ture
Lega
l
Financial Management
Real Property & Installation Lifecycle Management
Fiel
d
Mai
nten
ance
Ope
ration
al
Usa
ge
Stra
tegi
c St
orag
e
& T
rans
port
atio
n
WMA Training
Materiel Supply & Service Management
Weapon System Lifecycle Management
Medical
Personnel Management
Services Oriented Implementation
6A Warrior’s Approach to Business Architecture
EA is NOT “A CIO Thing”
It’s About Better Business Process Management, NOT Computer Systems!
7A Warrior’s Approach to Business Architecture
Roles of CIOTechnical Strategy
Support/Assistance
Honest Broker/ Facilitator
Integrator/Librarian
8A Warrior’s Approach to Business Architecture
Enterprise Information Environment Mission Area (EIEMA)DoD Lead: DoD CIO/ASD(NII) | Army Lead: CIO/G-6
Governance
Business Mission Area (BMA)DoD Lead: USD(C) | Army Lead: USA
Ac
qu
isit
ion
Ow
ner:
US
D(A
T&
L) |
Arm
y Le
ad:
AS
A(A
LT)
Fin
an
cia
l M
an
ag
em
en
tO
wne
r: U
SD
(C)
| Arm
y Le
ad:
AS
A(F
M&
C)
Hu
man
Res
ou
rce
Man
agem
ent
Ow
ner:
US
D(P
&R
) | A
rmy
Lead
: A
SA
(MR
&A
)
Lo
gis
tic
sO
wne
r: U
SD
(L&
MR
) | A
rmy
Lead
: A
SA
(ALT
)
Ins
tall
ati
on
s &
En
vir
on
me
nt
Ow
ner:
US
D(A
T&
L) |
Arm
y Le
ad:
AS
A(I
&E
)
Civ
il W
ork
sA
rmy
Ow
ner:
A
SA
(CW
)
Governance
Warfighting Mission Area (WMA)DoD Lead: CJCS | Army Lead: G-3/5/7
Ba
ttle
sp
ac
e A
wa
ren
es
sO
wne
r: V
. D
ir In
tel,
J-2,
JS
| A
rmy
Lead
: G
-2
Bat
tles
pac
e C
om
mu
nic
atio
ns
Ow
ner:
V.
Dir.
C4,
J-6
, JS
| A
rmy
Lead
: G
-6
Fo
cu
se
d L
og
isti
cs
Ow
ner:
V.
Dir.
Log
., J
-4,
JS |
Arm
y Le
ad:
G-4
Pro
tec
tio
nO
wne
r: D
ep. D
ir F
P, J
-4, J
S |
Arm
y Le
ad: G
-8
Fo
rce
Ap
pli
ca
tio
nO
wne
r: D
ep.
Dir
JWC
S,
JS |
Arm
y Le
ad:
G-8
Information AssuranceDomain
Owner: Director, Information Assurance | Army Lead: CIO/G-6
Communications
Owner: D, Wireless | Army Lead: CIO/G-6
Computing InfrastructureOwner: D, Architecture
& Interoperability | Army Lead: CIO/G-6
Core Enterprise Services
Owner: D, Information Management |
Army Lead: CIO/G-6
Governance
National Intelligence Mission Area
DoD Lead: USD(I) | Army Lead: G-2
Governance
In Work
In Work
Governance
National Intelligence Technical Infrastructure
Mission Area (NITMA)
Owner: ICSIS | Army Lead: In Work
Draft Army Alignment with GIG ES Governance
4 Mission Areas: - 15 Domains - 9 Domain Owners
DoD and Army Governance Structure
9A Warrior’s Approach to Business Architecture
Domain Strategic Plan including APG TAP Assignments
Business Process Mgmt Plan
CONOPS
Lifecycle Management
Strategic IRM Plan
CM Plan COOP PlanSSAA
CIR/PIR Assessment
RequirementsDocs
Unit Level Doctrine
Detailed Design Docs
T&E and Audit/Monitor PlansBuild Systems
Outcomes BasedPerformance Metrics
System Architecture
Portfolio Mgmt
Vulnerability Assessment (& PNE)
Threat Analyses
Domain Architecture
Domain LeaderActivities
PM/PEO Activities
Critical
Prerequisite
Domain Leader Activities
Iterative
Feedback
10A Warrior’s Approach to Business Architecture
Notional Domain Organization
Domain Leader
Strategic PlanningWorking Group
RequirementsWorking Group
TechnicalWorking Group
Strategic Planning
Portfolio Management
SRS Metrics
Army OperationalRequirements
Army DoctrineChanges & Requirements
JointRequirements
System Planning
Technical Requirements & Standards
Technical COAAnalyses & Assessments
Domain LevelEnterprise Architecture
Working Group
DomainAction Officer
11A Warrior’s Approach to Business Architecture
Federated Architecture Approach
Army EA
JointFederated
Architecture
JointBEA
DoDLOG
JointLOG
NavyLOG
ArmyLOG
AFLOG
ArmyBEA
ArmyWF
ArmyEIE
ArmyIntel
OSDLOG
GCSS-A PLM+ LMP LDSS
The Army is too big to manage as a single monolithic entity; A federated architecture breaks
the elephant into interoperable, bite-size segments.
ArmyFM
ArmyI&E
ArmyHR
ArmyCE
Legend Collaborative Design Federated Governance Combined Collaborative Design & Governance
Navy EA AF EA
12A Warrior’s Approach to Business Architecture
Technical Guidance for
Materiel Developers Constrained,
FederatedArchitectures
EA Must Impact Development
Analyze & Integrate Domain Architectures• Cross Domain Integration• Optimization Analyses
• Bandwidth Reduction Opportunities • Footprint Reduction Opportunities
•Assess Information Assurance Vulnerabilities
Develop Technical Strategies & Provide Technical Guidance• Interoperability• Reduced Footprint• COTS Utilization/Optimization
Unconstrained, Stove-Piped
DomainArchitectures
Help Domains Develop Architectures•Develop & Provide Common Templates•Standardize Processes•Develop & Teach EA Courses
Materiel Developer
Input to Domain
Architectures
PMs Develop & Field Systems
CIO EA Team Roles
13A Warrior’s Approach to Business Architecture
EA Is An Iterative Process
GroupOrganizationBy Functions
EnterpriseStrategic
Plan
EstablishStakeholder
Groups
Phase I: Establish Domains
DevelopBusiness Process
Management Plans
High LevelOperational
Architectures
DevelopDetailed
Architectures
FederateOperational
Architectures
CompleteFunctional Group
Architectures
Phase 3: Initial EA Development
Phase 4: Iterative Improvement
Recognize Constraints; Change & Improve Continuously.
14A Warrior’s Approach to Business Architecture
Hybrid Service Oriented Architecture
Hybrid Model
• Enterprise Services provide Interoperability for Common Requirements
• System-System Interfaces used where required/more effective
Enterprise Services-Core (CES)-Business (BES)
Intra-DomainService Bus orIntegration Broker
System-SystemInterfaces
15A Warrior’s Approach to Business Architecture
Different Types of Processes Need to be Handled Differently:
‣Transactional Processes – Not good SOA Candidates
‣Verification Processes – Good SOA Candidates
‣Management Processes – Good SOA Candidates
Order to Cash
Order Capture
Product Creation
Inventory Receipt
Pick Ship
Billing Delivery A/R Return
Credit Check
Order Promising
Sales & Operations Planning
Three Types of Processes
Concept taken from Corning, Inc.
16A Warrior’s Approach to Business Architecture
Only Share Some Services
Order Capture
Product Creation
Inventory Receipt
Pick Ship
Order Capture
Product Creation
Inventory Receipt
Pick Ship
Order Capture
Product Creation
Inventory Receipt
Pick Ship
Order Capture
Product Creation
Inventory Receipt
Pick Ship
Billing AR PostingDelivery
Returns
Returns
Returns
Returns
Domain Processes
Business Enterprise Services
Domain Processes
Not all processes should be “shared”• Some processes are different/unique for a reason• 10 roofers are sometimes less efficient than 5 on a small roof• 50M Gallons of soda is no cheaper per gallon than 25M (but costs more to store and handle) Concept taken from Corning, Inc.
17A Warrior’s Approach to Business Architecture
Army/DOD Hybrid Architecture
GIG-ESUSAF-
ES
Individual Programs and Proponents
HRWeb-
Sphere
CW
TBD
ACQ
TBD
I&E
TBD
LOGNet-
Weaver
FM
TBD
Domain Integration Brokers/ESBs
ARMY LandWarNet Core Enterprise Services (CES)
Enterprise Services-Core (CES)-Business (BES)
18A Warrior’s Approach to Business Architecture
Current Implementation Concept
GIG-ESUSAF-ES
Individual Programs and Proponents
HRWeb-
Sphere
CW
TBD
ACQ
TBD
I&E
TBD
LOGNet-
Weaver
FM
TBD
Domain Integration Brokers/ESBs
ARMY LandWarNet Core Enterprise Services (CES)
Vendor Neutral Services;
Published, Discoverable and
Re-usable.
19A Warrior’s Approach to Business Architecture
Sample Implementations
LandWarNet - ES DOD GIG-ES
Federated ESB/SOI-Enterprise Service Bus-Services Oriented Implementation
NMCI - ES
GCSS-A
LOG SOA LayerPLM+/SAP Netweaver
LMP DIMHRS
HR SOA Layere.g. IBM WebSphere
SOA CapableApplication
eHRS
BCS3
GCCS-A XML Data Synch
FCS
EA Template Details
21A Warrior’s Approach to Business Architecture
Common Templates Are Critical
Common Templates
22A Warrior’s Approach to Business Architecture
Systems Inventory
System Name Acronym System Manager AITR Reference # System Status* System IOC DatePlanned
Replacement System
System A
System B
System C
System D
System E
System F
System G
System H
System I
System J
* System Status Options include: New Start, Milestone A, Milestone B, Milestone C, Operational/Core and Legacy
23A Warrior’s Approach to Business Architecture
Enterprise Level Domain-Capability Matrix
24A Warrior’s Approach to Business Architecture
System Group
Capability
Capability A P C C CCapability B C P C CCapability C C PCapability D C C P C CCapability E PCapability F PCapability G
Capability H PCapability I
Capability J
Domain Name
Note: P=Provider or Single Authoritative Source and C=Consumer
System Group A
System Group H
System Group G
System Group F
System Group E
System Group D
System Group C
System Group B
Domain Level Program-Capability Matrix
•The Army Domain Level SV-5 acts to specifically assign Domain Level ROCs to one or more Programs within the domain.
•This Matrix specifically enables the tying of MDEP funding lines (occurring at the program level) back to ROCs from The Army Plan (TAP Codes).
25A Warrior’s Approach to Business Architecture
Domain Level System-Capability Matrix
System Group C
System 1 System 2 System 3 System 4 System 5 System 6
Operational Activity A P C COperational Activity B C P COperational Activity C C POperational Activity D C C P COperational Activity E POperational Activity F
Operational Activity G
Operational Activity H
Capability C Operational Activity I
Capability D Operational Activity J
Capability
Capability A
Capability B
System Group BSystem Group A System
Operational Activity
26A Warrior’s Approach to Business Architecture
System Service Exchange Matrix
• Identifies the operational processes being enabled by information systems providing specific services.
• Enables managing systems development to better support continuously improving (i.e. changing) operational business processes. It also supports Information Assurance and Standards development efforts.
Information Service a1
Info Svc a2
Info Svc a3
Info Svc a4
Info Svc a5
Info Svc b1
Info Svc b2
Info Svc b3
Info Svc c1
Info Svc c2
Info Svc d1
Info Svc d2
Info Svc d3
Info Svc e1
Info Svc e2
Info Svc e3
Info Svc f1
Info Svc f2
Info Svc f3
Info Svc f4
Info Svc f5
Info Svc g1
Info Svc g2
Info Svc g3
Info Svc h1
Info Svc h2
Info Svc i1
Info Svc i2
Info Svc i3
Info Svc j1
Info Svc j2
Info Svc j3
System 1 P P C P C
System 2 C P P P P C
System 3 P P
System 1 C C C P P C
System 2
System 3
System 4
System 5
System 1
System 2
System 3
System 4
System 1
System 2
System 3
System 4
System 5
System 1
System 2
System 3
System 4
System 5
Program B
Program C
Program D
Program E
ROC / TAP Code PCnnnn
Use Case/IT Enabled Process a Process b Process eProcess c Process d
Specific Capability
Specific Capability from Doctrine
Program A
Specific Capability from Doctrine
An "IT Enabled Process" is analogous to a "Use Case" developed by an operational architect and reduced to Army instruction/regulation describing the method in which a task is performed within the Army.
Use Case/Process f Process g
ROC / TAP Code PCnnnn
Specific Capability
Process h Process i Process j
Specific Capability from Doctrine
27A Warrior’s Approach to Business Architecture
Communications Matrix
Min BW Max Lat S M L S M L MCO Sust MCO Sust MCO Sust MCO Sust MCO Sust
U U U U U U U U U U U U U U U U
System 1
System 2
System 3
System 1
System 2
System 3
System 4
System 5
System 1
System 2
System 3
System 4
System 1
System 2
System 3
System 4
System 5
System 1
System 2
System 3
System 4
Permanent Garrison Expeditionary Units
UEy BN COBCTUEx
Program E
Per User
Program A
Domain-Level SV-2
Program B
Program C
Program D
CONUS Garrison
OCONUS Garrison
28A Warrior’s Approach to Business Architecture
Information Assurance Category
C I A N C I A N C I A N C I A N C I A N C I A N C I A N C I
System 1 H L M H H L M H
System 2 H H H H H H H H H H H H H H H H
System 3 H H M L H H
System 4
System 5
Every "Information Service" can be identified/defined as a service that is used to either Collect & Forward (CF), Store (S), Process (Fx) or Present (P) information as some grouping of data elements.
Information is identified by existing DoD/NSA regulations as having either a "High", "Medium" or "Low" level of "Information Criticality" with respect to each of the Information Assurance parameters (i.e. Confidentiality, Integrity, Availability and Non-Repudiation). These information criticality levels can be obtained from existing NSA/NIST instructions for information assurance.
Process (Fx)
Use Case/IT Enabled Process
Information Service Information Service
Collect & Forward (CF)
Store (S) Process (Fx) Present (P)Present (P)
The purpose of this matrix is to identify information criticality levels for each system within a domain based on the information services provided or consumed by that system.
Store (S)Collect & Forward
(CF)
Enterprise Service – Info Assurance Matrix
Uses existing standards and tools for data element IA Criticality Assessment, and provides an easy way to assess the level of IA effort each system within the Domain will need.
29A Warrior’s Approach to Business Architecture
Services Standards Profile
CF S Fx P CF S Fx P CF S Fx P CF S Fx P CF S Fx P CF S Fx P
System 1 WS* WS*
System 2 WS* WS*
System 3
System 4 WS* WS*
System 5 WS* WS*
Required Operational Capability - TAP Code
Must be developed through an iterative process. System developers, assigned responsibility to provide specific information services in support of various business processes, determine (with input from appropriate shareholders) which standard web service
An "IT Enabled Process" is analogous to a "Use Case" developed by an operational architect and reduced to Army instruction/regulation describing the method in which a task is performed within the Army.
Specific Capability
Use Case/IT Enabled Process IT Enabled Process
Information Service Information Service
Every "Information Service" can be identified/defined as a service that is used to either Collect & Forward (CF), Store (S), Process (Fx) or Present (P) information as some grouping of data elements.
By identifying information services in terms of the action they perform relative to a data set, we 1) enable the architecture to more clearly show how specific services are used by different systems, 2) align the "services oriented" nature of our architec
Information Service
Specific Capability
Use Case/IT Enabled Process IT Enabled Process
Information Service Information Service Information Service
30A Warrior’s Approach to Business Architecture
Back Up Slides
31A Warrior’s Approach to Business Architecture
Challenges
Data, Data and Data Security, Security and SecurityVertically Integrated Tool SetsGovernance – Mindset Change
Portfolio Management Details
33A Warrior’s Approach to Business Architecture
DOD BEA Certification Process
CIO/G6Certifies
DomainLeader
SubmitsArmy Validation
35A Warrior’s Approach to Business Architecture
What Is Enterprise Architecture ?
NOT Portfolio Management
NOT IT/MIS Management
A Tool for Managing Business Processes & Assets
StrategicPlanning
PerformanceMetrics
EnterpriseArchitecture
BusinessProcess
Redesign
StrategicPlanning
PerformanceMetrics
EnterpriseArchitecture
36A Warrior’s Approach to Business Architecture
The Value of Architecture (1 of 2)
Deliver More Effective Systems In Less Time with Less Money● Architectures provide a tool to better manage and document
requirements. Better requirement definition leads to fewer program cost and schedule overruns.
Eliminate “Stove-Pipes”● Architectures help identify functional gaps and overlaps
Ensure Information Infrastructure Planning Meets Operational Needs● Architectures provide a means to forward plan & program bandwidth
Less Cost & Schedule Overruns
Clearly Defined Requirements =
LandWarNet Requirements
LOG ACQ HR CW I&E
37A Warrior’s Approach to Business Architecture
The Value of Architecture (2 of 2)
Enable Interoperability Between Force Sustainment and Projection Systems● Architectures provide common frameworks for technology development,
thereby ensuring alignment of technology strategies Make the Army More Adaptable
● Architectures allow Business Process Management to drive technology (and not technology to drive processes)
Enhance Army Joint Warfighting Capabilities● Architectures provide common frameworks for the development of
solutions which cross services and agencies (e.g. Medical, Logistics, Joint Fires, etc.)
GCSS-A
LOG SOA LayerPLM+/SAP Netweaver
LMP DIMHRS
HR SOA Layere.g. IBM MQ Series
SOA CapableApplication
eHRS
BCS3
GCCS-A XML Data Synch
FCS
GCSS-A
LOG SOA LayerPLM+/SAP Netweaver
LMP DIMHRS
HR SOA Layere.g. IBM MQ Series
SOA CapableApplication
eHRS
BCS3
GCCS-A XML Data Synch
FCS
38A Warrior’s Approach to Business Architecture
Notional CIO Team Organization
Army Enterprise Architecture
WMA Architecture
BattleSpace CommsDomain Architecture
BattleSpace AwarenessDomain Architecture
ForceProtectionDomain Architecture
EIEMA Architecture BMA Architecture NIMA Architecture
…
CES Domain Architecture
CommunicationsDomain Architecture
Computing InfrastructureDomain Architecture
Information AssuranceDomain Architecture
Logistics
Financial ManagementDomain Architecture
Human ResourcesDomain Architecture
39A Warrior’s Approach to Business Architecture
Core Enterprise Services (CES)
ConferencingConferencing Shared Information
Space
Shared Information
Space
Application Sharing
Web Conference
People Discovery
Text Messaging
Whiteboard
Workspaces
Content Delivery
Content Discovery
Content Store
Identity and Metadata Management
Net-Centric Applications
Net-Centric Applications
Service Discovery
Service Security
Mediation
Service Management
Service Messaging
Enterprise ServicesSupport Infrastructure
40A Warrior’s Approach to Business Architecture
ESB/Integration Layer Parts
Capability Communications
(aka Message Oriented
Middleware)
Connectivity Transformation Intelligent Routing (aka
Process Mapping)
Core Enterprise Services
Function Enterprise Messaging between Systems
RPC Capability for XML
Searchable registry of
XML Services
Describes XML
Services
Maps one XML Schema to
another
Provide Common Services
Standard Java Messaging (JMS)
Simple Object Access Protocol (SOAP)
Universal Description, Discovery & Integration
(UDDI)
(WSDL) eXtensibel Style Sheet Language Transformation
(XSLT)
Not Truly “Standards”
…BPNM, BPEL4WS,
etc.
Not Truly “Standards”
…Authenticati
on, Discovery,
etc.
Vendor Products• BEA – WebLogic• IBM – WebSphere Suite• Microsoft – BizTalk, etc.• Oracle – • SAP – NetWeaver• Sonic – Sonic ESB• Sun –
OpenSource Efforts
• WDI Business Integration Engine
• MULE Framework
41A Warrior’s Approach to Business Architecture
Hybrid Architecture
GIG-ESUSAF-
ES
Individual Programs and Proponents
HRWeb-
Sphere
CW
TBD
ACQ
TBD
I&E
TBD
LOGNet-
Weaver
FM
TBD
Domain Integration Brokers/ESBs
ARMY LandWarNet Core Enterprise Services (CES)
Enterprise Services-Core (CES)-Business (BES)
42A Warrior’s Approach to Business Architecture
Army Pre-Certification Process
Ensure Army Business Information Systems beyond FY-2011:Align to WMA (Operational) Architecture; Don’t Create Gaps or Overlaps
● Business architectures aligned to Army warfighting architecture & operational requirements (G3, in coordination with TRADOC and appropriate Domain leaders, validates OV-5 to APGM/COCOM 127 and Army Doctrine)
Align to EIE MA Architecture● Will work with future LandWarNet (G6 Validates AV-2, SV-2 and TV-1)
Interoperate with Other Business Systems● Follow Army technical strategy for interoperability (G6 Validates AV-2, SV-2 and TV-1) ● Use Army-wide Taxonomies and Ontologies (NetCentric Data Strategy, SW Blocking, JTA, etc.)
Do Not Conflict with Other Business AIS; Align with POM● Transition Plan matches Army Acquisition Plans and POM (ASA(ALT), in coordination with G8, validates SV-8)
CIO/G6Staffs forDomain Leader
Army CIOPre-Certifies
To OSD
G6Validates
X-MA Interop.(SV & TV)
CIO/G6Technical &
InteroperabilityAlignment
G3WarfightingAlignment
TRADOC
G-8
ASA(ALT)Acquisition Plan
& POM Alignment
CIO/G6Submits to OSD
Domain DevelopsArchitecture
CIO/G6 AAICTeams with &
SupportsDomains
Domain LeaderApproves
Architecture Only;NOT PfM
43A Warrior’s Approach to Business Architecture
Component Planning Guidance Drives BEA
Army Planning Guidance Memorandum (APGM)
TAP Capability Codes (PC code)
TRADOC & FM 3-0Defined Tasks (AUTL/JUTL)
Specific Capabilities
Task Oriented, IT Enabled Operational Processes
Army Doctrine
Enabling Information Services
*WS Web Services
OV-5a and 5b
OV-5c
SV-5
SV-4 TV-1
44A Warrior’s Approach to Business Architecture
OV-5a & 5b: Required OperationalCapabilities (ROC) listed by TAP Code (PCnnnn) from Army Planning Guidance
(APG) in Section II of The Army Plan (TAP)
SV-4 & 5: Use Cases / IT-Enabled ProcessesDefined in DoD and Army Regulations
and Operating Procedures
OV-5c: Specific Tasks/CapabilitiesDefined in Army Doctrine and
Unit Level Doctrine
Army BEA Design Process Flow Example Using Logistics Process
PC1029: An inland bulk fuel storage and distribution system supporting U.S., joint, and Allied Forces in theaters of operation
TRADOC documentation of process(es) by which battalions will order and receive fuel
at forward deployed locations including which sub-tasks are IT-enabled
Ability for Stryker Battalion S-4 staff to order fuel delivery at forward position and
have fuel arrive just before Stryker Battalion
Information Services provided by FCS/LDSS and GCSS-A as required to support automated portions of TRADOC developed process for forward fueling
SV-4a, 5a & TV-1: Information ServicesAs Implemented in
Supporting Information Systems
Army “Perspective” Drives Army Process
45A Warrior’s Approach to Business Architecture
Data Challenge
46A Warrior’s Approach to Business Architecture
Vertical Toolset Challenge
47A Warrior’s Approach to Business Architecture
Security Challenge