1 Continuity Communications Working Group Status Report Mr. Roy Roebuck Chief Architect Continuity Communications Enterprise Architecture Program Office.

1

Continuity CommunicationsWorking Group

Status Report

Mr. Roy RoebuckChief 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 Basic Communications • TelephoneTelephone• FaxFax• No VTCNo VTC• No E-MailNo E-Mail• Etc….Etc….

PM

EF

1P

ME

F 1

PM

EF

2P

ME

F 2

U.S. Government

PM

EF

8P

ME

F 8

PM

EF

7P

ME

F 7

PM

EF

5P

ME

F 5

PM

EF

6P

ME

F 6

• Basic CommunicationsBasic Communications

• TelephoneTelephone• FaxFax• E-Mail E-Mail • Etc….Etc….

PM

EF

3P

ME

F 3

Department ADepartment AP

ME

F 4

PM

EF

4Department BDepartment B

• Basic Communications Basic Communications • TelephoneTelephone• FaxFax• SVTS….SVTS….• Etc….Etc….

Department CDepartment 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

MeasurementArea

MeasurementCategories

MeasurementIndicators

ProjectPlans

Planning, Operation, Development, and

Maintenance Performance

Funding Strategy

Performance and ProgressAssessment

Service Domain

Service Type

ServiceComponent

Technical Service Area

Technical ServiceCategory

D&A IT Exh 300 (Development, Implementation), and

Exh 53 (Operation, and Maintenance)

CPIC

TechnicalService Standard

D&A TechnologyProduct Specification

BusinessArea

Line of Business

SubFunction

Exh. 300and 53

Submissions

FEA RM Item

D&A FEA Extension and IT

EA/IT Ontology And Semantics (Orthogonal to Taxonomies)

EA/IT TaxonomyAnd Semantics

Metadata(Context)

Metadata(Container)

Data(Content)

OMB FEAReference

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

MeasurementArea

MeasurementCategories

MeasurementIndicators

ProjectPlans

Planning, Operation,

Development, and Maintenance Performance

Funding Strategy

Acquisition Strategy

Performance and ProgressAssessment

ServiceDomain

ServiceType

ServiceComponent

Technology Area

TechnologyCategory

IT Product Inventory

IT DevelopmentAnd Implementation

Process (CMMI)

Infrastructure(System of Systems)Engineering Project

SystemEngineering

Project

SoftwareEngineering

Project

CPIC

IT Operations And Maintenance

(ITIL)

TechnologyStandard

D&A TechnologyProduct Specifications

BusinessArea

Line of Business

SubFunction

Exh. 300and 53

Metadata(Context)

Metadata(Container)

Data(Content)

OMB FEAReference

Models

Vendor

Version

Release

Source

Brand

EA/IT TaxonomyAnd 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 IT6.5.1.1 D&A Systems6.5.1.2 D&A Infrastructure

OMB FEA

CC EA

.01.01 .02.02 .03.03 .04.04 .05.05 .06.06LOCATIONLOCATIONCATALOGCATALOG

ORGANIZATIONORGANIZATIONCATALOGCATALOG

WORK UNITWORK UNIT(OFFICE/BILLET)(OFFICE/BILLET)

CATALOGCATALOG

FUNCTIONFUNCTIONCATALOGCATALOG

(BRM+)(BRM+)

PROCESSPROCESSCATALOGCATALOG

(SRM+)(SRM+)

RESOURCERESOURCECATALOGCATALOG

(DRM+/TRM+)(DRM+/TRM+)

MISSIONMISSIONCATALOGCATALOG

(PRM+)(PRM+)

.07.07

1.01.0ENTERPRISEENTERPRISE

CONTAININGCONTAININGCONTAININGCONTAINING CONTAININGCONTAINING CONTAININGCONTAINING CONTAININGCONTAINING CONTAININGCONTAINING CONTAININGCONTAINING

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.01 .02.02 .03.03 .04.04 .05.05 .06.06LOCATIONLOCATIONCATALOGCATALOG

