ONTAC And SICOP Handouts2

Copyright Roy Roebuck, 1982-2006. Used with permission by the U.S. Federal Executive Branch under the GEM Service Provider License of CommIT Enterprises, Inc.

GEM Premise 1. Connection: A Fishing Net = Knots and Strings

• FACT: Every Thing is Directly Connected to Every Other Thing– David Bohm’s Implicate Order (2)– Bell’s Interconnection Theorem (2)– Aspect’s Non-Locality Laboratory Proof– Zero Point Field/Energy Mathematical Proofs (2) (3) (4)– Consciousness and Reality (2)

• The Readiness of People to Accept the Science of Connection Varies from Person to Person– Connection is the Basis for Our Physical Universe– Connection is the Basis for Cause and Effect phenomena– Connection is the basis for the “systems” and “object” engineering views

• Everyone mentally does architecture and ontology as their connection method. Everyone builds a personal world view by: sensing/perceiving their world, identifying/distinguishing distinctive things in it; naming things, describing things, relating things, and tracking past and projected changes in things. This world view is also called an “ontology”, and also called an “architecture”.

• Sharing world views/ontologies/architectures to establish interpersonal, organizational and global group communication, coordination, and collaboration requires a structured means of storing and transferring signals, data, information, knowledge, awareness, decisions, and actions.

• Prior to electronic communication our means to transfer world views was limited to our physical senses. With electronic communication we are now able to transfer world views at a distance. We can now effectively communicate, coordinate, and collaborate while at different locations.

• Prior to electronic data processing (e.g., IT) our means to share world views was limited to the single receiving person or group currently anywhere on a communication circuit with us (e.g., across the room or on the other end of the telegraph, radio, or telephone). With electronic data processing we are now able to transfer world views to multiple persons and groups at different times. We can now effectively communicate, coordinate, and collaborate with all persons and groups on the network at different locations and times.

• As a result of the global Internet and our ontology and architecture modeling processes and technology, we can now provide the means for all persons and groups anywhere to know everything they need to know, when they need to know it, from those with the greatest expertise or situational information, knowledge, and awareness.

• Everyone can now be connected, knowledgeable, and aware of the whole world around them, from their own local vantage point and decisions, including both the world within their control and that beyond their control.

Thing

OtherThing

OtherThing

OtherThing

Think of the world as being a collection of different knots, each connected to other knots by multiple strings, like layers of interwoven fishing nets.

Knots are nouns/things, and strings are verbs/relations.

RR1

roy.roebuck

Text Box

This series of slides, with links to comments in the top left of each, provide a bit of the history and evolution of the General Enterprise Management (GEM) approach

roy.roebuck

Text Box

http://www.one-world-is.com/beam

http://www.one-world-is.com/beam

Slide 1

RR1 This diagram took form from 1957, starting with a dream about a fishnet.Roy Roebuck, 1/20/2006


An Object Model (For A Connection View)

Attribute Attribute AttributeValue Value Value

Object N Attributes


Association Attributes


Change Attributes

Container/Predecessor

Object X

Component/Successor

Object Y

BaseObject N

ChildObject B

ParentObject A

ParentageInheritance

DescendantInheritance

InputAssociation

OutputAssociation

PastChange

FutureChange

Present Change

“Kind-Of” Hierarchy

“Part-Of” Hierarchy

Categorize

Associate

Plan/History

RR2

Slide 2

RR2 Here's a 1984 variant that evolved from the fishnet concept, which eventually took form as a generalized object model.Roy Roebuck, 1/20/2006


A Dynamic Object(For An Information System To Manage Any Thing, And Every Thing)

Container/Predecessor

Object X

Component/Successor

Object Y

BaseObject N

ChildObject B

ParentObject A

ParentageInheritance

DescendantInheritance

InputAssociation

OutputAssociation

PastChange

FutureChange

Present Change


Basic Association AttributesAttribute Attribute Attribute

Value Value Value

Basic Object Attributes


Object Detail Attributes


Object Interface Metadata Attributes


Object Security/Privacy Metadata Attributes


Association Detail Attributes


Association Interface Metadata Attributes


Association Security/Privacy Metadata Attributes

RR3

Slide 3

