CEIM-P

Engineer Pamphlet

25-1-6

Department of the Army

U.S. Army Corps of Engineers

Washington, DC 20314-1000

EP 25-1-6

11 February 1991

Information Systems Modernization Program

COMMAND DATA MODEL 

AND DICTIONARY

Distribution Restriction Statement

Approved for public release; distribution is 

unlimited.
EP 25-1-6

 11 February 1991

Command

Data Model

and Dictionary

Information

Systems

Modernization

Program
EP 25-1-6

11 Feb 91

i

Foreword

The U.S. Army Corps of Engineers has developed a product that will help manage

information in such a way that it can be shared throughout the organization. The Corps

recognizes the importance of information as a growing resource. The use of technology to collect,

store, and disseminate information is increasing. Thus, the importance of managing information is

paramount.

Historically, there have been many systems in place for logically organizing and controlling

information and data. For instance, libraries use systems to catalog and track books, periodicals,

videos, and other information. As a result of our Command resolve to treat data as a corporate

resource in the same manner that we do our personnel, materiel, etc., the Corps has developed a

system to store and locate data using computer technology and manual systems. This system is the

Corps of Engineers Data Encyclopedia developed by HQUSACE CEIM-PD.

At the center of the Encyclopedia is the Command Data Dictionary (CDD). The

Command Data Dictionary is a special kind of database which acts as a repository of information

about data we use to manage our programs and projects.

ROBERT L. HERNDON

Colonel, Corps of Engineers

Chief of Staff
EP 25-1-6

11 Feb 91

ii

Command Data Model and Dictionary

Table of Contents

Chapter 1- Introduction Paragraph Page

Purpose ............................................. 1-1 1-1

Applicability .......................................... 1-2 1-1

References ........................................... 1-3 1-1

Objectives ........................................... 1-4 1-1

Scope ............................................... 1-5 1-2

Corrections, Inquiries and Improvements .................... 1-6 1-2

Chapter 2- General Concepts

General ............................................. 2-1 2-1

Information and Data ................................... 2-2 2-2

Data Objects ......................................... 2-3 2-2

Entities .............................................. 24 2-2

Data Elements ........................................ 2-5 2-2

Naming Conventions ................................... 2-6 2-2

USACE Data Encyclopedia .............................. 2-7 2-3

IDEF Modeling Techniques .............................. 2-8 24

Command Data Dictionary ............................... 2-9 24

Command Data Model .................................. 2-10 24

Extracting a Data Model View ............................ 2-11 2-5

Fundamental and Derived Data ............................ 2-12 2-5

Conceptual Data Models vs. Physical Data Models ............. 2-13 2-5

How are the CDM and the CDD Used in Routine FOA Work? .... 2-14 2-6

Chapter 3- Data Administration Procedures and Change Control ............... 3-1

Chapter 4- Accessing the Corps Central Data Encyclopedia ................... 4-1
EP 25-1-6

11 Feb 91

iii

Appendices Page

Appendix A Command Data Model (CDM) .................................. A-1

Appendix B Command Data Dictionary (CDD) ................................ B-1

Appendix C Data Classes ................................................ C-1

Appendix D Common and Standard Domains ................................. D-1

Appendix E Legacy System to CDM Correlation .............................. E-1

Appendix F Data Element Defining and Naming Conventions ..................... F-1

Appendix G Glossary of Terms ............................................ G-1

Figures

Figure 2-1 USACE Encyclopedia Data Administration and Database

Administration Models, Operations and Interfaces .................... 2-5

Figure 3-1 Manage Data Administration for USACE

AO Context Diagram ......................................... 3-3

Figure 3-2 Manage Data Administration for USACE

AO Decomposition Diagram .................................... 3-4

Figure 3-3 Activity Descriptions .......................................... 3-5

Figure 3-4 ICOM Descriptions ........................................... 3-6

Figure 4-1 Encyclopedia Network Configuration ............................. 4-1

Figure A-1 Simple IDEF Data Model ...................................... A-2

Figure A-2 Key Based (K/B) Data Model ................................... A-3

Figure B-2 Role Name ................................................. B-4

Figure D-1 Common Domains ............................................ D-2

Figure D-2 Standard Domains ........................................... D-3

Figure F-1 Data Element Defining and Naming

Examples and Case Study ...................................... F-4

