Upload
aamir97
View
2.695
Download
0
Tags:
Embed Size (px)
Citation preview
Army Business EnterpriseDomain Level Architecture
Development Process
HQDA, CIO/G6, Architecture, Operations, Network and Space (AONS)
Army Architecture Integration Cell (AAIC)
http://aaic.army.mil
June 16, 2005Joe Paiva, 703-602-6235, [email protected]
2 Our Army At War – Relevant and Ready
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.
3 Our Army At War – Relevant and Ready
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
4 Our Army At War – Relevant and Ready
The Role of EA in the Army
NOT Portfolio Management
NOT IT/MIS Management
A Tool for Managing Business Processes & Assets
StrategicPlanning
PerformanceMetrics
EnterpriseArchitecture
BusinessProcess
Redesign
StrategicPlanning
PerformanceMetrics
EnterpriseArchitecture
5 Our Army At War – Relevant and Ready
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
6 Our Army At War – Relevant and Ready
Federated 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
7 Our Army At War – Relevant and Ready
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
8 Our Army At War – Relevant and Ready
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
9 Our Army At War – Relevant and Ready
Cross Mission Area Interoperability
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
10 Our Army At War – Relevant and Ready
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
11 Our Army At War – Relevant and Ready
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
12 Our Army At War – Relevant and Ready
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 ProcessesConcept from Corning, Inc.
13 Our Army At War – Relevant and Ready
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)
14 Our Army At War – Relevant and Ready
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)
15 Our Army At War – Relevant and Ready
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
16 Our Army At War – Relevant and Ready
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.
17 Our Army At War – Relevant and Ready
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 MQ Series
SOA CapableApplication
eHRS
BCS3
GCCS-A XML Data Synch
FCS
Questions ?
Back-Up Slides
..
20 Our Army At War – Relevant and Ready
Iterative EA Development 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.
21 Our Army At War – Relevant and Ready
Army SV-6: System Service Exchange
• 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
22 Our Army At War – Relevant and Ready
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 A N
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 M L
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)
Army SV-6a: BES-IA 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.
23 Our Army At War – Relevant and Ready
Army SV-2: Communications
BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML BW ML
System 1System 2System 3System 1System 2System 3System 4System 5System 1System 2System 3System 4System 1System 2System 3System 4System 5System 1System 2System 3System 4System 5
MCO = Major Combat Operations
Sust = Sustainment / Low Intensity Operations
BW = Required bandwidth; Calculated as (Number of Users) x (Bandwidth per User)
ML = Maximum Allowable Latency which System will support
Permanent Garrison Expeditionary Units
SustMCO
UEy BN COBCTUEx
MCO
CONUS Permanent Garrison
Small Large
OCONUS Permanent Garrison
Small Medium Large Sust MCO Sust MCO Sust MCO Sust
Legend:
Program A
Domain-Level SV-2 Medium
Program B
Program C
Program D
Program E
24 Our Army At War – Relevant and Ready
Army Enterprise Level SV-5
•The Army SV-5 ties the Mission Area architecture back to The Army Plan by mapping Title 10 Required Operational Capabilities (ROCs) as found in Section II of The Army Plan to responsible domains.
•The Army SV-5 provides Mission Area Level detail by identifying specifically which Domains within a Mission Area are responsible for providing specific Operational Capabilities identified in The Army Plan.
25 Our Army At War – Relevant and Ready
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
Army Domain Level SV-5
•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).
26 Our Army At War – Relevant and Ready
Army Expanded SV-5
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
27 Our Army At War – Relevant and Ready
Army TV-1: BES 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
28 Our Army At War – Relevant and Ready
Modified SV-1 (used as SV-8)
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
Back-Up Slides
..
30 Our Army At War – Relevant and Ready
Technical Guidance for
Materiel Developers Constrained,
FederatedArchitectures
EA Should 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/G6 BEA Team Roles
31 Our Army At War – Relevant and Ready
Army Interoperability Vision
Enterprise Services-Core (CES)-Business (BES)
32 Our Army At War – Relevant and Ready
Stakeholders,Including MACOMs,Participate at All Levels
Domain Leader
DomainExecutive Committee
InteroperabilityWorking Group
RequirementsWorking Group
Business ProcessManagement Group
Single AuthoritativeService Providers
Service Request& Reply Standards
Required ServicesTaxonomies and
Ontology
Investment(Portfolio Management)
Working Group
SRS PerformanceMetrics Working Group
Sample Domain Organization
CIO/G6 Support:- Common Tools- Common Templates- Technology Strategy
DoctrineWorking Group