enterprise architecture in the intelligence community: - cryptome
TRANSCRIPT
The Joint Architecture Working Group (JAWG)
Enterprise Architecture in the Intelligence Community:
Randy Marks; Chair, Joint Architecture Working GroupNSA/TE Deputy Chief System Engineer for Enterprise Architecture
JOINT ARCHITECTURE WORKING GROUP 4
Collect Process Exploit Disseminate
Data Info KBs
Task
Intel
Process Exploit Disseminate
Task
ObtainData
ProcessData
Analyze &Produce
Intelligence
AssessOptions
ManageRequirements
ManageCustomerRelations
Manage theProduction
ProcessKBs
Event Store IIB EP
ObtainData
ProcessData
Analyze &Produce
Intelligence
AssessOptions
ManageRequirements
ManageCustomer
Manage theProduction
Process
ObtainData
ProcessData
Analyze &Produce
Intelligence
AssessOptions
ManageRequirements
ManageCustomerRelations
Manage theProduction
ProcessKBs
Event Store IIB EP
ObtainData
ProcessData
Analyze &Produce
Intelligence
AssessOptions
ManageRequirements
ManageCustomerRelations
Manage theProduction
Process
ObtainData
ProcessData
Analyze &Produce
Intelligence
AssessOptions
ManageRequirements
ManageCustomerRelations
Manage theProduction
ProcessKBs
Event Store IIB EP
ObtainData
ProcessData
Analyze &Produce
Intelligence
AssessOptions
ManageRequirements
ManageCustomer
Manage theProduction
Process
ObtainData
ProcessData
Analyze &Produce
Intelligence
AssessOptions
ManageRequirements
ManageCustomerRelations
Manage theProduction
ProcessKBs
Event Store IIB EP
ObtainData
ProcessData
Analyze &Produce
Intelligence
AssessOptions
ManageRequirements
ManageCustomerRelations
Manage theProduction
Process
AcquireData
Process Data& Perform
Cryptanalysis
PerformCryptologic
Analysis
Tailor &DeliverResults
Data Info KBs Intel
INDB
SIGDEV SIGDEV SIGDEVSignal
Targeting Tasking
Coordinate Cryptologic Operations
Process Data& Perform
Cryptanalysis
PerformCryptologic
Analysis
Tailor &DeliverResults
DataDataData Info KBsSIGDEV SIGDEV
Coordinate Cryptologic Operations
Detect/Find
Locate/Fix
Identify/Track
Strike/Engage
Decide/Target
Data Info KBs
Assess
Locate/ Identify/Track
Decide/Target
Assess
Identify/
Detect/Find
Locate/Fix
Identify/Track
Strike/Engage
Decide/Target
Data Info KBs
Assess
Detect/Find
Locate/Fix
Identify/Track
Strike/Engage
Decide/Target
Assess
Detect/Find
Locate/Fix
Identify/Track
Strike/Engage
Decide/Target
Data Info KBs
Assess
Detect/Find
Locate/Fix
Identify/Track
Strike/Engage
Decide/Target
Assess
Detect/Find
Locate/Fix
Identify/Track
Strike/Engage
Decide/Target
Data Info KBs
Assess
Detect/Find
Locate/Fix
Identify/Track
Strike/Engage
Decide/Target
Assess
Collection Processing AnalysisProduction
&Dissemination
Data Info KBs Intel
Planning & Tasking
RequirementsTasking
Processing AnalysisProduction
&Dissemination
DataData Info KBs
Planning & Tasking
Collection Processing AnalysisProduction
&Dissemination
Data Info KBs Intel
Planning & Tasking
RequirementsTasking
Processing AnalysisProduction
&Dissemination
DataData Info KBs
Planning & Tasking
Collection Processing AnalysisProduction
&Dissemination
Data Info KBs Intel
Planning & Tasking
RequirementsTasking
Processing AnalysisProduction
&Dissemination
DataData Info KBs
Planning & Tasking
Collect Process Exploit Disseminate
Data Info KBs
Task
Intel
Process Exploit Disseminate
Task
National Tactical
Detect/Find
Data
Detect/Find
KBs
DCGSDCGSDCGS
GSTs
DCGS
• Info Sharing/Integration is a grassroots effort – not an enterprise principle
– Phone call, email, word of mouth– Warfighters are unaware of solutions
• Current implementation hampers Information Integration
– Point-to-point interfaces– Inability to find information– Service provider– Private libraries
• Standards need to be enterprise focused
Intelligence
5
Enterprise Architecture to the rescue!
UNCLASSIFIED//FOR OFFICIAL USE ONLY
JOINT ARCHITECTURE WORKING GROUP
The Architecture Trifecta
• The “AS IS” Architecture• The “To Be” Architecture• The Architecture Transition Plan -
Roadmap
JOINT ARCHITECTURE WORKING GROUP
Multiple ways to produce an architecture…
8
DOD Architecture Framework
Enterprise Architecture (circa 2006)
* Acknowledgement to Dr. Scott Bernard, Introduction to Enterprise Architecture
JOINT ARCHITECTURE WORKING GROUP
The Joint Architecture Reference Model: 10 Layer Model
11
Undercarriage Services• “Enterprise”-wide
software and hardware services utilizing shared networks and facilities
• For unique mission capabilities, these layers may be dedicated to specific operations
Operations-specific Services• Software performing
specific activities
Operational Drivers• Abstract Models and
Architectures used to build the lower layers
• People using IT that is provided below
6. Software Frameworks and Content Structure
10. Operational Objectives & Policies
7. Applications and Content
5. Enabling Services for Applications and Content
4. Computing and Storage Platforms (HW & OS)
3. Networks (OSI Layers 2 & 3)
2. Physical Connectivity Infrastructure (OSI Layer 1)
1. Facilities Infrastructure (Power, Space, & HVAC)
9. Capability Areas (and Threads)
8. Enterprise Activities and Exchanges
6. Software Frameworks and Content Structure
5. Enabling Services for Applications and Content
4. Computing and Storage Platforms (HW & OS)
2. Physical Connectivity Infrastructure (OSI Layer 1)
1. Facilities Infrastructure (Power, Space, & HVAC)
6. Software Frameworks and Content Structure
5. Enabling Services for Applications and Content
6. Software Frameworks and Content Structure
5. Enabling Services for Applications and Content
Data
2. Physical Connectivity Infrastructure (OSI Layer 1)
1. Facilities Infrastructure (Power, Space, & HVAC)
SecurityManagem
ent
Model Comparisons
Other Enablers
13
Example of the way we did EA
Enter the Joint Architecture Working Group
JAWG
JOINT ARCHITECTURE WORKING GROUP
The JAWG’s Objective
…to define the IC Federated Enterprise Architecture and provide tools to support IC Element and IC Enterprise investment (acquisition) decisions across the IC
14
JOINT ARCHITECTURE WORKING GROUP
JAWG Timeline
15
Sep ’08: IC Architecture-focused forum established (JAWG)
May ‘08: NRO Ground transformation
May ‘09: 2nd
Community Review (JAR);JAWG subsumed into IC CIO under ICI2P
Oct ‘09: Community Status Review (JASR);JSEF became the Architecture Standards & Engineering Committee (ASEC)
Mar ‘10: 3rd
Community Review (AER)
Nov ‘10: Community Status Review (JICSR)
Jul ‘10: IC Core TEM 1
Sep ‘10: IC Core TEM 2
May ‘11: 4th
Community Review
Apr ‘11: DoD EAConference
Aug ‘08: JSEF forms
Dec‘08: 1st
Community Review (IGCR)
Membership
Significant Events2008 2009 2010 2011
Sep‘08 Sep‘08 Sep‘08 Oct ‘08 Oct ‘08 Nov ‘08 Dec ‘08 Jan ‘09 Feb ‘09 Jul ‘09 Apr ‘10
NRO NSA NGA ODNI DIA OUSD(I) CIA FBI DHS USN (N2) JCSDoD CIO
Aug ‘09
JOINT ARCHITECTURE WORKING GROUP 16
JOINT ARCHITECTURE WORKING GROUP 17
The Joint Architecture Reference ModelThe Tools
To be effective, we need to use the JARM in a standard way toward a shared goal…
JOINT ARCHITECTURE WORKING GROUP
The Joint Architecture Reference Model: 10 Layer Model
18
Top Down
Bottoms Up
Supports
Specific Areasof Interest
JOINT ARCHITECTURE WORKING GROUP
The Joint Architecture Reference Model: 10 Layer Model
19
JOINT ARCHITECTURE WORKING GROUP
The Joint Architecture Reference Model: 10 Layer Model
20
JOINT ARCHITECTURE WORKING GROUP
Enterprise Competency Model (ECM)• The ECM is a standard characterization of mission and business
functions and activities – It’s a way to represent what our agencies do– It’s related to the FEA Business Reference Model
• Functions identified within the ECM represent Layer 8 “Enterprise Activities and Exchanges”
• The ECM introduces three concepts– Enterprise Competencies– Enterprise Components– Accountability Levels
21
The ECM provides a more in-depth representation of IC mission and business functions than the current IC BRM
JOINT ARCHITECTURE WORKING GROUP 22
A Closer Look at the ECM
JOINT ARCHITECTURE WORKING GROUP
JOINT ARCHITECTURE WORKING GROUP 23
UNCLASSIFIED
Enterprise Services List (ESL) • The ESL provides a
mission/business-driven, functional framework classifying enterprise services
• ESL terminology is consistent with the FEA Service Reference Model– Service Domains– Service Types– Service Components
UNCLASSIFIEDUNCLASSIFIEDThe ESL provides a more comprehensive list of enabling services for the IC
JOINT ARCHITECTURE WORKING GROUP
The Joint Architecture Reference Model: 10 Layer Model
24
25
So why do we care?
JOINT ARCHITECTURE WORKING GROUP 26
Start With A Common Language
27
That’s the Enterprise…let’s narrow our focus a bit more…
JOINT ARCHITECTURE WORKING GROUP 28
A Federated Environment Enabling Information Integration
“Any data, any time, any place, usable by any authorized consumer; preventable only by law or policy, not technology.”
JOINT ARCHITECTURE WORKING GROUP
The IC Core Defined
• The IC Core is a focused set of joint & community services, specifications and standards, processes, and policies for enabling the Business of Intelligence for the federated Intelligence Community Enterprise
• IC Core elements must: be foundational enable the Business of Intelligence, and foster interoperability and integration
29
The focus of the IC Core is on the technical service capabilities and discrete services
JOINT ARCHITECTURE WORKING GROUP 30
Service Offerings
IC Core Baseline Increment 1Identity & Access
Management (IdAM)
Access Control
Digital Policy Management
Intrusion Prevention
Computers / Automation Management
Cryptography
Digital Resource Identification
Audit Trail Capture & Analysis
Forensics
Identification and Authentication
Digital Signature Management
Collaboration
Organizational Messaging
Voice Communication
Audio Conferencing
Workgroup / Groupware
Video Conferencing
Computer / Telephony Integration
Real-Time Chat
Threaded Discussion
Document LibraryShared
CalendaringTask
ManagementInstant Messaging
Text Messaging
Personalization
Community Management
Multimedia
Content Discovery & Retrieval
(CDR)
Information Retrieval
Subscriptions
Alerts & Notifications
Data Exchange
Metadata Management
Knowledge Distribution and Delivery
Knowledge Categorization
Precision / Recall Ranking
Infrastructure Enablers
Network Management
Communications
Enterprise Infrastructure Assessment
Virus Protection
Intrusion Detection
Cross Domain Data Transfer
Incident Response
General Enterprise Enablers
Indexing
Service Discovery
Workforce / Directory Locator
Information Mapping / Taxonomy
Mission Assessment
Personnel Administration
Document Categorization
Document Classification
Security Classification
Service Monitoring
Service Publication
Content Acquisition
Directory Services
Legend
Service Offering
IC Core Enterprise Service Component
Enterprise Service Component
Requires synchronization with ESL
31
So we’ve got another framework, another taxonomy…What do we do with it?
JOINT ARCHITECTURE WORKING GROUP
Need to make acquisition decisions based on functions (capabilities) rather than individual programs
32
So how do we use the JAWG products to better inform acquisition decisions?
JOINT ARCHITECTURE WORKING GROUP
10 Layer Architecture Model
Team Effort with SME support
Information Portfolio (IP)Structure
Enterprise Architecture to Investment Portfolio Alignment
33
Agen
cy T
rans
form
atio
n
Proc
essi
ng
Prod
uctio
n
Ope
ratio
ns
Expl
oita
tion
Anal
ytic
s
Mis
sion
M
anag
emen
t
Enterprise Mgt
Agency StrategyAgency “Concise Look Forward”
Investment Portfolio StrategyAgency Program Guidance
Enterprise Mgt
Enterprise IT
JOINT ARCHITECTURE WORKING GROUP
Overlaps, Possible Duplication, or areas of Common Concern
34
Then – look for hotspots or concentrations of activityBudget Center Bxxx
Effort 1MaterialLabor
Mgmt, Sys Engr, HW Main, SW Dev …Travel , Transportation & SuppliesInfrastructureFacilities
Effort 2MaterialLabor
Mgmt, Sys Engr, HW Main, SW Dev …Travel, Transportation & SuppliesInfrastructureFacilities
JOINT ARCHITECTURE WORKING GROUP
InfrastructureInfrastructureInfrastructureInfrastructureBudget Center Byyy
Effort 1MaterialLabor
Mgmt, Sys Engr, HW Main, SW Dev …Travel , Transportation & SuppliesInfrastructureFacilities
Effort 2MaterialLabor
Mgmt, Sys Engr, HW Main, SW Dev …Travel, Transportation & SuppliesInfrastructureFacilities
Capability GAP!Mission Critical Capability but no evidenceof financial support
Operational objectives and policy layer
Capability Areas and Thread Layer
Enterprise Activites and Exchange LayerAccomplish the Mission
A1 Coordinate Operations (1.2)
A1.1 Manage Mission Resources & CapabilitiesA1.1.1 Provide Mission Planning
A1.1.2 Manage Health, status and perfoA1.1.3Maintain TradecraftA1.1.4 Provide target planning
A1.1.4.1 Identify requirementsA1.1.4.2 Command & ControlA1.1.4.3 Manage DiscoveryA1.1.4.4 Provide IA TaskingA1.1.4.5 Endpoint Resources
A1.1.5 Mange IA portfolioA1.1.6 Manage gig protfolio
A1.2 Maintain implementation plans
A1.3 Manage external relationships
A1.3.1 Manage IA community educationA1.3.2 Manage international relations
A2 Direct Operations A2.1 Acquire Data
A2.1.1 Provide Mission Planning
A2.1.2 Manage Health, status and perfoA2.1.3Maintain Tradecraft
A2.2 Process intercept
A2.2.4.1 Select & promote objects
A2.2.4.2 reconstruct packet streamsA2.2.4.3 Create objectsA2.2.4.4 Analyze objects
A2.3 Process DataA2.3.1 Provide Mission Planning
A2.3.2 Manage Health, status and perfoA2.3.3Maintain Tradecraft
A2.3.3.1 Identify personnel informationA2.3.3.2 transform processed dataA2.3.3.3Recognize activity of interest
A3 Enable Analysis
A3.1 Manage Mission Resources & CapabilitiesA3.1.1 Provide Mission PlanningA3.1.2 Develop Analytic TechniquesA3.1.3Maintain TradecraftA3.1.4 Provide target planning
A3.1.4.1 Identify requirementsA3.1.4.2 Conduct DiscoveryA3.1.4.3 Manage DiscoveryA3.1.4.4 Display ResultsA3.1.4.5 (U)Perform Analysis
A3.1.5 Mange IA portfolioA3.1.6 Understand Netorks
A3.2 Maintain implementation plansA3.3 Apply Information Policy
A3.3.1 Manage IA community educationA3.3.2 Content Analysis
A
C
B
ProgramsA, B & C
Within an Agency
What do I have on the floor?What do I have in Development?What areas am I doing research in?
UNCLASSIFIED
36
So why not do it on a grander scale?
JOINT ARCHITECTURE WORKING GROUP
IC CIO Requirement for FY12 Program BuildExhibit 53 & 300 Mapping to the JARM
• Exhibit 300 Data– Required: Mapping to the ECM– Required: Mapping to the ESL
• Exhibit 53 Data– Optional: Mapping to the ECM– Optional: Mapping to the ESL
• Required pre-2010– Reporting data for the FYDP, not just a single FY– Percentage of the Budget allocated to the BRM– Percentage of the Budget allocated to the SRM
37
JOINT ARCHITECTURE WORKING GROUP
Ser
vice
Dom
ain
Ser
vice
Typ
esC
usto
mer
Rel
atio
nshi
p M
anag
emen
t
Cus
tom
er P
refe
renc
es
Cus
tom
er In
itiat
ed
Ass
ista
nce
Trac
king
& W
orkf
low
Rou
ting
& S
ched
ulin
g
Man
agem
ent o
f P
roce
ss
Org
aniz
atio
nal
Man
agem
ent
Inve
stm
ent
Man
agem
ent
Sup
ply
Cha
in
Man
agem
ent
Con
tent
Man
agem
ent
Doc
umen
t Man
agem
ent
Kno
wle
dge
Man
agem
ent
Rec
ords
Man
agem
ent
Ana
lysi
s &
Sta
tistic
s
Mis
sion
Per
form
ance
Inel
ligen
ceA
naly
sis
Vis
ualiz
atio
n
Kno
wle
dge
Dis
cove
ry
Bus
ines
sIn
ellig
ence
Rep
ortin
g
Dat
aM
anag
emen
t
Hum
anR
esou
rces
Fina
ncia
lM
anag
emen
t
Ass
ets
/ Mat
eria
lsM
anag
emen
t
Dev
elop
men
t &In
tegr
atio
n
Hum
an C
apita
l /
Wor
kfor
ce M
anag
emen
t
Sec
urity
Man
agem
ent
Col
labo
ratio
n
Sea
rch
Com
mun
icat
ion
Sys
tem
sM
anag
emen
t
Form
sM
anag
emen
t
Ser
vice
Man
agem
ent
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
1 8.1.1 8.2.1 8.3.1 8.4.1 8.5.1 8.6.1 8.7.1 8.8.1 8.9.1 8.10.1 8.11.1 8.12.1 8.13.1 8.14.1 8.15.1 8.16.1 8.17.1 8.18.1 8.19.1 8.20.1 8.21.1 8.22.1 8.23.1 8.24.1 8.25.1 8.26.1 8.27.1 8.28.1 8.29.1 8.30.1 8.31.1 8.32.1 8.33.12 8.1.2 8.2.2 8.3.2 8.4.2 8.5.2 8.6.2 8.7.2 8.8.2 8.9.2 8.10.2 8.11.2 8.12.2 8.13.2 8.14.2 8.15.2 8.16.2 8.17.2 8.18.2 8.19.2 8.20.2 8.21.2 8.22.2 8.23.2 8.24.2 8.25.2 8.26.2 8.27.2 8.28.2 8.29.2 8.30.2 8.31.2 8.32.2 8.33.23 8.1.3 8.2.3 8.3.3 8.4.3 8.6.3 8.8.3 8.9.3 8.10.3 8.11.3 8.12.3 8.13.3 8.14.3 8.15.3 8.16.3 8.17.3 8.18.3 8.19.3 8.20.3 8.21.3 8.22.3 8.23.3 8.24.3 8.25.3 8.26.3 8.27.3 8.28.3 8.29.3 8.30.3 8.31.3 8.33.34 8.1.4 8.3.4 8.6.4 8.9.4 8.10.4 8.11.4 8.12.4 8.13.4 8.14.4 8.15.4 8.16.4 8.17.4 8.21.4 8.22.4 8.23.4 8.24.4 8.25.4 8.26.4 8.27.4 8.28.4 8.29.4 8.30.4 8.31.4 8.33.45 8.1.5 8.3.5 8.6.5 8.9.5 8.10.5 8.11.5 8.12.5 8.14.5 8.15.5 8.16.5 8.17.5 8.21.5 8.22.5 8.23.5 8.24.5 8.25.5 8.26.5 8.27.5 8.28.5 8.29.5 8.30.5 8.31.5 8.33.56 8.1.6 8.3.6 8.6.6 8.9.6 8.11.6 8.12.6 8.15.6 8.16.6 8.17.6 8.21.6 8.22.6 8.23.6 8.26.6 8.27.6 8.28.6 8.30.6 8.31.67 8.1.7 8.3.7 8.6.7 8.9.7 8.11.7 8.12.7 8.15.7 8.16.7 8.17.7 8.21.7 8.22.7 8.23.7 8.26.7 8.27.7 8.28.7 8.30.7 8.31.78 8.1.8 8.6.8 8.9.8 8.11.8 8.12.8 8.15.8 8.16.8 8.21.8 8.22.8 8.23.8 8.26.8 8.27.8 8.30.89 8.1.9 8.6.9 8.9.9 8.11.9 8.15.9 8.16.9 8.21.9 8.22.9 8.23.9 8.26.9 8.27.9
10 8.1.10 8.9.10 8.15.10 8.21.10 8.22.10 8.23.10 8.27.1011 8.1.11 8.9.11 8.15.11 8.21.11 8.22.11 8.23.11 8.27.1112 8.1.12 8.9.12 8.15.12 8.21.12 8.27.1213 8.1.13 8.9.13 8.15.13 8.21.13 8.27.1314 8.1.14 8.15.14 8.21.14 8.27.1415 8.15.15 8.21.15 8.27.1516 8.15.16 8.21.16 8.27.1617 8.15.17 8.21.17 8.27.1718 8.15.18 8.21.1819 8.15.19 8.21.1920 8.15.20 8.21.2021 8.15.2122 8.15.2223 8.15.23
Sup
port
Ser
vice
s
Ser
vice
Com
pone
nts
Cus
tom
er
Ser
vice
s
Pro
cess
A
utom
atio
n S
ervi
ces
Bus
ines
sM
anag
emen
tS
ervi
ces
Dig
ital A
sset
Ser
vice
s
Bus
ines
s A
naly
tics
Ser
vice
s
Bac
k O
ffice
Ser
vice
s
JARM Enterprise Services List (ESL)
38
Ass
ista
nce
Trac
king
& W
orkf
low
Rou
ting
& S
ched
ulin
g
Man
agem
ent o
f P
roce
ss
Org
aniz
atio
nal
Man
agem
ent
Inve
stm
ent
Man
agem
ent
Sup
ply
Cha
in
Man
agem
ent
Con
tent
Man
agem
ent
Doc
umen
t Man
agem
ent
Kno
wle
dge
Man
agem
ent
Rec
ords
Man
agem
ent
Ana
lysi
s &
Sta
tistic
s
Mis
sion
Per
form
ance
Inel
ligen
ceA
naly
sis
Vis
ualiz
atio
n
Kno
wle
dge
Dis
cove
ry
Bus
ines
sIn
ellig
ence
Rep
ortin
g
Dat
aM
anag
emen
t
Hum
anR
esou
rces
Fina
ncia
lM
anag
emen
t
Ass
ets
/ Mat
eria
lsM
anag
emen
t
Dev
elop
men
t &In
tegr
atio
n
Hum
an C
apita
l /
Wor
kfor
ce M
anag
emen
t
Sec
urity
Man
agem
ent
Col
labo
ratio
n
Sea
rch
Com
mun
icat
ion
3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
8.3.1 8.4.1 8.5.1 8.6.1 8.7.1 8.8.1 8.9.1 8.10.1 8.11.1 8.12.1 8.13.1 8.14.1 8.15.1 8.16.1 8.17.1 8.18.1 8.19.1 8.20.1 8.21.1 8.22.1 8.23.1 8.24.1 8.25.1 8.26.1 8.27.1 8.28.1 8.29.1 8.30.18.3.2 8.4.2 8.5.2 8.6.2 8.7.2 8.8.2 8.9.2 8.10.2 8.11.2 8.12.2 8.13.2 8.14.2 8.15.2 8.16.2 8.17.2 8.18.2 8.19.2 8.20.2 8.21.2 8.22.2 8.23.2 8.24.2 8.25.2 8.26.2 8.27.2 8.28.2 8.29.2 8.30.2
Aut
omat
ion
Man
agem
ent
Dig
ital A
sset
Bac
k O
ffice
8.3.3 8.4.3 8.6.3 8.8.3 8.9.3 8.10.3 8.11.3 8.12.3 8.13.3 8.14.3 8.15.3 8.16.3 8.17.3 8.18.3 8.19.3 8.20.3 8.21.3 8.22.3 8.23.3 8.24.3 8.25.3 8.26.3 8.27.3 8.28.3 8.29.3 8.30.38.3.4 8.6.4 8.9.4 8.10.4 8.11.4 8.12.4 8.13.4 8.14.4 8.15.4 8.16.4 8.17.4 8.21.4 8.22.4 8.23.4 8.24.4 8.25.4 8.26.4 8.27.4 8.28.4 8.29.4 8.30.48.3.5 8.6.5 8.9.5 8.10.5 8.11.5 8.12.5 8.14.5 8.15.5 8.16.5 8.17.5 8.21.5 8.22.5 8.23.5 8.24.5 8.25.5 8.26.5 8.27.5 8.28.5 8.29.5 8.30.58.3.6 8.6.6 8.9.6 8.11.6 8.12.6 8.15.6 8.16.6 8.17.6 8.21.6 8.22.6 8.23.6 8.26.6 8.27.6 8.28.6 8.30.68.3.7 8.6.7 8.9.7 8.11.7 8.12.7 8.15.7 8.16.7 8.17.7 8.21.7 8.22.7 8.23.7 8.26.7 8.27.7 8.28.7 8.30.7
8.6.8 8.9.8 8.11.8 8.12.8 8.15.8 8.16.8 8.21.8 8.22.8 8.23.8 8.26.8 8.27.8 8.30.88.6.9 8.9.9 8.11.9 8.15.9 8.16.9 8.21.9 8.22.9 8.23.9 8.26.9 8.27.9
8.9.10 8.15.10 8.21.10 8.22.10 8.23.10 8.27.108.9.11 8.15.11 8.21.11 8.22.11 8.23.11 8.27.118.9.12 8.15.12 8.21.12 8.27.128.9.13 8.15.13 8.21.13 8.27.13
8.15.14 8.21.14 8.27.14
JARM Enterprise Competency Model (ECM)
JOINT ARCHITECTURE WORKING GROUP
Ser
vice
Dom
ain
Ser
vice
Typ
es
Cus
tom
er R
elat
ions
hip
Man
agem
ent
Cus
tom
er P
refe
renc
es
Cus
tom
er In
itiat
ed
Ass
ista
nce
Trac
king
& W
orkf
low
Rou
ting
& S
ched
ulin
g
Man
agem
ent o
f P
roce
ss
Org
aniz
atio
nal
Man
agem
ent
Inve
stm
ent
Man
agem
ent
Sup
ply
Cha
in
Man
agem
ent
Con
tent
Man
agem
ent
Doc
umen
t Man
agem
ent
Kno
wle
dge
Man
agem
ent
Rec
ords
Man
agem
ent
Ana
lysi
s &
Sta
tistic
s
Mis
sion
Per
form
ance
Inel
ligen
ceA
naly
sis
Vis
ualiz
atio
n
Kno
wle
dge
Dis
cove
ry
Bus
ines
sIn
ellig
ence
Rep
ortin
g
Dat
aM
anag
emen
t
Hum
anR
esou
rces
Fina
ncia
lM
anag
emen
t
Ass
ets
/ Mat
eria
lsM
anag
emen
t
Dev
elop
men
t &In
tegr
atio
n
Hum
an C
apita
l /
Wor
kfor
ce M
anag
emen
t
Sec
urity
Man
agem
ent
Col
labo
ratio
n
Sea
rch
Com
mun
icat
ion
Sys
tem
sM
anag
emen
t
Form
sM
anag
emen
t
Ser
vice
Man
agem
ent
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
1 4 6 6 10 3 12 4 8 11 4 4 9 4 1 1 0 4 4 3 9 10 1 6 8 10 2 13 7 9 4 10 2 82 2 4 6 4 3 12 8 3 5 4 3 6 8 1 0 2 1 3 2 8 7 1 5 6 9 1 13 5 1 4 6 2 43 2 6 6 1 13 4 7 2 4 7 3 0 2 1 1 5 4 5 9 2 5 7 9 4 7 6 3 4 10 44 7 2 15 5 3 7 6 0 0 3 2 2 5 2 2 5 9 1 8 6 2 3 7 55 2 0 9 8 0 4 4 2 2 1 2 4 3 4 8 9 0 7 3 4 5 9 96 8 2 13 10 3 7 2 0 0 4 1 4 1 8 4 5 127 4 8 8 3 4 5 2 0 3 7 1 2 0 6 4 1 118 8 14 4 5 2 0 3 10 1 4 0 9 49 5 10 1 6 1 2 6 3 4 0 10
10 7 2 0 4 1 2 511 4 3 1 9 2 1 612 5 2 1 11 913 7 1 0 12 214 6 0 3 515 2 10 516 2 1 217 1 2 118 1 219 1 320 0 121 122 223 3
Sup
port
Ser
vice
s
Ser
vice
Com
pone
nts
Cus
tom
er
Ser
vice
s
Pro
cess
A
utom
atio
n S
ervi
ces
Bus
ines
sM
anag
emen
tS
ervi
ces
Dig
ital A
sset
Ser
vice
s
Bus
ines
s A
naly
tics
Ser
vice
s
Bac
k O
ffice
Ser
vice
s
All (22) Ex 300 Programs Mapped to ESL for FY12
39
(U) Do the circled boxes indicate potential critical business service gaps? We do not know. Data set is incomplete.
(U) ESL Component 8.3.5 Multi-Lingual Support defines the set of capabilities that allow access to data and information in multiple languages.
JOINT ARCHITECTURE WORKING GROUP
Most Common JARM ESL Mappings in Ex 300s for FY12
• Product Management• Customer/Account Management• Alerts and Notifications• Process Tracking• Requirements Management• Program/Project Management• Governance/Policy Management• Quality Management• Business Rule Management• Risk Management• Procurement
At least five (out of six) of the reporting agencies mapped to each of the following service components for FY12 within the JARM ESL:
• Invoice Requisition Track/Approve • Library Storage• Document Creation/Validation• Information Retrieval• Information Mapping/Taxonomy• Information Sharing• Knowledge Capture• Document Classification• Ad-Hoc• Standardized/Canned• Data Exchange
Mapping of all Ex 300 reporting programs across the community highlights areas where the IC might collaborate today in our respective development efforts
The “heat map” shows all service component mappings across all six agencies [for illustration only]
(Source: Exhibit 300s)
• Data Warehouse• Data Recovery• Data Access• Cross Domain Data Transfer• Software Development• Identification and Authentication• Access Control• Query• Systems Engineering
40
JOINT ARCHITECTURE WORKING GROUP
Ser
vice
Dom
ain
Ser
vice
Typ
esC
usto
mer
Rel
atio
nshi
p M
anag
emen
t
Cus
tom
er P
refe
renc
es
Cus
tom
er In
itiat
ed
Ass
ista
nce
Trac
king
& W
orkf
low
Rou
ting
& S
ched
ulin
g
Man
agem
ent o
f P
roce
ss
Org
aniz
atio
nal
Man
agem
ent
Inve
stm
ent
Man
agem
ent
Sup
ply
Cha
in
Man
agem
ent
Con
tent
Man
agem
ent
Doc
umen
t Man
agem
ent
Kno
wle
dge
Man
agem
ent
Rec
ords
Man
agem
ent
Ana
lysi
s &
Sta
tistic
s
Mis
sion
Per
form
ance
Inel
ligen
ceA
naly
sis
Vis
ualiz
atio
n
Kno
wle
dge
Dis
cove
ry
Bus
ines
sIn
ellig
ence
Rep
ortin
g
Dat
aM
anag
emen
t
Hum
anR
esou
rces
Fina
ncia
lM
anag
emen
t
Ass
ets
/ Mat
eria
lsM
anag
emen
t
Dev
elop
men
t &In
tegr
atio
n
Hum
an C
apita
l /
Wor
kfor
ce M
anag
emen
t
Sec
urity
Man
agem
ent
Col
labo
ratio
n
Sea
rch
Com
mun
icat
ion
Sys
tem
sM
anag
emen
t
Form
sM
anag
emen
t
Ser
vice
Man
agem
ent
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
1 1000 4 1000 1000 1000 1000 4 1000 1000 1000 1000 6 1000 1000 1000 1000 1000 1000 1000 1000 5 1000 1000 1000 1000 1000 5 3 6 2 1000 1000 32 1000 4 1000 1000 1000 1000 4 1000 1000 1000 1000 5 5 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 5 3 1 2 1000 1000 43 1000 5 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1 1000 1000 1000 1000 1000 1000 1000 1000 2 2 4 1000 1000 1000 34 1000 1000 1000 1000 3 1000 4 1000 0 1000 1000 1000 3 1000 1000 1000 1000 1000 3 3 1000 2 1000 45 1000 1000 1000 1000 1000 1000 1000 2 1000 1000 1000 1000 1000 1000 3 1000 1000 3 2 1000 4 1000 10006 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 4 2 3 10007 1000 1000 1000 1000 4 4 1000 1000 1000 1000 1000 1000 1000 3 2 1 10008 1000 1000 1000 4 1000 1000 1000 1000 1 1000 1000 4 29 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000
10 1000 1000 1000 1000 1000 1000 100011 1000 1000 1000 1000 1000 1000 312 1000 1000 1000 1000 413 1000 1000 1000 1000 100014 1000 1000 2 100015 1000 5 100016 1000 1000 100017 1000 1000 100018 1000 100019 1000 100020 1000 100021 100022 100023 2
Sup
port
Ser
vice
s
Ser
vice
Com
pone
nts
Cus
tom
er
Ser
vice
s
Pro
cess
A
utom
atio
n S
ervi
ces
Bus
ines
sM
anag
emen
tS
ervi
ces
Dig
ital A
sset
Ser
vice
s
Bus
ines
s A
naly
tics
Ser
vice
s
Bac
k O
ffice
Ser
vice
s
ESL Mapping Snapshot: IC Core Overlay
41
Ser
vice
Dom
ain
Sup
port
Ser
vice
s
Cus
tom
er
Ser
vice
s
Pro
cess
A
utom
atio
n S
ervi
ces
Bus
ines
sM
anag
emen
tS
ervi
ces
Dig
ital A
sset
Ser
vice
s
Bus
ines
s A
naly
tics
Ser
vice
s
Bac
k O
ffice
Ser
vice
s
Ser
vice
Dom
ain
Man
agem
ent
Dig
ital A
sset
Bac
k O
ffice
(U) The circled boxes indicate Enterprise Service components in which 1 or fewer of the 6 reporting agencies are investing. (Exhibit 300s, FY12)
.
8.29.2 Precision / Recall Ranking – Defines the set of capabilities that support selection and retrieval of records ranked to optimize precision against recall.
42
Less than 5% of the budget accounted for in the Exhibit 300’syet we still find overlaps in capability.
Think about what we might find if everything was aligned to a common framework
43
Some Final Thoughts regarding IT Efficienciesand Enterprise Architecture
Where will the cost savings come from?
44
People attending the conference ~600
($300K per contractor, $250K per govie,say, 2/3 of audience is contractor, 1/3 govie) $120,000,000
+ $ 50,000,000------------------$170,000,000/year
Annual Loaded Cost to Government ($300K/per year)
Associated Activity: Architecture
50% to 75% of an Agency’s budget goes to manpower!
$180,000,000/year
JOINT ARCHITECTURE WORKING GROUP 45
JOINT ARCHITECTURE WORKING GROUP
The Bottom Line on the JAWG• We work together collaboratively• Each IC Element has unique skills and abilities, that when
combined with other IC Elements’ respective skills and abilities supports the overarching Mission of the Intelligence Community
• IT is all about providing agility for the Mission; a force multiplier!
• Our JARM tools can scale and are usable at multiple levels of an organization/enterprise/community, for many different perspectives.
• It is all about providing “…any data, any time, any place, usable by any authorized consumer; preventable only by law or policy, not technology.”
46
JOINT ARCHITECTURE WORKING GROUP
For More Information:
►JAWG on Intelink:– (JWICS) www.intelink.ic.gov/wiki/Joint_Architecture_Working_Group– (NIPR) www.intelink.gov/wiki/Joint_Architecture_Working_Group
► More Questions:– [email protected]– [email protected]
JOINT ARCHITECTURE WORKING GROUP
Questions
48
The greater danger for most of us lies not in setting our aim high and falling short;
but in setting our aim too low, And achieving our mark.”
…Michelangelo