ORGANIZATIONORGANIZATIONCATALOGCATALOG

WORK UNITWORK UNIT(OFFICE/BILLET)(OFFICE/BILLET)

CATALOGCATALOG

FUNCTIONFUNCTIONCATALOGCATALOG

(BRM+)(BRM+)

PROCESSPROCESSCATALOGCATALOG

(SRM+)(SRM+)

RESOURCERESOURCECATALOGCATALOG

(DRM+/TRM+)(DRM+/TRM+)

MISSIONMISSIONCATALOGCATALOG

(PRM+)(PRM+)

.07.07

Resource Satisfies Requirement

1.01.0ENTERPRISEENTERPRISE

Organization Occupies Location

Billets Perform Mission

Function Justifies Billet

Process Achieves Function

Resource Inputs-To/Results-From Process

Requirements are Satisfied by Resource

CONTAININGCONTAINING

The CC EA approach extends the OMB FEA Enterprise operational management capability

CONTAININGCONTAINING CONTAININGCONTAINING CONTAININGCONTAINING CONTAININGCONTAINING CONTAININGCONTAINING CONTAININGCONTAINING

8

CC EA Has An Extended OMB FEA Structure

1. BRM(Assigned Functional Missions + Assumed Supporting Functions)1.1 Policy1.2 Assignment1.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 People6.2 Intelligence6.2.1 Functional Intelligence6.2.2 CC Intelligence6.3 Funds6.4 Skills6.4.1 CC Skills6.5 Materiel6.5.1 Physical IT6.5.1.1 Systems6.5.1.1.1 CC Systems6.5.1.2 Infrastructure6.5.1.2.1 CC Infrastructure6.5.2 Goods6.6 Facilities6.6.1 CC Facilities6.7 Services6.7.1 CC Services6.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)

Nor

mal

and

CC

Cap

abili

ty B

usin

ess

Cas

e an

d B

udge

t

Capability Implementation

1. NEF/PMEF

9

CCEA FEA Extension For Operations Management And Architecture Integration (FYO5 Plan)

Function Catalog

Mission Catalog

Process Catalog

Resource (Data)Catalog

Resource (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

PerformanceTargets

BRM

ControlledVocabulary

OrganizationUnit Catalog

OrganizationCatalog

Location Catalog

FunctionalSemantics

FunctionalPlanning

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)

FunctionalServices

Service (i.e., Performance) Level Management (SLM)

Metadata

Data ETL

Data Migration

Virtual DB

Controlled Technology Product Catalog (TRM)

TechnologyTime Phasing

IT ProductInventory

Vendor

Version

Release

IT DevelopmentAnd Implementation

(CMMI)

Infrastructure(System of Systems)

Engineering

SystemEngineering

SoftwareEngineering

CPIC

IT Operations And Maintenance

(ITIL)

TechnologyInsertion

and Deprecation

EA, IT, CM, DB, SPEM, BPM, AD, LDAP Metadata (e.g., MOF) Repository

Taxonomy (ControlledVocabularyInheritanceRelations)

Concept Map(Associative

Relation)

SemanticData Model

Ontology

KnowledgeBase

Source

EA Composition(EA/IT Subject Taxonomy and Controlled Vocabulary)

EA “Line of Sight”(EA/IT Subject Associations, Giving Semantic and Ontology Context)

OMB FEAReference

Models

CC EAReferenceCatalogs

Records Management andAsset Management

Business Area

Line of Business

SubFunctions

Function Catalog(BRM Extension)

MeasurementArea

MeasurementCategories

MeasurementIndicators

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 ServiceCategory

TechnicalService Standard

Product EvaluationProcess

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

COOPCapability

PMEF

SMEF

NEF

EA as Whole-Enterprise System Analysis, Requirement Analysis, and Operational Model

10

CC EA Framework Model1 – 1

Location Catalog

1 – 2Location to

Organization Relation

1 – 3Location to

Organization Unit Relation

1 - 4Location to FunctionRelation(BRM)

1 - 5Location to

