History and evolution of the General Enterprise Management (GEM) approach

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

RR1
GEM Premise 1. Connection: A Fishing Net = Knots and Strings
• FACT: Every Thing is Directly Connected to Every Other Thing http://www.one-world-is.com/beam
Other – David Bohm’s Implicate Order (2)
Thing
Thing – Bell’s Interconnection Theorem (2)
– Aspect’s Non-Locality Laboratory Proof
– Zero Point Field/Energy Mathematical Proofs (2) (3) (4)
– Consciousness and Reality (2)
Other Other
Thing Thing
• 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
Think of the world 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
as being a collection projected changes in things. This world view is also called an “ontology”, and also called an
“architecture”.
of different knots, • Sharing world views/ontologies/architectures to establish interpersonal, organizational and
global group communication, coordination, and collaboration requires a structured means of
each connected to storing and transferring signals, data, information, knowledge, awareness, decisions, and
actions.
other knots by • 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
multiple strings, like distance. We can now effectively communicate, coordinate, and collaborate while at different
locations.
layers of interwoven • 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.,
fishing nets. 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.
Knots are • 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
nouns/things, and everything they need to know, when they need to know it, from those with the greatest
expertise or situational information, knowledge, and awareness.
strings are • Everyone can now be connected, knowledgeable, and aware of the whole world around them,
verbs/relations. from their own local vantage point and decisions, including both the world within their control
and that beyond their control.
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.

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

RR2
An Object Model (For A Connection View)
Categorize
“Kind-Of” Hierarchy
Object N Attributes
Attribute Attribute Attribute
Associate
Parent Value Value Value

Plan/History Object A Association Attributes
Value Value Value
Past Parentage
Change Inheritance
“Part-Of” Hierarchy

Container Base Component
/Predecessor Input Object N Output /Successor
Object X Association Present Change Association
Object Y
Descendant Future
Inheritance Change Change Attributes
Value Value Value

Child
Object B


RR2 Here's a 1984 variant that evolved from the fishnet concept, which eventually took form as a generalized object model.

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

Basic Object Attributes Basic Association Attributes
Attribute
Value
Attribute
Value
Attribute
Value Parent Attribute
Value
Attribute
Value
Attribute
Value

Object A
Past Parentage
Change Inheritance

Container Base Component
/Predecessor Input Object N Output /Successor
Association
Object X Association Present Change Object Y
Descendant Future
Object Detail Attributes Inheritance Association Detail Attributes
Attribute Attribute Attribute Change Attribute Attribute Attribute
Value Value Value Value Value Value

Object Interface Metadata Attributes Association Interface Metadata Attributes
Attribute Attribute Attribute Child Attribute Attribute Attribute

Object Security/Privacy Metadata Attributes Object B Association Security/Privacy Metadata Attributes
Attribute Attribute Attribute Attribute Attribute Attribute


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.

RR4
The Spiral of Knowledge
pirit

Humanities
S

Re

my
lig

Society
no
ion

xo
y
Phi log

Ta
loso io
sis phy Soc
sis

the
Hy ae
the

po

Unknown

e
Recorded and
n
po

ipl
me

Hy

Research ry Known
Applied Knowledge Psychology

nc
eo
Wo heno

d

tics

Pri
Th
pte

World
thema
ng

Universe Ma Ph
ce
rki
P

Ac

ys
iol
s og
sic

Bio
y

ry
y
Ph
ist

logy
Chem
Legend:
Learning and Insight Scien
Evolving Mind ce


RR4 Here's a virtually unchanged model of my 1965 wheel of knowledge that I used to plan my educational and career focus.

RR5
An Enterprise Is An Object
(In Its Dynamic Environment)

ENVIRONMENT

Opportunity
and
Competition
ENTERPRISE
(Organization)
(Organism)
(Organ)
(Object)

Strength and
Weakness

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


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.)

RR6
32. GEM Basic Questions
WHERE IS ___? WHO IS RESPONSIBLE FOR ___?
WHO HAS THE AUTHORITY TO ___?
WHO HAS THE RESOURCES FOR ___?
WHEN IS ___? LOCATION
HOW MANY ___? CATALOG /
HOW OFTEN ARE ___?
INVENTORY
HOW MUCH IS ___?

