Department of the Navy Enterprise Architecture Enterprise Taxonomies Briefing for AFD Working Group 11 July 2002
Department of the NavyEnterprise Architecture
Enterprise Taxonomies
Briefing for AFD Working Group11 July 2002
Outline
• Taxonomies and Architecture– Why are they important?– How is DON implementing?
• Taxonomy Tool– CADM– CONOPS– Use in architecture data development
• Demo
Taxonomies?
• Categorization (types-of) and composition (parts-of) are so fundamental to human reasoning they are almost indescribable, yet are essential to almost all human thought
• They are the most valuable tool known for dealing with what would otherwise be an intractably complex number of variables
• Hence their critical role in dealing with the intractably large number of variables in large enterprise architectures
Major Taxonomy Types in Architecture
1. Operational Nodes2. Process-Activities3. Information Elements4. System Functions5. Systems6. Platforms / Facilities / Units7. Performance Attributes8. Technical Standards9. Science and Technology
Taxonomies Relationships to AFD Reports
The dictionary of words or terms used in the architectureThe Enterprise common terms of reference (SME’s already use)The Enterprise objects and elementsThe categories and composition of those objects and elements
Taxonomies =
OV2
OV5
OV3
OV7
SV4p1
SV5
SV1p2/3
SV1p1b
TV1 SV7SV8
SV11
SV9
TV2SV6p1SV1p1SV4p2
SV6p2
Mapping Metadata to Info.
Elements
10. SystemTech.
Taxonomy
10. SystemTech.
Taxonomy
OV4
9. Technical
Stds.Taxonomy
9. Technical
Stds.Taxonomy 8.
Comm/Network Types
8. Comm/Network
Types
1. Op Nodes
1. Op Nodes
2. Processes / Activities
2. Processes / Activities
3. Info.Elements3. Info.
Elements
4. SystemFunctions
4. SystemFunctions
5. Platforms / Facilities /
Units
5. Platforms / Facilities /
Units6. SystemsTaxonomy
6. SystemsTaxonomy
SV2
7. PerformanceAttribute
Templates
7. PerformanceAttribute
Templates
SV6p1SV1p2/3
SV1p2/3 = System Interface Description, Intranodal and IntrasystemSV6p1SV1p1 = System Information Exchange Desription, InternodalSV6p1SV1p2/3 = System Information Exchange Description, Intranodal and Intrasystem
Product Subparts Legend:SV4p1 = System Functions TaxonomySV4p2 = Function Information Flow Spec./Desc.SV4p3 = Functional AllocationSV1p1a = Operational Node PFU Operation Rqmts/Desc.SV1p1b = System Interface Description, Internodal
SV4p3
SV1p1a
Reports
EnterpriseTaxonomies
Challenge
• Consensus and communication across a large enterprise– No mature, complete, or well-defined starting points– Many legitimate and useful categorizations– Definition of terms– Tools didn’t exist until recently
• Flat tools (Excel, PowerPoint, Word) don’t work
• Need– Central Forum for debate– Tools (see next slide)
Taxonomy Tools
Find by various criteriaMatch up like concepts
Many-many mappingRelate to local taxonomies or multiple authoritative sources
Move branchesTrial branch moves
RestructureMergeReconcileCollapse and expand branchesNavigate the taxonomyTree, hierarchy“See” the taxonomy
What the DON is Doing with the 23 Functional Area Managers
• General session to layout top-tier of taxonomy and procedures
• Install startup DB’s with FAM teams (23 synchronizable DB’s)
• Upload and sync periodically or when done
• Sync and download
• Convene general session for any needed reconciliation
T1 T/OCT/OC
T/OCT/OC
T1 T/OCT/OC
T/OC
T/OC
DON Taxonomy Tools
Facilities, Locations, Units, and Platforms
FLUPs
Standards
Performance
FunctionsSystems
Data Information
Tasks / ActivitiesOrganizations
A database
An application
- DoD designed (CADM)- Open
Functions -->>>
Sys tem/Application v v 24
.1.1
- E
xecu
te e
ngag
emen
t (E
E)
24.1
.2 -
For
ce P
ositi
onin
g (F
P)
24.2
.1 -
Dec
isio
n (D
)
24.2
.2 -
Pla
n (P
)
24.2
.3 -
Situ
atio
nal A
sses
smen
t (S
A)
24.3
.1 -
Com
mun
icat
e C
omm
on
Nav
igat
ion
& T
ime
Dat
a (C
NT)
24.3
.2 -
Com
mun
icat
e fo
rce
orde
rs (
CFO
)
24.3
.3 -
Com
mun
icat
e IS
R D
ata
(CIS
R)
24.3
.4 -
Com
mun
icat
e or
der
(CO
)
24.3
.5 -
Com
mun
icat
e se
nse
da
ta (
CSD
)
24.3
.6 -
Com
mun
icat
e st
atus
(C
S)
24.4
.1 -
Com
mon
Tac
tical
Pic
ture
(C
TP)
24.4
.2 -
Int
ellig
ence
, Sur
veill
ance
, R
econ
nais
sanc
e (I
SR)
24.4
.3 -
Tac
tical
Sen
se (
TS)
1.1.1 - (AADC) AREA AIR DEFENSE COMMANDER SYSTEM � �
1.1.7 - GCCS � �
1.2.1 - (AWS) AEGIS WEAPONS SYSTEM � � � � � � � � �
1.2.12 - AN/USG -2(V) Coope ra tive Engage me nt Ca pa bility (CEC) � �
1.2.17 - MC (E-2C) � � �
1.2.18 - MC(F-14) � � � � � �
1.2.19 - MC(F/A-18 C/D) � � � � � �
1.2.20 - MC(F/A-18 E/F) � � � � � �
1.2.21 - MC(J SF) � � � � � �
1.2.22 - MCU (E-2C) �
1.2.3 - (NTDS) Na va l Ta ctica l Da ta Syste m � �
1.2.4.1 - Ship Se lf Defe nse Syste m, MK 1 MOD 0 � � � � � � � �
1.2.4.2 - Ship Se lf Defe nse Syste m, Mk 2 � � � � � � � �
1.2.9 - AN/SYQ-20(V) Adva nce d Combat Dire c tion Syste m � � � � � � � � �
10.1 - Adv. Se nsor Ne tting � �
10.10 - NUCAV + EO/IR �
10.11 - Re a ctive Warhe ad �
10.12 - SBIRS - Low �
10.13 - SM-3 �
10.14 - SM-5 �
10.15 - TAMD Ra da r S � �
10.16 - TAMD Ra da r X � �
10.17 - UESA �
10.18 - VSR �
10.2 - Auto ID �
10.3 - CCID �
Overlap Co unt 46 10 10 4 10 4 3 5 18 12 12 15 5 28
Taxonomy and Mapping Tools
Biz Process Modeling Tools
FoS / SoS / and System / App
Characterization Tools
Interface and Comms
Characterization Tools
System / App Requirements
Tools
Reporting and Diagramming
Tools
Export, Import, and Shared Data
Tools
Taxonomy and Mapping Tools
Biz Process Modeling Tools
FoS / SoS / and System / App
Characterization Tools
Interface and Comms
Characterization Tools
System / App Requirements
Tools
Reporting and Diagramming
Tools
Export, Import, and Shared Data
Tools
Why Taxonomies and CADM Are Essential to an EA
• An EA Cannot be Construed From “Stovepiped” Architectures– “Product” or diagram driven
• employing various artistic tools; spreadsheets, word processors, home-made stand-alone databases, etc.– Replicates the current problem of stovepiped systems, one of the primary problems architectural techniques
were created to address!– All specific architectures need to be within the context of others, that is, an EA
• To achieve a true EA:– Standard architectural concepts and conceptual relationships.
• largely accomplished by the AFD and CADM– Products are used to communicate but the real strength lies in the underlying data
• Products referenced in the Architecture Framework are predefined subsets of the architecture’s information– Common architecture object taxonomies.
• often overlooked• learned over many years to be critical to architecture success
– Architecture data sharing and reuse• relate to the vast number of architectural objects within the DON and with which the DON interoperates• many stakeholders in the enterprise architecture
– not developed as a single effort, but is made up of data throughout the enterprise that is » continuously developed» validated» maintained» evolves over time.
– sources of the data may be varied and loosely coupled, – architecture federated but shared and integrated
• Needed:– Tool built from the ground-up as CADM-compliant so CADM’s object model is inherent
• Import/export, interfaces, subsets, translators, etc. have many un-addressed issues, e.g., lossy translations, non-affine models
– Taxonomy tools– Sharing and re-use tools– Manipulation tools for fundamental architectural data– Basic reporting and product tools
Taxonomies are a Big Part of CADMSource Code:Blue = DMIRGreen = DIADTurq = Both
Source Code:Blue = DMIRGreen = DIADTurq = Both
employs
include
pertains to
is needed to achieve
performs to
complies with
is needed by
is needed by
is needed by
includes is a part of
specify
performs to
complies withis a component of
is dependent on
is the consumer of
is the producer of
is a component of
maps to
may be a
may be used as a
may be supported by
applies to
identifies a set of values for
is-described-by
P
Bases
Areas
Info Stds
Information Processing
HCI
IA
Condition
Mission Capabilty
Association type codes:connected tolinked withis a part ofis a subtype ofis type ofis installed/assigned tois allocated tosupportsperformmust be done beforemust be started beforeoperate at or in
Type of Op Node
Operational Nodes
Military UnitsOPFACs
EQUIPMENT-TYPE
SECURITY-CLASSIFICATION
PLAN
Events
Occupational Specialities
System Functions
Information Exchange
Time Period
TECHNICAL-SERVICE
Comm Protocol
OBJECT-CLASS
DATA-DICTIONARY
INFORMATION-TECHNOLOGY-STANDARD Category Code
Platforms
DATA-ATTRIBUTE
DATA-ENTITY
DATA-DOMAIN
INFORMATION-ELEMENT
CONCEPTUAL-DATA-MODEL
INTERNAL-DATA-MODEL
INFORMATION-ASSET TYPE CODE
INFORMATION-ASSET
FUNCTIONAL-AREA
NETWORK
Systems
Node AssociationsNodes
Architectures
Missions
TECHNOLOGY
Standard
SOFTWARE-ITEM
Profile
Organizations
Performance Characteristic
Actions
GUIDANCE
Organization Types
AGREEMENT
Tasks
Mission-Areas
Materiel Items
Process-Activities
REFERENCE-MODEL-SERVICE
Buildings
Facilities
Facility Types
Aircraft
Space
Physical Nodes
Ships
Physical Node Types
An IRS is in development
An IRS is in development
DIAD DB
ADMS DB
NDE DBs
GIG DB
TBD DBs
NCEE DBs
3. Modeling and Analysis
Tools
3. Modeling and Analysis
Tools
1. Authoritative Data Sources,
stakeholders and oversight
1. Authoritative Data Sources,
stakeholders and oversight
2. Interfaces2. Interfaces
Org
aniz
atio
ns
Activ
ities
/Tas
ks
Info
rmat
ion
Dat
a
Syst
ems/
Apps
Syst
em F
unct
ions
Perfo
rman
ce
Cha
ract
eris
tics
Tech
nica
l Std
s
Faci
litie
s / L
ocat
ions
/ U
nits
/ Pl
atfo
rms
DON CIO o o o o o o o A oASN RDA o A A s sNavy / Marine Corps IOs s s s sFAMs s A A A s s AFDMs A AEch 2 CHENG/CIO s s s s A sEch 2 PM's s s s s sNWDC/MCCDC A A s s
Facilities / Locations / Units / Platforms(FLUP interfaces)
Taxonomies
Architecture Data
Systems/Apps(Interfaces, Functional allocation, Performance & Tech Stds, assign/install to FLUPs)
System Functions(Funcational design, perf characteristics, tech stds per function)
Performance Characteristics(relate to Tech Stds, spec for FLUPs)
Technical Stds(Interdependency, spec to FLUPs)
Organizations(Needlines, Command Relationships, Info Rqmts, FLUP rqmts)
Activities/Tasks(Activitylines, Sequences, Activity Info Rqmts)
Information(Data mapping, System / App, System Function, FLUP interfaces)
Data(System / App, FLUP, System Function interfaces)
(symetric)
DON CONOPS Vision
DIAD ApplicationBPWinRational RoseBonapartSystem ArchitectNetVizVisioMS ProjectDOT/NEATOCOREOPNETG2NetwarsExtendDOORSJCOATNaval Simulation SystemSLATEAppliCADothers TBD
Challenge
• Meet the letter of the law:– AFD– OMB– Etc.
• Also must be:– Useful– Easy but rigorous; high-level but detailed; graspable but full-
featured; overview but in-depth; simple but complex; quick-and-dirty but authoritative-and-executive-DSS; no-training-required but sophisticated; object-oriented but diagramatic; pictures but CADM; etc.
Taxonomy Tools Demo
• AV-2 Taxonomy Tools– Building and re-arranging– Importing and mapping– Using
• Use in Building Products