Template Approach To GEM 20020422

General Enterprise Management (GEM)

Template-Analysis ApproachFrom Blank Forms

To Enterprise Engineering

Pick a Form – Any Form!• GEM is about asking and answering questions in a structured and

consistent manner, enabling much reuse of information, in a more effective, efficient, and responsive way than is now typical.

• Most people have worked with forms, either as a customer or a provider of goods or services.

• Forms serve the purpose of collecting customer information for subsequent action by the provider.

• When some or all of the information on a customer’s form is already filled out in advance by the provider, it makes the customer happier. They can just validate it, which makes the providers happier. Both win.

• An organization can start GEM implementation by collecting and analyzing the blank forms and other information TEMPLATES (e.g., reports, checklists, documents, graphs, diagrams, models, databases, spreadsheets, etc.) used across the organization, and by its customers, suppliers, authorities, partners, and the public.

GEM Repository Components(A Generalized MIS)

GEMAssertions

GEM Repository

GEMRequirements

GEMTaxonomy(Concept

Categories andInventories)(Subjects)

GEM stores the data for forms and other templates in a single repository for enterprise “concepts”, “assertions”, and “requirements”. These will be discussed in later diagrams.

Where do Templates Fit in the Big Picture of the Enterprise?

• Note the placement of Templates such as Blank Forms in this GEM outline.

• GEM implementation can start at the top of this outline and work down into the details, or can start with the details such as Templates and work back up to the top, or various combinations of these approaches.

Enterprise (e.g., Organization) – Business Function

– Functional Guidance • Function Assignment

– Responsibility » Authority » Assigned Organization Unit

• Functional References – Policy

» Process – Procedure

– Template – Form – Report – Etc.

– Tool (Manual, Automated, etc.) – Constraint (Rule, Role-based Access, Standard, principle, etc.)

– Vocabulary » Concepts

– Assertions – Data Models (e.g., IDEF1X, ER, CWM)

– Metadata Management – Data Management

– Semantic Models (e.g., ORM) – Ontologies (e.g., OWL)

– Knowledge – Knowledge Bases

– Application Models (e.g., UML) – Applications (e.g., UML, CWM)

– Operational Data Stores – Analytical Data Stores

– Taxonomies (Concept Categories) • Function Operation

– Functional Mission » Vision

– Goal – Objective

– Strategy – Plan (Recurring Operations, New Initiatives) – Implementation – Review – Adjust All Above

GEM Template Terms• A blank template (e.g., a blank form) contains

“metadata”, (i.e., data about data) which are the template’s empty fields and their arrangement. This blank template represents the structure of a subject’s knowledge, its “ontology”. An ontology is metadata about a subject.

• A populated template (e.g., a filled in form) contains “data” values in the template’s populated fields. This populated template represents an “instance” of subject knowledge. An knowledge instance is data about a subject.

• A template field (metadata) is populated with a value (data).

A Basic GEM TemplateNotice that the fieldnames, such as “Subject”are metadata, while the blank underlined spaces are where the “subject” data are written.

Notice also that this form “drills down” from the subject title into the details of the subject. To collect different subject knowledge, a different instance of this form would be needed for every variation in the detail data.

Subject: ________________________________________________________________________ Location: ______________________________________________________________________ Organization: __________________________________________________________________ Office: ______________________________________________________________________ Job Title: ___________________________________________________________________ Job Function: ________________________________________________________________ Functional Process: ___________________________________________________________ Process Description: __________________________________________________________ Process Diagram: ____________________________________________________________

Process Resources: __________________________________________________________ Process Outputs (Products/Services/ByProducts): _________________________________ Status: __________________________________________________________________ Quantity: _______________________________________________________________ Quality: _______________________________________________________________

Process Inputs (Consumables, Catalysts, etc.): ___________________________________ Status: __________________________________________________________________ Quantity: _______________________________________________________________ Quality: _______________________________________________________________

Process Constraints (Budgets, Rules, Law, etc.): _________________________________ Status: __________________________________________________________________ Quantity: _______________________________________________________________ Quality: _______________________________________________________________