Process Relation(SRM)

1 - 6Location to Resource

Relation (DRM, TRM)

1 - 7Location to

Mission Relation (RM) (PRM)

7 - 7Mission Catalog(e.g., Budget to Budget and Plan

to Plan Comparison)

(PRM to PRM)[Resource

Requirement Management

Life Cycle]

6 - 6Resource

Catalog (DRM/TRM to DRM/

TRM

6 - 7Resource to

Mission Relation (DRM/TRM to

PRM

5 - 5Process

Catalog (SRM to SRM)

5 - 6Process to Resource

Relation (SRM to DRM/TRM)

5 - 7Process to

Mission Relation (SRM to PRM)

4 - 4Function

Catalog (BRM to BRM)

4 - 5Function to

Process Relation (BRM

to SRM)

4 - 6Function to Resource

Relation (BRM to DRM/TRM

4 - 7Function to

Mission Relation (BRM to PRM)

3 - 3Organization Unit Catalog

3 - 4Organization

Unit to Function Relation (BRM)

3 - 5Organization

Unit to Process Relation (SRM)

3 - 6Organization

Unit to Resource Relation (DRM,

TRM)

3 - 7Organization

Unit to Mission Relation (PRM)

2 - 2Organization

Catalog

2 - 3Organization

to Organization Unit Relation

2 - 4Organization to

Function Relation (BRM)

2 - 5Organization to

Process Relation (SRM)

2 - 6Organization to

Resource Relation (DRM,

TRM)

2 - 7Organization to Mission Relation

(PRM)

CC EA Reference Catalogs1. Location2. Organization3. Organization Unit4. Function (Operation Capability)5. Process6. Resource7. Mission Requirement

CC EA Relation Typesa. Categorizationb. Containmentc. Sequenced. Changee. Equivalencef. Varianceg. Reference

Subject Composition Mapping(Content/Data)S

ubje

ct D

istri

butio

n M

appi

ng(C

onte

xt/M

etad

ata)

Subject Associations

LeverageBRM

LeveragePRM

LeverageSRM

LeverageDRM/TRM

11

Questions?

Contact Roy Roebuck

[email protected]

703-598-2351

12

CC EA Supports NEF and PMEFLife Cycle Management, Including CC

4. NEF/PMEF Operation

Management

5. D&A PMEF and CC

IntelligenceRefinement

1. D&A PMEF IntelligenceInventory (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 EAFor Resource

Distribution and AccessProvisioning

Enterprise Operations and CC

Enterprise Intelligence

CC EASpiral

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 GeneratedInformation

Products

M0 InformationRequirements

M0 DecisionSupport

M0 Decision

EnterpriseManagement

ArchitectureFramework

ArchitectureTechnology

EnterpriseArchitectureMethodology

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-basedApplication Instance(Tool Artifacts)

UML (SPEM)

RUP

ImplementedProject

SW Process Metamodel

SW Process Model

SW Process Performance Or AggregatedPerformance

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

ImplementedProject

SW Design Metamodel

SW Design Model

SW DesignFor System orAggregated Design

GEM Metaschema

GEM Schema

ImplementedProject

Enterprise Model (GEM Design Metamodel)

EA Framework(GEM Design Model)

EA Instance (GEM EA Instance In Enterprise Or AggregatedGEM Capability)

CIM Metaschema

CIM Schema

IT ManagementRepository

CIM Design Metamodel

CIM Design Model

CIM InstanceOn Device, orAggregatedIT Management

CWM Metaschema

CWM Schema

Data ManagementRepository

Data Design Metamodel

Data Design Model

Data Model Or AggregatedData Models

16

General Enterprise Management (GEM) Model Driven Enterprise Management - MDEM (EM Support) Via Model Driven Architecture (MDA)-M3/M2/M1/M0)

GEM M3/M2Schema Tools(IntegratedEnterprise,Function,Process, Data,System,Software,Security, &Semantics, KnowledgeModeling 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 ToolsStandards 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 Process

Activities 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

CC EA Framework