+ All Categories
Home > Documents > TAPES Screenshots

TAPES Screenshots

Date post: 17-Jan-2017
Category:
Upload: holisticmeta
View: 153 times
Download: 0 times
Share this document with a friend
31
This document provides screeshots of the Total Architecture, Plans, and Execution System (TAPES), built by Roy Roebuck and used by the HQ, US Army Europe, Deputy Chief of Staff, Information Management (DCSIM) during the period 1989 till 1992. TAPES is an implemented IT Management subset of the General Enterprise Management (GEM) methodology for whole-enterprise management. A SQL variant of TAPES was built by USAREUR in 1993. The TAPES application and documentation was submitted by USAREUR to U.S. Department of the Army in 1990 as a request that it be further developed and standardized across the U.S. Army. TAPES was subsequently accepted as a MACOM Information Service Module (MISM) by Dept. of Army, and a requirement for TAPES was included in the DoD SBIS Phase II RFP. Neither the Army nor OSD implemented TAPES, even though the USAREUR DCSIM, in 1991, said that TAPES was the “whole goldmine”, in relation to OSD (Mr. Paul Strassman) asking for the field to submit their IT “golden nuggets”. GEM was conceived an initially implemented and demonstrated during the period from 1982 till 1989. GEM and TAPES are the copyrighted creations of Roy Roebuck. GEM was originally implemented in Lotus 123 and then dBase II and III. TAPES was originally implemented in dBase IV as a partial GEM migration from dBase III.
Transcript
Page 1: TAPES Screenshots

This document provides screeshots of the Total Architecture, Plans, and Execution System (TAPES), built by Roy Roebuck and used by the HQ, US Army Europe, Deputy Chief of Staff, Information Management (DCSIM) during the period 1989 till 1992. TAPES is an implemented IT Management subset of the General Enterprise Management (GEM) methodology for whole-enterprise management. A SQL variant of TAPES was built by USAREUR in 1993.

The TAPES application and documentation was submitted by USAREUR to U.S. Department of the Army in 1990 as a request that it be further developed and standardized across the U.S. Army. TAPES was subsequently accepted as a MACOM Information Service Module (MISM) by Dept. of Army, and a requirement for TAPES was included in the DoD SBIS Phase II RFP. Neither the Army nor OSD implemented TAPES, even though the USAREUR DCSIM, in 1991, said that TAPES was the “whole goldmine”, in relation to OSD (Mr. Paul Strassman) asking for the field to submit their IT “golden nuggets”.

GEM was conceived an initially implemented and demonstrated during the period from 1982 till 1989. GEM and TAPES are the copyrighted creations of Roy Roebuck. GEM was originally implemented in Lotus 123 and then dBase II and III. TAPES was originally implemented in dBase IV as a partial GEM migration from dBase III.

Total Plans and Execution System – Screen 0

Page 2: TAPES Screenshots

TAPES Screen 1.0 – Main Menu, Repository Menu Items

Page 3: TAPES Screenshots

TAPES Screen 2.0 – Menu Bar and Life Cycle Management Menu Items

Page 4: TAPES Screenshots

TAPES Screen 3.0 Menu Bar and Maintenance Menu Items

Page 5: TAPES Screenshots

TAPES Management Model Screen 1.1, Enterprise Top Level Object Classes

Page 6: TAPES Screenshots

TAPES Screen 1.1.1.5. European Location Objects

Page 7: TAPES Screenshots

TAPES Screen 1.1.1.5.5.5.13. Heidelberg Location Objects

Page 8: TAPES Screenshots

TAPES – Screen 1.1.1.5.5.1.13.1 –F6 Campbell Barracks Object Information

Page 9: TAPES Screenshots

TAPES, Screen 1.1.1.5.5.1.13.1 Cross-Index (Context) (PC’s in Theater Surgeon’s Office)

Page 10: TAPES Screenshots

TAPES Screen 1.1.5.1.1.1, Request Statement Object Ancestry and Descendants

Page 11: TAPES Screenshots

Tapes Screen 2.1, Resource Distribution View

Page 12: TAPES Screenshots

TAPES Screen 2.2. Object Composition View

Page 13: TAPES Screenshots

TAPES Screen 2.3 Object Composition/Inventory View

Page 14: TAPES Screenshots

TAPES Screen 3.1, Life Cycle Management View,

Page 15: TAPES Screenshots

Expanded LCM Stages

Page 16: TAPES Screenshots

TAPES 3.1.x, Prepare Request Description MIS

Page 17: TAPES Screenshots

Page 2, Request Description

Page 18: TAPES Screenshots

Page 3, Request Description

Page 19: TAPES Screenshots

LCM, POC MIS

Page 20: TAPES Screenshots

Categories of POC

Page 21: TAPES Screenshots

TAPES – Create Association, Select Base Object

Page 22: TAPES Screenshots

Select Objects Associated with Goeppingen

Page 23: TAPES Screenshots

TAPES Design Concepts

Asking and Answering Any Question, from Simple to Complex (Circa 1982)

2/28/2004 Proprietary and Copyright Roy Roebuck, 1982-2003 28

LOCATION (SPACE) CONTEXTWHERE IS ___?

ORGANIZATION CONTEXTWHO IS RESPONSIBLE FOR ___?WHO HAS THE AUTHORITY TO ___?WHO HAS THE RESOURCES FOR ___?

FUNCTION CONTEXTWHAT IS DONE FOR ___?WHY IS ___?

PROCESS CONTEXTHOW DO WE ___?

RESOURCE CONTEXTWHAT GOES INTO ___?WHAT RESULTS FROM ___?

REQUIREMENT LIFE CYCLE (TIME) CONTEXT

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

WHEN IS ___?