REQUIREMENT ORGANIZATION
LIFE CYCLE 1 CATALOG /
CATALOG / INVENTORY
INVENTORY 7 2
WHAT GOES INTO CONTEXT
___? ENGINE
RESOURCE WORK UNIT
WHAT RESULTS 6 3
CATALOG / (OFFICE / BILLET)
FROM ___?
INVENTORY CATALOG /
4 INVENTORY
5
WHO DOES ___?
WHO SUPPLIES ___?
PROCESS FUNCTION WHO PRODUCES ___?
CATALOG / CATALOG /
INVENTORY INVENTORY

HOW DO WE ___? WHAT IS DONE FOR ___?
WHY IS ___?


RR6 My 1982 model of the General Enterprise Management subject categories and how they'd be related through the quot;context enginequot;.
Each wedge would now be called a taxonomy or thesaurus. The context engine would now be called a 2nd order logic strong
ontology.

RR7
7. GEM Context/Intelligence Functions
To Manage Enterprise Context (1.2),
Context Functions (for Subjects and Relationships):
•Create Manage Enterprise Subjects and Their Relationships
•Update Subject Subject
•Move Subject I
F B
•Copy Subject A
•Modify Properties
•Merge A Is A Kind-Of A Will Become
•Deactivate (Never Delete) A Follows or or Type-Of B or May Become I
•Read Is Successor-
•Characterize of F
•Relations
Subject A
•Properties Subject
Methods
•Methods J
•Qualifiers A is an
•Security Alias for J
GEM Subject Categories (Tree) A Is Part-Of Subject
•Locations (e.g., Physical, Virtual, Conceptual) Subject or quot;Aquot; and A Contains or Subject
•Organizations (e.g., Private, Commercial, Government) D Contained its Basic Consists-Of E E
•Organization Units (e.g., Offices, Teams, Projects) Within D Relations
•Functions (e.g., Executive, Production, Support) A is a
•Processes (e.g., Manual, Automated, Mechanical, Electrical) Reference for K
•Resources (e.g., Persons, Intelligence, Funds, Skills, Subject A
Qualifiers Subject
Materiel,Facilities, Services, Space, Energy, Time)
K
GEM Relationship Types (Noun – Verb – Noun)
•Class (Parent/Child, Class/Subclass, Class/Instance) A Was Previously
•Containment (Master/Detail, Container/Component) or Was
•Sequence (Predecessor/Successor, Cause/Effect) Possibly H A Categorizes or A Leads or Is
•Change (Previous/Current, Current/Future Is the Basis of C Predecessor-Of G
•Reference Subject A
•Alias Security
•Architecture/Structure (Multiple Relations Types, showing Subject Subject Subject
Component-Interface-Component) H C G
Context Meaning Properties = Object Attribute/Value Pairs, Inheritable from Class Type
Methods = Behaviors performed by Object
•Concepts (Keywords, Words) Qualifiers = Filters, Rules, Facts, and Roles Constraining Object
•Semantic (noun – verb – noun, Subject-Verb-Predicate) Security = Combination of Properties, Methods, and Qualifiers defining the need for a person or process to
•Ontology (Semantic-Verb-Semantic) see, show, or know some aspect of an object, or to do or avoid doing some action with or affecting an
object. Also known as Role-Based Access Control - RBAC.
•Knowledge (Ontology-Verb-Ontology)

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 quot;enterprise-levelquot; manager and analyst assignments since 1982. The relationships around the object model provide the
GEM quot;knowledge-representation modelquot;, which I document as the M3 layer of the GEM four-layer metamodel architecture.

RR8
Progression of Written Information, Adding Structure and Order
Outline
(List of Lists)
Thing Words Lists
Deer Nourishment
(Object) Deer Bear List
Concept Word Bear Deer
(Object) (Object)
Sky Water Sky Bear
Water Deer
Food Deer Man Bear Cave Water
Cave Water Spear Shelter
Man Cave
Spear
Weapon
Spear

Table Table Data Tree
(List with Attributes)
Food Implement Season
Association Join (Self-Joined, Drill-Down Hierarchy, i.e.,
and Crew Table Outline with Row Attributes)
(Entity/Relation for
(Lookup) Parent/Child Relations)
Data Tree
Deer Arrow - 1 Spring,
Root
Summer,
Fall, Class 1
Winter
Bear Spear - 3 Spring, Subclass 1.1

Large Rocks Summer, Instance 1.1.1
- 2 Fall Instance 1.1.2
Class 2
Berries Cloth, cup, Summer,
or basket - Fall Subclass 1.2
1
Instance 1.2.1
Instance 1.2.2

Data Snowflake (Ontology) Data Jewel (General Ontology)
Data Star (Taxonomy) (Simple Data Warehouse, Multidimensional, (Compound Data Warehouse, Multidimensional, multicentric,
(Simple Data Mart, Multidimensional, Drill- multi-level Drill-Out views of single type object, multifaceted, multilevel Drill-Anywhere views of all recorded
Out, single level views of single object, i.e., i.e., single facet E/R application controlling a objects, i.e., All applications for controlling all objects built
profiles and simple fact tables for a single class of objects. Applies First Order Logic) from single core of highly refined data. Applies Second Order
type of object) Logic)
Database and Database and
Application Application
Access Access
Locations Performance Management Performance
Situational Management Situational
(Strategic and Context (Strategic and
Service Level) Context
Organizations Service Level) Management
Resources Management Management
Management

System/Software System/Software
Network Network
Engineering Engineering
Facts Management Management
Management Management

Processes Groups/Roles Network Messaging Network
Accounts Messaging
Management Accounts Management
Management Management
Security/Key Security/Key
Functions Management Management


RR8 This is my model representing the progression of our technology and conceptual readiness to add structure to our recorded
knowledge. The quot;thingquot; node corresponds the the quot;pragmaticsquot; label briefed by Dr. Orbst over the past week, the quot;conceptquot; node
corresponds to the quot;semanticsquot;, and the quot;wordquot; node corresponds to the quot;syntaxquot; and quot;termquot; labels.

RR9
A Model of Technology

Society
Spirit Humanities
Integration Efforts
Taxonomy (synthesis, synectics, synergy)
Connection Religion
(wholeness, unity)
Technology
Advances
Sociology
Philosophy Believe Feel across
Science to
Self form Social
Psychology Tools
Mathematics Sense
Increasing Subjectivity
(Direct) (Less Empirical)
Physiology
Physics

Chemistry Biology
Science Increasing Objectivity
(Indirect Sense) (More Empirical)

Perception of Separation
(differentiation, analysis)


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.

RR10
Team CommIT GEM Framework (Leveraging OMB FEA)


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.

RR11
Team CommIT Enterprise Management Spiral Life Cycle Process (SLCP) Model
2. Concurrent Functions Inventory
Enterprise Reference Architecture (e.g., Functional Maturation via Policy, Process, etc. Documents)
And Function Enterprise Modeling and Architecture
Mission Management
Operations Risk (i.e., Threat) (Concurrent for Hierarchy of Organizations, Functions, Programs, Projects, and Persons)
Management and Vulnerability Mission (Strength and Opportunity Management)
Using A (i.e., Weakness) Vision
Common Goals
Management Performance Objectives (e.g., Measures, Service Levels, Contracts)
Management Targets/Indicators
Repository Strategies (Requirements Management and Analysis)
Baseline Service Operations (Functions/Programs/Projects)
Strength, Activities /Services (Performance Metrics)
Weakness, Products /Systems (Product/System Specifications)
Costs/Benefits
Opportunity, and Projects / Initiatives (New/Improved Functions/Programs/Projects)
Threat (SWOT) Investment Cost (Infrastructure, Development, Procurement)
Assessment Performance Impact
Operations Cost Impacts
Implemented Plans
1.1 Function
Actual Performance Intelligence
Value Chain Assessment Track Performance
Account for Resources Inventories
(Relationship Management for Manage Configurations Diverse Content,
Customers, Suppliers, Partners, Measure Performance
Authorities, Public, Internal Performance Review Data, Metadata,
Analysis)
Performance Adjustment for Mature Mission Management Vocabulary,
Manage Full Enterprise Configuration
Keywords,
1.4 Enterprise Virtual Applications (EA Repository-based Templates and Composite Applications) Concepts,
Propositions /
1.3 Enterprise Mission-Based Security Controls (For Security Access and Asset Distribution) Assertions,
Taxonomy,
1.2 Enterprise Common Context/Intelligence/Architecture Semantics,
SUBJECT Location Organization Organization Function Process Resource Resource Life Cycle Thesauri,
Context and Context and Unit Context (Mission) Context Context and Context and State Context and
Context Content and Content and Content Content Content Content Ontology,
Knowledge


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 quot;balanced scoredardquot;, 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 a
non-fragmented repository containing or linking to the totality of enterprise management information, providing a wholistic view of the
dynamic enterprise in its dynamic environment.

RR12 Enterprise Leadership and Management Functions
- Progression from Current Disorder to New Order, With Cohesion
Leadership
Management
Leadership Provides
Cohesion (i.e., Control)
By Managing
The Configuration Of 1 3 2
Enterprise Architecture” Our Status Yesterday… How We’ll Get There Now Our Intended Status Tomorrow…
1. Enterprise Components (As-Is Disorder) (Migration, Control) (To-Be Order, Command)
1.1. Location Risk and Vulnerability Assessment,
1.2. Organization Performance Measurement,
1.3. Organization Unit Operating Environment And Adjustments Mission
1.4. Function
1.5. Process Evolving Operation Strategy
1.6. Resource To Close Gaps and Reduce Overlaps Vision
Value-Lattice
2. Component Relations (Integrated Value Chains) (Adaptation Decisions)
2.1. Categorization
2.2. Containment
2.3. Sequence Strength,
2.4. Version Weakness, Opportunity, Goal
2.5. Equivalence and Threat Awareness
Objective
2.6. Variation
Criteria
2.7. Reference
3. Capability Requirements
3.1. Conceptual
3.2. Specified
3.3. Authorized
3.4. Funded Tightening “Acceptable Performance”
3.5. Implemented Operation Indicators from Lessons Learned
3.6. Operational (Intelligence Refinement)
3.7. Disposed

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

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 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.

RR13
Nature’s Value-Chain
THE PHYSICAL ENVIRONMENT RECYCLER
(BASIC RESOURCES/PRODUCTS) (NATURAL AND INDUSTRIAL
INORGANIC MATERIAL (UNEXTRACTED OR PROCESSED) RECYCLING OF BY-PRODUCTS TO
ORGANIC MATERIAL (UNHARVESTED OR PROCESSED) PRODUCE MATERIAL AND ENERGY,
ENERGY (UNHARNASSED OR PROCESSED) AND RECORDING/SHARING OF
HUMAN KNOWLEDGE (INITITAL INSIGHTS/EXPERIENCE OR KNOWLEDGE)
PROCESSED)

CUSTOMER
EXTRACTOR ALL CUSTOMERS ARE (CONSUMER=
CUSTOMERS ONLY BY-PRODUCT
INTERNAL CUSTOMERS, IF
WANT TO PAY FOR SUPPLIER)
YOU DEFINE THE ENTERPRISE
THE ADDED VALUE BOUNDARY BROADLY
THEY REQUIRE. IF ENOUGH. THE PRIMARY
THEY DON'T SUPPLIER IS THE DYNAMICAL
REQUIRE IT, IT HAS PHYSICAL ENVIRONMENT.
NO VALUE TO
THEM.
REFINER
SUPPLIER YOUR
(VAA)
ENTERPRISE

VALUE
ADDED VAA VAA
ACTIVITY
-VAA

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


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 quot;reduction of cycle timequot;, 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.

RR14
Enterprise Value Chain
Natural
Environment

Extractor Recycler

6. 1.
Refiner Supplier
d.
Customer Consumer
2. Pr
(Output,

a.
ov
(Input )

Ex an ct
Your io is Outcome)

pe d i on
e.
n
Enterprise

cta
Sa
Value-Added

tio
t is
5. (Internal, Insource,

fa

n
Activity

c.
b.
and Outsource

Pr
Public Re
6.

od
(Input, Control) Activity) qu

uc
ire Public

tio
m
Perform,
en ( Output,

n
2.1 t
Control)
Measure,
Products
3. and
Improve
Authority 2.4
(Control)
Culture
4. 2.3 2.2 4.
Partner Structure Process
(Input,
Partner
Mechanism) (Output,
Mechanism)


RR14 This is another 1992 variant of the previous value-chain model.

RR15
A Transaction Is More Than It Appears - The Value Lattice
Component Interface Component
(VAA:N) VAA:N+1

Main Transaction
Exchange/Transport of:
•Materiel
VAA = Value Added Activity Interchange/Transfer of:
B = Business
2 = To •Data
•Information
•Knowledge
Associated Resource Transactions
Awareness/Knowledge/Information/Data/Signals Transferred
Funds Transferred
Person/Team Actions
Skill/Experience Exercised
Materiel Consumed, Stored or Transported
Services Performed
Facility Used
Space Occupied or Traversed
Time Spent
Energy Applied or Produced

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.

RR16
Service Categories Needed to Support The
President’s Management Agenda (PMA)
Target Leaders Enterprise Management Services (EMS) PMA Initiatives
•CEO (Management Solutions Including Enterprise and Functional 1.Human Capital
•COO Governance support, Extending EA into Full Enterprise 2.Competitive Sourcing
•CFO Engineering, Performance/Quality/Cost Improvement, BPR, Cycle
•CHCO 3.Financial Performance
Time Reduction, Decision Latency Improvement, Security 4.Enhanced eGovernment (EA)
•CKO
•CIO Management, Continuity/Risk Management, Metadata Management, 5.Budget/Performance
•Functional Knowledge Management, Virtual Enterprise Database, Value-Chain Integration (Scorecard)
Managers Integration, Situational Awareness, C2, Real Time Enterprise, and
Requirement, Asset, Portfolio, Program, Project, and Change There are no competing EM
Management) methodologies

•CFO Enterprise Architecture Services There are multiple competing
•CIO EA Vendors and Approaches,
•CTO (EAS) but very few competing EA
(Advising-On and Implementing FEA, DoDAF/C4ISR, methodologies
Zachman, TOGAF, Spewak, etc.)

There are many competing IT
IT Services (ITS) and Network Service Vendors
•CIO (Providing Web, LAN/WAN/Wireless, Applications,
•CTO
Application and Data Integration, Databases, Data
•System / Software
Development Warehousing, IT Operations, Customer Service, Legacy,
Managers etc.)

Network Infrastructure Services


RR16 This 2000 model was assembled as marketing material to present the quot;consulting servicesquot; 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.

RR17
FEA Extension For Operations Management And Architecture
Integration
EA as Whole-Enterprise System Analysis, Requirement Analysis, and Operational Model

Function Mission Process Resource (Data) Resource (Technology) Location Catalog (LC)
Catalog Catalog Catalog Catalog Catalog
Organization Catalog (OC)
BRM PRM SRM DRM TRM
OMB FEA Organization Unit Catalog (FC)
Function Catalog (FC)
Business Area
Measurement Service Metadata Technical Service Reference
Area Domains (Context) Area Mission Catalog (MC)
Models Process Catalog (PC)
Measurement Service Metadata Technical Service
Line of Business Resource Catalog –
Categories Type (Container) Category
Data (RC-D)
Measurement Service Data Technical Resource Catalog –
SubFunctions
Indicators Component (Content) Service Standard Technology (RC-T)

Function Catalog Mission Catalog Process Catalog Resource Catalog Resource Catalog
D&A Resource (e.g. IT)
CC EA
(PRM Extension) (SRM Extension) (DRM Extension) (TRM Extension)
(BRM Extension) Management Reference
Functional Functional
Planning Services
Metadata Controlled Technology
Product Catalog (TRM) IT Product
Catalogs
NEF Reference
Spiral Life Cycle Inventory
(What) Data ETL
(Priority) Service (i.e., Performance)
Vendor
PMEF Policy Level Management (SLM)
Data Migration Vendor
Mission Brand
Process
Assignment
(SRM Service Domain) Virtual DB Version Brand
SMEF (Who) Vision

Goal Procedure (Rules) Version
Release
Responsibility (SRM Service Type) Taxonomy
Objective (Controlled Release
Performance Source
(Indicators) Template Forms, Reports, Vocabulary
Organization Targets
etc.) (SRM Service Inheritance Technology Source
Unit Catalog Strategy (Portfolio) Component) Relations) Time Phasing IT Development
Authority And Implementation
Organization Plans (When Technology (CMMI)
Technology Concept Map
Catalog Resource Insertion
Budget (TRM Item) (Associative
Requirements, and Infrastructure
Relation)
Location Dependency, Deprecation (System of Systems)
Catalog Schedule) Metadata
Semantic Engineering
(DRM Item) Product
Recurring Plans Data Model
Evaluation System
Controlled Process
EA Composition Engineering
Initiative Plans Vocabulary Ontology
(EA/IT Subject Taxonomy
and Controlled Funding Strategy Functional Knowledge Software
Vocabulary)
Semantics Base Engineering
Acquisition Strategy CPIC
EA “Line of Sight” IT Operations
(EA/IT Subject Associations, Giving COOP
Performance And Maintenance
Semantic and Ontology Context) Capability
(ITIL)
Assessment (Performance,
Plan, Strategy, Value-Chain,
EA, IT, CM, DB, SPEM, BPM, AD, LDAP Metadata (e.g., MOF) SWOT, Risk, Vulnerability, Records Management and
Asset Management
Repository and Mission)


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.


