Embed Size (px)
Citation preview
1
Continuity Communications
Working Group
Status Report
Mr. Roy Roebuck
Chief Architect
Continuity Communications Enterprise
Architecture Program Office
August 5, 2005
2
Background…
• September 11th
– Illustrated that the Federal Executive Branch (FEB) does not have the ability to quickly access and share information, collaborate among senior leaders, and make informed decisions.
• Enduring Constitutional Government Coordination Council (ECG CC) Report– Review of the FEB’s COOP, COG, and ECG preparedness
– ECG CC Report Tasks include:• Complete an evaluation of government-wide COOP communications capabilities
• Establish Minimum Communications Requirements for the Federal Executive Branch
• Create a Continuity Communications Enterprise Architecture (CC EA) to ensure execution of FEB Mission Essential Functions under all circumstances
• Tasked to the National Communications Systems (NCS) Committee of Principals (COP)– Established the Continuity Communications Working Group (CCWG)
• ASD NII – Chair
• FEMA – Co-Chair
– Established the CC EA Program Office• CCWG Terms of Reference (TOR) assigned tasking through August 2005
3
Key Questions, Initial Round…
• Basic Communications
• Telephone
• Fax
• No VTC
• No E-Mail
• Etc….
PM
EF
1
PM
EF
2
U.S. Government
PM
EF
8
PM
EF
7
PM
EF
5
PM
EF
6
• Basic Communications
• Telephone
• Fax
• Etc….
PM
EF
3
Department A PM
EF
4Department B
• Basic Communications
• Telephone
• Fax
• SVTS….
• Etc….
Department C
Key Questions
• Can the D&A Priority Mission Essential Functions (PMEF) be
performed at a COOP site?
• Can information about PMEFs be shared to support a common
operational picture and collaborative planning by senior
leadership?
• What are the Minimum COOP Communications Capabilities?
• What communications support execution of PMEFs
• Do systems used to execute PMEFs use common standards?
4
Illustration of OMG FEA Reference Models
(Taxonomies) For IT Investment Management
BRM PRM SRM DRM TRM
Measurement
Area
Measurement
Categories
Measurement
Indicators
Project
Plans
Planning, Operation,
Development, and
Maintenance Performance
Funding Strategy
Performance
and Progress
Assessment
Service Domain
Service Type
Service
Component
Technical Service
Area
Technical Service
Category
D&A IT
Exh 300 (Development,
Implementation), and
Exh 53 (Operation, and
Maintenance)
CPIC
Technical
Service Standard
D&A Technology
Product Specification
Business
Area
Line of
Business
SubFunction
Exh. 300
and 53
Submissions
FEA RM Item
D&A FEA Extension and IT
EA/IT Ontology
And Semantics
(Orthogonal to
Taxonomies)
EA/IT
Taxonomy
And
Semantics
Metadata
(Context)
Metadata
(Container)
Data
(Content)
OMB FEA
Reference
Models
FEA, to Establish Federal IT Investment Governance
5
Typical D&A FEA Extension,
For IT Investment Management
BRM PRM SRM DRM TRM
D&A IT
Management
Measurement
Area
Measurement
Categories
Measurement
Indicators
Project
Plans
Planning,
Operation,
Development, and
Maintenance
Performance
Funding Strategy
Acquisition Strategy
Performance
and Progress
Assessment
Service
Domain
Service
Type
Service
Component
Technology
Area
Technology
Category
IT Product
Inventory
IT Development
And Implementation
Process (CMMI)
Infrastructure
(System of Systems)
Engineering Project
System
Engineering
Project
Software
Engineering
Project
CPIC
IT Operations
And Maintenance
(ITIL)
Technology
Standard
D&A Technology
Product Specifications
Business
Area
Line of
Business
SubFunction
Exh. 300
and 53
Metadata
(Context)
Metadata
(Container)
Data
(Content)
OMB FEA
Reference
Models
Vendor
Version
Release
Source
Brand
EA/IT
Taxonomy
And
Semantics
EA/IT Ontology
And Semantics
(Orthogonal to
Taxonomies)
FEA RM Item
Typical D&A FEA
Extension Into IT
Management
EA to Satisfy OMB Exhibit 300 and 53 Requirements and Facilitate IT Decisions
6
CC EA Requires Extension Of The
OMB FEA Beyond Investment Management
1. BRM(Assigned Functional
Missions + Assumed
Supporting Functions)
2 and 7. PRM
(Strategic Mgmt, Ops & Invest.
Strategies, Priorities)
3. SRM
(Best Practice,
Re-usable
Processes)
4. DRM
(Metadata)
5. TRM
(Technology
Catalog and
Qualifying
Products)
6.5.1 D&A Physical IT
6.5.1.1 D&A Systems
6.5.1.2 D&A Infrastructure
OMB FEA
CC EA
.01 .02 .03 .04 .05 .06LOCATION
CATALOG
ORGANIZATION
CATALOG
WORK UNIT
(OFFICE/BILLET)
CATALOG
FUNCTION
CATALOG
(BRM+)
PROCESS
CATALOG
(SRM+)
RESOURCE
CATALOG
(DRM+/TRM+)
MISSION
CATALOG
(PRM+)
.07
1.0
ENTERPRISE
CONTAININGCONTAINING CONTAINING CONTAINING CONTAINING CONTAINING CONTAINING
7
CC EA Information Structure
(Upper/Integrating Ontology)
Location Contains Organization
Organization Organizes Billets
Billet Accomplishes Function
Function Applies Process
Process Produces/Consumes Resource
.01 .02 .03 .04 .05 .06LOCATION
CATALOG
ORGANIZATION
CATALOG
WORK UNIT
(OFFICE/BILLET)
CATALOG
FUNCTION
CATALOG
(BRM+)
PROCESS
CATALOG
(SRM+)
RESOURCE
CATALOG
(DRM+/TRM+)
MISSION
CATALOG
(PRM+)
.07
Resource Satisfies Requirement
1.0
ENTERPRISE
Organization Occupies Location
Billets Perform Mission
Function Justifies Billet
Process Achieves Function
Resource Inputs-To/Results-From Process
Requirements are Satisfied by Resource
CONTAINING
The CC EA approach extends the OMB FEA
Enterprise operational management capability
CONTAINING CONTAINING CONTAINING CONTAINING CONTAINING CONTAINING
8
CC EA Has An Extended OMB FEA
Structure
1. BRM
(Assigned Functional Missions
+ Assumed Supporting
Functions)
1.1 Policy
1.2 Assignment
1.3. Strategic Management
2. PRM
(Strategic Mgmt, Ops & Invest.
Strategies, Priorities)
7. PRM (Portfolios, Budgets)
3. SRM
(Best Practice,
Re-usable
Processes)
4. DRM
(Metadata
and Data)
5. TRM
(Technology
Catalog of
Standards and
Qualifying
Products)
Service Oriented Architecture (SOA)Enterprise Service Bus
(ESB)
6. Organization Unit
(OU) Assigned The
Asset
1. Parent Organization
of OU
1. Location of OU
(Physical and Virtual)
1. OU Assigned
Functional
Responsibility
Schema and/or Data
Added by CC EA
Schema and Data Largely or
Wholly Present in FEA
6. Required Mission
Resources over their life
cycle.
6.1 People
6.2 Intelligence
6.2.1 Functional Intelligence
6.2.2 CC Intelligence
6.3 Funds
6.4 Skills
6.4.1 CC Skills
6.5 Materiel
6.5.1 Physical IT
6.5.1.1 Systems
6.5.1.1.1 CC Systems
6.5.1.2 Infrastructure
6.5.1.2.1 CC Infrastructure
6.5.2 Goods
6.6 Facilities
6.6.1 CC Facilities
6.7 Services
6.7.1 CC Services
6.8 etc.
Enterprise Architecture
Service (e.g., Loosely Coupled, NetCentric)
Capability Process Improvement and Solution Design
Operational Capability (Primary and Alternate Sites, Primary and Alternate Providers)
Norm
al and C
C C
apabili
ty B
usin
ess C
ase a
nd B
udget
Capability Implementation
1. NEF/PMEF
9
CCEA FEA Extension For Operations Management
And Architecture Integration (FYO5 Plan)
Function
Catalog
Mission
CatalogProcess
Catalog
Resource (Data)
CatalogResource (Technology)
Catalog
D&A Resource (e.g. IT)
Management
Reference
(What)
Policy
Process
(SRM Service Domain)
Procedure (Rules)
(SRM Service Type)
Template Forms, Reports,
etc.) (SRM Service
Component)
Metadata
(DRM Item)
Technology
(TRM Item)
Assignment
(Who)
Responsibility
Authority
Budget
Performance
Targets
BRM
Controlled
Vocabulary
Organization
Unit Catalog
Organization
Catalog
Location
Catalog
Functional
Semantics
Functional
Planning
Spiral Life Cycle
(Priority)
Mission
Vision
Goal
Objective
(Indicators)
Strategy (Portfolio)
Plans (When
Resource
Requirements,
Dependency,
Schedule)
Recurring Plans
Initiative Plans
Performance
Funding Strategy
Acquisition Strategy
Assessment (Performance,
Plan, Strategy, Value-Chain,
SWOT, Risk, Vulnerability,
and Mission)
Functional
Services
Service (i.e., Performance)
Level Management (SLM)
Metadata
Data ETL
Data Migration
Virtual DB
Controlled Technology
Product Catalog (TRM)
Technology
Time Phasing
IT Product
Inventory
Vendor
Version
Release
IT Development
And Implementation
(CMMI)
Infrastructure
(System of Systems)
Engineering
System
Engineering
Software
Engineering
CPIC
IT Operations
And Maintenance
(ITIL)
Technology
Insertion
and
Deprecation
EA, IT, CM, DB, SPEM, BPM, AD, LDAP Metadata (e.g., MOF)
Repository
Taxonomy
(Controlled
Vocabulary
Inheritance
Relations)
Concept Map
(Associative
Relation)
Semantic
Data Model
Ontology
Knowledge
Base
Source
EA Composition
(EA/IT Subject Taxonomy
and Controlled
Vocabulary)
EA “Line of Sight”
(EA/IT Subject Associations, Giving
Semantic and Ontology Context)
OMB FEA
Reference
Models
CC EA
Reference
Catalogs
Records Management and
Asset Management
Business Area
Line of Business
SubFunctions
Function Catalog
(BRM Extension)
Measurement
Area
Measurement
Categories
Measurement
Indicators
Mission Catalog
(PRM Extension)
Service
Component
Service
Type
Service
Domains
Process Catalog
(SRM Extension)Resource Catalog
(DRM Extension)
Resource Catalog
(TRM Extension)
Technical Service
Area
Technical Service
Category
Technical
Service Standard
Product
Evaluation
Process
Vendor
Version
Release
Source
Metadata
(Context)
Metadata
(Container)
Data
(Content)
Brand
Brand
Mission Catalog (MC)
Organization Unit Catalog (FC)
Process Catalog (PC)
Resource Catalog –
Data (RC-D)
Resource Catalog –
Technology (RC-T)
Organization Catalog (OC)
Function Catalog (FC)
Location Catalog (LC)
PRM SRM DRM TRM
COOP
Capability
PMEF
SMEF
NEF
EA as Whole-Enterprise System Analysis, Requirement Analysis, and Operational Model
10
CC EA Framework Model
1 – 1
Location
Catalog
1 – 2
Location to
Organization
Relation
1 – 3
Location to
Organization
Unit Relation
1 - 4
Location to
Function
Relation
(BRM)
1 - 5
Location to
Process
Relation
(SRM)
1 - 6
Location to
Resource
Relation (DRM,
TRM)
1 - 7
Location to
Mission Relation
(RM) (PRM)
7 - 7
Mission Catalog
(e.g., Budget to
Budget and Plan
to Plan
Comparison)
(PRM to PRM)
[Resource
Requirement
Management
Life Cycle]
6 - 6
Resource
Catalog (DRM/
TRM to DRM/
TRM
6 - 7
Resource to
Mission Relation
(DRM/TRM to
PRM
5 - 5
Process
Catalog (SRM
to SRM)
5 - 6
Process to
Resource
Relation (SRM
to DRM/TRM)
5 - 7
Process to
Mission Relation
(SRM to PRM)
4 - 4
Function
Catalog (BRM
to BRM)
4 - 5
Function to
Process
Relation (BRM
to SRM)
4 - 6
Function to
Resource
Relation (BRM
to DRM/TRM
4 - 7
Function to
Mission Relation
(BRM to PRM)
3 - 3
Organization
Unit Catalog
3 - 4
Organization
Unit to Function
Relation (BRM)
3 - 5
Organization
Unit to Process
Relation (SRM)
3 - 6
Organization
Unit to Resource
Relation (DRM,
TRM)
3 - 7
Organization
Unit to Mission
Relation (PRM)
2 - 2
Organization
Catalog
2 - 3
Organization
to
Organization
Unit Relation
2 - 4
Organization to
Function
Relation (BRM)
2 - 5
Organization to
Process
Relation (SRM)
2 - 6
Organization to
Resource
Relation (DRM,
TRM)
2 - 7
Organization to
Mission Relation
(PRM)
CC EA Reference Catalogs
1. Location
2. Organization
3. Organization Unit
4. Function (Operation Capability)
5. Process
6. Resource
7. Mission Requirement
CC EA Relation Types
a. Categorization
b. Containment
c. Sequence
d. Change
e. Equivalence
f. Variance
g. Reference
Subject Composition Mapping
(Content/Data)Su
bje
ct D
istr
ibu
tion
Ma
pp
ing
(Co
nte
xt/M
eta
da
ta)
Subject
Associations
Leverage
BRM
Leverage
PRM
Leverage
SRM
Leverage
DRM/TRM
12
CC EA Supports NEF and PMEF
Life Cycle Management, Including CC
4. NEF/PMEF
Operation
Management
5. D&A PMEF
and CC
Intelligence
Refinement
1. D&A PMEF Intelligence
Inventory (CC Portion of D&A
EA Framework/Ontology and
PMEF EA Content)
2. CC EA for
Merged FEB
NEF/PMEF
Intelligence
Structure and
Operational
Knowledge
(Mapping of D&A
EA Frameworks
and EA Content to
CC EA Integrating
Framework, i.e.,
Upper Ontology)
3. CC EA
For Resource
Distribution and Access
Provisioning
Enterprise Operations and CC
Enterprise Intelligence
CC EA
Spiral
Life Cycle
13
CC EA Four Layer Model
Continuity Communication Enterprise
Architecture (CC EA), Providing GSA-
Recommended EA Framework,
Methodology, and Tools/Repository
Layer Contents OMG
MDA
Layer
Layer 1. Enterprise Architecture (EA) content, as
KB or Filled Application/Template
CC EA Data and Reports M0
Layer 2. EA Framework (Product Designs,
Tools/Repository tailored Metaschema extension,
as Ontology or Application/Template)
CC EA application forms
and additional data structure
(or OMB FEA, D&A EA,
C2, HR, SOA, other
functional applications) as
tailored variant of CC EA
M1
Layer 3. Enterprise Model (i.e., Reference
Models or Reference Catalogs, Enterprise
Methodology, Foundation EA data-
structure/Metaschema)
Normalized/generalized
enterprise management
Methodology and
Metaschema
M2
Layer 4. Architecture Engine (i.e., Object Model
and Object Database in SQL, XML, ISAM, etc.)
Architecture/Object DB
Application running on
Data Store (e.g., ODBC,
SQL, XML (RTF or OWL)
M3
14
CC EA Use of MDA Layers
M1 Designs for
Intended
Information
Products
M1 Design for Required Data Structure (i.e., EA
Metaschema) to Hold Information Product’s Data
Content
M2 Model (i.e., EA metaschema)
M3 Modeling Tools and Repository
M0 Generated
Information
Products
M0 Information
Requirements
M0 Decision
SupportM0 Decision
Enterprise
Management
Architecture
Framework
Architecture
Technology
Enterprise
Architecture
Methodology
15
CC EA 4 Layer Metamodel for Model Driven Enterprise
Management (e.g., C2 Ontology Integration ) (Extending the OMG 4 Layer Metamodel’s MDA, SPEM, XMI, CIM, CWM Standards)
M3 MOF
M2
M1
M0
MetaObject Facility
(metadata repository)
MOF
Extension/Profile
(Tool Standard)
MOF-based
Application Design
(Specific Tool)
MOF-based
Application Instance
(Tool Artifacts)
UML (SPEM)
RUP
Implemented
Project
SW Process
Metamodel
SW Process
Model
SW Process
Performance
Or Aggregated
Performance
Architecture Model (Generalized Object (Metadata) Repository for Model Driven
Architecture - MDA). Extended for GEM Context Schema (as Object Metaschema for
Generalized Object Relationships – Category, Container, Sequence, Change,
Equivalence, Variance, Reference)
UML (XMI)
RUP
Implemented
Project
SW Design
Metamodel
SW Design
Model
SW Design
For System or
Aggregated
Design
GEM Metaschema
GEM Schema
Implemented
Project
Enterprise Model
(GEM Design
Metamodel)
EA Framework
(GEM Design
Model)
EA Instance
(GEM EA
Instance In
Enterprise
Or Aggregated
GEM Capability)
CIM Metaschema
CIM Schema
IT Management
Repository
CIM Design
Metamodel
CIM Design
Model
CIM Instance
On Device, or
Aggregated
IT Management
CWM Metaschema
CWM Schema
Data Management
Repository
Data Design
Metamodel
Data Design
Model
Data Model
Or Aggregated
Data Models
16
General Enterprise Management (GEM) Model Driven Enterprise Management - MDEM (EM Support)
Via Model Driven Architecture (MDA)-M3/M2/M1/M0)
GEM M3/M2
Schema Tools
(Integrated
Enterprise,
Function,
Process, Data,
System,
Software,
Security, &
Semantics,
Knowledge
Modeling And
Management
via OWL)
Standards and Products Supporting EA and
EM via MDA
OMG Managed Object Format (MOF) M3 Repository (XML + LDAP + XMI + Object Schema)
M2 Enterprise Architecture Business, Data,
Application, & Technical Schema(BEAM, FEA, DoDAF, TOGAF, etc.)
•Ontology EA Tools/Repositories (M3/M2/M1/M0)
•Agilense WebModeler
•Adaptive
•CASE EA Tools (M1/M0)
•Popkin SA
•PTech
•Computas Metis
•Other
M3/M2/M1 IT
Management Tools
OpenGroup and OMG Object Metaschema (M3)
GEM-based M3/M2/M1 Identity, Operation, Asset, Vulnerability, and Security Management Tools
M2 CWM/XMI Schema
(Data and Metadata
Models)
•Data Modeling
•Metadata Management
•BI Tools
•OLAP Tools
•Data Warehouse Tools
•3HT eSnap
•Schema Logic
•MetaMatrix
•ORM Tools (for
Semantic and Data
Modeling)
•MS Visio for EA
•MS VisioModeler
M2 XMI Schema
(Application Models)
•UML Tool Examples
•Rational
•Poseidon
•ORM M2 Tools
(Semantic/Data Models)
•MS Visio for EA
•MS VisioModeler
M2 Open
Standard
Software Process
Engineering
Metaschema
(SPEM/XMI)
Standards and
Tools
M2 Open
Standard
Application
Integration (EAI),
Business Process
Management
(BPM) (WSDL,
OWL-S), and
Workflow (WfMC,
UAN) Standards
and Tools
ITIL/ITSM/CMDB/CIM
Schema (IT Models)
(MOF)
•Troux (HW/SW/Net/EA)
•Isogon (SW)
•Tivoli TM1
•MS SMS
•BMC Patrol
•HP OpenView
•Other WBEM Tools
Standards Subsumed by
CIM/MOF
•SNMP IP Tools (MIB)
•Desktop Mgmt Tools (MIF)
•HelpDesk Tools (SES/SIS)
•Others
Used with Permission by CommIT Enterprise, Inc. and the U.S. Federal Executive Branch under the Creative Commons License at http://www.one-world-is.com/beam.
17
CC EA Foundation Is Enterprise Engineering
Management
ProcessActivities Roles
Configuration
Change
Management
•Technology
Insertion
•Product/Service
Test and Evaluation
•Governance of
Implementation
•Governance of
Change
Enterprise Engineering
Business Architect
(e.g., Enterprise
Architect and
Management
Analyst)
Enterprise Management
Enterprise Architecture
Strategic Management
IT Portfolio
Infrastructure Engineering Network
Architect/Engineer
System Engineering System
Architect/Engineer
Software Engineering Software
Architect/Engineer
Data Engineering / Management Data
Architect/Engineer
18
CC EA Framework (i.e., ConOps or Ontology) Mapped to
OMB FEA Reference Models and DoDAF Views
DoDAF Views CC EA Methodology Steps
Enterprise: AV1, OV4 Identify Enterprise: 0
Location: AV1, OV4 Identify Relevant Locations:1
Organization: AV1, OV2,
OV4, SV1, SV2, SV3
Identify Relevant Organizations:
2
Organization Unit: AV1,
OV4, SV1, SV2, SV3
Identify Relevant Organization
Units: 3
Function:AV1, OV4, OV1,
OV5, OV6b, SV1, SV2,
SV3, SV5, SV6, SV7, SV8,
SV9, SV10a, SV11
Identify Relevant Function: 4, 5,
6, 7, 8, 9, 10, 11, 12, 13, 14, 30,
31
Process: AV2, OV3, OV4,
OV5, OV6a, OV6c, OV6b,
OV6c, OV7, SV4, SV5,
SV10b, SV10c
Identify Relevant Processes: 15,
16, 17, 18, 19, 20, 21
Resource: SV1, SV2, SV3,
SV5, TV1, TV2
Identify Relevant Resources:
22, 23, 24, 24.1, 24.2, 24.3,
24.4, 24.5, 24.6, 24.7, 24.8,
24.9, 24.10
Requirement:SV3, SV5,
SV8, SV9, SV10a
Identify Relevant Requirements
by Life Cycle Stage: 25, 26, 27,
27.1, 27.2, 27.3, 27.4, 27.5,
27.6, 27.7, 27.8, 27.8, 27.9,
27.10, 27.11, 27.12, 28, 29
1 - 1
Location to
Location
1 - 2
Location to
Organization
1 - 3
Location to
Organization
Unit
1 - 4
Location to
Function
(BRM)
1 - 5
Location to
Process
(SRM)
1 - 6
Location to
Resource
(ICOM)
(DRM, TRM)
1 - 7
Location to
Resource
Management
(RM) (PRM)
7 - 7
RM to RM
(e.g., Budget
to Budget
and Plan to
Plan
Comparison)
(PRM to
PRM)
6 - 6
Resource to
Resource
(DRM/TRM
to DRM/TRM
6 - 7
Resource to
RM (DRM/
TRM to PRM
5 - 5
Process to
Process
(SRM to
SRM)
5 - 6
Process to
Resource
(SRM to
DRM/TRM)
5 - 7
Process to
RM (SRM to
PRM)
4 - 4
Function to
Function
(BRM to
BRM)
4 - 5
Function to
Process
(BRM to
SRM)
4 - 6
Function to
Resource
(BRM to
DRM/TRM
4 - 7
Function to
RM (BRM to
PRM)
3 - 3
Organization
Unit to
Organization
Unit
3 - 4
Organization
Unit to
Function
(BRM)
3 - 5
Organization
Unit to
Process
(SRM)
3 - 6
Organization
Unit to
Resource
(DRM, TRM)
3 - 7
Organization
Unit to RM
(PRM)
2 - 2
Organization
to
Organization
2 - 3
Organization
to
Organization
Unit
2 - 4
Organization
to Function
(BRM)
2 - 5
Organization
to Process
(SRM)
2 - 6
Organization
to Resource
(ICOM)
(DRM, TRM)
2 - 7
Organization
to RM (PRM)
EA Data Categorization Facets
EA Subject Tree
(i.e., Facets of Taxonomy)
1. Location
2. Organization
3. Organization Unit
4. Function (Operation Capability)
5. Process
6. Resource
7. Requirement
EA Relation Types
1. Inheritance
2. Containment
3. Sequence
4. Change
5. Equivalence
6. Variance
7. Reference
Subject Composition Mapping
(Content/Data)Su
bje
ct D
istr
ibu
tio
n M
ap
pin
g
(Co
nte
xt/M
eta
da
ta)
Subject
(Facet)
Associations
(Ontology)
CC EA Framework
