I put GEM into the public domain at the beginning of 2008. Prior to that, I seldom fully shared this metamodel, unless under NDA. 

 

 

GEM Four-Layer Metamodel

M3=object (i.e., root thing) model (Metamodel in EA Tool):

·          OpenGroup and OMG Object Metaschema (Basic Common Object Model) extended for GEM dynamic management of any domain and dynamic integration, shared situational awareness, and cooperation across domains.

·         Built on data store with standard data types including autofilled standard universally-unique ID (UUID, as absolute, permanent, at-creation key) and event-recalculated ASN.1 compliant hierarchical (dot.decimal, like a project’s WBS or legal outline numbering) numbered object ID (OID, as relative, mutable taxonomic key) [Object type attributes: object name, object UUID, hypernym (i.e., more general, broader object) UUID, object OID, hypernym OID, object-create author, object-create-date, object-modify author, object-modify-date].

·         Have core inherited attributes for all objects and core relationship types (i.e., relationship as first object subtype, with lookup attributes for relationship subtypes of equivalence, categorization, containment, sequence, change/version, variance, and description, encompassing the relationships in the universal physical and conceptual aspects of intelligence, time, space, energy, and matter).

·         Have all object type instances, subtypes and subtype instances, relationship instances, and attributes having a UUID, thus supporting automation of repository content merges and synchronizations.

M2=reference model (Metamodel in EA Tool): 

·         RawWord type containing instances, with UUID, of all words used by individuals, groups, and organizations applying a shared world view (e.g., ontology, architecture, metamodel, domain), populated manually, via import or data-interface, and during the GEM “intelligence inventory (II) process, with attributes for identifying (manually or automated) the part(s) of speech such as noun, verb, adjective, adverb, etc. (the maximum population of RawWord would include all recorded words, acronyms, abbreviations, and word-spelling variants in all languages).  Corresponds to Expression within the OMG SVBR (Vocabulary Expression, Representation, Meaning, Extension)  [RawWord type attributes: all root object attributes with Word instance populating object name, with this RawWord type providing a lookup list for all subsequent other object subtypes’ attribute names, relationship instance names, and type instance values]

·         VocabularyTerm type containing all RawWord instances (with original UUID) as well as instances of word combinations (word-categorizes-word, with UUID) having a root word and one or more modifier words (which also provides a metamodel/domain structured-data field list), populated manually, via import or data-interface, and during the GEM (II) process.  Also corresponds to SBVR Vocabulary Expression. [Has related or included RawWord type structure, with the Term root-word instance populating the object name, and with lookup attributes (as subclass or multi-value attribute) for modifier words]

·         TermDictionary type, with UUID, containing all considered definitions of a term used in a worldview, including local individual/group/organization/community/market/global definitions, citing the definition source, authority, and date, populated by individual, group, and organization manual or automated efforts.  Corresponds to Vocabulary Representation within SBVR.  [Has related or included VocabularyTerm structure, with attributes for manually or automatically populated definition subclass or multi-value attribute, with lookup attributes for synonym, WordNet synset ID, antonym, hypernym, and homonym of the root term for each definition]

·         SubjectCatalog type containing noun and verb taxonomic structures for “term-categorizes-term” instances (with UUID) that relate hypernym/hyponym (broader/narrower) terms using an instance (with UUID) of the “categorization” relationship type, applying a calculated taxonomic OID derived from the hypernym term.  The OID provides the means to build a hierarchical subject tree for the catalog, and the OID enables faster/simpler navigation, sorting, and querying of subtypes/instances.  Since taxonomies are in constant flux with the participants in the world view being modeled, the OID is mutable.  Taxonomies resulting from repository content merges and synchronization require subsequent recalculation of the full taxonomy’s OID hierarchy.   By giving taxonomic/categorization context for a term, the SubjectCatalog type and its subtypes partially corresponds to OMG SBVR Vocabulary Meaning, and Vocabulary Extension at the Instance level.  []

o   EndeavorCatalog type contains all subtypes and instances for subjects that have the term “endeavor” as a direct/specified/adjacent hypernym or as an indirect/inferred/remote hypernym. [OID of “0.”, for individual/personal, group, community, organization, or combination endeavors]

