Army Business Enterprise Domain Level Architecture Development Process

1
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, 2005
• Joe Paiva, 703-602-6235, Arthur.Paiva_at_us.army.mil

2
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
DoD and Army Governance Structure
Draft Army Alignment with GIG ES Governance
Business Mission Area (BMA) DoD Lead USD(C)
Army Lead USA
Warfighting Mission Area (WMA) DoD Lead CJCS
Army Lead G-3/5/7
National Intelligence Mission Area DoD Lead
USD(I) Army Lead G-2
Governance
Governance
Governance
In Work
Battlespace Awareness Owner V. Dir Intel, J-2,
JS Army Lead G-2
Battlespace Communications Owner V. Dir. C4,
J-6, JS Army Lead G-6
Focused Logistics Owner V. Dir. Log., J-4, JS
Army Lead G-4
Protection Owner Dep. Dir FP, J-4, JS Army
Lead G-8
Force Application Owner Dep. Dir JWCS, JS Army
Lead G-8
Acquisition Owner USD(ATL) Army Lead ASA(ALT)
Financial Management Owner USD(C) Army Lead
ASA(FMC)
Human Resource Management Owner USD(PR) Army
Lead ASA(MRA)
Logistics Owner USD(LMR) Army Lead ASA(ALT)
Installations Environment Owner USD(ATL)
Army Lead ASA(IE)
Civil Works Army Owner ASA(CW)
In Work
Governance
National Intelligence Technical Infrastructure
Mission Area (NITMA) Owner ICSIS Army Lead
In Work
Information Assurance Domain Owner Director,
Information Assurance Army Lead CIO/G-6
Communications Owner D, Wireless Army Lead
CIO/G-6
Computing Infrastructure Owner D, Architecture
Interoperability Army Lead CIO/G-6
Core Enterprise Services Owner D, Information
Management Army Lead CIO/G-6
4 Mission Areas - 15 Domains - 9 Domain
Owners
Governance
Enterprise Information Environment Mission Area
(EIEMA) DoD Lead DoD CIO/ASD(NII) Army Lead
CIO/G-6
4
The Role of EA in the Army
A Tool for Managing Business Processes Assets
5
Domain Leader Activities
Iterative Feedback
6
Federated Approach
Joint Federated Architecture
The Army is too big to manage as a single
monolithic entity A federated architecture
breaks the elephant into interoperable, bite-size
segments.
Army EA
Navy EA
AF EA
Joint BEA
Army BEA
Army WF
Army EIE
Army Intel
DoD LOG
Joint LOG
Navy LOG
Army LOG
AF LOG
OSD LOG
Army FM
Army IE
Army HR
Army CE
GCSS-A
PLM
LMP
LDSS
7
DoD and Army Governance Structure
Draft Army Alignment with GIG ES Governance
Business Mission Area (BMA) DoD Lead USD(C)
Army Lead USA
Warfighting Mission Area (WMA) DoD Lead CJCS
Army Lead G-3/5/7
National Intelligence Mission Area DoD Lead
USD(I) Army Lead G-2
Governance
Governance
Governance
In Work
Battlespace Awareness Owner V. Dir Intel, J-2,
JS Army Lead G-2
Battlespace Communications Owner V. Dir. C4,
J-6, JS Army Lead G-6
Protection Owner Dep. Dir FP, J-4, JS Army
Lead G-8
Force Application Owner Dep. Dir JWCS, JS Army
Lead G-8
Focused Logistics Owner V. Dir. Log., J-4, JS
Army Lead G-4
Acquisition Owner USD(ATL) Army Lead ASA(ALT)
Financial Management Owner USD(C) Army Lead
ASA(FMC)
Human Resource Management Owner USD(PR) Army
Lead ASA(MRA)
Logistics Owner USD(LMR) Army Lead ASA(ALT)
Installations Environment Owner USD(ATL)
Army Lead ASA(IE)
Civil Works Army Owner ASA(CW)
In Work
Governance
National Intelligence Technical Infrastructure
Mission Area (NITMA) Owner ICSIS Army Lead
In Work
Information Assurance Domain Owner Director,
Information Assurance Army Lead CIO/G-6
Communications Owner D, Wireless Army Lead
CIO/G-6
Computing Infrastructure Owner D, Architecture
Interoperability Army Lead CIO/G-6
Core Enterprise Services Owner D, Information
Management Army Lead CIO/G-6
4 Mission Areas - 15 Domains - 9 Domain
Owners
Governance
Enterprise Information Environment Mission Area
(EIEMA) DoD Lead DoD CIO/ASD(NII) Army Lead
CIO/G-6
8
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(ATL), USD(C) and other DoD Requirements
• Executive Orders and other (i.e. OMB) guidance

9
Cross Mission Area Interoperability
Services Oriented Implementation
Medical
WMA Training
Garrison Storage Transportation
Depot Maintenance
Human Resources
Design Development
Field Maintenance
Operational Usage
Procurement
Disposition
IT Infrastructure
Legal
Strategic Storage Transportation
Planning, Budgeting
10
Core Enterprise Services (CES)
Conferencing
Shared Information Space
People Discovery
Content Discovery
Text Messaging
Workspaces
Web Conference
Content Store
Application Sharing
Content Delivery
Whiteboard
Identity and Metadata Management
Enterprise Services Support Infrastructure
11
Hybrid Service Oriented Architecture

• Enterprise Services
• Core (CES)
• Business (BES)

Intra-Domain Service Bus or Integration Broker
System-System Interfaces

• Hybrid Model
• Enterprise Services provide Interoperability for
  Common Requirements
• System-System Interfaces used where
  required/more effective

12
Three Types of Processes
Concept from Corning, Inc.

• 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

13
Only Share Some Services

• 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
Army/DOD Hybrid Architecture
USAF-ES
GIG-ES
ARMY LandWarNet Core Enterprise Services (CES)
HR Web- Sphere
CW TBD
ACQ TBD
IE TBD
LOG Net- Weaver
FM TBD
Domain Integration Brokers/ESBs

• Enterprise Services
• Core (CES)
• Business (BES)

Individual Programs and Proponents
15
ESB/Integration Layer Parts

• 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
Current Implementation Concept
USAF-ES
GIG-ES
ARMY LandWarNet Core Enterprise Services (CES)
HR Web- Sphere
CW TBD
ACQ TBD
IE TBD
LOG Net- Weaver
FM TBD
Domain Integration Brokers/ESBs
Vendor Neutral Services Published, Discoverable
and Re-usable.
Individual Programs and Proponents
17
Sample Implementations

• Federated ESB/SOI
• Enterprise Service Bus
• Services Oriented Implementation

NMCI - ES
DOD GIG-ES
LandWarNet - ES
18
Questions ?
19
Back-Up Slides

• ..

20
Iterative EA Development Process
Recognize Constraints Change Improve
Continuously.
21
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.

22
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
Army SV-2 Communications
24
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
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
Army Expanded SV-5
27
Army TV-1 BES Standards Profile
28
Modified SV-1 (used as SV-8)
29
Back-Up Slides

• ..

30
EA Should Impact Development

• Help Domains Develop Architectures
• Develop Provide Common Templates
• Standardize Processes
• Develop Teach EA Courses

PMs Develop Field Systems

• 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

CIO/G6 BEA Team Roles
31
Army Interoperability Vision

• Enterprise Services
• Core (CES)
• Business (BES)

32
Sample Domain Organization
Stakeholders, Including MACOMs, Participate at
All Levels
CIO/G6 Support - Common Tools - Common
Templates - Technology Strategy
Doctrine Working Group