Configuration management and accounting utilizing interactive forms mode technology

Compat. & Indus. Eagng Vo[. 5. No. 2, pp. 67-79. 19~1 0360~352/81/02006%13502.00/0 Printed in Great Britain Pergamon Press Ltd

CONFIGURATION MANAGEMENT AND ACCOUNTING UTILIZING INTERACTIVE FORMS MODE TECHNOLOGY

F. MAX CROFT and DONALD T. WHITE Marshall Space Flight Center--National Aeronautics and Space Administration, Huntsville. Alabama,

U.S.A.

(Revised 6 November 1980; received for publication 10 November 1980)

A~traet--This paper describes an online computer system designed to support the establishment, implementation, and maintenance of a Configuration Management Control System. Configuration Management is a discipline for technical and administrative tracking of the:

(I) Identification and documentation of technical requirements of a project specifically associated with the end product.

(2) Control of changes, deviations, and waivers to those technical requirements. (3) Recording and reporting of changes to the "baseline" requirements and the implementation status of

the changes.

The Configuration Management discipline dictates establishment of a technical requirements baseline for each group of hardware/software, or "end item", to be produced by the project. Baselines, plus approved changes, constitute the current approved configuration identified at any point in time in te project life cycle. A "'Configuration Control Board" is established at each level of project management to identify and maintain a baseline. This Board is the authority for authorizing changes, deviations, or waivers to established baselines.

The Configuration Management discipline has become a standard requirement on space and defense projects to identify, control, and account for the configuration of project end items. In addition, the Configuration Management discipline is becoming widely accepted as essential to computer software development projects. In large-scale, complex projects, an automated system is essential for integrating and tracking change processing activities. An automated system can also track accounting and reporting of approved baselines and all approved changes to those baselines.

The online system for Configuration Management and Accounting that is described provides a highly efficient system utilizating the most advanced forms mode capabilities of an intelligent terminal with 16 K forms mode memory built in. A comparative analysis is made relating advantages of the forms mode online system and the resulting savings in computer time, manpower, and system operation costs. This Online System offers the following advantages over batch processing:

(1) Rapid retrieval and display of systems forms. (2} Form scroll capability. (3) Large screen size provided by the forms mode terminal. (4) Use of ASCII indexed sequential files.

This paper describes a significant improvement to an online computer system designed to support the establishment, implementation and maintenance of a Configuration Management System. This system employs a forms mode capability at the user's terminal to radically improve the effectiveness of configuration accounting and control methods in large government research and development programs such as the Space Shuttle.

The basic concepts of configuration management are presented initially. This discussion provides a background of earlier batch methods for processing configuration management data. This paper concludes with a description of the forms mode technology, its resulting enhancements, increased efficiencies and reduced costs.

Configuration management is a discipline for technical and administrative tracking of the:

(1) Identification and documentation of technical requirements of a project specifically associated with the end product of the project.

(2) Control of changes, deviations, and waivers to those technical requirements. (3) Recording and reporting of changes to the "baseline" requirements and the im-

plementation status of the changes. The term "configuration" refers to the physical and functional characteristics of a product--

characteristics such as its weight, shape, size, materials, processes, power consumption and performance. For sophisticated products built to stringent standards such as those imposed by

67

68 F. M. CROFT and D. T. WHITE

the government on aerospace and military systems, managers have recognized the value of a formalized configuration management system. The concept is not new. It is really the formulation of a discipline which every effective manager adopts at least informally.

Configuration management is the means through which the integrity and continuity of technical and cost decisions related to product performance, productibility, operation and maintenance are recorded, communicated+ and controlled by project managers[l].

The configuration management discipline has become a standard requirement on space and defense projects. It assists the manager in knowing just what the product consists of as the projects evolves, including operational computer software and supporting documentation (drawings, operating manuals and repair instructions). During the project's life cycle of conception, definition, production and use of a particular product, it provides the manager with a basis for making decisions as to whether or not to adopt a change to the product design. If a change is adopted, this system shows the manager how to handle changes to all the affected elements of the product.

The government has pioneered the development and application of formalized configuration management techniques. The set of prodedures establishing configuration management has grown primarily out of military specifications and contract exhibits[2]. The discipline has evolved over the years in conjunction with major hardware development programs. This system was first applied in the Department of Defense (DOD) and then in the National Aeronautics and Space Administration (NASA).

The Configuration Management System is also becoming widely accepted in the management of applications software development projects as well as hardware. For example, NASA specifies the establishment of a configuration management plan in its software development projects, both in-house and contractor. This plan defines a process to be followed for baseline configuration definition procedures, change control procedures, and change evaluation and reporting procedures [31.

An automated system is essential for supporting the Configuration Management System in large-scale complex projects whether they are hardware or software.

The configuration management discipline dictates establishment of a technical requirements baseline for each group of hardware/software to be produced by the project. The term applied to selected portions of the product is Contract End Item (CEI), or Configuration Item (CI). Baselines, plus approved changes, constitute the current approved configuration identification at any point in the project life cycle.

In planning and implementing the configuration management discipline, the life cycle of a project is divided into phases. Although these project phases may be labeled differently by various organizations, they always exist as good engineering and business practices in government and industry. A project can be divided into the following basic phases[4]:

(I) Concept formulation phase. (2) Definition phase. (3) Acquisition phase. (a) Design and development stage; (b) Production stage. (4) Operational phase.

As shown in Fig. 1, (adapted from Ref. [1]), each phase terminates when the baselines are reached. The baselines are as follows:

(1) Functional baseline. (2) Allocated baseline. (3) Product baseline. (4) Operational baseline.

The baselines are the review and decision points in the life cycle of the project. Theoretically, a new phase is not initiated until issues related to the previous phase have been resolved. The idea of progressive definition has particular significance in this phased project planning scheme. As a product proceeds through research, conceptual design, development, detailed design+ qualification and production, its configuration becomes progressively more definite and precise.

IDEF'N

'T'ONI

I P"A

sE

I

J F

UN

CT

ION

AL

! ( P

RO

GR

AM

R

EQ

UIR

E-

ME

NT

S

BA

SE

LIN

E)

• S

YS

TEM

SP

EC

IFIC

ATI

ON

C

OM

PLE

TIO

N

• W

OR

KS

TATE

ME

NT

ISS

UA

NC

E

PR

EL

IMIN

AR

Y

AL

LO

CA

TE

D

(DE

SIG

N

RE

QU

IRE

- M

EN

TS

B

AS

EL

INE

)

I I !

• C

EI P

ER

FOR

MA

NC

E

• S

PE

CIF

ICA

TIO

N

• IN

TER

FAC

E D

OC

UM

EN

TS •

C

OM

PLE

TE

• IN

TER

FAC

E A

ND

SU

BC

ON

TRA

CTO

R •

CH

AN

GE

CO

NTR

OL

CO

NTR

OL

ES

TAB

LIS

HE

D

• C

ON

FIG

UR

ATI

ON

MA

NA

GE

ME

NT

OR

GA

NIZ

ATI

ON

ES

TAB

LIS

HE

D

• C

ON

FIG

UR

ATI

ON

MA

NA

GE

ME

NT

PLA

N C

OM

PLE

TED

• D

ES

IGN

CR

ITE

RIA

DE

FIN

ED

• S

YS

TEM

TR

AD

EO

FF A

NA

LYS

ES

INIT

IAT

ED

• H

AR

DW

AR

E A

LLO

CA

TIO

NO

LI

STS

• "B

RE

AD

BO

AR

D"

AN

D

MO

CK

UP

DE

SIG

N D

ATA

• LO

NG

LE

AD

TIM

E

PR

OC

UR

EM

EN

TS

DE

SIG

N

BA

SE

LIN

E

I I I I I

AC

QU

ISIT

ION

PH

AS

E

,,J

QU

AL

IFIC

AT

ION

/PR

O-

DE

TA

IL

TO

TY

PE

MO

DE

L

DE

SIG

N

FA

BR

ICA

TIO

N

AN

D

QU

AL

IFIC

AT

ION

T

ES

TIN

G

%BAS

EL,NE

PR

OD

UC

TIO

N

FA

BR

IC

AT

ION

EN

GIN

EE

RIN

G M

OD

EL

• O

UA

LIFI

CA

TIO

N/P

RO

TOTY

PE

•

OP

ER

ATI

ON

AL

AR

TIC

LE

DR

AW

ING

RE

LE

AS

E

DR

AW

ING

RE

LEA

SE

D

RA

WIN

G R

ELE

AS

E

QU

ALI

FIC

ATI

ON

TE

ST

• O

UA

LIFI

CA

TIO

N

TES

T •

FIN

AL

TES

T P

LAN

S

PR

OC

ED

UR

ES

P

RO

CE

DU

RE

S

EN

GIN

EE

RIN

G M

OD

EL

• U

PD

ATE

D C

EI

TES

T--P

RO

CE

DU

RE

B

PE

RF

OR

MA

NC

E SP

EC

.

LAY

OU

T D

RA

WIN

GS

•

INIT

IAL

CE

I DE

SIG

N

SP

EC

IFIC

ATI

ON

A

DV

AN

CE

LIS

TS

OF

MA

TER

IAL

DE

SIG

N R

EV

IEW

D

AT

A

CE

I PE

RF.

$P

EC

. AP

PR

OV

ED

I C

ON

TIN

UE

D

/ i

PROD

UCTIO

N /"

d PR

OD

UC

T

| (P

RO

DU

CT

P

RO

DU

CT

ION

|

CO

NF

IGU

R-

| A

TIO

N

BA

SE

LIN

E|I

I

BA

SE

LIN

E)

' I

I I

• T

ES

T.~

4FG

DA

TA

A

VA

ILA

BLE

• H

AR

DW

AR

E

CO

NFI

GU

RA

TIO

N

AP

PR

OV

AL

• C

EI D

ES

IGN

S

PE

CIF

ICA

TIO

N C

OM

PLE

TE

• FI

RS

T A

RTI

CLE

A

CC

EP

TED

•

QU

ALI

FIC

ATI

ON

TE

ST

DA

TA

Fig~

I.

o =_.

70 F. M. ('ROF3 and I). [. Wml~

And, in most cases, the configuration is continually modified throughout the life cycle of the product.

The overall objective of configuration management is to guarantee that a given product is what it was intended to be, functionally and physically. This is defined by contractual drawings and specifications, in addition, configuration management identifies the configuration to the lowest level of assembly required to assure repeatable performance, quality, and reliability in future products of the same type. To satisfy this objective, the following five major goals are commonly an integral part of the configuration management effort[2}.

(1) Definition of all documentation required for product design, fabrication and test. (2) Correct and complete description of the approved configuration (drawings, parts lists,

specifications, test procedures, and operating manuals). (3) Traceability of the resultant product and its parts to their descriptions. (4) Accurate and complete identification of each material, part, subassembly and assembly

that goes into the product. (5) Accurate and complete pre-evaluation control and accounting of all changes to product

descriptions and to the product itself. The Configuration Management System provides technical and administrative direction as well as tracking of configuration baselines. It also maintains increasing control as each baseline is established. The basic disciplines involved in the application of the system are identification, accounting and configuration control as shown in Fig. 2 (adapted from Ref. [4]).

The identification discipline consists of creating and formally releasing a complete and accurate description of the products during each phase of the project. This includes specifications, drawings and data lists which define the originally approved configuration (baseline) and subsequently define all approved changes to the individual CEIs. Configuration identification assures that the product and all supporting documentation are continually compatible for the life of the CEI.

The accounting discipline establishes a procedure for documenting all descriptions and revisions so that complete and accurate data relating to the product can be retrieved when desired. This data includes the following:

(1) Where a product is located o r installed. (2) The identification of product items by serial number. (3) Current modification status.

CONFIGURATION MANAGEMENT

. I 1 .ccoo.,,.o I

PRODUCT CONFIGURATION PRODUCT DESCRIPTION RECORDS IDENTIFIERS

I CONTROL I

CHANGE CONTROL PRO- CEDURES

IDENTIFICATION OF PRODUCT CONFIGURATION VERIFICATION CHANGE CONTROL AND ACCEPTANCE REQUIREMENTS RECORDS REVIEW ORGANIZATION

IDENTIFICATION OF CHANGES TO PRODUCTION ITEMS

CHANGE STATUS RECORDS CHANGE CRITERIA

CONFIGURATION REVIEWS & INSPECTIONS

FILES OF CHANGE AUTHOR- IZATION AND APPROVALS

DRAWING, :SPECIFI- CATION AND TEST PROCEDURE REVISION

DATA RELEASE IOEPJTtFICATION REQUIREMENTS

Fig. 2.

Configuration management and accounting 71

Configuration control assures that whatever is done during a particular phase is approved by the authorized officials and is accurately and completely shown in the baseline documents. Control is a continuing function from the earliest stages of the project. It consists of systematic procedures by which configuration changes are proposed, evaluated, coordinated and either approved or rejected for incorporation.

Depending on the project scope, a Configuration Control Board (CCB) is necessary to act as the final authority on proposed major changes to the product configuration. A typical CCB includes representatives of engineering, production control, manufacturing engineering, pur- chasing, contracts, quality assurance, reliability, and document/data control. Although CCBs will differ in size and level of activity, they have the common responsibility for the direction of change evaluation, change planning, and change incorporation. A Configuration Control Board is established to act as the decision-maker on proposed changes to the product.

With this brief description of the concepts of the configuration management discipline, let us consider now the computer techniques that are employed in support of the operational activity associated with implementation of the discipline.

Two separate and distinct computer systems are an integral part of the configuration management system within NASA. These are the Standard Integration and Tracking System (SCIT) and the Configuration Management Accounting System (CMA).

The system that traces the progress of paper relative to every change processing activity associated with identified hardware and software end items is called the Standard integration and Tracking System (SCIT)[5]. The SCIT System provides the basis for maintaining the control element of configuration management. It tracks the proposed change, and related activity, from initiation through change disposition and implementation. It was initially developed to control the processing of changes to the Saturn vehicles, Special reports were available on request to provide all levels of management with the status of any change being processed.

The Configuration Management Accounting (CMA) System[6] was developed to account for the approved configuration with all approved changes at any point in time in the life cycle of the project. CMA also provided reports on a scheduled basis or on request to all levels of management. These systems operated in the batch mode for many years. The activities involved in the SCIT and CMA Systems and the relationship between the two systems is shown in Fig. 3.

(BASELINE ESTABLISHMENT AND CHANGE CONTROL)

CHANGE CHANGE ESTABLISH B/L INITIATION DISPOSITION IMPLEMENTATION

V V V V [ I

(SClTI

(CMA}

CONTRACTOR'S CHANGE MANAGER'S IMPLEMENT ACCEPTANCE OF INITIATION DISPOSITION DIRECTION DIRECTION

~' V V V

F"--CHANGE INTEGRATION " -~ CHANGE PACKAGE AND PROCESSING CLOSE-OUT

(APPROVED CHANGES}

NOTIFICATION OF INCORPORATION AND VERIFICATION

STATUS MODIFICATION BASELINE ~'7 "

1 ,OAL T NEW APPROVED CONFIGURATION BASELINE

r

l_ Fig. 3 SCIT and CMA relationship.

72 F. M. Ceo~ and D. T. WHITE

The SCIT System begins when the initial item of change data associated with a proposed change is received. This change data can be a contractor-originated Engineering Change Proposal (ECP) or government-originated Engineering Change Request (ECR). The initial item of change data is assigned a Program Control Number (PCN) and a change package bearing the same PCN is established (see Fig. 4.) This package will include:

(1) Engineering change requests/change requests. (2) Engineering change proposals. (3) Interface revision notices. (4) Interface control documents. (5) Configuration control board directives. (6) Change orders. (7) Other related/pertinent data.

All subsequent change data related to the proposed change must reference the assigned PCN. This insures that all related change data are consolidated into the same change integration package and that each action and associated responsibility necessary to complete processing of the change is identified, scheduled and accomplished.

As each item of change data is received, it is reviewed to determine the next actions, assign responsibilities and to establish scheduled completion dates. Once determined, this information is recorded on SCIT Master input Sheets and then transferred to tape and verified for incorporation into the SCIT data base. Each engineering change remains open until all change actions are completed, incorporated into the SCIT data base, and shown in the SCIT Master Report.

The SCIT data base is updated each working day by prepared SCIT Master Input Sheets. The update of the data base may be accomplished to record any transaction such as: (a) Establishing a new PCN record; (b) Revising an existing PCN record; (c) Incorporating two or more PCN records into one; (d) Closing a PCN record; (e) Deleting a PCN record: (f) Canceling a PCN record; (g) Reopening a closed PCN record.

The CMA System an efficient means for identifying the approved configuration baseline (original baseline and subsequent authorized changes). The CMA System provides various reports for management utilization. Included are: (a) Configuration Identification Index which defines the authorized configuration for a given CEI: (b) Contractual Interface Control Docu- ments (ICDs) which define the compatible interface design parameters between interfacing

~ m

CO KS¢ I I MSFC [ [ JSC '~

ICD

B00-123 D00---480 D~-790

Fig. 4 PCN-program controtnumber unique to each change


CEIs; (c) Contractor or government noncompliance reports which define noncompliances which exist at the time of delivery: (d) Contractor Test and Checkout Requirements, Specifications and Criteria Documents (or equivalent) which set forth requirements to be employed by NASA using sites in establishing tests and test procedures necessary to demon- strate the readiness of CEIs for integration into the launch configuration.

The CMA System activity is initiated for a CEI upon the receipt of the government approved detail specification which defines the CEIs performance/configuration. This specification is entered into the CMA Computer Master File and constitutes the recording of the approved configuration baseline for the CEI. After that, each approved or disapproved change to the baseline is entered into the CMA Computer Master File. (See Fig. 5 for information tracked in CMA.)

As each item of configuration baseline and authorized change data is reviewed, it is recorded on CMA input sheets and then transferred to keytape and verified for incorporation in the CMA data base. The status of each approved change involving modification kits remains open until the change data signifying complete incorporation of the modification kit is received, incorporated into the CMA data base and shown in the CMA modification status report.

Special status reports concerning the configuration status of any CEI identified in the CMA data base can be obtained on an as required basis.

The CMA System provides the government Configuration Management Offices with an effective baseline and product hardware accounting system. CMA is basically divided into three Sections.

(1) The Base Data Section--This Section records the configuration baseline data associated with the product.

(2) The Configuration Identification Section--This Section records the approved hardware changes (ECPs) to the above baseline.

(3) The Mod Status Section--This Section records the mod incorporation status by serial number and effectivity of each approved hardware change above.

As in SCIT, the CMA System, through its report generating flexibility, provides the user with timely reports designed especially for each user (see Fig. 6).

Figure 7 depicts the typical change processing activity and denotes when data is incorporated into the SCIT and CMA System.

A comparison of the data bases of SCIT and CMA is shown in Fig. 8. During the first version of the SCIT/CMA System, in the batch processing mode (Fig. 9),

responding to rapid change or deviation within the tracking environment was not feasible. In batch mode, all input is initiated from the SCIT or CMA user via a transaction input

form. This form is translated into a computer format through keytape processing methods. From this step, the data base files are updated in a batch mode environment. This process involves a time lag due to a correction interaction cycle required to insure the validation of the

2.

BASELINE INFO NORMALLY STATIC

CONFIGURATION IDENTIFICATION SECTION

3. MOD STATUS SECTION

DATA ELEMENT

CE, NOMENCLATORE eEl SPEC. NO. CEI SERIAL NO. FLIGHT VEHICLE NO. ECP NO. ECP TITLE

~10 CCBD NO. CCBD ISSUE DATE CONTRACT ACTION NO.

,11. MOD KIT REQUIRED 12. PROGRAM CONTROL NO. 13. EFFECTIVITY 14. EST. M/H (TO INSTALL CHANGE) 15. KIT LOCATION (INSTALLING AGENCY) 16. COMPLETION DATE 17. KIT O/D !SHIP DATE)

Fig. 5 Inform:ilion IFacked in CMA.

• ""

AP

PR

OV

ED

SS

ME

EC

PS

PE

R C

O 7

74,

775,

97

8,

97

9"'

" A

S O

F 0

4 J

UN

B0

RE

LA

TE

D D

OC

C

OD

E/N

O

EF

FE

CT

IVIT

Y

AC

T

DO

CU

A~

NT

CO

iDE

/IM

O.

D/D

AT

E

S-N

O.

EC

P

R K

DO

279

F-R

1

E6+

02+

03

A

CC

BO

ME

3--

00

-10

01

) 11

0679

37

001

EC

P

R K

DG

212

F

E6+

02+

03

A

CC

IDA

~3

--0

0--

09

68

2

00

47

9

3701

2

EC

P

R K

D0

2IM

E

E

B+O

E--

0e+S

U

C

CC

BO

ME

3--

O0

-10

23

2S

0679

37

015

EC

P

R K

D0

21

4

E

E6+

02+

03+

04

C

CC

BID

ME

3--

00

-10

23

2

54

~7

9

37

01

5

EC

P

R K

DO

2114

E

E

6+02

+03

+04

A

C

Cm

DM

E

3--

00

--0

07

0

20

04

79

3

70

15

EC

f' R

KD

02

84

F

-R1

E

9+

06

--0

7

A

CC

IID

ME

3-0

0-1

08

3

22

06

79

37

015

EC

P R

K D

02

14

F

-R1

E

6+02

+03

A

C

Cm

DM

E

3--

00

-10

a3

22

0679

3

70

15

EC

P

R K

D0

28

4

F-R

1

E6

+O

2-0

6+

SU

D

C

CB

DM

E 3

--0

0-1

06

4

1806

79

3701

5

EC

P

RK

D0

2S

5

F

E9

+0

5--

07

A

C

CII

DM

E3

-O0

--1

10

e

29

01

79

37

045

EC

P

R K

D02

/16

F

ES

+ES

+02+

SU

C

C

CB

DM

E3

-00

-- 1

058

1806

79

3704

5

NA

RR

AT

IVE

(R

EM

AR

KS

)

SE

RV

ES

AS

CO

PE

R H

OD

7

7~

B

Y E

EP

AR

AT

E

SE

RV

ES

AS

CO

PE

R M

OO

77

4

SE

RV

ES

AS

CO

PE

R M

OO

77

5

SE

RV

ES

AS

CO

PE

R M

OO

77

4

SE

RV

ES

AS

CO

PE

R M

OO

774

SE

RV

ES

AS

CO

PE

R M

OO

77

5

SE

RV

ES

AS

CO

PE

R M

OO

774

SE

RV

ES

AS

CO

PE

R M

OlD

77

5

EC

P

RK

D02

116

F-R

1

E9

+0

6-0

7

A

A

CC

JDM

E3

-00

--1

11

6

20

07

79

3

70

45

S

ER

VE

S A

S C

O P

ER

MO

D 7

7G

CC

BD

ME

3--

-

O P

ER

M

Fig.

6.

Sam

ple

repo

rt.


CHANGE INITIATOR (NASA OR CONTRACTOR)

PROJECT OFFICE

ENGINEERING MANAGEMENT OFFICE

B&E DIRECTORATE

MffT/MVGVT SITE CCBS

SYSTEM INTEGRATION CONTRACTOR

PROJECT OFFICE LEVEL III CCR

i INITIATE ORTAINPCN SUBMIT

RECEIVE. PACKAGE. TRACK. SCHEDULE

(SI

I

STAFF COORDINATOR

iSl

EVALUATE FOR SYSTEM IMPACT

i IL

EVALUATE FOR IMPACT TO TEST PROGRAM REQUI REMENTS. SCHEDULES ETC.

HOLD FOR EVALUATION IF APPROVED

PRESENT TO LEVELI I I

'ql" CCR

EVALUATE.PRO-- VIOE TECHNICAL INPUT RECOk~4ENDED

{COORDINATE )

IMPLEMENT DIRECTION

! ; iMPLEMENT i

' ~ 1 CCBD TRACK ACTIONS

ISI(C)

L CLOSE-OUT

(S)(C) L

S&E SUPPORT FOR EVALUATION AND DETERMINATION OF M P T ~ G V T IMPACT WILL BE PROVtOED TO THE SITE CCR IS)

ilNFOl ASSURE NO . . . . . ~ SYSTEM

IMPACT

DISPOSITION VIA CCBD

ISIIC)

IS) - SCIT UPDATE (CI - CMA UPDATE Fig. 7. Change flow.

C M A

I BASIC DATA. PRIME DOCUMENT NUMBER. TYPE EFFECTIVITIES. TITLE. ETC.

L APPROVED CHANGE. APPROVAL DATES APPROVAL A U T H O R I T Y AND REFERENCES

SCHEDULE AND RECORD OF ACTUAL MODIFICATIONS PER EFFECTIVITY

I PPROVE CHANGE. ETC.

I ETC. BASIC DATA.

ETC.

S C I T

PROPOSED CHANGE TO PRIME DOCUMENT EFFECT]VITIES. DESCRIPTION OF CHANGE. DATES. ETC.

I PROJECT AFFECTED. ORIGINATOR DOCUMENT. DATES

ACTION ITEM - SCHEDULE BOARD MEETING. OTHER REQUESTS, DATES. ETC.

ACTION ITEM - ETC.

ACTION ITEM - ETC.

i PROJECT AFFECTED, ETC.

J PROPOSED CHANGE . . . . . (ETC.)

Fig. 8. Data ba~e structure,

76 F.M. CROF'r and D. "I'+ Wnlte

I .1 _[

il O E U ~

+_

i|

? Ill I~,1 nPI . .

j+j _ ¢. ~ 0

Z o I--

±

E


data base. After this necessary interaction step, the specific reports needed are generated and delivered to the original users.

The delay involved in batch processing become more impractical because of the critical need of the mission. This deficiency of the system led to the development of an interactive Online System utilizing a cathode ray terminal giving immediate updating and retrieval capabilities in addition to other user enhancements. In this time frame, the updating process made use of a pre-printed graphic form having spaces or shaded areas for changes or updating capabilities. However, the entire contents of the graphic form including the data entered into the form, were transmitted due to limited terminal capabilities. This created a large overhead which resulted in excessive computer time; the system was also difficult to program. As an example, the form and data required over 200 writes to display a formatted form and insert the data on the video terminal.

Improved terminal technology provided an intelligent forms mode capability with internally programmed controls built into the system. This particular terminal has 16 K form mode memory built in. This allowed the user to employ the forms mode display without transmission of the form but allowed data entry to be transmitted. (See Fig. 10 for a typical form used in SCIT System.)

This technique, having the form in memory at the terminal, in conjunction with index sequential file organization a particular data set organization which combines the efficiency of sequential organization with the ability to rapidly access records out of sequence reduced the total online processing time by more than 50%. Part of this savings was due to reducing the number of forms from 10 to 4 forms.

The major enhancements for the SCIT redesign improved processing capabilities which in turn increased the efficiency and effectiveness of the CMS system. The redesign of the access mode enabled more rapid response to the user. The throughput was enhanced an input errors decreased through the ease of the online forms mode capabilities.

The SCIT System has a very large data base. The data base encompasses over 265,000 records to be tracked with files expanding at a rate of 6-10% per month. This massive data base, with daily retrieval and updating ability, requires a tool that is flexible. In addition, this system gives each user his own data arrangement and complete retrieval access to each user's own format.

The data base may be updated simultaneously on a multidrop 9600 Baud line with record lock out techniques. (See Fig. 11 for schematics of online system.) Any data record can now be updated within a ten second response time. The previous data base, utilizing a special NASA system, "Marshall Information Retrieval and Display System (MIRADS)" required from three

~ l 'EASE" DATA eo ~ PCN ~ (MASTER RECORD)

m , . . E O OR,~,N C T O Y RE~ON/ENG,.EER CtOStO R E V , S E PRODRAm PRE DATE DATE DATE ADCDEF~.URt..O

~ [ ] I SYROM/SPENCER I { - - ~ ~ I A DEF l

3: 5:

DESCRIPTION OF PCIN

ETLIDUIDHYDROGENTANK 4:2:[ AFTSULKHEAOPRESSUREROMT 1

PC~II~ELECTED'ITEM DATA PROJ ~ ITEM ~ (DETAIL RECORD)

ODCUMERTCOOE/NUMEER RELDOC. CODE/NUMBER T A S L DOC EFFECTIVITY SY DATE

FCR--'][ sIS17E I ]"~(ET-SAR-3m ] [ ~ N 0 0 ~ i TI÷OI-u ] [ ]

NEXT REIF SCRED RECD A S C O t F G H I J K t M m O ACT OflO DATE DATE

L, I f - - I [ - - I F- - - - I O00000000OO0000 REUA, . : [ ]I l

Fig. 10. Form mode used for on-line updating.

CAIE Vol. 5. No 2--B

78 F. M. CROVT and l). F. WHH[

Fig. I I.

to six minutes to retrieve a record. After complete analysis of the required user demands, the analyst in conjunction with the user identified these benefits from the new SCIT/CMA System:

(i) One common government source for all data: (a) Eliminates conflicting reports; (b) Standardizes data element nomenclature; (c) Establishes common communication media among all organizational elements; (d) Provides common acceptance criteria for CEIs and modification kits customer and contractor quality control: (e) Provides early data input by the agency responsible for the action.

(2) Provides cost savings by using one computer program and reduction in multiple inputting of same data

(3) Reduces computer time by 50%. Cost savings of $560.00 per day. (4) Online update: (a) Eliminates excessive paper utilization. Reduces paper output for

approximately $40.00 a day savings; (b) Reduces the time required for form mode training; (c) Helps to eliminate input errors. Approximately 1200 transactions per day are processed; this eliminates at least a 10% error factor.

(5) Reduces turnaround time to user. The batch system required overnight turnaround of reports; the online system gives virtually instant turnover.

(6) Makes the System flexible to the users.

The input parameters specify the selected report data to be retrieved, sorting sequences and format of printed reports. All data in the SCIT/CMA Data Bank can be retrieved through this technique, with the resultant savings of many programmer man-hours that would normally be required to design and program a new report generator with every new report requirement. In addition, a new report can be produced from the remote terminal within minutes after submitting it and from the daily batch cycle within 24 hr of the known requirements.

Some of the flexible features for the user to request special reports:

(1) User-defined select criteria for any field. (2) User-defined data format across page. (3) User-defined sequence of data. (4) User-defined column and report titles. (5) User-defined page numbering and new page control. (6) User-defined Xerox copying and delivery instruction. (7) Master standard reports flexible for user on request to change report titles and column

headings. (8) Standard report generators totally flexible for user through program changes. (9) Library of previously defined special reports always available for re-use or use with

changes. (10) All input data validated by machine and/or by programmed editing rules. ([1) Reduce man power requirements for peak work loads


The SCIT/CMA Common Retrieval System has resulted in a reduction in contractor support in the area of configuration management since the early batch version of the system; recognition by the user of a greatly increased level of accuracy within the data base: a reduction in the amount of reports necessary for control along with a substantial savings to the project office.

(I) Better computer utilization: (a) Terminal or batch: (b) Index sequential file organization to generate rapid response in relationship to the generalized data base of MIRADS.

(2) Form mode used for online updating: (a) Easily readable: (b) Eliminates high degree of input errors.

The SCIT/CMA System, as presently designed, has resulted in more than a 50% savings in computer time. Using batch processing, the System took 8 hr of processing time. The Online System takes less than 4 hr. This is because of the streamline approach in conjunction with the latest hardware forms mode techniques. In turn, there is a manpower reduction due to the ease of online updating and the eliminating of excessive paper output. This creates a substantial cost savings.

The Forms Mode Online System. utilizing hardware forms mode terminals with index sequential file organization linked with pointers to satisfied rapid response. This system is adaptable for any tracking or recording of any project pertaining to a Change Integration Package concept.

REFERENCES 1. Thomas T. Samaris & Frank L. Czerwinski, Fundamentals a[ Configuration Management. Wiley-lnterscience, New York

(1971). 2. Configuration management. Navmatinst 4130(IAI, Department of Defence, Washington D.C. (19741. 3. C•mputer res•urces management• NHB 24••( • B ). Nati•na• Aer•nautics and Space Administrati•n• Washingt•n D.C• ( • 979 )• 4. Victor G. Hajek, Management o[ Engineering Projects. McGraw-Hill, New York (1977). 5. Standard change integration and tracking (SCIT) system manual MSFC programs, MM 8040(13A), Marshall Space Flight

Center, Alabama (1974). 6. Configuration Management Accounting and Reporting System Manual. MM 8040(5CL Marshall Space Flight Center

(1974).