Figure F-2 Class Word List and Definitions ................................. F-5

Figure F-3 Class Words by Category ...................................... F-9
EP 25-1-6

11 Feb 91

1-1

Chapter 1 1-2. Applicability

Introduction This pamphlet is applicable to all

1-1. Purpose ordinate Commands (MSC), Districts, LabThis pamphlet provides to users the structure (FOA).

of the Corps' shared data and their definitions.

Included herein are the business rules 1-3. References

expressed in the data relationships and the

dictionary of data elements. The graphic a. AR 25-l.

depiction of the entities, data elements, and

their relationships is the Command Data b. AR 25-9.

Model (CDM). See Appendix A for a

description of the CDM. The Command Data 1-4. Objectives

Dictionary (CDD) in Appendix B contains the

definitions of the data entities and data The objectives of the Command Data Model

elements. This model forms the basic frame- and Dictionary are:

work for all business systems development

that envisions sharing of data The goal of this a. Facilitate user involvement in informapamphlet is to facilitate functional user tion system requirements and development.

involvement in Information System

development and to ensure maximum b. Document the business rules and relaconsistency and shareability of data by tionships that govern the Corps' data.

providing:

a. The means by which functional users users by establishing common data structures

identify data currently managed within the and definitions.

Corps.

b. The means to assure common participation in the Corps' data administration

definitions of data collected and reported (new proposals, changes, refinements, etc.).

throughout the Corps.

c. The mechanism to document the Data functional representatives of the Data

Architecture Control Committee’s (DACC) Architecture Control Committee.

consensus of the Corps' data and definitions.

HQUSACE/OCE elements, Major Suboratories, and Field Operating Activities

c. Facilitate communications among

d. Provide a basis to solicit MSC

e. Publish a record of decisions by the

f. Control data redundancies.

g. Encourage adherence to data policies.
EP 25-1-6

11 Feb 91

1-2

h. Provide a structured approach to the functions closely related to project

development of databases and applications. management. The early accounting baseline

1-5. Scope

a. This Command Data Model is based Data Model is that our business is related to

on the recently developed "baseline" concepts managing work, whether it be a large

for accounting and work management. It will multiyear project or a smaller task. Our

eventually represent all that we know about objective is to get the work done on time and

the Corps' shared data requirements. within budget. So naturally, the data model is

b. The Command Data Model was origi- FUNDING ACCOUNT, RESOURCE

nally created in March 1989, by the integra- ESTIMATE, COST-ACCOUNT, and

tion of the three baseline Prototype MILESTONE. This version also includes

Development Concept (PDC) data models: those data elements that the AMPRS and

Work Breakdown Structure, Work Item Re- PRISM functional users felt represented the

source Structure, and Accounting Structure. current AMPRS and PRISM databases.

It was augmented by data from the Design

PDCs and by reverse engineering the 1-6. Corrections, Inquiries and

Automated Management and Progress Improvements

Reporting System (AMPRS) and Project and

Resource Information System for Questions concerning any inconsistencies,

Management (PRISM) databases. inquires, and recommendations for improvec. At this stage it includes data about to HQUSACE, CEIM-PD, Washington, D.C.

project management and some about other 20314-1000.

structure will be updated by the Accounting

PDC. Team when validated.

d. The key concept of the Command

driven by the entities: WORK-ITEM

ments regarding this pamphlet should be sent
EP 25-1-6

11 Feb 91

2-1

Chapter 2 characteristics when structured, combined,

General Concepts business process.

2-1. General 2-4. Entities

These concepts define and describe the a. Entities are the persons, places, things,

components which constitute the Command concepts events, or activities about which we

Data Model (CDM) environment. A basic, want to collect data. The data object, entity, is

Corps-wide understanding of these concepts is a logical place to store the characteristics of

necessary to ensure consistency when refer- the real world objects. Analysts show the relaring to the Command Data Model and tionships between entities and the rules affectDictionary. The importance of a common ing their relationship graphically. The entities

structure and definition of data cannot be and their relationships are the building blocks

overemphasized The Corps must share its used to depict, or model, the data needed to

data, must communicate its data, and must support a business process.

understand its data.

2-2. Information and Data areas or classes of information. See Appendix

The Corps defines information as a and a listing of USACE Data Classes.