RR3 Here's another 1988 variant on the generalized object model, representing the idea that it could serve as the foundation for any MIS. This idea has been called dynamic data structures since the mid 90's.Roy Roebuck, 1/20/2006


SpiritSociety

ScienceTa

xono

my

Hum

anities

Religion

Philosophy

Mathematics

Physic

s

Che

mis

try

Biology

Physiology

Psychology

Sociology

Known World

Unknown

Universe

Princ

ipleRecorded and

Applied KnowledgeTh

eory

Acce

pted

Hyp

othe

sis

Wor

king

Hypo

thes

is

Phen

omen

ae

Research

Legend:Learning and Insight

Evolving Mind

The Spiral of KnowledgeRR4

Slide 4

RR4 Here's a virtually unchanged model of my 1965 wheel of knowledge that I used to plan my educational and career focus.Roy Roebuck, 1/20/2006


ENTERPRISE(Organization)

(Organism)(Organ)(Object)

ENVIRONMENT

METABOLIC ACTION ON RESOURCES(TRIGGER, INPUT, CONTROL, OUTPUT, MECHANISM)

Opportunity and

Competition

Strength and Weakness

An Enterprise Is An Object(In Its Dynamic Environment)

RR5

Slide 5

RR5 This is my 1982 concept for managing the enterprise as a single entity, as part of my Master's program (i.e., Masters of Science in Systems Management from Univ. of Southern Cal.)Roy Roebuck, 1/20/2006


LOCATIONCATALOG / INVENTORY

ORGANIZATIONCATALOG / INVENTORY

WORK UNIT (OFFICE / BILLET)

CATALOG / INVENTORY

FUNCTIONCATALOG / INVENTORY

PROCESS CATALOG / INVENTORY

RESOURCECATALOG / INVENTORY

CONTEXTENGINE

REQUIREMENTLIFE CYCLE CATALOG / INVENTORY

WHERE IS ___? WHO IS RESPONSIBLE FOR ___?WHO HAS THE AUTHORITY TO ___?WHO HAS THE RESOURCES FOR ___?

WHAT IS DONE FOR ___?WHY IS ___?

HOW DO WE ___?

WHAT GOES INTO ___?

WHAT RESULTS FROM ___?

HOW MANY ___?HOW OFTEN ARE ___?HOW MUCH IS ___?

WHEN IS ___?

WHO DOES ___? WHO SUPPLIES ___? WHO PRODUCES ___?

1

7

6

5 4

3

2

32. GEM Basic QuestionsRR6

Slide 6

RR6 My 1982 model of the General Enterprise Management subject categories and how they'd be related through the "context engine". Each wedge would now be called a taxonomy or thesaurus. The context engine would now be called a 2nd order logic strong ontology.Roy Roebuck, 1/20/2006


7. GEM Context/Intelligence FunctionsTo Manage Enterprise Context (1.2),

Manage Enterprise Subjects and Their RelationshipsSubject

B

SubjectC

Subject I

SubjectG

SubjectF

SubjectD

SubjectH

SubjectE

Subject"A" andits BasicRelations

A Is A Kind-Ofor Type-Of B

A Categorizes orIs the Basis of C

A Contains orConsists-Of E

A Is Part-Ofor

ContainedWithin D

A Follows orIs Successor-

of F

A Leads or IsPredecessor-Of G

A Will Becomeor May Become I

A Was Previouslyor Was

Possibly H

SubjectJ

A is anAlias for J

SubjectK

A is aReference for K

Subject AProperties

Subject AMethods

Subject AQualifiers

Subject ASecurity

Properties = Object Attribute/Value Pairs, Inheritable from Class TypeMethods = Behaviors performed by ObjectQualifiers = Filters, Rules, Facts, and Roles Constraining ObjectSecurity = Combination of Properties, Methods, and Qualifiers defining the need for a person or process tosee, show, or know some aspect of an object, or to do or avoid doing some action with or affecting anobject. Also known as Role-Based Access Control - RBAC.

Context Functions (for Subjects and Relationships):•Create•Update

•Move•Copy•Modify•Merge

•Deactivate (Never Delete)•Read•Characterize

•Relations•Properties•Methods•Qualifiers•Security