RR18
Implementing GEM: Aligning Mission, Function, and IT


RR18 This is a model represent the cycle of development of an EA in blue, development of the EA-based enterprise management capabilities
in 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 oversight
and tracking of IT and other functional operations.

RR19
CommIT EA Has An Extended OMB FEA Structure

Enterprise Architecture
Service Oriented Architecture (SOA)
Enterprise Service Bus
1. NEF/PMEF Service (e.g., Loosely Coupled, NetCentric) (ESB)

Capability Process Improvement and Solution Design Capability Implementation

Operational Capability (Primary and Alternate Sites, Primary and Alternate Providers)
1. BRM
(Assigned Functional Missions 5. TRM 6. Required Mission
+ Assumed Supporting 3. SRM (Technology Resources over their life
4. DRM
Functions) (Best Practice, Catalog of cycle.

Capability Business Case and Budget
(Metadata
1.1 Policy Re-usable Standards and 6.1 People
and Data)
1.2 Assignment Processes) Qualifying 6.2 Intelligence
1.3. Strategic Management Products) 6.2.1 Functional Intelligence
6.3 Funds
6.4 Skills
1. OU Assigned 6.5 Materiel
2. PRM
Functional 6.5.1 Physical IT
(Strategic Mgmt, Ops & Invest.
Responsibility 6.5.1.1 Systems
Strategies, Priorities)
6.5.1.2 Infrastructure
6.5.2 Goods
7. PRM (Portfolios, Budgets)
1. Parent Organization 6.6 Facilities
of OU 6.7 Services
6.8 etc.
6. Organization Unit
(OU) Assigned The
Asset

Schema and Data Largely or
1. Location of OU Wholly Present in FEA
(Physical and Virtual)

Schema and/or Data Added
by Team CommIT EA


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.

History and evolution of the General Enterprise Management (GEM) approach

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to History and evolution of the General Enterprise Management (GEM) approach

Similar to History and evolution of the General Enterprise Management (GEM) approach (20)

More from HolisticMeta (Self Employed, Part Time)

More from HolisticMeta (Self Employed, Part Time) (10)

Recently uploaded

Recently uploaded (20)

History and evolution of the General Enterprise Management (GEM) approach