representation of facts, concepts, and

assumptions that are derived from data for use 2-5. Data Elements

in performing the various Corps' missions.

Data is defined as meaningful facts about a. Data elements are uniquely defined

persons, places, things, concepts, events, and and identifiable characteristics of the person,

activities in a defined format and structure place, or thing defined by an entity. When valfrom which information may be derived. Data ues are given to these data elements, the valis considered a Command resource that is ues represent facts about specific instances of

shared among many users as appropriate. an entity important to the business. Data eleData is manipulated and processed to create ments are the smallest unit of meaningful data.

information from which business decisions can

be made. Identifying the role that the data b. The definition of a data element inplays in deter-mining the Corps' business rules cludes a description of the characteristic that it

is an essential part of identifying reliable data. represents, such as CONTRACT-START2-3. Data Objects work under a specific contract. The definition

Data objects are entities, data elements, values that a data element may assume, usurelationships, and data models and their ally defined by the data element's length and

and analyzed, provide an understanding of the

b. The USACE has categorized data into

C “USACE Data Classes," for an explanation

DATE, the date that the contractor may begin

also includes the Domain which is the set of
EP 25-1-6

11 Feb 91

2-2

format, or by a specific list of values. (Refer (1) The methodology for Information

to Appendix D for lists of Common and Systems development includes:

Standard Domains.)

c. To provide continuity from current

(legacy) data systems to the Command Data (b) Conceptual Design

Model (CDM), it is helpful to see the correlation between the Legacy System Data (c) Iterative Application Development

Elements and the Command Data Elements.

This is further discussed in Appendix E, (2) Throughout the process of this

“Legacy System to CDM Correlation." methodology, the data administrative

2-6. Naming Conventions

When dealing with data objects (e.g., entities business, the information needed by the variand data elements), it is important to under- ous business activities is defined. This inforstand and agree on the object's name and defi- mation includes the Inputs, Controls, Outputs,

nition. As a system is developed, the structure and Mechanisms (ICOMs) used by the busiand definition of all data should be stored in ness people in their activities.

the Data Encyclopedia or Dictionary. The

Data Encyclopedia is a valuable tool for (b) Entities are identified which will

organizing, tracking, and controlling the vast contain the fundamental data elements repreamounts of data used by the Corps. In order sented in the inputs, controls, outputs and

to effectively use this tool, naming conven- mechanisms as well as other data that needs to

tions have been established that help users to be kept; then an Entity-Relationship (E-R)

quickly locate data objects and identify dupli- Data Model is developed.

cate data objects. The Corps of Engineers

“Data Element Defining and Naming (c) The entities are defined.

Conventions" appear in Appendix F of this

document. (d) The entities key data elements are

2-7. USACE Data Encyclopedia entities reviewed.

a. The USACE Data Encyclopedia (e) The non-key data elements that

addresses the Corps' needs by providing users describe the entity are identified.

with an information sharing tool, a repository

of metadata (information about data), and an (f) All data elements are defined.

automated cross reference resource tool (for

cross referencing activity and data models) b. The Data Encyclopedia will facilitate

used in the information resource methodology each stage of this process. It will: Improve

adopted by the Corps.

(a) Requirements Analysis Planning

functions will occur as follows:

(a) In concert with the modeling of the

determined and the relationships among
EP 25-1-6

11 Feb 91

2-3

system documentation; provide accurate, means for displaying the current (AS-IS) and

timely metadata during system development; the planned (TO-BE) environments; a means

provide extensive cross references of corpo- to accomplish interaction and consensus

rate data; help coordinate the documentation between user groups as part of system

needs of all users; and assist in enforcing development; consistency, which facilitates

standards. data integration and sharing; and the use of

c. The inquiries and listings available conceptual design.

from the Data Encyclopedia will enable

management and users to spot redundant data. 2-9. Command Data Dictionary CDD

Redundant data are likely to cause

inconsistencies in the information derived a. The Command Data Dictionary is a

from it. The same piece of data may have printed glossary of data terms. Its information

different formats or many versions, resulting can also be retrieved online from the

in inconsistent, or even inaccurate business Encyclopedia system. If Webster's dictionary

decisions. is essential to clear communication in the

d. The benefits provided by the USACE definitions in the Encyclopedia are essential to

Data Encyclopedia during system clear communication within systems design,