o   LocationCatalog type contains all subtypes and instances for subjects that have the term “location” as a direct/specified/adjacent hypernym or as an indirect/inferred/remote hypernym. [OID of “1.”]

o   OrganizationCatalog type contains all subtypes and instances for subjects that have the term “organization” as a direct/specified/adjacent hypernym or as an indirect/inferred/remote hypernym. [OID of “2.”]

o   OrganizationUnitCatalog type contains all subtypes and instances for subjects that have the term “organization unit” as a direct/specified/adjacent hypernym or as an indirect/inferred/remote hypernym. [OID of “3.”]

o   FunctionCatalog type contains all subtypes and instances for subjects that have the term “function” as a direct/specified/adjacent hypernym or as an indirect/inferred/remote hypernym. [OID of “4.”]

o   ProcessCatalog type contains all subtypes and instances for subjects that have the term “process” as a direct/specified/adjacent hypernym or as an indirect/inferred/remote hypernym. [OID of “5.”]

o   ResourceCatalog type contains all subtypes and instances for subjects that have the term “resource” as a direct/specified/adjacent hypernym or as an indirect/inferred/remote hypernym. [OID of “6.”]

o   RequirementCatalog type contains all subtypes and instances for subjects that have the term “requirement” as a direct/specified/adjacent hypernym or as an indirect/inferred/remote hypernym.  The RequirementCatalog type, by broadening the context (i.e., SBVR Reference Scheme) of an instance (i.e.., resources for processes for functions for organization units for organizations at locations) further increases the correspondence  to OMG SBVR Vocabulary Meaning, and Vocabulary Extension at the Instance level.   [OID of “7.”  Has additional manual or automated entry attributes for resource quantity, quality, schedule, duration, frequency, and also lookup attributes with UUID (as subclass or multi-value attribute) for resource name, process name, function name, organization unit name, organization name, and location name. ]

M1=domain model (i.e., many Types, Relationships, and Attributes for world view, ontology, architecture, schema, metamodel, application-design, process-model, logical data model, concept map, each specified, with all possible defining Types/Relationships/Attributes/Values selected from a lookup in the SubjectCatalog type)

·         GEM Domain (Metamodel in EA Tool)

o   GEM Concept Map

§  GEM Methodology (Concept/Role/Process Model)

§  GEM Metamodel (Semantic/Metadata/Data/Resource Model)

·         GEM Data Model

·         GEM Resource Model

·         GEM Requirement Model

·         GEM Object Model

o   GEM Thesaurus (Preferred, alternate, acronym, alias, alternate-spelling terms, for Terminology “Active Words” and Term/Language Translation service)

o   GEM Ontology (Processes, Data, Rules, Products)

§  Operations Management, Integration, Unification, and Federation Ontology

·         General Strategic Management Process

§  Intelligence Management Integration, Unification, and Federation Ontology

·         Enterprise Management Architecture

o   Extended and Integrated FEA, DoDAF, TOGAF, MODAF, NAF, etc. architectures

o   GEM SBVR Vocabulary (Standardized Thesaurus-Subset for Human-Machine Communication and Translation)

o   GEM SBVR Rule Model (Standardized Thesaurus-Subset for Human-Machine Interaction and Workflow)

o   GEM Axiology (Value Streams in Value Chains in Value Lattices in Global Value Web, showing aggregate process models showing customer-valuation/satisfaction of inputs)

·         Diverse Domain Metamodels (Mapped to GEM during/after domain metamodel build to enable GEM-centric domain identification, collection, aggregation, integration, standardization, unification, and federation) (These are metamodels in various EA Tools, complying with such standard EA approaches/frameworks as Zachman, DoDAF, MODAF, PRINCE2, NAF, ArchiMate, COBIT, ITIL, OMB FEA, by various organizational EA implementations/metamodels)

o   Concept Map for domain

§  Object Role Model (ORM) for domain

§  Data Model (ERD) for domain

§  BPMN Process Model for domain

o   Thesaurus for domain

o   Ontology for domain (typical EA start point)

o   SBVR Vocabulary Model for domain (New standard)

o   SBVR Rule Model for domain (New standard)

o   Axiology for domain (aggregate process models showing customer-valuation/satisfaction of inputs).

M0=Instance model (e.g., populated domain models using values from daily endeavor activities within this domain) (Model in EA Tool).