Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

TAPES Screenshots

208 views

Published on

  • Be the first to comment

  • Be the first to like this

TAPES Screenshots

  1. 1. 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
  2. 2. TAPES Screen 1.0 – Main Menu, Repository Menu Items
  3. 3. TAPES Screen 2.0 – Menu Bar and Life Cycle Management Menu Items
  4. 4. TAPES Screen 3.0 Menu Bar and Maintenance Menu Items
  5. 5. TAPES Management Model Screen 1.1, Enterprise Top Level Object Classes
  6. 6. TAPES Screen 1.1.1.5. European Location Objects
  7. 7. TAPES Screen 1.1.1.5.5.5.13. Heidelberg Location Objects
  8. 8. TAPES – Screen 1.1.1.5.5.1.13.1 –F6 Campbell Barracks Object Information
  9. 9. TAPES, Screen 1.1.1.5.5.1.13.1 Cross-Index (Context) (PC’s in Theater Surgeon’s Office)
  10. 10. TAPES Screen 1.1.5.1.1.1, Request Statement Object Ancestry and Descendants
  11. 11. Tapes Screen 2.1, Resource Distribution View
  12. 12. TAPES Screen 2.2. Object Composition View
  13. 13. TAPES Screen 2.3 Object Composition/Inventory View
  14. 14. TAPES Screen 3.1, Life Cycle Management View,
  15. 15. Expanded LCM Stages
  16. 16. TAPES 3.1.x, Prepare Request Description MIS
  17. 17. Page 2, Request Description
  18. 18. Page 3, Request Description
  19. 19. LCM, POC MIS
  20. 20. Categories of POC
  21. 21. TAPES – Create Association, Select Base Object
  22. 22. Select Objects Associated with Goeppingen
  23. 23. 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) CONTEXT WHERE IS ___? ORGANIZATION CONTEXT WHO IS RESPONSIBLE FOR ___? WHO HAS THE AUTHORITY TO ___? WHO HAS THE RESOURCES FOR ___? FUNCTION CONTEXT WHAT IS DONE FOR ___? WHY IS ___? PROCESS CONTEXT HOW DO WE ___? RESOURCE CONTEXT WHAT GOES INTO ___? WHAT RESULTS FROM ___? REQUIREMENT LIFE CYCLE (TIME) CONTEXT HOW MANY ___? HOW OFTEN ARE ___? HOW MUCH IS ___? WHEN IS ___? (USER PERSPECTIVE) Basic Questions in Context (USER QUERY) WORK UNIT (TEAM/OFFICE/BILLET) CONTEXT WHO DOES ___? WHO SUPPLIES ___? WHO PRODUCES ___? WHO RECEIVES ___? BASIC ENTERPRISE QUESTIONS
  24. 24. 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 CHAIN 92. Customer /Supplier Value Chain 6. Supplier (Input) 2.1 Products 2.2 Process 2.3 Structure 2.4 Culture 2. Your Enterprise (Internal, Insource, and Outsource Activity) 1. Customer (Output, Outcome) 4. Partner (Output, Mechanism) 3. Authority (Control) 6. Public (Output, Control) Perform, Measure, and Improve a.Expectation and e.Satisfaction b.Requirem ent c.Production d.Provision 4. Partner (Input, Mechanism) 5. Public (Input, Control) Natural Environment RecyclerExtractor Refiner Value-Added Activity Consumer
  25. 25. 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. MEASURE SATISFACTION BASELINE 2. IDENTIFY REQUIREMENTS 3. PRODUCE PRODUCT 4. PROVIDE PRODUCT 1. MEASURE SATISFACTION MEASURED QUALITY IMPROVEMENT CYCLE TIMECURRENT CYCLE TIME =100 UNITS CYCLE TIMEEXPECTED CYCLE TIME =40 UNITS 1. 2. 3. 4. 1. MEASURED QUALITY IMPROVEMENT 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
  26. 26. 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 Attribute Value Value Value Object N Attributes Attribute Attribute Attribute Value Value Value Association Attributes Attribute Attribute Attribute Value Value Value Change Attributes Container /Predecessor Object X Component /Successor Object Y Base Object N Child Object B Parent Object A Parentage Inheritance Descendant Inheritance Input Association Output Association Past Change Future Change Present Change “Kind-Of” Hierarchy “Part-Of” Hierarchy Categorize Associate Plan/History
  27. 27. A modern view of the early GEM-TAPES structure. (Circa 1998) 2/28/2004 Proprietary and Copyright Roy Roebuck, 1982-2003 39 39. Object Metaschema Object 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)
  28. 28. Early GEM Physical Structure (Circa 1989) COPYRIGHT ROY ROEBUCK, 1982 -1997. GEM DATA TABLES AND VIEWS A REPOSITORY BASED REQUIREMENT LIFE CYCLE SYSTEM CONTEXT MANAGEMENT OBJECT PROFILE OBJECT CONTEXT OBJECT MIS (E.G., REQUIREMENT LCM)OBJECTS ASSOCIATIONS OBJECT DETAIL ATTRIBUTES OBJECT DISTRIBUTION OBJECT ANCESTORS OBJECT DESCENDENTS OBJECT COMPOSITION TABLE VIEW (DATABASE) VIEW-DERIVED TABLE SOFTWARE MODULE EVENTUAL DATA AND FUNCTIONAL MIGRATION OF LEGACY MIS LDAP MetaDirectory Object Warehouse Starburst DB Object Warehouse Starburst DB Object Warehouse Starburst DB Object Warehouse Starburst DB Extended X.500 DIT (Hierarchy) Star DB Snowflake DB Snowflake DB Star DB DSS/EIS DEMIS Physical Structure
  29. 29. 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 CUSTOMER NEED REQUIREMENT DATABASE VALIDATE REQUIREMENT PRODUCE PLAN/BUDGET * ROI/FEA PRODUCE LONG RANGE PLAN RESOURCE ALLOCATION DEFINE THE REQUIREMENT SATISFY THE REQUIREMENT REVALIDATE THE REQUIREMENT ACQUIRE/PROCURE/FIELD OPERATE/MAINTAIN MANAGEMENT CATALOG SEARCH PLAN REPOSITORY SEARCH * NOTE: ROI = RETURN ON INVESTMENT FEA = FUNCTIONAL ECONOMIC ANALYSIS ABC= ACTIVITY BASED COSTING DEFINED APPROVED ALLOCATED ASSIGNED AUTHORIZED GENERALIZED PLAN LIFE CYCLE MANAGING THE CUSTOMER REQUIREMENT REQUESTED * ABC One World InformationSystem
  30. 30. A more detailed view of the resource management process as part of a larger Functional Process Improvement process. (Circa 1983)

×