development include: The minimization of development, and use.

data redundancy; ease in developing and

maintaining current documentation (therefore, b. The Data Encyclopedia provides a

minimizing change impact); and extensive mechanism to define and use information

cross references and multiple views of existing about data. It is a central repository of this

Corps data sources. information about data called metadata.

2-8. IDEF Modeling Technique of methods used to collect, compute, and

The U.S. Air Force's Integrated Computer understand the characteristics and

Aided Manufacturing (ICAM) invented a relationships of the data itself. The

technique required on many of its projects Encyclopedia provides the technology to

which evolved into the Integrated Computer record, analyze, and share this. The data

Aided Manufacturing Definition, ICAM dictionary is a report of the metadata about

Definition (IDEF) Modeling Technique. The the Corps' data. The Corps' CDM and CDD

IDEF Modeling Techniques have been are based on the IDEA Modeling Techniques.

adopted by the Corps of Engineers to be used

during system development. The Corps uses 2-10. Command Data Model (CDM)

the IDEF Modeling Techniques in the

development of activity and data models a. The Command Data Model is a

which graphically and descriptively depict the graphical representation of the structure of the

Corps' business processes. The IDEF USACE corporate data. It contains the 

Modeling Techniques provide: An effective

documentation and audit trails during system

English language, then data structures and

Consistent with the increase in the efficiency

disseminate mission data is the need to
EP 25-1-6

11 Feb 91

2-4

entities, relationships, and data elements of the NOTE: Sequencing numbers denote normal

Corps' data. Like the Command Data Dictio- development cycle.

nary, it is a representation of the metadata that

describes the important shared data of the 2-11. Extracting a Data Model View

Corps. This metadata is stored in the

Encyclopedia. For the CDM, it is a graphical a. The Encyclopedia has the capability to

representation. It serves as a communication extract a subset from a model. This feature is

tool between functional and technical users. invoked by first creating a Data Model Header

b. Because it is graphical, it best shows tions for extracting a data model which is acthe structure and, of course, the complexity of cessed under the Encyclopedia menu of

the totality of the Corps' data that has been "Other Data Model Functions."

defined as of a particular point in time. But,

because it is graphical, the full definitions b. The new data model is populated by

cannot be shown on it without destroying its selecting the relationships that are going into

structural message. Thus, the Command Data it which indirectly selects the entities of

Dictionary report or the many Encyclopedia choice. If the entities selected are "Registered"

search and retrieval functions are used to or "Approved," they can be only borrowed or

present this detail. shared because they represent Corps-wide

c. The Command Data Model and DACC. A new project can create "Candidate"

Command Data Dictionary (CDM/CDD) are entities and relationships. Relationships can be

the base from which shared information will deleted only if they do not affect the key

evolve in the Corps. The model flow (in Fig- structure of the CDM.

ure 2-10) shows how the CDM/CDD serves

to: 2-12. Fundamental and Derived Data

(1) Provide a starter model for a new Fundamental data is the lowest level, basic

project. piece of information or fact. The data model

(2) Integrate project final data models data. Derived data is information prepared by

after they have been validated and have passed algorithms, conditional extractions, or formuthe In-Process Reviews (IPRs) and alpha las, such as "the sum of costs from 7/89 thru

tests. 10/89" or "inflation adjusted project estimate."

(3) Interface legacy systems to the PROJECT-ESTIMATE and INFLATIONCDM. RATE.

(4) Provide a physical database design

from a conceptual project final model.

for the new model, then following the instrucentities, approved and controlled by the

and dictionary deal with basic or fundamental

The latter is derived using the data elements
EP 25-1-6

11 Feb 91

2-5

2-13. Conceptual Data Models vs Physical a neutral view of the data. For example, an

Data Models “inflation adjusted cost estimate" has the same

a. The Conceptual Data Model (or viewpoint' a project manager's viewpoint' or

Command Data Model in the Corps) is the the viewpoint of virtually any function within

normalized basic structure of the business the Corps.

rules, entities, and data elements that describe

the things the Corps needs to operate. A b. When a subset of the CDM

conceptual model deals with the fundamentals, (Command Data Model) is formed into a

following specific rules for accuracy and specific database to support one or more

communication The conceptual data model is applications, the may be adaptations made for