(USER PERSPECTIVE)

Basic Questionsin Context

(USER QUERY)

WORK UNIT(TEAM/OFFICE/BILLET)

CONTEXTWHO DOES ___? WHO SUPPLIES ___? WHO PRODUCES ___? WHO RECEIVES ___?

BASIC ENTERPRISE QUESTIONS

Page 24: TAPES Screenshots

Asking Questions About the Enterprise and Its Environment (Circa 1987)

2/28/2004 Proprietary and Copyright Roy Roebuck, 1982-2003 37

THE SUPPLIER/CUSTOMER VALUE CHAIN92. Customer /Supplier 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

Page 25: TAPES Screenshots

Reducing Process Cycle Time while increasing quality and accuracy is a GEM-TAPES Goal. (Circa 1982)

2/28/2004 Proprietary and Copyright Roy Roebuck, 1982-2003 38

COPYRIGHT ROY ROEBUCK, 1982 -1997.

1. MEASURESATISFACTION

BASELINE2. IDENTIFYREQUIREMENTS

3. PRODUCEPRODUCT

4. PROVIDEPRODUCT

1. MEASURESATISFACTION

MEASUREDQUALITY

IMPROVEMENT

CYCLETIMECURRENT CYCLE

TIME =100 UNITS

CYCLETIMEEXPECTED CYCLE

TIME =40 UNITS

1.2.

3.

4.

1.MEASUREDQUALITYIMPROVEMENT

IMPROVING THE CUSTOMER SATISFACTION LIFE-CYCLE

CREATE CONTINUOUS IMPROVEMENTS BY:- LEADERSHIP/MANAGEMENT/MEMBER DEVELOPMENT;- REDUCING PROCESS/SYSTEM COMPLEXITY (SIMPLIFYING); - INCREMENTAL PROCESS/SYSTEM IMPROVEMENTS;- PROCESS/SYSTEM (RE)ENGINEERING; AND/OR- TECHNOLOGY INSERTION.

ACHIEVE:- FASTER RESPONSE;- LOWER COST;- HIGHER QUALITY; AND - GREATER ADAPTABILITY.

Supplier Cycle Time

8. Reducing Cycle Time

Page 26: TAPES Screenshots

An Early GEM-TAPES logical structure model. (Circa 1957)

2/28/2004 Proprietary and Copyright Roy Roebuck, 1982-2003 49

99. Context of a Simple Dynamic Object

Attribute Attribute AttributeValue Value Value

Object N Attributes

Attribute Attribute AttributeValue Value Value

Association Attributes

Attribute Attribute AttributeValue Value Value

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

Page 27: TAPES Screenshots

A modern view of the early GEM-TAPES structure. (Circa 1998)

2/28/2004 Proprietary and Copyright Roy Roebuck, 1982-2003 39

39. Object MetaschemaObject Metaschema Structure

Object

Parent Object

Derived Object

Object 3Object 2

Object Class, Subclass, Instance Taxonomy

Class Properties (property/value pair)

Class Methods (method name, return type, parameters)

Class Triggers (object change)Object

Indication

Object Associations

Association References

(time predecessor/successor relations, space

container/component relations)

Page 28: TAPES Screenshots

Early GEM Physical Structure (Circa 1989)

COPYRIGHT ROY ROEBUCK, 1982 -1997.

GEM DATA TABLES AND VIEWSA REPOSITORY BASED REQUIREMENT LIFE CYCLE SYSTEM

CONTEXTMANAGEMENT

OBJECT

PROFILE

OBJECT

CONTEXT

OBJECT MIS(E.G.,

REQUIREMENTLCM)OBJECTS ASSOCIATIONS

OBJECTDETAIL

ATTRIBUTES

OBJECT DISTRIBUTION

OBJECT ANCESTORS

OBJECT DESCENDENTS

OBJECT COMPOSITION

TABLE VIEW(DATABASE)

VIEW-DERIVEDTABLE

SOFTWARE MODULE

EVENTUAL DATA AND

FUNCTIONAL MIGRATION OF LEGACY

MIS

LDAPMetaDirectory

Object WarehouseStarburst DB

Object WarehouseStarburst DB

Object WarehouseStarburst DB

Object WarehouseStarburst DB

Extended X.500 DIT(Hierarchy) Star DB Snowflake DB Snowflake DB Star DB

DSS/EIS

DEMIS Physical Structure

Page 29: TAPES Screenshots

GEM-TAPES was intended as a resource management tool to implement this process. (Circa 1985)

COPYRIGHT ROY ROEBUCK, 1983 -1996.

DEVELOP

REVALIDATE

1

1

APPLY STANDARDS

CUSTOMERNEED

REQUIREMENT DATABASE

VALIDATE REQUIREMENT

PRODUCE PLAN/BUDGET

* ROI/FEAPRODUCE LONG RANGE PLAN

RESOURCE ALLOCATION

DEFINE THE REQUIREMENT

SATISFY THEREQUIREMENT

REVALIDATE THEREQUIREMENT

ACQUIRE/PROCURE/FIELD

OPERATE/MAINTAIN

MANAGEMENTCATALOG

SEARCH

PLANREPOSITORY

SEARCH

* NOTE:ROI = RETURN ON INVESTMENTFEA = FUNCTIONAL ECONOMIC ANALYSISABC= ACTIVITY BASED COSTING

DEFINED

APPROVED

ALLOCATED

ASSIGNED

AUTHORIZED

GENERALIZED PLAN LIFE CYCLEMANAGING THE CUSTOMER REQUIREMENT

REQUESTED

* ABC

One World InformationSystem

Page 30: TAPES Screenshots

A more detailed view of the resource management process as part of a larger Functional Process Improvement process. (Circa 1983)


Recommended