Process Mechanisms (Workforce, Tools, Enablers): ______________________________ Status: __________________________________________________________________ Quantity: _______________________________________________________________ Quality: _______________________________________________________________

Template ID: GEM Form 1

GEM Template RelationsA template represents relationships between the subject and its detail data. Both the subject and the details are “concepts” of interest to the template users.

The relationship between two or more concepts is called an “assertion”. Types of assertions are: facts, opinions, questions, speculation, interpretations, etc. As in sentence grammar, the assertion has a subject noun, a predicate verb describing the relation, and a predicate object noun representing the detail data.

A blank template provides assertions about the structure (i.e., ontology) of the subject.

A populated template provides assertions about the detailed knowledge of the subject.

Subject: ________________________________________________________________________ Location: ______________________________________________________________________ Organization: __________________________________________________________________ Office: ______________________________________________________________________ Job Title: ___________________________________________________________________ Job Function: ________________________________________________________________ Functional Process: ___________________________________________________________ Process Description: __________________________________________________________ Process Diagram: ____________________________________________________________

Process Resources: __________________________________________________________ Process Outputs (Products/Services/ByProducts): _________________________________ Status: __________________________________________________________________ Quantity: _______________________________________________________________ Quality: _______________________________________________________________

Process Inputs (Consumables, Catalysts, etc.): ___________________________________ Status: __________________________________________________________________ Quantity: _______________________________________________________________ Quality: _______________________________________________________________

Process Constraints (Budgets, Rules, Law, etc.): _________________________________ Status: __________________________________________________________________ Quantity: _______________________________________________________________ Quality: _______________________________________________________________

Process Mechanisms (Workforce, Tools, Enablers): ______________________________ Status: __________________________________________________________________ Quantity: _______________________________________________________________ Quality: _______________________________________________________________

Template ID: GEM Form 1 Assertions

GEM Template Main Views1. Location Subject: 2. Organization: 3. Organization Unit: 4. Function: 5. Process: 6. Input Resource: 7. Output Resource 8. Constraint Resource 9. Mechanism Resource

GEM View 1

2. Organization Subject: 1. Location: 3. Organization Unit: 4. Function: 5. Process: 6. Input Resource: 7. Output Resource 8. Constraint Resource 9. Mechanism Resource

GEM View 2

3. Organization Unit Subject: 2. Organization: 1. Location: 4. Function: 5. Process: 6. Input Resource: 7. Output Resource 8. Constraint Resource 9. Mechanism Resource

GEM View 3

4.Function Subject: 3. Organization Unit: 2. Organization: 1. Location:

5. Process: 6. Input Resource: 7. Output Resource 8. Constraint Resource 9. Mechanism Resource

GEM View 4

5.Process Subject: 4. Function: 3. Organization Unit: 2. Organization: 1. Location:

6. Input Resource: 7. Output Resource 8. Constraint Resource 9. Mechanism Resource

GEM View 5

6. Input Resource Subject: 5.Process:

4. Function: 3. Organization Unit: 2. Organization: 1. Location:

7. Output Resource 8. Constraint Resource 9. Mechanism Resource

GEM View 6

7. Output Resource 6. Input Resource:

5.Process: 4. Function: 3. Organization Unit: 2. Organization: 1. Location:

8. Constraint Resource 9. Mechanism Resource

GEM View 7

8. Constraint Resource 7. Output Resource 6. Input Resource: 5.Process:


9. Mechanism Resource GEM View 8

9. Mechanism Resource 8. Constraint Resource 7. Output Resource 6. Input Resource: 5.Process:


GEM View 9

For Location 1 (Where?) Show Organization 2 (Who’s

Responsible?) By Organization Unit 3 (Who Performs?) Responsible for Function 4 (What?, Why?) Performing Process 5 (How?) Consuming Resource 6 (With What?) And Producing Resource 7 (For What?) And Constrainted by Resource 8 (Bounded by What?) And Enabled by Resource 9 (Using What?) At Resource State 10 (When for each Resource?) In Quantity 11 (How Many?) With Qualities 12 (What Type?)