meaning whether it is seen from an accounting
EP 25-1-6

11 Feb 91

2-6

performance or security reasons. The result is (1) Help the field Information

called an physical model. The physical model Management (IM) staffs develop better

may contain derived values, may combine or systems.

split entities into records that suit the

performance requirements better, or may even (2) Help information users throughout

repeat data elements in different records. the Corps to better understand the data with

c. The following CDD and CDM relate

to physical models in that: (3) Facilitate data sharing and the

(1) They provide the conceptual

metadata which includes the fundamental data (4) Identify and promote the use of a

and definitions, the building blocks, of the common set of data structures that represent

physical model. the way the Corps does business.

(2) Many (or most) entities will be- (5) Standardize data definitions and

come a table in the physical model without do- mains, including data type, size, and

change. standard lists of values where appropriate

(3) The fields of the physical model code, etc.)

usually correspond to data elements in the

conceptual model although sometimes there b. In the pursuit of happiness and better

may be derived fields in the physical model Information Systems throughout the field, you

that combine multiple conceptual data will find it useful to:

elements algorithmically (such as: summation,

ratio, or complex formula). (1) Familiarize yourself with the

(4) The domain attributes specified in roadmap of the CDD.

the dictionary are recommended for use in

physical models throughout the Corps and (2) If you are beginning a new applicaprovide the rules for input editing. tion development, see if you can extract a

2-14. How are the CDM and the CDD first make your job easier, and second, tie in

Used in Routine MSC Work? to the structures that other Corps IM projects

a. The IDEF Modeling Techniques and

the continuing evolution of the Command (3) Browse through the CDM and

Data Model and the Command Data CDD to see if there are entities or data

Dictionary will assist the MSCs in these ways: elements that have already been defined that

which they are dealing.

interchange of data.