GEM Subject Categories (Tree)•Locations (e.g., Physical, Virtual, Conceptual)•Organizations (e.g., Private, Commercial, Government)•Organization Units (e.g., Offices, Teams, Projects)•Functions (e.g., Executive, Production, Support)•Processes (e.g., Manual, Automated, Mechanical, Electrical)•Resources (e.g., Persons, Intelligence, Funds, Skills, Materiel,Facilities, Services, Space, Energy, Time)

GEM Relationship Types (Noun – Verb – Noun)•Class (Parent/Child, Class/Subclass, Class/Instance)•Containment (Master/Detail, Container/Component)•Sequence (Predecessor/Successor, Cause/Effect)•Change (Previous/Current, Current/Future•Reference•Alias•Architecture/Structure (Multiple Relations Types, showing Component-Interface-Component)

Context Meaning•Concepts (Keywords, Words)•Semantic (noun – verb – noun, Subject-Verb-Predicate)•Ontology (Semantic-Verb-Semantic)•Knowledge (Ontology-Verb-Ontology)

RR7

Slide 7

RR7 This is the model that extends the basic object model to encompass more of the relationships I discovered in my 1982-85 Master's work and my "enterprise-level" manager and analyst assignments since 1982. The relationships around the object model provide the GEM "knowledge-representation model", which I document as the M3 layer of the GEM four-layer metamodel architecture.Roy Roebuck, 1/20/2006


Thing(Object)

Deer

Word(Object)

Outline(List of Lists)Words

Bear

Spear

ManCave

WaterSky

Deer List

DeerBearWater

ListsDeerBearWater Sky

CaveSpearMan

NourishmentDeerBearWater

ShelterCave

WeaponSpear

Table(List with Attributes)

Food Implementand Crew

Season

Deer Arrow - 1 Spring,Summer,Fall,Winter

Bear Spear - 3Large Rocks- 2

Spring,Summer,Fall

Berries Cloth, cup,or basket -1

Summer,Fall

AssociationTable

(Lookup)

TableJoin

(Entity/Relation for Parent/Child Relations)

Data Star (Taxonomy)(Simple Data Mart, Multidimensional, Drill-Out, single level views of single object, i.e., profiles and simple fact tables for a single

type of object)

Facts

Resources

Processes

Functions

Groups/Roles

Locations

Organizations

Data Jewel (General Ontology)(Compound Data Warehouse, Multidimensional, multicentric, multifaceted, multilevel Drill-Anywhere views of all recorded objects, i.e., All applications for controlling all objects built

from single core of highly refined data. Applies Second Order Logic)

Security/Key Management

Performance (Strategic and Service Level) Management

Network Management

Network Accounts

Management

Messaging Management

Database and Application

AccessManagement

System/Software Engineering Management

SituationalContext

Management

Data Snowflake (Ontology)(Simple Data Warehouse, Multidimensional,

multi-level Drill-Out views of single type object, i.e., single facet E/R application controlling a class of objects. Applies First Order Logic)

Security/Key Management

Performance (Strategic and Service Level) Management

Network Management

Network Accounts

Management

Messaging Management

Database and Application

AccessManagement

System/Software Engineering Management

SituationalContext

Management

Data Tree(Self-Joined, Drill-Down Hierarchy, i.e.,

Outline with Row Attributes)Data Tree

Instance 1.1.1Instance 1.1.2

Subclass 1.1

Class 1

Instance 1.2.1Instance 1.2.2

Subclass 1.2

Class 2

Root

Progression of Written Information, Adding Structure and Order

Food

Concept(Object)

RR8

Slide 8

RR8 This is my model representing the progression of our technology and conceptual readiness to add structure to our recorded knowledge. The "thing" node corresponds the the "pragmatics" label briefed by Dr. Orbst over the past week, the "concept" node corresponds to the "semantics", and the "word" node corresponds to the "syntax" and "term" labels.Roy Roebuck, 1/20/2006


A Model of Technology

SocietySpirit

Science(Indirect Sense)

Believe Feel

Sense(Direct)

Self

Mathematics

Physics

Chemistry Biology

Physiology

Psychology

Sociology

Taxonomy

Humanities

Religion

Philosophy

Perception of Separation(differentiation, analysis)

Integration Efforts(synthesis, synectics, synergy)Connection

(wholeness, unity) Technology Advances

across Science to

form Social Tools

Increasing Subjectivity(Less Empirical)

Increasing Objectivity(More Empirical)

RR9

Slide 9

RR9 This is a model I put together around 1985 to extend the wheel of knowledge into a form that could be used to explain where technology fit and how it evolved.Roy Roebuck, 1/20/2006


Team CommIT GEM Framework (Leveraging OMB FEA)RR10

Slide 10

RR10 This is the GEM framework, first used in 1987, for organizing enterprise general subject taxonomies, a general ontology of subject relationships over time, and the value-lattice of the totality of enterprise subjects and their relations.Roy Roebuck, 1/20/2006


Team CommIT Enterprise Management Spiral Life Cycle Process (SLCP) Model

Resource Context and Content

Organization Unit Context and Content

Process Context and Content

Resource Life Cycle State Context and Content

Function (Mission) Context and Content

Organization Context and Content

LocationContext and Context

SUBJECT

Strength, Weakness,

Opportunity, and Threat (SWOT)

Assessment

Value Chain Assessment (Relationship Management for Customers, Suppliers, Partners,

Authorities, Public, Internal Analysis)

Functions InventoryReference Architecture (e.g., Functional Maturation via Policy, Process, etc. Documents)Enterprise Modeling and ArchitectureMission Management (Concurrent for Hierarchy of Organizations, Functions, Programs, Projects, and Persons)

Mission (Strength and Opportunity Management)Vision

GoalsPerformance Objectives (e.g., Measures, Service Levels, Contracts)

Targets/IndicatorsStrategies (Requirements Management and Analysis)

Baseline Service Operations (Functions/Programs/Projects)Activities /Services (Performance Metrics)Products /Systems (Product/System Specifications)

Costs/BenefitsProjects / Initiatives (New/Improved Functions/Programs/Projects)

Investment Cost (Infrastructure, Development, Procurement)Performance ImpactOperations Cost Impacts

Implemented PlansActual PerformanceTrack PerformanceAccount for ResourcesManage ConfigurationsMeasure Performance

Performance ReviewPerformance Adjustment for Mature Mission ManagementManage Full Enterprise Configuration

2. Concurrent Enterprise

And FunctionOperations

Management Using A

Common Management Repository

1.2 Enterprise Common Context/Intelligence/Architecture

1.1 Function Intelligence Inventories

Diverse Content, Data, Metadata,

Vocabulary, Keywords, Concepts,

Propositions / Assertions, Taxonomy, Semantics, Thesauri, Ontology,

Knowledge

1.3 Enterprise Mission-Based Security Controls (For Security Access and Asset Distribution)

1.4 Enterprise Virtual Applications (EA Repository-based Templates and Composite Applications)

Risk (i.e., Threat) and Vulnerability (i.e., Weakness)

Management

RR11

Slide 11

RR11 This is a variant of my 1987 strategic management process flow-model that represents evolving operations supported by dynamic operational and analytical data. The #2 item represents the strategic management process, wich is a spiral life cycle that provides to the enterprise and all of its functions a concurrent and integrated superset of what is now known as a "balanced scoredard", plus strategy/portfolio/program/project management, performance tracking/reporting/assessment and adjustment, value-chain relationship management, and stregth/weakness/opportunity/threat assessment. (Weakness = vulnerability, threat = risk). The GEM ontololgy in item 1.2 integrates the diverse functional (i.e., middle) ontologies from 1.1, which in turn provides the data needed to associate resources with user access authority in 1.3 and to virtualized knowledge-base functional applications in 1.4. All of this operates from anon-fragmented repository containing or linking to the totality of enterprise management information, providing a wholistic view of the dynamic enterprise in its dynamic environment.Roy Roebuck, 1/20/2006


Enterprise Leadership and Management Functions- Progression from Current Disorder to New Order, With Cohesion

1Our Status Yesterday…

(As-Is Disorder)

2Our Intended Status Tomorrow…

(To-Be Order, Command)

Value-Lattice(Integrated Value Chains)

Operating Environment Mission

Vision

Tightening “Acceptable Performance”Operation Indicators from Lessons Learned

(Intelligence Refinement)

Risk and Vulnerability Assessment, Performance Measurement,

And Adjustments

Objective Criteria

GoalStrength,

Weakness, Opportunity, and Threat Awareness

Evolving Operation StrategyTo Close Gaps and Reduce Overlaps

(Adaptation Decisions)

3How We’ll Get There Now

(Migration, Control)

Leadership Provides Cohesion (i.e., Control)By ManagingThe Configuration Of Enterprise Architecture”1. Enterprise Components1.1. Location1.2. Organization1.3. Organization Unit1.4. Function1.5. Process1.6. Resource2. Component Relations2.1. Categorization2.2. Containment2.3. Sequence2.4. Version2.5. Equivalence2.6. Variation2.7. Reference3. Capability Requirements3.1. Conceptual3.2. Specified3.3. Authorized3.4. Funded3.5. Implemented3.6. Operational3.7. Disposed

Leadership Provides Measured and Adjusted Progression, Transforming Enterprise Into An Intended Future State (i.e., Command)

LeadershipManagement

Leadership and Management of the “Operational Part of Architecture” Both Depend On Organization of Data (i.e., “the Intelligence Part of Architecture”) About The Enterprise and Its Environment

RR12

Slide 12

RR12 This is my 1991 leadership and management model that realigns the strategic management spiral life cycle to illustrated the concepts of command, control, strategy, performance, etc. supported by the enterprise architecture.Roy Roebuck, 1/20/2006


INORGANIC MATERIAL (UNEXTRACTED OR PROCESSED)ORGANIC MATERIAL (UNHARVESTED OR PROCESSED)ENERGY (UNHARNASSED OR PROCESSED)HUMAN KNOWLEDGE (INITITAL INSIGHTS/EXPERIENCE OR PROCESSED)

THE PHYSICAL ENVIRONMENT(BASIC RESOURCES/PRODUCTS)

EXTRACTORCUSTOMER

(CONSUMER=BY-PRODUCT

SUPPLIER)

REFINER

VALUEADDED

ACTIVITY-VAA

RECYCLER(NATURAL AND INDUSTRIAL

RECYCLING OF BY-PRODUCTS TOPRODUCE MATERIAL AND ENERGY,

AND RECORDING/SHARING OFKNOWLEDGE)

VAA

SUPPLIER(VAA)

VAA

ALL CUSTOMERS AREINTERNAL CUSTOMERS, IFYOU DEFINE THE ENTERPRISEBOUNDARY BROADLYENOUGH. THE PRIMARYSUPPLIER IS THE DYNAMICALPHYSICAL ENVIRONMENT.

NOTE: INTERCHANGE OF INFORMATION, AND EXCHANGE OF MATERIAL, ENERGY, AND/OR CURRENCY

CUSTOMERS ONLY WANT TO PAY FOR THE ADDED VALUE THEY REQUIRE. IF THEY DON'T REQUIRE IT, IT HAS NO VALUE TO THEM.

Nature’s Value-Chain

YOURENTERPRISE

RR13

Slide 13

RR13 This is my 1992 model representing the value-chain aspects subsequently included in the GEM approach. Prior to this time I was focusing more on the "reduction of cycle time", from an operational and management-engineering perspective. This was when I was subsuming TQM and BPR (e.g., IDEF0) concepts and processes into the GEM approach.Roy Roebuck, 1/20/2006


Enterprise Value Chain

6.Supplier

(Input)

2.1Products

2.2 Process

2.3 Structure

2.4Culture

2.Your

Enterprise(Internal, Insource,

and OutsourceActivity)

1.Customer

(Output, Outcome)

4.Partner(Output,

Mechanism)

3.Authority

(Control)

6.Public(Output, Control)

Perform,Measure,

andImprove

a. Expectation

and

e. Satisfaction

b. Requirement

c. Production

d. Provision

4.Partner

(Input, Mechanism)

5.Public

(Input, Control)

NaturalEnvironment

RecyclerExtractor

Refiner

Value-AddedActivity

Consumer

RR14

Slide 14

RR14 This is another 1992 variant of the previous value-chain model.Roy Roebuck, 1/20/2006


Component ComponentInterface(VAA:N) VAA:N+1

Main TransactionExchange/Transport of:

•MaterielInterchange/Transfer of:

•Data•Information•Knowledge

Associated Resource TransactionsAwareness/Knowledge/Information/Data/Signals TransferredFunds TransferredPerson/Team ActionsSkill/Experience ExercisedMateriel Consumed, Stored or TransportedServices PerformedFacility UsedSpace Occupied or TraversedTime SpentEnergy Applied or Produced

VAA = Value Added ActivityB = Business2 = To

A Transaction Is More Than It Appears - The Value LatticeRR15

Slide 15

RR15 This 1996 model represents business to business interactions, in the GEM context, in one of my first commercial/contractor efforts to support an early B2B technology firm.Roy Roebuck, 1/20/2006


Enterprise Management Services (EMS)(Management Solutions Including Enterprise and Functional

Governance support, Extending EA into Full Enterprise Engineering, Performance/Quality/Cost Improvement, BPR, Cycle

Time Reduction, Decision Latency Improvement, Security Management, Continuity/Risk Management, Metadata Management, Knowledge Management, Virtual Enterprise Database, Value-Chain Integration, Situational Awareness, C2, Real Time Enterprise, and

Requirement, Asset, Portfolio, Program, Project, and Change Management)

Service Categories Needed to Support The President’s Management Agenda (PMA)

Enterprise Architecture Services (EAS)

(Advising-On and Implementing FEA, DoDAF/C4ISR, Zachman, TOGAF, Spewak, etc.)

IT Services (ITS)(Providing Web, LAN/WAN/Wireless, Applications,

Application and Data Integration, Databases, Data Warehousing, IT Operations, Customer Service, Legacy,

etc.)

Network Infrastructure Services

•CEO•COO•CFO•CHCO•CKO•CIO•Functional Managers

•CFO•CIO•CTO

•CIO•CTO•System / Software Development Managers

Target Leaders

There are no competing EM methodologies

There are multiple competing EA Vendors and Approaches, but very few competing EA methodologies

There are many competing IT and Network Service Vendors

PMA Initiatives1.Human Capital2.Competitive Sourcing3.Financial Performance4.Enhanced eGovernment (EA)5.Budget/Performance Integration (Scorecard)

RR16

Slide 16

RR16 This 2000 model was assembled as marketing material to present the "consulting services" that could be enabled by the GEM approach. It was then extended to encompass the PMA and FEA as they became prominent in government contracting. GEM has encompassed what is now called EA since its 1982 inception.Roy Roebuck, 1/20/2006


FEA Extension For Operations Management And Architecture Integration

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

LocationCatalog

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

RR17

Slide 17

RR17 This is a 2002 variant of the GEM metaschema that has been re-aligned to show the mapping-to and extension-of the OMB FEA. It was subsequently included as part of the offering in a DOE ITSS contract, a DoD Encore win for a small business prime contractor, a DOI EA support contract, a Navy BUMED R&D EA contract, the Fed CC EA contract, and a Navy SPAWAR Engineering Support contract. Roy Roebuck, 1/20/2006


Implementing GEM: Aligning Mission, Function, and ITRR18

Slide 18

RR18 This is a model represent the cycle of development of an EA in blue, development of the EA-based enterprise management capabilitiesin green, implementation of EA-based BPR (ToBe process) and EA-governed IT Design (ToBe IT), EA-governed oversight of the IT implementation, EA-based IV&V and C&A of the IT implementation, EA-governed process and IT deployments, and EA-based oversightand tracking of IT and other functional operations.Roy Roebuck, 1/20/2006


CommIT 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 Team CommIT 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.3 Funds6.4 Skills6.5 Materiel6.5.1 Physical IT6.5.1.1 Systems6.5.1.2 Infrastructure6.5.2 Goods6.6 Facilities6.7 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)

Cap

abilit

y Bu

sine

ss C

ase

and

Budg

et

Capability Implementation

1. NEF/PMEF

RR19

Slide 19

RR19 This 2003 model represents the OMB FEA in relation to capability design, SOA, and GEM. With the 2005 CCEA project, the National Essential Functions (NEF) and Priority Mission Essential Functions (PMEF) elements were added as variants of the OMB FEA BRM.Roy Roebuck, 1/20/2006