GEM View 1 - Basic Query1

GEMAssertions

GEM Repository

GEMRequirements

GEMTaxonomy(Concept


GEM Template Metadata and Data Creation and Storage(GEM Repository as Generalized Information System)

For Subject A At Location 1

Show Organization 2 By Organization Unit 3 Responsible for Function 4 Performing Process 5 Consuming Resource 6 And Producing Resource 7 And Constrainted by Resource 8 And Enabled by Resource 9 At Resource State 10 In Quantity 11 With Qualities 12


Blank Template

as Structure

of Ontology Assertion(Template Fields are Metadata)(Template Name is

Metadata)

Populated Template

as Instance of Knowledge Assertion(Template

Field Values are

Data)

Legend:Template AutoPopulate and/or Lookup Selection of Template Fields and Values

Add New Concepts As Needed to Taxonomy and/or Assertions, as Needed for Template Completion

ResourceTaxonomy Assertion

ResourceObjects

AssertionProcessObjects

AssertionFunctionObjects

AssertionOrganizationUnit Objects

AssertionOrganization

Objects

AssertionLocationObjects

GEM AssertionSubjects

GEM Repository

Requirements

ProcessTaxonomy

FunctionTaxonomy

OrganizationUnit Taxonomy

OrganizationTaxonomy

LocationTaxonomy

GEMTaxonomy(Concept


GEM Template Metadata and Data Creation and Storage(GEM Repository as Generalized Information System)

For Subject A At Location 1

Show Organization 2 By Organization Unit 3 Responsible for Function 4 Performing Process 5 Consuming Resource 6 And Producing Resource 7 And Constrainted by Resource 8 And Enabled by Resource 9 At Resource State 10 In Quantity 11 With Qualities 12


Blank Template

as Structure

of Ontology Assertion(Template Fields are Metadata)(Template Name is

Metadata)

Populated Template

as Instance of Knowledge Assertion(Template

Field Values are

Data)

Legend:Template AutoPopulate and/or Lookup Selection of Template Fields and Values


Categories


ResourceObjects





Objects



GEM Repository

Requirements

ProcessTaxonomy

FunctionTaxonomy



LocationTaxonomy

GEMTaxonomy(Concept


GEM Functional Management Information (View 4) Mapped to GEM Assertions

Enterprise (e.g., Organizational Endeavor) – Business Function

– Functional Guidance • Function Assignment

– Responsibility » Authority

– Functional Budget (Resource Constraint) » Assigned Organization Unit

– Parent Organization – Parent Location

– Unit Location • Functional References

– Policy » Process

– Procedure – Template

– Form – Report – Etc.

– Tool (Manual, Automated, etc.) – Constraint (Rule, Role-based Access, Standard, Principle, etc.)

• Function Operation – Functional (Program, Project, Person) Mission

» Vision – Goal

– Objective – Strategy

– Plan – Recurrent Operation

– Deliverables (Output Resource) – Tasks (Applied Policy/Process/Procedure) – Schedule (Constraint Resource) – Budget

– Input Resource – Constraint Resource – Mechanism Resource

– Quality – New Initiative

– Deliverables (Output Resource) – Tasks (Applied Policy/Process/Procedure) – Schedule (Constraint Resource) – Budget

– Input Resource – Constraint Resource – Mechanism Resource

– Quality Legend:Template AutoPopulate and/or Lookup Selection of Template Fields and Values


Categories

GEM Repository Structure(A Generalized MIS)


ResourceObjects





Objects



GEM Repository

Requirements

ProcessTaxonomy

FunctionTaxonomy



LocationTaxonomy

GEMTaxonomy(Concept


Categories

PK

AKAK

AK

AK

AK

AK

AK

PK

AK

AK

AK

AK

AK

AK

FK

FK

FK

FK

FK

FK

FK

FK

FK

FK

FK

FK

FK

FK

OID GUID

GUID