(such as, organization code, project status

overall structure of the CDM. Use it as a

starter data model from the CDM in order to

are using.

you can use in your systems development.
EP 25-1-6

11 Feb 91

2-7

(4) Check any system or database that (5) If the CDM/CDD structures or

you must interface with to see if any of the definitions don't work for you, let Data

data that you will be sharing is already defined Administration know. The evolution and

in the CDM/CDD. If not, contact Data quality of the CDM/CDD can only occur if

Administration because you have just discov- you make it happen.

ered data that needs to be shared. That data

needs to be incorporated into the CDM/CDD c. Later, after the next development

so the two known users and any more that phase of the Encyclopedia, we will include

come along can be assured of consistency. suggestions for the inclusion of current and

legacy systems into the Encyclopedia.
EP 25-1-6

11 Feb 91

3-1

Chapter 3 on the left side of the activity model while the

USACE Data Administration Procedures

and Change Control c. A development project, shown as

3-1. General elements as it proceeds, or it may wait until

a. The activities involved in managing the Throughout the design process, the team will

Command Data Model (CDM) and thereby check the Encyclopedia to see if the CDM or

the Command Data Dictionary (CDD) are de- some other project's data model has already

picted in the following activity diagrams: discovered and defined the data they require.

(1) The Context Diagram in Figure 3-

1 (activity AO) represents the overall activity d. The responsible data proponents

of managing Data Administration for the U.S. participate in the reviews of development

Army Corps of Engineers (USACE). projects in activity Al and fulfill their

(2) Figure 3-2 is the decomposition or the data in their assigned data classes.

graphical representation of the AO subactivities performed to accomplish managing the e. The proposed changes that are not alUSACE Data Administration activity. ready addressed are forwarded to HQ Data

(3) Figure 3-3, Activity Descriptions, integration with the CDM and other proposed

lists the activity number, name, and changes.

description of activities displayed on the AO

Decomposition Diagram. f. Any user of data may submit a request

(4) Figure 3-4, ICOM Descriptions, proponent who will revise and approve it

defines the Inputs, Controls, Outputs, and (activity A2) and pass it on to the HQ Data

Mechanisms involved on the AO Administration for integration. If the

Decomposition Diagram. proponent rejects a user request, the user can

b. There are three sources of change to

the Command Data Model: Project g. In activity A3, the HQ Data

Requirements discovered by an Information Administrator accepts Project Final Models or

System Development Project, requests from the changes that have been approved by the

users, and data administration technical proponents and checks them for standard adrequirements arising as the HQ Data herence, quality definitions, appropriate entity

Administration works to integrate all the field placement of data elements, and nonredundproposals. The first two are shown as inputs ancy. If they pass these QA checks, then they

third is internal to activity A3.

activity Al creates new entities and data

the end and submit a Project Final Model.

If so, they can arrange to share it.

responsibilities of managing the definition of

Administration (activity A3) for QA and

for change or addition to the appropriate data

"appeal" to the HQ DA directly.
EP 25-1-6

11 Feb 91

3-2

are sent to the Data Architecture Control must evaluate the benefits versus the impact

Committee (DACC). The Command DBA will of these changes (activity A4). The DACC is

negotiate any conflicting proposals as much as the user's checkpoint.

possible to reach a suitable compromise. Any

unsolved issues are forwarded to the DACC i. When the DACC approves a set of

for resolution. changes or a new CDM, the Command Data

h. The DACC is made up of data propo- clopedia and a new CDM is available online

nents who have active modernization projects (activity A5). Periodically, an updated EP 25-

in process. Since changes that are genuine im- 1-6 is released that summarizes major mileprovements and pass all the QA checks may stones in the evolution of the CDM/CDD.

still have impact on existing users, the DACC

Administrator makes the updates in the Ency-
EP 25-1-6

11 Feb 91

3-3
EP 25-1-6

11 Feb 91

3-4
EP 25-1-6

11 Feb 91

3-5

ID ACTIVITY NAME DESCRIPTION

Al Administer-Data-at-Application- The administration of data at the MSC

Development-Project (Division, District, or other) or HQ

directorate as part of an Information

System Project. The range of activities

goes from requesting change of a data

element definition to developing a full

scale Project Final Model.

A2 Coordination-of-Data-Definition The proponents who are responsible for

-by-Proponents their business areas coordinate changes

to the CDM or CDD that are requested,

implied, or demanded

A3 Administer-Data-at-HQ The administration and integration of

Corps* data definitions, structure, and

usage. This will include review of proposed new data entities and data

elements, mediating different viewpoints,registering the data entities and

data elements, integrating new models, as

well as administering the change procedures, and chairing the Data Architecture

Control Committee (DACC).

Project Starter Data Models may also be

generated for new IS projects.

A4 Review-and-Approval-by-DACC The DACC Proponents review proposed

new entities, data elements, and models,

as well as changes to the Command

Data Model and the Command Data

Dictionary.

A5 Update-CDM-and-CDD The actual encyclopedia metadata defin

ing the CDM and the CDD are updated, and

appropriate diagrams and reports are

published.

Figure 3-3: Activity Descriptions
EP 25-1-6

11 Feb 91

3-6

ICOM NAME DESCRIPTION

Appeal An Appeal may be generated by a user

or IM person when the proponent of an

entity or business area rejects his proposed change. This usually occurs

across business areas. The appeal goes

to the Corps Data Administrator who

will consider it and process it through

the full DACC, if appropriate.

CORPS-Data-Guidelines The regulations and guidelines issued by

USACE HQ to implement the Corps*

data management policy.

Command-Data-Administrator The headquarters office responsible for

recommending Data Administration

policies, preparing guidelines, and

providing support to the MSCs in their

staffing and operation of the Data

Administration function. This Command DA is also responsible for the

management of the Corps* Data

Encyclopedia, providing starter models

to IM projects, registering entities and

data elements within the Corps*, acquiring Army approval where required,

maintaining the Command Data Model

and Dictionary, as well as integrating

new MSC models into the CDM.

DA-Approved-Entities-DE-Updates Updates to Data Entities and Data

Elements that have been reviewed by

the HQ Data Administrator and

approved. They must yet be reviewed

and approved by the DACC before they

are officially incorporated into the

CDM.

Figure 3-4: ICOM Descriptions
EP 25-1-6

11 Feb 91

3-7

ICOM NAME DESCRIPTION

DA-Integrated-CDM A CDM that integrates some new

entities, data elements, or Project Final

Models with the current version of the

CDM. It is not yet the new version of

the CDM until the DACC reviews and

approves it.

DACC-Approved-Ent-DE-Updates Updates to the current entities and data

elements of the CDM that have been approved by the DACC for inclusion in

the next update.

DACC-Approved-Integrated-CDM An integrated CDM including changes

and new Project Final Models that has

been reviewed and approved by the

DACC.

DACC-Proponents Those data proponents who serve as voting members of the DACC for the resolution of definition issues and who

review and approve CDM updates.

DACC-Rejections These are proposed model entity or data

element changes whose impact is considered untenable at the present time.

Data-Proponents Functional users who are designated by

their directorates or MSCs as the individual (or office) responsible for the defininon of data that is assigned to that office

for caretaking.

Figure 3-4: ICOM Descriptions (cont*d)
EP 25-1-6

11 Feb 91

3-8

ICOM NAME DESCRIPTION

Encyclopedia-System The software, supporting hardware, and

network that provide a repository for the

metadata about the Corps* data. The Encyclopedia System includes PC Modeler, the Host Encyclopedia modules,

and the Leverage model analysis package. There is a central repository in an

SQL relational database accessed

through a nationwide network.

Field-DAs Data Administrators at the Divisions,

Districts, or HQ Directorates who support users and IM staff in the definition

and sharing of data.

They are particularly involved in new

application development and upgrading of

legacy systems.

HQ-DA-Rejections These are proposed model entity or data

element changes that do not pass quality

assurance checks.

New-CDM The newest , now the current, version of

the CDM which has been updated with

the DACC approved changes or new

model integrations.

New-Entities-and-Data-Elements Updated Entities and Data Elements (or

their metadata) that have been added to

the CDM/CDD following approval by

the DACC.

Old-CDM The current, or previously current version, of the CDM that will be changed

or expanded.

Figure 3-4: ICOM Descriptions (cont*d)
EP 25-1-6

11 Feb 91

3-9

ICOM NAME DESCRIPTION

Project-Final-Model An IDEF, fully attributed, data model

which represents the final result of the

conceptual design phase of a project

Project-Requirements The requirements of the users, or requirements inherent in the business process, for data to be stored and possibly

shared.

Project-Starter-Model A selected subset of the Command Data

Model extracted to provide an application development project with a nucleus

of registered and defined data entities

and data elements. The purpose is to facilitate data sharing and to assure consistency of data structure and definition.

Proponent-Accepted-Changes Proposed changes to entities, data elements, and relationships that have been

reviewed by proponents and are being

forwarded to the Command Data Administrator for a quality assurance check

and final approval by the DACC.

Proponent-Rejection A requested change to the CDM or

CDD that a data proponent has rejected

as not consistent with the intent and

meaning of the data for which he is the

shepherd.

Reg-Laws-Ext-Agency-Requirements Requirements from new or revised laws,

regulations, or external agency requirements.

Figure 3.4: ICOM Descriptions (cont*d)
EP 25-1-6

11 Feb 91

3-10

ICOM NAME DESCRIPTION

Registered-Entities-Data-Elements Entities and data elements that have

been quality checked by the Command

Data Administrator and whose status

has then been raised to Registered.

STAMIS-and-Legacy- Systems-Requirements Requirements imposed on the data

entities, data elements, or structure

imposed by STAMIS or legacy systems.

User-Request Requests from users for additions or

changes to the CDM or CDD.

Figure 3-4: ICOM Descriptions (cont*d)
EP 25-1-6

11 Feb 91

4-1

Chapter 4 Encyclopedia Network Configuration, depicts

Accessing the Corps Central central computer where the Host

Data Encyclopedia

4-1. To Access the Encyclopedia: main menu of the Encyclopedia system will be

Use Vistacom and the CEIM-PD provided maintenance or search and retrieval functions

Script (see the Encyclopedia Users Manual or of the Encyclopedia.

the Data Administration/Data Encyclopedia

course Participants Guide for detailed c. Most of the functions display results

instructions in using the script). on the screen in a mini-report format. Some

a. Enter RUNE to execute the Run tory. The screens that you use to initiate these

Encyclopedia batch file on the PC. It will longer reports have options you can specify

prompt you for host identifiers and which will cause the Encyclopedia system to

passwords. After successful connection to the download the report file to the ENCVCOM

host, it will prompt you for your Encyclopedia directory on your PC, where you can peruse it

identifier and password. Figure 4-1, or print it.

the remote work station connected to the

Encyclopedia operates.

b. Following the security checks, the

displayed. At this time you can use any of the

generate reports into files in your VMS direc-