NBSIR 80-2144

Residential Solar Data Center

MIRADS User's Guide

Patricia M. Christopher

Michael Vogt

Douglas Hall

Center for Building Technology

National Engineering Laboratory

National Bureau of Standards

U.S. Department of Commerce

Washington, DC 20234

October 1980

100 ^

.U56

80-2144 ; 1980 ! Vc. 2' y

Department of Housing and Urban Development

Division of Energy, Building Technology and Standards

Washington, DC 20410

NatiorMl Burtau o< SUBKltrii

Llbftn. Mnuln. BW|.

FEB 1 6 1981

Cxt NBSIR 80-2144

RESIDENTIAL SOLAR DATA CENTER

MIRADS USER'S GUIDE

Patricia M. Christopher

Michael Vogt

Douglas Hall

Center for Building Technology

National Engineering Laboratory

National Bureau of Standards

U.S. Department of Commerce

Washington, DC 20234

October 1980

Prepared for: Department of Housing and Urban Development

Division of Energy, Building Technology and Standards

Washington, DC 20410

U.S. DEPARTMENT OF COMMERCE, Philip M. Klutznick, Secretary

Luther H. Hodges, Jr., Deputy Secretary

Jordan J. Baruch. Assistant Secretary for Productivity, Technology, and Innovation

NATIONAL BUREAU OF STANDARDS, Ernest Ambler. Director
Hi !wTOfU^< ^ ^^3 .fti'ulij

.•' I'/i ;k‘’>'^- . '''<0 '^Vs^iViTS^.'/'^'^^aO .il.U

.viVu*'‘. •' .V- ••IVV ''''' •

’ •- "’S*- '

. .i... V' '^{^oir.,

m
FOREWORD

The Residential Solar Data Center of the National

Bureau of Standards (NBS) has prepared this MIRADS

(Marshall information Retrieval ^nd D^lsplay System)

User’s Guide as a supplement to the MIRADS User's

Manual [1]* published by the National Aeronautics and

Space Administration (NASA) . While the NASA manual

provides detailed documentation of the overall MIRADS

package, the present publication Is Intended for use

exclusively by those who employ the MIRADS system for

retrieving data from the Solar Data Base maintained by

the Residential Solar Data Center.

This User's Guide supercedes User's Manual for Online

Retrieval of Grant Application Data [2] and User ' s Manual

for Online Retrieval of Grantee Report Data [ 3 ]

.

* Numbers In brackets [] refer to references on page 134.
ACKNOWLEDGMENTS

Brenda B. Eidson, technical writer, Rehab Group, Inc.,*

has done an excellent job in assisting the authors in structuring this material into a self- teaching manual.

The Solar Data Diet ionary /Directory in appendix B was

produced by computer programs written by Mrs. Fran Knisley

of Old Dominion Systems, and modified by George Yu of the

Solar Data Base project staff. Solar Technology Program,

Building Economics and Regulatory Technology Division, CBT.

The authors would like to express their appreciation to

Mrs. Ann Pararas for her patience in preparing the final

drafts of this document.

*The name of this company derives from their dedication to

the employment and training of the handicapped.
RESIDENTIAL SOLAR DATA CENTER

MIRADS USER'S GUIDE

TABLE OF CONTENTS

Page

FOREWORD ill

ACKNOWLEDGMENTS iv

LIST OF FIGURES, TABLES, AND EXAMPLES .... vii

ABSTRACT ix

1. INTRODUCTION

1.1 Background 1

1.2 Purpose 5 1.3 Organization and Approach 5 PART I - USING MIRADS

2. THE BASICS OF GETTING ON AND OFF THE COMPUTER

2.1 Connecting the Terminal 8

2.2 Logging on the System 9

2.3 Activating MIRADS 10

2.4 Terminating the Session 11

3. THE BASICS OF USING MIRADS

3.1. General 13

3.2 The QUERY Command 14

3.3 The SORT Command 17

3.4 The COMPUTE Command 18

3.5 The PRINT Command 20

4. A SAMPLE MIRADS SESSION

4.1 Processing a Query 22

4.2 Editing and Processing a Saved Query Set 26

4.3 Saved Fragments 30

5. THINGS TO REMEMBER ABOUT USING MIRADS .... 33

PART II - USING THE DATA

6. USING MIRADS WITH THE GRANT FILE 34

7. USING MIRADS WITH THE SOLAR MASTER FILE ... 39

V
Page

8. USING MIRADS WITH THE MANAGEMENT INFORMATION

SUMMARY (MIS) FILE 41

9. A COMPARATIVE ANALYSIS OF THE USE OF MIRADS

WITH THE DIFFERENT SOLAR FILES 44

APPENDICES

A. MIRADS LANGUAGE SUMMARY 46

B. SOLAR DATA DICTIONARY/DIRECTORY 52

o GRANT File 54

o MASTER File 57

o MIS (Management Information Summary) File. . 70

C. CODES/VALUES FOR CERTAIN DATA ELEMENTS .... 78

D. MIRADS COMPUTER SESSIONS 117

REFERENCES 134

Vi
LIST OF FIGURES

Page

Figure 1 : SOLAR DATA SYSTEM 2 Figure 2 ; Typical Residential Solar Grant .... 34

Figure 3 : Tree Diagram of Typical Grant 35

Figure 4 : Tree Diagram of Grant With Multiple

Locations 36

Figure 5: Some GRANT File Data Elements Shown at

Different Levels 37

Figure 6: Tree Diagram of MASTER File Representation of Typical Grant 39

Figure 7 : Tree Diagram of MASTER File Representation of Grant With More Systems Than

Units 40

Figure 8 : Tree Diagram of MIS File Representation

of Typical Grant 42

LIST OF TABLES

Table 1; SUMMARY RULES vs. MIS DATA ELEMENTS . . 42

Table 2 : USAGE CHARACTERISTICS vs. INTERACTIVE

SOLAR FILES 45

LIST OF EXAMPLES

Example 1

Example 2

Example 3

Example 4

Example 5

Example 6

Example 7

Example 8

Example 9

Example 10:

Example 11:

Example 12:

Example 13:

Example 14 : Example 15:

Simple QUERY Command

QUERY Command With Alpha Qualifier . . QUERY Command With Numeric Qualifier

QUERY Command With Data Element

Qualifier

QUERY Command Using 'AND'* Connector . . Descending SORT Command

Compound SORT Command . COMPUTE Command Using 'NONE'

Breakfleld

COMPUTE Command Using 'ALL' Breakfleld

COMPUTE Command Using Name Breakfleld . COMPUTE Command Using Algebraic

Expression

PRINT Command Using Numeric Output

Limit

PRINT Command Using 'SUM' Output Limit

Processing a Query and Saving a Query

Set

Editing and Processing a Saved Query

Set

vii

118

118

119

119

120

121

122

123

124

125

126

127

128

129

131
LIST OF EXAMPLES (Continued)

Page

Example 16: Adding a Saved Fragment 132

Example 17 : Adding to a Saved Fragment 133

viii
RESIDENTIAL SOLAR DATA CENTER

MIRADS USER'S GUIDE

Patricia M. Christopher

Michael Vogt

Douglas Hall

ABSTRACT

The Residential Solar Data Center project staff in

the Center for Building Technology, National Bureau of

Standards, maintains a computerized data base containing noninstrumented residential data from the DoE/HUD Solar Heating

and Cooling Demonstration Program. Data contained in the

solar data base are accessible online to users of the NBS

Central Computer via remote terminals with a data base retrieval software package called MIRADS (Marshall I^nformation

Retrieval ^nd display System) . This document is a selfteaching user's guide to the solar data base. It is complete

with the basic MIRADS language rules, examples of use, and a step-by-step walk-through of a typical interactive session.

Appendices contain all the data element names and coded

values needed to use the solar data with MIRADS, as well as

many examples of actual computer sessions.

Key Words: Automatic data processing; computer retrieval;

data base retrieval; residential buildings;

solar data base; solar energy system; solar

heating and cooling.

ix
,jy “ ' w ^

3tj |«<saJt.d*^'.^it;6|^4<i'a^:^'^ T«Jrt*0 drf?.

-oo'e |ia i«i. •^a.w^ik -'.iButl a^Jisb. _.« a^^aabaalSj

aW/bS' '«0lis;i' ,aS0

.

bt3fl#«:v»J*ijl<

' llX {t.Mi-jT«.ioo^’’' dl«».G .*;:j(&«-s,S;Cl'J ,

ra-j 9iiA(i: srr-%: i$ '^'4i^ *i'v »4i»)(j«c?9 Xia3«»3 '

I iatlafah) 3aA«l)f

«i iWwopD ©''Xii,T Ja

.4‘jIq«od af'ri.r jjttUob i«ioa '^»:4|/' ©bi;i/;;^: |olrfa«*3 ‘

u iif»A-',*%lr*/ tS'' »€A'*XW,

hivfcoP ' bA i ^f^krAis &X'i*b X'i*

ftfa, ir>»w && /iiiv i:#f4 ,f

’ ' ‘“ ” ‘ a t itfmax*;' V'O

. 4> fit t i « a,i> K "it'-& 3';A<5<»

. »» -,1*ik »/^

. jjl ,. , > ^^, rfi,-, - , f|.»«aWT4* iiJ aiJ^Ji«iboJ;WiA “'

XbA4ii'4>tai»V!» »#ta4;

. n ya*Mfi ;ft<*'''5'«"ti^ ‘-^bloik ,!( aasd 'ail^’ab

f, .,,.a«iX'a,o3

' - ' *''' -'W irija

'

u
1 . INTRODUCTION

1.1 Background

The Residential Solar Data Center (SDC) of the National

Bureau of Standards is responsible for the establishment and

operation of an automated data base containing non-instrumented (i.e., not collected by Instruments, but through

interviews and forms), residential solar data collected from

the Residential Solar Heating and Cooling Demonstration Program which is managed by the Department of Housing and Urban

Development. (HUD) . Data collection contractors to HUD collect and forward

data to the SDC where a solar data base (shown in figure 1,

page 2) is stored on the NBS Univac 1108 computer. This

data base consists of the following files:

a. Grant File : This file contains basic information

about the building project and the solar systems

for each application funded by HUD. These data

are derived from grant applications submitted to

HUD and updated with information from periodic

field reports.

b. Grantee Report File : Data in this file are based

upon reports submitted by each grantee (the

builder/designer who is awarded a grant) to Boeing

Aerospace Corporation describing the progress of

the grant from design and award of construction

financing through actual construction, sale, and

permanent financing. The grantee's perception of

the ease or difficulty in obtaining construction

or permanent financing, and in obtaining building

and zoning approval, as well as problems with construction, equipment, or installation are Included.

c. Technical Description File : This file contains

basic system design and predicted performance data

collected for HUD by Dubin-Bloome Associates from

a large number of selected non-ins trumented

systems. A more detailed set of data is collected

for HUD by the American Institute of Architects/

Research Corporation for those systems which are

to be instrumented.

d. Technical Concerns File : Contained in this file

are data on problems found during the design,

construction, or operational phase which were

recorded in field activity reports submitted by

1
2
Dubin-Bloome and Boeing field representatives. It

also contains data on problems found after

construction, as recorded by the grantee.

e. Marketing Survey File ; This file contains

extensive survey questionnaire results collected

for HUD by the Real Estate Research Corporation

from selected builders, lenders, homebuyers, code

officials, utility companies, and other market

participants. The data sample includes representatives of those who chose to build, lend, or buy a funded solar house and "comparatives'* who did not

become involved. Data are also collected after

the sale to gauge builder and consumer reactions

over a period of time.

f. Utility Consumption File ; This file contains

information on auxiliary or "back-up" fuel consumed for selected solar projects. The data are

collected from utility companies (with purchaser

agreement) . "Comparative" data are also collected

(l.e., utility bills for similar, but non-solar,

homes )

A series of. computer reports (shown in figure 1, page 2)

produced from the solar data base are available to solar

researchers.* These reports range from complete listings

of all data in a file to more detailed "custom" computer

reports. Custom reports are produced to meet specific user

requirements and may print only selected data from a file

and may re-sort the selected data into a new sequence.

The computer reports are either listings of all the

data in a file or a prespecified subset of these data.

To provide flexibility in satisfying requests for other subsets of the data, some of the data base files are available

interactively (i.e., with interaction by the data base user

over a computer terminal). The interactive user can formulate an inq/iiry (also called a query) to the data base,

select his own subset of the data, request it to be sorted

into a particular sequence, and then request only desired

pieces of data (also called data elements or data fields)

to be printed.

*References [4] and [ 5 ] describe these reports in detail

and explain how to obtain copies of individual reports.

3
There are many computer programs available which allow

an inexperienced computer user to reference a data base

interactively. These programs are generically referred

to as information retrieval packages. An experienced computer professional is usually needed to "load" the data base

onto the computer in a format (i.e., an arrangement of the

data on the computer storage device) acceptable to the

package and to "define" the data elements that are in the

data base: their names, their locations in the data base

records, their sizes, etc. This "definition of data" becomes known as the data map or data dictionary/directory

The information retrieval package used by the SDC to

reference the solar data base on the NBS Univac 1108 Computer is called MIRADS (Marshall information Retrieval aind

display iystem) . MIRADS is a large computer program

(actually a series of many computer programs) which was

written by contractors for the National Aeronautics and

Space Administration (NASA) at the George C. Marshall Space

Flight Center in Alabama. An official MIRADS User’s Manual

[1] is published by NASA as well as a MIRADS Implementation

Manual [7]*. Both MIRADS manuals are available to NBS

computer account holders from the NBS Computer Services

Division.

Three solar files are available Interactively with

MIRADS, as shown in figure 1, page 2:

a. the GRANT File;

b. the MASTER File - a combination of other files

expanded to a common of detail;

c. the MIS (Management Information Summary) File - a combination of data from other files,

summarized to the highest common level.

The MASTER File was created to aid solar researchers

who needed a file which would allow them to count similar

"items" of data. The MIS File was created to aid HUD project managers and other data collection managers who needed

data in summary form to make management decisions.

Chapters 6, 7, 8, and 9 contain a further explanation

of why these three files are available interactively.

*This manual is for the use of the computer professional

in loading and defining the data base.

4
1 . 2 Purpose

This user's guide has three purposes;

a

.

to give current users of the solar data base a reference guide for the MIRADS commands and an

up-to-date, concise data dictionary /directory

to the data element names;

b. to give potential users of the solar data base a self-t eaching guide to the MIRADS commands and

rules for formulating a query to the data base;

also to offer a detailed description of the

interactive files available and examples of how

to use them effectively;

c . to present a model for a MIRADS user's guide for

use by anyone with a MIRADS data base.

1.3 Organization and Approach

This user's guide is organized into two parts:

a

.

PART I - USING MIRADS presents in chapters 2

through 5 a step-by-step approach to using the

computer interactively, from dialing the computer

and signing on (shown in chapter 2) to a sample

MIRADS session (shown in chapter 4) . PART I is

supported by appendix D which contains 17 actual

interactive sessions using MIRADS commands discussed in chapter 3. A summary of MIRADS commands is

given in appendix A and a one-page list of "things

to remember" about using MIRADS is given in

chapter 5.

b. PART II - USING THE DATA presents in chapters 6

through 9 a discussion of the structure of the

three solar files available interactively with

MIRADS: the GRANT, MASTER, and MIS Files. A

knowledge of the data structure is necessary to

make queries about the data and to interpret the

results of the queries. These chapters should be

read carefully and thoroughly by any user unfamiliar with the solar data. Chapter 6 covers the

GRANT File structure; chapter 7 covers the MASTER

File structure; chapter 8 covers the MIS File

structure; and chapter 9 analyzes the difference

in using the three files with MIRADS.

5
Current users of the solar data base might use the following outline in reviewing this guide:

a. chapters 6, 7, 8, and 9 -- read carefully;

b. chapters 3 and 5 -- scan briefly;

c. appendix D -- read through list of examples in the

table of contents and review any examples which

might be useful.

d. all other chapters and appendices -- scan to become familiar with contents.

New users of the solar data base might use the following outline in reading this guide:

a. chapters 2 and 4 -- read and follow carefully;

b. if necessary, obtain a NBS UNIVAC 1108 sign-on

protocol* and duplicate the interactive session

shown in chapters 2 and 4.

c. chapters 3 and 5 -- read;

d. chapters 6, 7, 8, and 9 -- read and study carefully;

e. appendix D -- read and study, referring to

chapter 3 to understand commands;

f. appendices A, B, and C — read to become familiar

with contents.

*A valid account number and a USERID/password are necessary.

Contact Computer Services Division, National Bureau of

Standards, Room A221, Administration Building, Washington,

D.C. 20234, or phone (301) 921-3424 for more information.

6
For those interested in using this document as a model

for their own user's guide to MIRADS data files, the following advice is offered:

a. PART I can be used in its entirety as a model.

Some paragraphs will require changes to reference

your MIRADS data base and the examples changed to

reflect your data.

b. PART II needs to be replaced with chapters which

describe the structure of your data files.

c. appendices B and C need to be replaced with

directories and value code lists for your data

files .

*Computer programs and data formats which will allow you to

automate your data description are available from the Solar

Data Center.

7
2. THE BASICS OF GETTING ON AND OFF THE COMPUTER

2.1 Connecting the Terminal

The user's terminal accesses computer-stored data on

the central UNIVAC 1108 computer at the National Bureau of

Standards through telephone lines. The following procedure will result in connecting the terminal to the computer:

a. Turn terminal on.

b. Make sure the switches on the terminal are set:

DUPLEX: HALF

PARITY: EVEN

TRANSMISSION RATE: 30 char ac t er s / s econd

(300 BAUD - High Speed)

c. Dial: Area Code (301) 840-1610, -1620, -1580 or

840-1536 (VADIC modem only)

d. Walt for carrier tone on telephone receiver.

e. Place receiver into coupler device.

f. Wait for carrier light to turn on.

g. Press return key.

The system will respond:

PLEASE ENTER HOST ID (l/B)>

IMPORTANT: Whenever > ("greater

than") symbol appears, the computer

will wait for some response from

the user. This is the "prompt"

message from computer to user.

To the question of host ID, the user should respond

with either "I" (for Interactive) or "B" (for Batch) followed by a carriage return. A carriage return (shown in this

document as "CR")used alone is the same as entering an "I",

because I is the default response.

8
IMPORTANT: A carriage return (CR) must

be entered by the user at the end of

each message. Essentially, the (CR)

is the "prompt" message from user to

computer

Next the computer prints:

OMNUS PORT NN. PARITY (E/0/N)?>

In response to the parity question, the user enters

either:

a. E - Indicating EVEN parity (a CR may be entered to

indicate EVEN also, since the computer defaults

to EVEN)

b. 0 - indicating ODD parity;

c. N - indicating NO checking for parity.

Thus far the display should read:

PLEASE ENTER HOST ID (l/B)>I or (CR)

OMNUS PORT NN. PARITY (E/0/N)?>E or (CR)

2.2 Logging on the System

When the question of parity has been answered (by CR

in most cases), the computer will request user's identification/password, as follows:

ENTER USERID/PASSWORD :

The user should respond with a valid user ID in the

format indicated in the request message. (These are assigned to NBS computer users by the Computer Services

Division. Solar Data Program participants who do not have

a user ID/PASSWORD may contact the Solar Data Center.) The

display now should read:

9
ENTER USER ID /PAS SWORD : > (valid user ID/password)

A message will appear reminding the user to tear off

and destroy this portion of printed display in order to

protect against user ID/PASSWORD misuse.

If there are any operator messages on the status of

the computer, they will appear at this point, followed by

the current date and time.

The computer assumes that the user's terminal has a 80-character width. For 80“character width, user makes no

entry and proceeds to the next step. If this is not the

case, the user must instruct the computer as follows:

a. For 72-character width, enter @@TTY W,72

b. For 132-character width, enter @@TTY W,132 ,d> 8

(The entry "D,8" requests a delay at the end of

each line to allow for carriage return.)

IMPORTANT: If carriage width information is entered, it will be acknowledg

ed by "***@(3 PROCESSING COMPLETE***".

The display should read;

DATE: 012279 TIME: 155401

>@@TTY W,132,D,8

|

Users of 80-character

/width terminals may dis

***@@ PROCESSING COMPLETE*** ) regard these two lines.

2.3 Activating MIRADS

When date and time have been posted, the MIRADS program may be activated by entering "@MIRADS , NB" . The display should read:

>@MIRADS,NB
The computer will ask for instructions as to which

MIRADS-f ormat ted file the user wishes to access:

ENTER QUALIFIER*FILENAME

>

The user responds as follows:

a. For GRANT File: SOLAR*GRANT

b. For MIS File: SOLAR*MIS

c. For MASTER File: SOLAR*MASTER

The computer will determine the availability of the

file required for the MIRADS program. A "READY" message

will appear if the file requested is available for use.

(If the file requested is not available for use, MIRADS

will ask the user to sign off and try again later.) When

the display reads:

ENTER QUALIFIER*FILENAME

>SOLAR*GRANT (or SOLAR*MIS or SOLAR*MASTER)

READY

the system is ready to accept the first MIRADS query set

to define and process a query. (These steps are described in the next chapter.)

2.4 Terminating the Session

When the processing is complete, or when the user desires to terminate the MIRADS session, the one-word command

"STOP" should be entered. The computer will indicate that

the session is terminated, to which the user should respond

"@FIN", as shown:

>STOP

MIRADS EXECUTION NORMALLY TERMINATED

>@FIN

11
«

Cost accounting information will be displayed followed

by the message "*TERMINAL INACTIVE*”. It is important for

the user to understand that although the session is terminated and the terminal has displayed an "inactive” message,

further action is required to disconnect the terminal. This

is accomplished by entering ”@@TERM”. The final display

should r ead

:

”*TERMINAL INACTIVE*”

@@TERM

IMPORTANT: User responses to the computer may be in either upper or lower

case.

IMPORTANT: USER MUST NOT ENTER A SPACE

BEFORE THE FIRST TYPED CHARACTER OF

RESPONSE

.

IMPORTANT: Incorrect entries: To cancel an entire line, press letter "X”

(labeled "CANcel” on some keyboards)

while holding down control key

(labeled "CTRL” on some keyboards).

To cancel individual characters,

press letter ”Z” (labeled "SUBstitute”

on some keyboards) while holding down

control key.

12
3. THE BASICS OF USING MIRADS

3.1 General

MIRADS is an online data storage and retrieval system

that allows the user to extract and process information from

any file which has been specifically defined in a MIRADS

format. Currently, these include the GRANT File, the MIS

(Management Information Summary) File and the MASTER File

(see figure 1, page 2).

The GRANT File, one of the files which comprises the

solar data base, contains basic descriptive information

about each grant, the building project(s), the residential

model(s) being built, and the solar system(s) being installed in the model types.

The MIS File contains data from the other data base

files which have been summarized to the grant level. For

example, one grant may fund four systems in four types of

housing models (e.g. they may be sized dif f erently--one

being a two-bedroom model and one being a three-bedroom

model). The MIS File would summarize (e.g. by averaging,

summing, etc.) the data about the four models and systems

into one set of data at the grant level.

The MASTER File contains data from the other data base

files which have been expanded to reflect as much detail as

possible about each unit (e.g. dwelling unit) and system

funded by the grant.

Chapters 6, 7 and 8, respectively, contain a more indepth discussion of the GRANT, MASTER and MIS Files -- their

contents, data structures, and intended uses and users.

Once the proper file has been selected, appendices B

and C can be referenced for the data element names and value

codes needed to formulate an inquiry (i.e. a query) to MIRADS.

Users can then use commands described in this chapter to

initiate searches for specific solar data, sort the data,

perform computations, and finally, print the results.

This section covers the most commonly used MIRADS commands and their options. It is intended that the beginning

user review these commands and options to gain a basic

understanding of the commands and their formats, then proceed to section 4 - A SAMPLE MIRADS SESSION, which guides

the user through an actual MIRADS query session. The actual

query session will demonstrate command relationships not

apparent in section 3. All examples of command options

used in this section are shown in actual MIRADS terminal

sessions in appendix D.

13
Having gained access to the MIRADS program through the

sign-on procedure outlined in the previous chapter, a user

may begin to formulate commands which comprise the MIRADS

BASIC QUERY SET and which will result in the processing of

information according to his specific requirements. This

BASIC QUERY SET may consist of up to four different types

of commands.

a. a QUERY command, which identifies the data

elements which are to be selected;

b. a SORT command, which specifies the sequence in

which the data selected by the QUERY are to be

sorted

c. one or more COMPUT E commands which provide the

capability of performing calculations on data

elements extracted by the QUERY command; and

d. a PRINT command which directs the printing of the

results

The order of this BASIC QUERY SET is first QUERY , then

SORT , then COMPUTE , and last PRINT . The QUERY and PRINT commands are required in every query set, whereas the SORT and

COMPUTE commands are optional. The commands are edited and

verified for correctness by the MIRADS program as they are

transmitted

Some of the major options available to operators using

MIRADS include the ability to review and edit commands which

have been formulated but not yet processed; the ability to

store a basic query set or a fragment thereof for later processing and/or editing; the ability to print locally (at the

terminal being used) or remotely (at a high-speed printer in

the computer facility) ; and the ability to interrupt or

suppress printing altogether.

3.2 The Query Command

Command + Data + Rela- + Criterion + Connector

Identifier Element tional (or

Name "Value")

Select all records with the specified field

(ENDSALEPRICE) present.

>Q ENDSALEPRICE P

(See appendix D, example 1, for an actual terminal

session which uses this command.)

14
Command Identifier : command as a QUERY

a . The letter Q identifies the

b. Data Element Name ; The computer name for the piece

of data about which inquiry is being made. Valid

Data Element Names are contained in the Solar

Data Diet ionary /Directory in appendix B.

c. Relational : This element instructs the computer how

the selection of records is to be made with regard

to the Data Element Name entered. A simple QUERY

might request the selection of all records with the

specified Data Element Name present (P) (i.e. a Data Element Name would be present if it was not

equal to spaces), while another might request

selection of those with the specified Data Element

Name not present (NP) (i.e. a data element name

would not be present if it was equal to spaces).

Other relationals are used to indicate the relationship of the general field named to a specific qualitative or quantitative value (or

criterion) which will be named. MIRADS relationals include:

P or PRESENT - Data Element Name present (not

equal to spaces)

NP or NOT PRESENT - Data Element Name not present

(equal to spaces)

EQ or = or EQUAL - Data Element Name value equal

to Criterion

GE or > or GREATER - Data Element Name value

Greater than Criterion

GE or GREATER-EQUAL - Data Element Name value

greater than or equal to

Criterion

LT or < or LESS - Data Element Name value less

than Criterion

LE or LESS-EQUAL - Data Element Name value ' greater than or equal to

Criterion

NE or UNEQUAL - Data Element Name value not equal

to Criterion

d. Criterion : This element represents the value with

which Data Element Name will be compared. It is

manatory for all relationals except P (PRESENT) and

NP (NOT PRESENT). A Criterion element may contain up to 48 numeric or alphanumeric characters.

If the Criterion element represents a range of

possible values for a particular Data Element Name,

these values will be included in the Solar

15
Data Diet ionary /Directory in appendix B or in

appendix C if the range was too long to list in

appendix B, For example, for the Data Element Name

"NEWRET”, only two values are available: N (for

new) and R (for retrofit).

The user has the option to use alpha and numeric

qualifiers to compare against the Data Element

Name .

(1) Alpha ; If the general field is a city where

a solar project is located (PJCITY) , the

user would need to spell out the name of the

city for which he desired information. Thus:

>Q PJCITY EQ BALTIMORE

would result in the selection of records of

project(s) located in Baltimore. (See appendix D, example 2, for an actual session

which uses this command.)

(2) Numeric ; In a general category such as average collector area (COLSQFT-G) , the user

might designate the specific size range desired. He would enter Data Element Name plus

Relational plus square footage in numeric

terms . Thus

>Q COLSQFT-G GE 10000

would result in the selection of records

which refer to buildings with an average

collector area equal to or greater than

10,000 square feet. See appendix D, example

3, for an actual terminal session which uses

this command .

In some cases a Criterion may be another Data

Element Name such as in the query:

>Q CFIN-YM = *MTGAPP AND GT 0

In such an instance, the selection of records is

based on a comparison of two Data Element Names

where the second Data Element Name must be preceded by an asterisk (*) because it does not

represent a data value. (See appendix D,

example 4, for an actual terminal session which

uses this command.)

16
e. Connectors : A Connector is used for joining together simple queries to form more complex queries.

More than one Connector may be used in a query.

Two Connectors are available for use:

(1) AND is used when the operator desires to

be more selective; that is, he requires

that more than one Criterion be met in

order for a record to be selected. For example :

>Q PJSTATE EQ VA AND COLSQFT-G GT 500 AND

LT 10000

specifies the selection of only those records

which indicate units built in Virginia with

an average collector area greater than 500

and less than 10,000 square feet. (See appendix D, example 5, for an actual terminal

session which uses this command.)

(2) 0^ is used when the operator wishes to be expansive; that is, when he will accept records

meeting either (or any) of the criteria

named

3.3 The Sort Command

The SORT command consists of the following elements:

Command Identifier + Data Element + Order of Sort

Name

a. Command Identifier : The letter "S” identifies

the command as a SORT command.

b. Data Element Name: The computer name as shown in

the Solar Data Die tionary /Directory , appendix B

(or $New-Var iable if the SORT command follows a COMPUTE command) which is to be used as a key

to sort the records selected by the QUERY.

c . Order of Sort :

A (ASCENDING) - The SORT command uses the

standard sorting sequence commonly referred to

as the commercial sequence. This sort sequence

is as follows: @, [, ], #, A, space, A through

Z, ), +, <, =, >, &, $, *, (, %, ?, !,

comma, 0 through 9, quote, ;, /, .,H,

17
D (DESCENDING) - This option causes the

sorting sequence to be reversed.

(NOTE: If no option is specified, this element

will default to A.

)

The SORT command is optional and may be omitted; however, if it is used, is should follow the QUERY command

and/or COMPUTE command. It must follow the COMPUTE command

if a $New-Var iable is to be used.

To sort average selling prices in descending order,

enter

>S ENDSALEPRICE D

(See appendix D, example 6, for an actual terminal

session which uses this command.)

Compound SORT commands are possible, for example in:

>S CYCLE A PJNO D

the user requests that records selected be printed

first, by CYCLE in ascending order and second, by project

number (PJNO) in descending order. The project number

(PJNO) will be sorted within each CYCLE number. (See

appendix D, example 7, for an actual terminal session

which uses this command.)

3.4 The COMPUTE Command

Command + BreakIdentifier Field

+ $New +

Variable

Equal + Calcu- + Period

Sign latlon

Request

Compute after all records have been processed, the

sum of all average selling prices.

>C NONE $TOTPRICE = SUM ENDSALEPRICE.

(See appendix D, example 8, for an actual terminal

session which uses this command.)

a. Command Identifier : The letter "C" identifies

the command as a COMPUTE command.

18
b. Break-Field : This element directs when the $NewVariable is to be printed and its computed value

reset to zero. Three options are available'.

(1) ALL directs the COMPUTE module to report the

specified calculation for each record selected by the QUERY. For example, in:

>C ALL $TOTPRICE SUM ENDSALEPRICE

.

the $TOTPRICE is listed for each record selected. (See appendix D, example 9, for an

actual terminal session which uses this

command .

)

(2) NONE directs that the specified calculation

be reported after all selected records have

been processed.

(3) NAME specifies the Data Element Name which

is to be used to direct the COMPUTE module to

report the specified calculation and reset to

zero when the value of that field changes.

It is important to SORT the Data Elejient Name

selected to be the break-field before using

this option of the COMPUTE command (see appendix D, example 10). In the above example

using the "NONE" break-field, the total of

all average selling prices was requested.

That total could be broken down by CYCLE, for

example, by using the NAME option of the

Break-Field

>C CYCLE $T0TPRICE = SUM ENDSALEPRICE.

(See appendix D, example 10 for an actual

terminal session which uses this command.)

c. $New-Variable : The user establishes a reference

name for the results of the requested computation.

This name may consist of up to thirty (30)

characters and must be preceded by a dollar sign

($). A $New-Var iable must have no embedded blanks.

d. Equal Sign : The $New-Variable must be separated

from the Calculation Request element by an equal

sign (=).

19
Calculation Request : There are three categories

of calculation requests:

e .

(1) SUM requests a running total of Data Element

Name values.

(2) COUNT tallies the number of Data Element Name

occurences

(3) ALGEBRAIC EXPRESSIONS permit the performance

of addition, subtraction, multiplication and

division by entry of appropriate symbol;

Addition - (+)

Subtraction - (-)

Multiplication - (*)

Division - (/)

To compute the average selling price

($AVGPRICE) of a unit by dividing the total

price ($TOTPRICE) by the number of units

($CNTPRICE), both $TOTPRICE and $CNTPRICE

must be calculated prior to determining

$AVGPRICE. Enter:

>C NONE $AVGPRICE = $TOTPRICE/ $CNTPRICE

(See appendix D, example 11, for an actual

terminal session which uses this command.)

f . Period ; Each COMPUTE command must be terminated

by a period. A series of COMPUTE commands may

be used in a single basic query set, each producing a $New-Var iable which may then be used in

ensuing COMPUTE commands.

3.5 The PRINT Command

The PRINT command consists of the following elements:

Command Identifier + Output Limit + Data Element Names

or $New-Var iables

a. Command Identifier ; The letter "P" identifies

the command as a PRINT command.

20
b. Output Limit : This element indicates the number

of lines of printed output desired. If omitted,

the named categories of all selected records

will be printed. This element restricts data

base searching; the QUERY module will search

only until the specified number of records has

been selected. This permits the operator to

sample the results of his basic query set and to

make adjustments as necessary through the MIRADS

EDIT capability. Two options are available with

the Output Limit element:

(1) NUMBER ; The operator may specify any number

of output lines up to 999999, as in the following :

>P 10 PJSTATE PJNO CONST-YM ENDSALEPRICE

(See appendix D, example 12, for an actual

terminal session which uses this command.)

(2) SUM r Used in conjuction with the COMPUTE

command (see "NAME” option of Break-Field

element, page 19) the SUM option will suppress the printing of all selected records

except for the record at the time a $NewVariable is to be printed.

To print the results of a computation to

find the sum of all average selling prices

by cycle (this sum assigned $New-Var iable

name $T0TPRICE) , listing not each record

per cycle, but the total for each cycle,

enter

>P SUM CYCLE $CNTPRICE $T0TPRICE

(See appendix D, example 13, for an actual

terminal session which uses this command.)

c. Data Element Names or $New-Var iables ; This

element indicates which Data Element Names or

$New-Var iables are to be printed in the output

(e.g. PJSTATE, $T0TPRICE)

21
4 A SAMPLE MIRADS SESSION

4.1 Processing a Query

A Solar Data Base user has decided to solve the following problem through MIRADS:

What is the average selling price for solar demonstration project units selling over $50,000 whose

construction was completed in 1979?

Having signed onto the NBS computer as directed in

chapter 1, he activates the MIRADS program:

DATE: 012279 TIME: 112443

> @MIRADS,NB

By referring to the Solar Data Dictionary /Directory in appendix B, the user determines that the information necessary for solving the problem is contained

in the MIS (Management Information Summary) File. Thus,

he enters the MIS File qualif ier/ filename

ENTER QUALIFIER*FILENAME

> S0LAR*MIS

While the computer determines the availability of

the file, the user begins to formulate his query command.

He needs to access only those records which indicate the

average selling price (ENDSALEPRICE) of units whose construction was completed (CONST-YM) between January and December of 1979. From the MIS dictionary entry for CONST-YM

(page 72), the user knows this data element is four

numeric digits and is coded as YR MO. (For example,

January of 1980 would be coded as 8001.) The dictionary

entry for ENDSALEPRICE (page73), reveals that this data

element is coded in dollars ($) and the numeric length of

the data element is a maximum of seven positions. The user

has chosen a final sales price greater than $50,000 and

enters it in the query statement as ENDSALEPRICE > 50000.

It is important to note that in a numeric Criterion

(or value) element, no punctuation may be used. Dollar

signs ($) and commas are omitted, and there may be n^

embedded blanks.

22
When the computer is ready, the user enters the

QUERY command

READY

>Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

Next, the user instructs that the records which will

be selected by the QUERY command should be sorted by the

average final sales price, and that the most expensive

average prices should be listed first:

READY

>S ENDSALEPRICE D

Three separate mathematical functions will have to be

performed upon the records selected in order to obtain the

average price for all grants. Each of these functions

must be entered via a separate COMPUTE command.

First, compute with no breaks (that is, do it once at

the end of all processing) a total (which will be designated $T0TPRICE) equal to the sum of all sales prices in

the records selected:

READY

>C NONE $T0TPRICE = SUM ENDSALEPRICE.

IMPORTANT: It is important to remember

that a $New-Var iable (the user-selected

name for the result of a computation)

always be preceded by a dollar sign ($).

It may contain up to 35 characters and

must have no embedded blanks. Hyphens

may be used.

IMPORTANT: A period must be used at the

end of a COMPUTE command.

23
Second, compute with no breaks another total (this

one to be called $CNTPRICE) which is equal to the total

number of grants with average selling prices available;

READY

>C NONE $CNTPRICE = COUNT ENDSALEPRICE

.

Third, compute with no breaks, another total (to be

called $AVGPRICE) which is equal to the sum of average

selling prices ($TOTPRICE) divided by the number of

grants with average selling prices available ($CNTPRICE)

READY

>C NONE $AVGPRICE + $TOTPRICE / $CNTPRICE

.

When the COMPUTE commands have been entered, the user

must instruct the computer as to how the requested information should be displayed. He decides that the information

most useful for his purposes includes the project number

(PJNO) , construction completion date (CONST-YM) , and

average selling price (ENDSALEPRICE) , in addition to the

results of the computation requested:

READY

>P PJNO CONST-YM ENDSALEPRICE $TOTPRICE $CNTPRICE

$AVGPRICE

Because the user knows that he will also want to later

determine the average selling price for units selling over

$70,000, he elects to SAVE the query set he has just entered.

Thus, later, he can recall the query set, change the. average

selling price (ENDSALEPRICEX and process again without having to reformulate the entire query set. (See section 4.2

for more information on how to list all query set names,

display a query set, and edit a query set.) The query set is

saved by assigning a user-defined reference name to the

query set (in this case "AVGPRICE") and instructing the

computer simply:

24
READY

>SAVE AVGPRICE

The save query command, SAVE, stores the entire query

set from QUERY command to PRINT command In a special MIRADS

save file. The save fragment command, SAVEC , (discussed

later in section 4.3) operates identically to the SAVE command. The difference between the two commands is that SAVEC

can save a single command or several commands which make up

a partial query set. The SAVE command retains the entire

QUERY set for later execution while the SAVEC retains a command (or commands) for Insertion into a query set at a later

t ime

Now is the time to process the query set. The oneword system command "RUN" initiates processing, and there

is a pause while the computer selects the records requested :

READY

>RUN

QUERY NOW PROCESSING

When the records have been selected, the computer will

report the total number of records in the file and the

number of those records which meet the criteria indicated

by the user. At this point the user must decide if the

volume of the output warrants printing locally (on the

terminal he is using) or if it should be processed on a high-speed printer at another location:

FILE CONTAINS 678 RECORDS

QUERY SELECTED 8 RECORDS

ENTER OUTPUT SITE ID

> (CR)

Since there were so few records selected, the operator decides to print locally. He enters a carriage return (CR) , because local production is the default option.

Any other production site would have required a specific

25
entry, (i.e. the entry "PR" would request production on

the high speed, wide-car r iage printer at the NBS Central

Computer .

)

IMPORTANT; If the volume of output appears to be much more than the user

anticipated, or if for any reason he

decides not to print the results of a query set, he may enter the one-word

command "NONE" in response to the computer's "ENTER OUTPUT SITE ID" request.

He may also, at this point, specify that

he would like to see only the first N

(number) of lines printed by entering

the command "PRINT N" (substituting

for the letter N the specific number

of lines, e.g. PRINT 10). Since he

has saved the query set, he can later

amend this request.

When the output site ID has been entered, the computer

prints the basic query set followed by the requested output.

Example lA , page 129 is an actual computer session which reflects the sample session discussed in this section.

4.2 Editing and Processing a Saved Query Set

A Solar Data Base user wishes to recall a basic query

set which he has requested the MIRADS program to save under

a name which was designated at the time the set was entered.

To be certain that the name of the saved query set is entered exactly as it was originally specified, the user first

instructs the program to list all saved query set names:

READY

>LIST

AVGPRICE STANDARD

IMPORTANT: The last query set executed

is always saved under the unique name

,

STANDARD. It is always Included in the

list of saved query set names unless

previously deleted.

The saved query set name he needs is "AVGPRICE". If

he wished simply to process this query as it was originally

26
AVGPRICE". However, fo

needs to amend the orlg

review the query set as

DISPLAY command is then

listing of the commands

Tet. AVGPRICE:

is pol n t enter th

r purp os es of t hi

inal q ue ry . He f

it wa s en tered 0

used to g ener a t e conta Ined with in

command "DO

example, the user

rst may want to

Iglnally. The

a line-by-line

his saved query

READY

>DISPLAY AVGPRICE

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

S ENDSALEPRICE D

C NONE $T0TPRICE = SUM ENDSALEPRICE.

C NONE $CNTPRICE = COUNT ENDSALEPRICE.

C NONE $AVGPRICE = $TOTPRICE/ $CNTPRICE

.

P PJNO CONST-YM ENDSALEPRICE $T0TPRICE $CNTPRICE

$AVGPRICE

In order to change

command .is entered:

the original query set. the EDIT

READY

>EDIT AVGPRICE (or ED AVGPRICE)

At this point, the user must specify the editor functions which will result in the modifications he desires:

There are three main functions:

a. Positioning

b . Editing

c. Exit

The user must first position

where a modification is to be made

of three ways: (1) by beginning a and advancing line by line; (2) by

line number if it is known; or (3)

cific element which is to be modif

editor will search and position it

found to contain that element.

In the present example, the user elects to position

the editor at the TOP ("T") of the query (that is, one

line) to begin his positioning sequence:

27

the editor at the point

. He may do this in one

t the top of the query

advancing to a specific

by indicating the speled, in which case the

self at the first line
ENTER EDIT COMMAND

>T

000 :

Next, by referring to the displayed saved query set,

the user selects the line containing the element to be

amended. He may position the editor at that line by entering one of the following commands:

N

Positions the editor at the beginning of the

NEXT LINE.

n Specifies the line number at which the editor

should be positioned. For example, if the value

of "n" is 2, the editor will be positioned at

line 2.

N n Advances the editor "n" lines below the present

line. For example, if the editor is at line 3

and line 5 is desired, the command "N 2" should be

entered

N - n Specifies that the editor will be positioned "n"

lines above the present position. For example,

if the present line is 3 and "n - 1” is entered,

the editor will then be positioned at line number

2 .

L (for "LOCATE") "ELEMENT-NAME " Causes the editor to search each line for a value matching the element name entered (up to

82 alphanumeric characters enclosed in quotation

marks) beginning with the line at which the editor is positioned. Lines below that point will

be searched, but not lines above.

The user, wishing to amend the first line of the saved

query set in the present example, may position the editor

either by entering the numeral "1" (since the line number

is obvious); or he may enter the letter "N" for NEXT (since

the editor is presently positioned at "TOP"), one line above

the first line:

28
READY

>N

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

001 : With the editor properly positioned,

ready to enter specific editing commands,

types of modifications which may be made:

and DELETE.

the user is now

There are three

CHANGE, INSERT,

CHANGE commands include:

C /QLD-VALUE/NEW-VALUE/

Replaces old value with new value for the first

occurence of old value on the line indicated.

C /OLD-VALUE/NEW-VALUE/ALL

Replaces old value with new value for each occurrence of old value on specified line and every

line thereafter.

The INSERT command is:

I INSERT-LINE

The new line will be inserted immediately after

the line at which the editor is positioned. It

may contain up to 82 characters and must be

separated from the "I" by one space.

The DELETE Command is:

D

This causes the line at which the editor is

positioned to be deleted and the editor repositioned at the line immediately preceding the deleted line. The line at which the editor is

repositioned will print out.

In this example, the user wishes to CHANGE the original

QUERY command by increasing the "VALUE" element from 50000

to 70000 . Thus

READY

>C 750000/70000/

29
In order that the user may check that the change entered agrees with his intention, the computer automatically

prints the line just edited. The user may request that any

line or lines be printed. He must first position the editor

as previously instructed to the line at which he wishes to

begin. He then enters "P** to print that one line; or he may

enter "P n” , assigning "n" to value of the number of lines

of print desired, (e.g. "P 5" would result in the printing of

f ive lines )

The user must EXIT from the EDIT program before the

amended saved query set can be processed:

READY

> EXIT

The command "DO SAVED-QUERY-SET-NAME" initiates processing. The saved query set (as amended) is printed

following the MIRADS request for the user to designate

the output site.

4.3 Saved Fragments

If the user desires to save only a fragment of his

query set to use at a later time, he may do so by creating

a reference name (e.g. PRICERANGE) and entering the save

fragment command, SAVEC , after his query statement. The

reference name will be stored in the saved query file with

other saved query set names and saved fragment names which

can then be LISTed, DISPLAYed , and EDITed by the user.

Fragment names nay contain from one to twelve alphanumeric

characters (A - Z, 0-9 plus the hyphen character).

READY

>Q C0N3T-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

READY

>SAVEC PRICERANGE

Since the SAVEC command immediately follows the QUERY

command, only that portion of the query set is saved. If

the SAVEC command had followed a SORT command, both the

QUERY command and the SORT command would have been saved.

30
The saved fragment may be inserted into a new query

set by the command "ADD SAVED-FRAGMENT-NAME" . Because the

saved fragment in this example contains a QUERY command, it

must be "added" prior to any other command. Thus:

READY

>ADD PRICERANGE

READY

>S ENDSALEPRICE

READY

>P PJNO PJSTATE ENDSALEPRICE CONST-YM

An important feature of the saved fragment capability

is the facility for adding to the saved fragment when it is

open ended - that is, when there is no period at the end of

the original command. For example, the QUERY command:

"Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000"

might be altered, when added to a new query set, to reflect

the results of selection of grants whose average selling

price of units is less than or equal to $95,000 as shown below :

READY

>ADD PRICERANGE

READY

>AND LE 95000

READY

>S ENDSALEPRICE D

READY

>P PJNO PJSTATE ENDSALEPRICE CONST-YM

Fragments may be saved and recalled other than during

the formation of an entire query set. For example, a report format may be designed and a complicated PRINT command entered and saved independent of other commands. All

31
that is required is;

a. that the user position himself at the TOP of the

"workspace" by entering the one-word system

command "TOP";

b. that the command be entered in accordance with

all rules for entering the same command in a normal query set; and

c. that a SAVEC SAVED-FRAGMENT-NAME be entered

immediately following the last line of commands

which are to be saved. All the commands entered

since the user positioned himself at the TOP of

the workspace will be saved.

Other

elude

:

a

.

b.

special rules which app

All COMPUTE commands mus

If the saved fragment co

COMPUTE commands, and mo

quired, then new COMPUTE

immediately preceding th

mediately following the

to the logic of the over

One and only one QUERY c one PRINT command can be

If a saved query fragmen

a new query set contains

no other QUERY or PRINT

ly to s aved fra gmen t s int be gr ouped to g e th er

nsists of one o r mo re

re comp utations are r n- comman ds must b e en t er ed

e added fragmen t , o r imadded f ragment

,

acc or ding

all que ry set

.

ommand

,

and one and o nly

presen t in any que ry set.

t which is to b e adde d in

a QUERY or PRINT c ommand

,

command may be used.

c. As was previously noted, MIRADS commands are held

in a "workspace" until an execute command (RUN

or DO) is entered. It is important for the user

to remember that this workspace should be

cleared - that is, the user should position himself at the beginning or TOP of this workspace

prior to formulating a new query set which will

include a saved fragment. This is done simply by

entering the system command "TOP".

d. To DELETE a saved fragment enter "DELETE [saved

fragment name]".

e. To DISPLAY a saved fragment enter "DISPLAY [saved

fragment name]".

32
5 . THINGS TO REMEMBER ABOUT USING MIRADS

1. The section on MIRADS commands discusses only those

frequently used command elements. More sophisticated

command construction is contained in the MIRADS User's

Manual . [ 1

2. Command statements which cannot be contained on one

line may be continued on the following line beginning

in any position.

3. Elements such as Data Element Names, Relatlonals,

Criteria, Negations, and Connectors cannot be broken

and continued on the following line.

4. A comma or any number of spaces must separate the

elements which comprise a command.

5. A COMPUTE command MUST end with a period.

6. When designating names for Saved-Query-Sets or for

Saved-Fragmen t s (up to 12 alphanumeric characters including hyphen character) , it is wise to individualize

entries with the user's initials or department code,

etc. When asked to LIST, the system will print not

only the present user's but all saved names. SavedQuery-Set names and Saved-Fr agment names are all

listed for each LIST request. Without a naming convention, it can be difficult to tell them apart. Therefore, it may also be wise to differ the individual

code for names in each category.

EXAMPLE: John Smith saves a query set regarding system

type under the name JS-Q-SYSTYPE (^John ^mith,

Saved-^uery-Set - SYSTYPE) . He also saves a fragment of that query under the name:

JS-F-SYSTYPE (^ohn ^mith, Saved-]Fragment - SYSTYPE)

7. A user may recall and edit his query set under the name

STANDARD if he had not saved it previously. The query

set may be edited according to the EDIT procedures outlined in section 4.2. The command "EDIT STANDARD"

should be used. The present query set is saved under

STANDARD until another query set is executed using the

RUN or DO commands.

33
6 . USING MIRADS WITH THE GRANT FILE

The GRANT File is one of the six computer files comprising the HUD Residential Solar Data Base. Figure 1 on

page 2 shows this file in relation to the other files of

the data base. For more background on the GRANT File and

its contents, see references [4 and 5].

There are four reasons why the GRANT File is available with MIRADS: (1) its completeness -- all data which

were to be collected, have been collected; (2) its quality -- the data is kept up-to-date by frequent updates as the

status of the grant changes; (3) its scope -- each grant

awarded by HUD has a corresponding entry on the GRANT File;

(4) its generality -- the most frequently questioned data

concerning a grant, unit, system or building are contained

on the GRANT File.

In order to use MIRADS with the GRANT File, the

structure of the grant data must be understood. Grants

were awarded to builders of homes. A typical grant might

include 5 single-family, detached units, each with its own

solar system. The homes are all in the same subdivision.

The separate units can usually be grouped according to

their size; 3 units may have 2000 sq. ft. of livable space

and 2 units may have 2500 sq. ft. of livable space, as shown below in figure 2.

Figure 2: Typical Residential Solar Grant

34
The way these data are structured for computer storage

as the GRANT File is shown below in figure 3.

Figure 3: Tree Diagram of Typical Grant

For a hypothetical grant number H-0000, two model types

are shown: model # 1 describes units 1, 2, and 3; model // 2

describes units 4 and 5. For each model, one system type is

described. (More than one system type will occur for the

same model when, for example, there is an active and a passive system for that model.) The system types shown in

figure 3 may be alike for the five units (i.e., all active

systems furnishing heat with flat plate, water collectors

made by Solaron) , but usually they are sized differently due

to the difference in model sizes. At any rate, because

there are two models, there have to be two system descriptions. There is no provision in this computer file

structure to allow a common system description.

There is one additional level to the GRANT File

structure which occurs infrequently. It is best illustrated, as in figure 4.

35
Figure 4: Tree Diagram of Grant with Multiple Locations

The new level is called the "location" or "project

location" level. It occurs only for grants where the

building projects are not in the same subdivisions, but

are in different locations: across town, across the state,

or even in different states.

The data elements (described in appendix B) which are

accessible with MIRADS, are each associated with a level

of the tree shown in figures 3 and 4. Appendix B is

annotated to show the level (grant, location, model or

system) for each of data elements. Figure 5 shows some of

the GRANT File data elements and typical values, broken

down at each level. It also shows in the right-hand column

the actual data element name and value that might occur for

this grant.

36
Levels of Data

Description of Some

Data Elements

Grant Grant number Is H-0000

Cycle Is 5

Model

Iff 1 Living area Is 2000 sq.

Housing type Is singlefamily, detached

Number of systems Is 3

Number of units Is 3

ft

Data Element

Name s/Values

PJNO»0000

CYCLE-5

SySHEATAREA=2UUU

HSGTYPE-SFD

PJSYS-3

PJUNITS-3

System*

# 1 Kind of system Is active

Transfer medium Is water

Size of collector Is 370

sq . ft*

SYSKINb-A

SYSTRMED-W

COLSQFT-370

Model

// 2 Living area Is 2500 sq. ft.

Housing type Is singlefamily, detached

Number of systems Is 2

Number of units Is 2

SYSHEATAREA-250U

HSGTYPE-SFD

PJSYS-2

PJUNITS-2

System

// 1 Kind of system Is active

Transfer medium Is water

Size of collector Is 560

sq . ft.

SYSKIND-A

SYSTRMED-W

COLSOFT-560

*Systems are numbered consecutively within models.

Figure 5: Some GRANT File Data Elements Shown at Different

Levels

37
It should now be easy to understand the results of a MIRADS query to the GRANT File. For example, the statements :

Q SYSTRMED=W AND PJNO“0000

P CYCLE SYSKIND HSGTYPE COLSQFT

would print

CYCLE SYSKIND HSGTYPE COLSQFT

5 A SFD 370

5 A SFD 560

Since the query criteria contained a request for a data element from the system level, all non-system data

would be repeated.

You can, if you prefer, request the location number

(PJLOCNO) , model number (MODSEQ) , and system number

(SYSNO) to be printed. If the PRINT command above were

modified to :

P PJLOCNO MODSEQ SYSNO CYCLE SYSKIND HSGTYPE COLSQFT

the following would print:

PJLOCNO MODSEQ SYSNO CYCLE SYSKIND HSGTYPE COLSQFT

1 1 1 5 A SFD 370

1 2 1 5 A SFD 560

The GRANT File

ment tool but is als

lookfor example , f

systems which HUD ha

last three ye ar s . S

of the use of the th

is used not only a

o valuable to rese

or trends in types

s awarded grants t ee chapter 9 for a ree solar MIRADS f

s a project

archers who

and kinds

o build ove

comparat iv

iles .

managemigh t of solar

r the

e analysis

38
7. USING MIRADS WITH THE MASTER FILE

The MASTER File Is a concatenation of the GRANT, Technl

cal Description, Grantee (Reports 1, 3 and 4), Technical

Concerns, and Utility Consumption files of the Solar Data

Base^*^ (see figure 1 on page 2). Designator data are also In

eluded In the MASTER File. These are a special set of data

which "map" the GRANT File structure to the data structure

In the other solar files. More Information on these individual files and their contents is contained in references

[ 4 and 5 ]

.

There are two reasons why the MASTER File was created:

(1) to link all files so queries across files could be

made: and (2) to give the researcher a tool for counting

"things" relating to units (i.e., dwelling units — houses

or apartments) and systems. The file structure necessary

to do this required the data to be expanded so that all

data elements relating to units and systems of a grant

would be accessible. Figure 6 shows the MASTER File tree

structure for the same grant referenced in chapter 6.

Figure 6: Tree Diagram of MASTER File Representation of Typical Grant

Instead of grouping similar units Into models, one

branch (equivalent to a computer record) exists for each

unit

.

*Marketing Survey data, which contains 2500 separate data

elements for each unit of a grant surveyed, was considered

too voluminous to include in the MASTER File -- these data

are rarely looked at item-by-ltem but are analyzed statistically as "sets" of "like items."

39
In the case where there are more systems than units

in a grant (about 5 percent of all grants), there would be

one computer record corresponding to each system , as shown

in fieure 7.

Figure 7: Tree Diagram of MASTER File

Representation of Grant with

More Systems Than Units

Unit # 1 has two systems, usually one active and one

passive. In the computer representation, the data elements

for unit // 1 would be repeated for systems // 1 and # 2.

In order to use MIRADS with the MASTER File, the

structure of tl^e resulting combined file must be understood.

This is a file expanded to its greatest level of detail

(usually, the individual units of the grant). Although a great deal of repetition was caused in that expansion, the

resulting structure is simple. For example, if you query

for all "hot water" systems in "Maryland," you can print

everything that exists in the data base for each unit

in Maryland that has such a system.

The researcher typically uses MIRADS with this file for

one of the following reasons: (1) to save the "subset" of

the original MASTER File which was selected when the query

was executed* for later processing on the computer with

another program; or (2) to count, sum, and make other calculations on individual data elements.

The repetition which benefits the researcher accounts

for the MASTER File's size -- approximately 3 million bytes

(characters) of storage, 10 times larger than either the

GRANT File or the MIS File. Because of its size and repetitious format, the MASTER File is rarely accessed by the

casual user.

*This is accomplished by using the "DRUM=fn" statement in

response to the "ENTER OUTPUT SITE ID" message (see page 47).

40
8. USING MIRADS WITH THE MANAGEMENT INFORMATION

SUMMARY (MIS) FILE

The Management Information Summary (MIS) File is a concatenation of data from five individual solar files which

have been summarized to the grant level. The five files

used to construct the MIS File are: GRANT, Grantee, Technical Concerns, Utility Consumption, and Market Survey* (see

figure 1 on page 2).** Designator data are also included in

the MIS File. These are a special set of data which "map"

the GRANT File structure to the data structure in the other

solar files. More information on these individual files and

their contents is contained in references [4 and 5].

In order to use MIRADS with the MIS FILE, the way the

file was created must be understood. The data were all

summarized to the grant level, using one of the following

five rules; (1) average -- numeric data element values for

individual units or systems of a grant were averaged; (2)

e qual value -- if data element values for individual units

or systems of a grant were equal, they were used; if unequal, "*" was used; (3) earliest -- the chronologically

earliest data associated with a data element for individual

units or systems of a grant was used; (4) comb Ine -- data

element values for individual units or systems of a grant

were combined (i.e., value A and value B became value AB)

and (5) total -- numeric data element values for individual

units or systems of a grant were summed together.

*The data elements themselves were not summarized for the

Market Survey File, but the availability of data (a count

of market ques t ionnar ies ) for each grant was used in the

MIS File.

**Technical Description data are not currently included in

the MIS File.

41
Table 1 below lists the five summary rules and the MIS

data elements to which they were applied.

SUMMARY RULES MIS DATA ELEMENTS

(1) average Utility Consumption numeric

data, ENDSALEPRICE

.

(2) equal value All data elements in MIS

Directory (appendix B) which

can have a value of

(3) earliest All dates from the Grantee file.

(4) comb ine All problem codes from the

Grantee File, SYSTYPE-G.

(5) total Marketing Survey data. Technical Concerns data, SYSHEATAREA,

COLSQFT-G, MODMBTU-G, SYSMBTU-G.

Table 1

Some data elements from the GRANT File are already at

the grant level (such as grant award amount) and, therefore, not referenced in table 1.

The MIS File was created for one reason: to give all

Solar Data Base users the ability to access the whole

data base at once and produce short, summary query results.

The MIS tree structure corresponding to the GRANT and

MASTER structures (see figs. 3 and 6) is shown in figure 8.

Figure 8: Tree Diagram of MIS File Representation

of Typical Grant

42
The MIS File is easy to use and the results are easy

to understand. The MIS user needs only to keep in mind the

summary rules used for creating the file and that all data

elements of the MIS File represent grant level data.

43
9. A COMPARATIVE ANALYSIS OF THE USE OF MIRADS WITH THE

DIFFERENT SOLAR FILES

The previous three chapters described the use of MIRADS

with the three solar interactive files: GRANT, MASTER and

MIS . Deciding which of these files to use to answer questions is sometimes straightforward -- the data elements from

the Technical Description file only occur in the MASTER interactive file -- but is frequently not straightforward.

For example, the data element SYSTYPE, describing the type

(heating, cooling, or domestic hot water) of solar system,

occurs in all three interactive files. Approximately 30

percent of all data elements occur in all three interactive

files. In many cases, however, the data element in the MIS

file has been summarized to the grant level and its original

value may have been lost.

One reason for choosing one solar interactive file over

another for a query may be Influenced by the level of data

in each of the three files. GRANT File data are at various

levels: grant, project location, model, and system; MASTER

File data are at unit and system level; and MIS File data

are at grant level.

Other reasons for choosing one solar interactive file

over another are shown in table 2. This table shows which

of the three interactive MIRADS files are "best" and which

are "worst" when viewed as to their usage characteritlcs

,

i.e., time required for computer to respond, level of detail

in the query results, the range of data elements the user

can choose from, ease of use of the query results, length of

query results generated, and the completeness of the data

values

.

A4
USAGE CHARACTERISTICS INTERACTIVE SOLAR FILES

GRANT MASTER MIS

RESPONSE TIME 2 3 1

LEVEL OF DETAIL 2 1 3

RANGE OF DATA AVAILABLE 2 1 3

EASE OF USE 2 3 1 AMOUNT OF OUTPUT GENERATED 2 3 1 COMPLETENESS OF DATA 1 2 3

1 2 3

1 1 1 BEST WORST

Table 2

45
APPENDIX A

MIRADS LANGUAGE SUMMARY

COMMAND EXAMPLE DESCRIPTION

BASIC QUERY SET

Q (QUERY) Q PJSTATE -= "DC" or "VA" Requests search

for records of

projects located

in Washington,

D . C . or in

Virginia.

S (SORT) S PJSTATE, GRNO Requests that

selected records

be sorted first

by location and

then by identication number in

ascending sequence.

C (COMPUTE) C NONE GRAWARD » SUM. Requests a running total of

grant amounts

for pro j ect

selected in

initial query.

P (PRINT) P PJSTATE, GRNO, PJCITY,

GRAWARD

Requests the

printing of

fields identified along with

appropriate

headings

SYSTEM COMMANDS

RUN RUN Begin processing

query set just

entered

CHECK CHECK List statements

entered in curr ent query set

46
APPENDIX A

MIRADS LANGUAGE SUMMARY (Continued)

COMMAND EXAMPLE DESCRIPTION

SYSTEM COMMANDS (Continued)

TOP TOP Erase current

query set and

begin again.

NEW NEW Switch to

another file

(System will re

spond: "ENTER

QUALIFIER*FILENAME")

TO CONTROL PRINTING DRUM=fn Results written

OF QUERY RESULTS to mass storage

file f n

.

NONE Do not print

results

.

PRINT N Print only N

lines of results . (CR) Print all results at terminal . PR Print all results at printer in computer

room

.

SAVED QUERY SET

SAVE SAVED-QUERY-SET-NAME SAVE AVGRATE User creates

reference name

for query set

just entered

and instructs

system to save

and recall it

upon demand

.

LIST LIST One-word command requesting

list of all

saved query set

names

.
APPENDIX A

MIRADS LANGUAGE SUMMARY (Continued)

COMMAND EXAMPLE DESCRIPTION

SAVED QUERY SET (Continued)

DO SAVED QUERY-SET-NAME DO AVGRATE Recalls specified saved

query set and

causes it to be

executed

.

DISPLAY SAVED-QUERY-SET-NAME DISPLAY

AVGRATE

Prints specifified saved

query set.

DELETE SAVED-QUERY-SET-NAME DELETE

AVGRATE

Deletes saved

query set from

the system.

SAVED FRAGMENTS

SAVEC SAVED-FRAGMENT-NAME SAVEC

PRICERANGE

User creates

reference name

for portion of

query set just

entered and instructs computer to save

and recall it

upon demand.

ADD SAVED-FRAGMENT-NAME ADD

PRICERANGE

Causes the frag

ment previously

formulated to

be recalled and

inserted at

this point in

the entry of a new query set.

48
APPENDIX A

MIRADS LANGUAGE SUMMARY (Continued)

COMMAND EXAMPLE DESCRIPTION

EDIT COMMANDS

EDIT (or ED) ED AVGRATE Invokes EDITOR

SAVED-QUERY-SET-NAME (or ED STANDARD) mode which per-

(or ED STANDARD) mits alternation of current

query set (in

STANDARD) or of

saved query set

T (TOP) T To locate

editor above

top line of

query set

.

N N Positions editor below present position.

N n N 3 Positions editor three lines

below present

position

.

N - n N - 2 Subtracts two

lines from

present position.

n 2 Positions editor on line 2.

L (LOCATE) "Value" L "OR MD" Causes editor

to search for

and to advance

to first line

found to contain value

"OR MD".

49
APPENDIX A

MIRADS LANGUAGE SUMMARY (Continued)

COMMAND EXAMPLE DESCRIPTION

EDIT COMMANDS (Continued)

C (CHANGE) /FROM/TO/ C /OR MD/ /

or C /OR MD/ /ALL

Change

value

to new

t

from old

"OR MD"

value

t (blank)

on the line

where presently

positioned

.

"ALL" option

requests same

change from

present position throughout

remaining lines .

I (INSERT) ADDITIONAL

ELEMENTS

I AND GRAWARD

GT 30000

Inserts a new

line "AND

GRAWARD

GT 30000"

immediately

following present position of

editor

.

D (DELETE D Commands the

deletion of the

line at which

the editor has

been positioned

Line above will

print out

.

P (PRINT) n P 5 Causes the

present line

and next four

lines to print

for user review

P ! P ! Causes all

lines in query

set to print

.

50
APPENDIX A

MIRADS LANGUAGE SUMMARY (Continued)

COMMAND EXAMPLE DESCRIPTION

OTHER COMMANDS

CTRL/X Cancels an

entire line.

CTRL/Z Cancels an individual character . EXIT EXIT Terminates the

editor and rewrites the

query set with

all changes

51
APPENDIX B

SOLAR DATA DICTIONARY/DIRECTORY

Introduction

Appendix B contains a directory for each interactive

solar file available with MIRADS: the GRANT, MASTERaand MIS

These directories give the data element name which is needed by a MIRADS user to reference the data along with several attributes (descriptive items) about the data element,

such as its size, data type (numeric or alphabetic), and

the codes/values it can have. One important attribute missing in this version of the data dictionary/directory is a definition of the data element. Another publication [6]

currently being revised into a final draft will contain

complete definitions.

The following is an explanation of the columns of information which are in these directories:

NUM : An "X" in this column means the data element being described is numeric and will

always have a numeric value of zero or

greater. A number after the "X" shows the

number of places from the right the decimal

is assumed to be. A blank in this column

means the data element is alphabetic and

will always contain blanks or numbers

and/ or letters

DATA LENGTH:

DATA ELEMENT

DESCRIPTION:

DATA ELEMENT

MIRADS NAME:

The length in characters (letters, numbers

or blanks) of the data element being deer ibed .

A brief description of the data element.

The name used to reference this data e ment in a MIRADS QUERY, SORT, COMPUTE,

PRINT statement. (Note that the data

element itself is a value stored on th

computer. This is the official name

which can retrieve that value.)

leor

e

UNITS

When appropriate, the terms of measure by

which the data element is recorded.

52
CODES/VALUES; Codes and their interpretations (or values)

for those data elements which are coded.

In cases where lists of codes and values

are long (half a page or more), a reference

is made here to appendix C where the complete list is shown.
APPEIfDIX

B

SOLAR

DATA

DICTIORART/DI

H eE 5< b;

00 1 u 8 S’"oo Wh 2 h

^| 5 SP"P» qS^ 0uM^<

iiiiiSii

U H U II U II U U nU^KD^JlidO

'I

I

!

i

eI

ig „ QHU

Sl^«o* 3

g

~

0.UQQU 0DNb<OUUU|agS

Q0QQO9(BQ0QDQ0Qgan(B(»S»» HHUSaUHUUUUH PD eoeooaoooaowan

• » 0 «Na«NCI«K»N 0 -<

»< »<

„ ^ ^ a a- u a a?<HHH 2

atataiatet*a*e^aitsieTidaiataiaiai mShuhuhuuuumuuuh

9333939999339233

DDDDDdPDD&PDDDDP AfiQAflatQCQPQSIOSCQCQaQfiQeQeQflQ ^e99s6«C|v»MlA>6NNCI^IdN

XX X

54
II II II II II II II

H

11 II

sPgSS

^ a B A n II II eg'

b!

i

N Cl Cl C4 » A

jSucn^uiE CRKU>^U fiuSeuiE

t-<Jpu

®

;ISg2g2g2§2g

S U CD CD QQ 09 QD CD

55

ei

SYSTEM

KIND

SYSKIND

A

=

ACTIVE

P

=

PASSIVE
I

1

I!M

g ggg CD QDQQQQ g gs^ 09 QDfiU

»<>«»<»< !X>i»<

56
£ i

•• go r

5 B 5 bH

g PL, g <400 e 2 e

u H uu R m MheRRMhonDRe k5\gHkgSaQOS

SShrrSSh^h]^ 0.oeS4B.O>-<i.J4R

I ^ BpM I ^ U4Ug

b Ji

LE

FAN

ATTACH

LE

FAN

DETACH

LE

HONE

EH

LOHRISE

1-FAN

NIDRISE

I-FAN

HIRISE

R

RRgS J jg SqqeSs&o

H II II II .11 II II

SFA 8FD

HOB GAL NFH NFH OTH R Si

PM

E

II

UU

1-l.J QkB. s «-

C9 9

ggH40,44B ili

«H — bRPu

SSSSSSSSm^BUU

^ s

4CUF

SSS

Spsrf «Pp4 I oooH «;»

B. S

P

Si

a. o

!3^^<3^3 GOOD uuun

99 '•ciseciieN( 9 ^ ^ ^ O 9 <

fcil fe

-QOUUOQN ^ G

H H H H H R

§22S22o

1222223

S § § 2 R D

• cuoua.sua.n •NC499Clien

> © CO ^ ® © ® CO ^0 ^0 ^0 ^0

ssa. On

GO OO

9 9

57
uooBB

HH.J

© . M 00 < 0. si I

< J

ua. B QO Oue

B B

eo

HH

ii0. a.

QQ QQ OO

-«

• «

1 a<a<a<Qoa<GDQEiQBiB

S2gS2

OSQSCD IB (BAU

»<X

© © © © ©

>!!X

58
APPENDIX

B

SOLAR

DATA

DICTIORARY/DIREGTORT

MASTER

FILE

-

GRANT

DATA

<

10

I

U 0M

II si

UB

siUS gg§2

gi oasS2S2g2g

QB<BOaU

I Bk

I ^

QO

gg

I

oaM

e I"

s”Joa g

u S

^2

t-U Pk N N

« «

P oa

oa

oa

on M

Oglik

uoac

«Bi& o o

fa fa

oamn oco

iiii BkODkU

NNNC)

o o o o

59
s

II II mcd

II IIII n

~ U

BO.

i

«\ed ^99

H

i

§

u

HM

g

I

J edB<

u

§

UUOONHU HHHHP

ggggP

iiiii

cu(Lia.Puu

d ««died *(

60

06

COnSTRUCTIOR

FIIIARCIRC

PBDB

CFIRPROB

SEE

APPERDIX

C
^ i

^ §

i

“

u

p<

04

%!u

QO

u V a aBB

a

5!U

CO a

g

ga«2

II II g g

bso o Sj

9i^

II II II II II O M B D H

Bcna.B o

i

• K U H

e^Qfi

leiilii

^gj.9

gsE tsBBBA

Ip^pl, hhBBiBBiaL; BhBBdqe eeeee

papaoaeQooo oooonnn nnnnu

Ed gSptH iU

HHBB A O »

OObEi.

U WUU

E

li

IISS

SS'^EggSis^ » M K < Q ^ QOQOOABH^^Hra

ODODr* iiliiiiiii

©"•2pB<<a<

“""SSSiffH hhBOBoawggg

ooStB^^gp® ®

p,p,moB§oi

^UOButtOO

I pcdSpbbb

PS M BB M

|^qd«^qo 323

...!»§goO0PD

u o b. u a 03 u n pa n

^ ^ ^ ^ ^ ^ ^ ^ ^ ^

|eL|

®w® Na

EEEE^Il

gg|gg|l Tft-Pp

BB M BB BB aaaa^^ eeeeHH

J<a

^ ^ ^ ^ BB BB BB

I fU Cl< 0< Pb BU Pb ^ ^ ^ oo^ouuu

5*££§55

9993fefefe BB BB BB BB U 0^ gggssss

BBSEES BB BB BB apasesa SPSS

Cl « Cl a « 9>

a 'M a 9 © a 9

><><>•>• uuuuaaa

uuuuaaa

aaaaaaa C9 ^ ® 9 CO 9

sssss

aaaaa a ”< 9 9 9

<rQH

aua a M M

uu

§1

a a —( l-H Eb b

a a oo 4

Nee

T?EE uui»a

a a a a 0900 uuuo

a - 9 a

— » 9

b Eh

61
o

II II II li II II ^S^oSfiuO

I ^ I I I ggggggg| I I I I mmmmmmms I

b n n s iJ h b« fih h h h tfa B Cu B B B Q UUUUUUUU U U U U S

© fa g

g|g|E^S:S BOSUQQNB

©©©©©©© BBBBBIBB M M M M M M M UUUVUUU

§555555 K B B B B B B M M M M M

B B B B B B B

B B B B B B B OOOOOOO

UUUUUUU^ gbgPPBDB

O)aimQ0 Q0 QDQ0 » SISSSSS!^ uuuuuuua

n 9>c4 «ci»«<e

o

QDN

©

fa

I

O

00C49

62
APPEIIDIX

B

DATA

DICTIOHARY/DIBECTORY

ILE

-

GRABTEE

REPORT

4

DATA

s

SI

II II IL PDtf

nD.o

u

Pl.

CD

oe

r

CO

^ B

I

s

I §§go |g^g||gg§§§o ®

5 g«««p|gggsi

^BLi«*-««(BOBeBeQr

HUB I I I I I '"crnbo

flS BS OrWHHHHH i i i

i

s

M »<»< X »<»<»<>; x>; X »4

n

Plj 0^ 04 ggggssssssg

SSggggSSgSI

iliililliil

NcoMioNOieciinocf <6 >c >0 m

B ® ® B

xxSS3

63
s

a» u V

»< M

I i

0. a,

CO 00

p

I

u

kJs

$ 9 9

Mix

I

64
s

I

• CD H K

b, O

u (J)

II II u o

HHH 1 b Cb Cb 1 oioiai 1 Q O (B(BC0 1

mS StfS OP cs§ •Jb bO

52

W*-|

II ii ^2

ASS 88 88 88 ooenoi uuc;4u<

SruUP^

2 SS3 S oooo UCiJUU

si

(BIB

i§E M UH

Hg<

<v

IIo o

g

e-?2

t-J nJ

UCd

eo ooon<

A

oooS PP ou uo uoo<o< OUOb (BX

OCI C4CI AA^CI

• « • • A w A CO d A Od A A A A

X X XXX X X

OCdbbbI

menioN'* 9 ® C4 ® ® ®

XXX Ux

65

02

BACK-DP

SYSTEM

TYPE

AUXTYPE-DBA

C0=

COAL

EL=

ELECTRIC
s

I

t

I

II U II II fc •

si I

iiii

Si Scn

.Q

e II

-s

nH ^ gu

S ut*

idi

ssssg "“S-

?lii

CQCQOO

O S 9 9 •

>!X>;>;

SNN

5 wP §9

apss

ffigbpo

^ii

2 ju 2

O ^ QDBbPu p|

UUO<Ub<.

99

id^

. .BKOte^^

Ji 9 jH^a^^ <SjQ<tgSJ^B

9pL.muna8raSS"odB^^^ HumunouQo

bb 6 b_hp “ r* J ?5 s5 » *= Jh. -N

ggsssssgg^g

9«vD99999IO«9NNN<eNIOIOIO

66
s

o>

I

«• I

I

S2 W O U « W W W EjSjjS

»< »< X >; X »< >: M M NM M M M M

^ ^ ^ ffl ffi g

^ P P P P h P h iSPmao^ m b (b b lb b (U < < < <! < < < II n II u n n II ii ii ii tsa&<ama (»£» U U U U U U U ngtidBUb bS^ S H S S 3 S 3 <SFpuu< OD 00 CO QD 00 QQ QO £ F 00 fi U E CDF<C5

CD B »

B U 00 O Qu 3 UOO

Ob S OOQ

e

i

U U Id Ed b 00 Q

OMOM

OM

OMO ^ PN « i ^ ^ ^ ^ ^ i S 3 3 3 H 3 <

O 00 3 3 CD 00 ^ 3 B B B B u

3 O O O O O B

b b b b b b 2

B B B B B B B »- O O © O O O

^ S ^ S 9 S g

B B eS B B B b

9 9 9 0 0 0 9

3

b

H

g

9

67

eS

RUHBER

OF

SIMILAR

PROBLEnS
s

9«i4

• D

V >

a

^ w

u qS

i

1

gf.g. OIL GAS WOO PRO

Jl II Jl

nnSe I 2 w

>CMia.

9 • 9 9 9

<<«f ^

MXX

999^9

68
Q0

N»ei

x>;x XX iO(!»<

69
^ a

£ i

i

P

tC geS O go gb

£u pCo ll£(b

I &&6

mmm

u

Bu

Sissll fa

iiiiill

11 II ji II II II

12

fa S B,

00 S rh H H g

s

5 g

•-J a

§ § D

BU Bk fa n

o m9

CO9

H

fa |g

u o S OO LO

H

(B Bl< QQ n CO CO

UQOCOCOCQQO

N C9 ^ ^ CO 9 O 9 o o ®

61 ^

< On II

11 II <fa»

XXX

70
sn i

••

go r • 11

K ft. glpl

ailss 8 ££SS ' III mgwfcft. S oaoo E 3 ®

e_,(aSH

Setf Doqi-)3

|DD

.eaeo

HU

UU

UO . jp 33 QOHmoo

.C CO CO ?4 9 ® ® ® CO

iX>i >3

71
I

u u u » M »

o a a

moocDCfiQOOOKiQatiocoaiK)

u u u u u u u u u H P

k k 2

»< »< i ^ a

S 1

a

S

a

s

a

sA ia

i

u

a1a

ft_ 1ss^ b«

0^

5!

Ok ft« 5!ft« Dk § 1 §

N4^ i

g

!SS

S

|KaStB§§S^(l<aObBSf'bOUB

< 5 SauaFuaoNuuEouos

<< u

«*-- Ia eocHaaca M M hho O ^ fi ^ ^ ^

<»(B asH .j^aaQo QOa)BO(BK<> £££igggp^g||!l aaH-^s^HSa^ — a^a DPUB J£Maaoupa u mco^BiJp Jb^SKQQ ah a >-• <! H Ba 4 a< >J u 4

^’'"ISSgiH^ 5! 5 '>'i|‘=' 4HHuaB5aiU«», b,HQI*,HH aaa <->^ fiaH aefauP

apuSSSa^ouaSSSa^S^go

POKPOOaP B3 BSOW 5! pmSprie Pr -- ga^KEoJglisS^apgwP

pppbSawSaSSSpSSoQSS

XXiOSiiOiBXBKiXBXBBBB

a a a ^

§ § § i S i

a £ £ S a a

_ ^ a a !j a S § § S

72
j

73
I

\

§

u

QK es xeoD

s®hS

ePl

w«fe”

fcsrs^

IBUHRRUkJRRH^H -iboaSttaSe^RRiB

.. _ „ j < R ft< ® 3 © F« ee o D "" QOaOBQOUOQnVQDpUCO

ll sssps (SO PuOOr(SQmQu 0<n gg^S_Qu

pL4 n E pu !(Q«»nMS§S^>iH>ig HMQQUQSBnBuSmm»Pra(a m3r£3kh cu uaPSSoon

Miaa.a.neu 3 R uhbx©cq 5 b r9 ,1^9 ao3GQEp(nn(aP(»o

=d|2 d-!:g=“'Sgu§ 2 Si

feS0<wnUQDK^03flBEH**^H

=§0 iigsig| 3 |g^|ig» RHae©EQDuoeS©«iHu<o

fiH6Mb<b<f«Cfahhb‘<^^lialihb<b•b<fetfa OOOOOOOOOOOOOOOOO

©•« 0 ©««« 99 © 9©«»»9

REERRiXRXERRRXRXXR

74
s

a

I

\

I

§

u

• Iaa • uu oo

I F«) I HQOH

IGQtIBQI

UU OOUU

U ^ ^ O ^ ^ Y UBSuSSn I HCO I HGOH

cc <!«!<<« <<<<<!<<

S!‘

II

OtfUUtf , > 03 > 0 W , <t fa oi < b. O) u

H & u

BI-XJkSH < - 89 " 83 g auSquo

|£i|iia

o cd o o M

CP

»<S^xxSI>i

^ b

-I S| uu o u w^mu

3 ofew'^£->

sliiiilW U pauoa w >OQO>OU <Cfaa<famu a o feHOBH < •gS- 83 g luSauo

I >< >< 00 >< >< 5 ' ISi^tJO

gSEgS!

g£ig££^

^ O O CP ^

75
SiI

I

i

\

§

u

iSfeS

B

I

^QoScOHBS nh M M M M

||SB=rSE„

HEffl5S2S

SES2|®® OUiBqqSkBO

Bh Gfa bb &b *"* ooSS^^H

Qu CU

oi CC Om ffi ^ ^ hShho^ s4 IW w 111

'^mciciceo ^ 9 9 ® ^ POOiX

76
I

I

t

\

§

u

II

oooooooooooooooooooooooooo BSCBBKBtSBggggggggggggggggBgg

C<CjNNnCIClC4C4ClCJClCieiC4CI(MC4CIC4C4CICIClCICI

Cd

77
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS

Introduction

Codes and their values are assoeiated with certain data

element names. For example, data element PJINSTR can be

coded in two ways: "IN" or "NO". The "values" or

"meanings" of these two codes are: "IN" means "instrumented" and "NO" means "not instrumented." Appendix C

contains all those codes and values which were too long

to fit into the SOLAR DATA DICTIONARY/DIRECTORY, appendix B. One characteristic of these longer codes and

value lists is that they are dynamic--additions are

frequently made to them.

The following pages contain a data element name at the

top of the page, followed by the name of the interactive

file or files, which reference this data element, followed by the codes and their corresponding values. The

data elements are in alphabetical order. The codes/

values lists are usually alphabetical with the exception

of EVENTS and HARDELEM. The number(s) in parentheses at

the top of the page references the page(s) of appendix B,

the SOLAR DATA DICTIONARY/DIRECTORY, where the data

element and its attributes are defined.

Updated lists of codes and values are available from the

Franklin Research Center.*

*1030 15th Street, N.W.

Suite 720

Washington, D.C. 20005

Telephone: (202) 223-8109

78
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS

Data Element Name: ACTIONS

Interactive File Where Used: MASTER (67)

ADED ADDED

ADEDl ANTIFREEZE

ADED2 FLUID

ADED3 INHIBITOR

ADED4 ADDITIONAL HARDWARE

ADED5 ADDITIONAL MEMBERS

ADJT ADJUST

ADJTl BLEED

ADJT2 CLEAN

ADJT3 THAW

ADJT4 TIGHTEN

ADJT5 LUBRICATE

BRAZ BRAZE

ELIM ELIMINATE

NONE NONE

NBAR NONE BUT ACTION REQD

NBARl AWAITING SHIPMT OF RPLMT ELEMENTS

MANI MANFTR INVESTG

OCIN OCCUPANT INSTRUCTED

OCINl ON PROPER USE OF SYS

OCIN2 ON RELSHP-FENES/ECON

RECT RECOAT

REGR REGROUTED

REMV REMOVE

REPK REPACK

REPA REPAINT

REPR REPAIR

RPLI REPLACE W/ IDENT ITEM

RPLIl LEVEL 1 RPLI2 LEVEL 2

RPLI3 LEVEL 3

RPLI4 LEVEL 4

RPLS REPLACE W/SUB ITEM

RPLSl LEVEL 1 RPLS2 LEVEL 2

RPLS3 LEVEL 3

RPLS4 LEVEL 4

RELO RELOCATE

RESL RESEAL

RETP RETAPE

REWK REWORK

REWR REWIRE

RSMA ROU OR SCHD MAIN

SLDR SOLDER

WELD WELD

NBAR2 WAITING OPPORTUNE TIME

REMVl ISOLATE FROM SYSTEM

79
V

f

APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name; AUXSUPPLIER

Interactive File Where Used: MASTER

ALOl Huntsville Utilities

P.O. Box 2048

Hunstsville, AL 35804

AZOl Arizona Public Service

P.O. Box 2907

Phoenix, AZ 85062

Co .

CAOl Pacific Gas & Electric

111 Almaden Blvd.

San Jose, CA 95198

Co .

CA02 Pacific Gas & Electric

314 "F" Street

Davis , CA 95616

Co .

CA03 San Diego Gas & Electric Co.

P.O. Box 1831

San Diego, CA 92112

CA04 So. California Gas Co.

340 N. Juanita St.

Hemet, CA 92343

CA05 California Edison Co.

10180 Telegraph Rd

.

Ventura, CA 92343

COOl Public Service Co. of

P.O. Box 840

550 15th St.

Denver, CO 80202

Colorado

C002 Public Service Co. of

1155 Canyon Blvd.

Box 551

Boulder, CO 80302

Colorado

C003 Public Service Co. of

HWY 7 4

P.O. Box 640

Evergreen, CO 80439

Colorado

COOS Union Rural Electric Assn.

P.O. Box 359

Brighton, CO 80601

80
I

i

APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: AUXSUFFLIER (Continued)

Interactive File Where Used: MASTER

COOS Fublic Service Co. of Colorado

F . 0 . Box 707

Frisco, CO 80443

C006 Fublic Service Co. of Colorado

9722 E. 16th St.

Aurora, CO 80010

C007 Fublic Service Co. of Colorado

209 S. Meldrum St.

Box 1668

Fort Collins, CO 80521

CTOl Hartford Electric Light Co.

34 Hopmeadow

Simsburg, CT 06070

CT02 The United Illuminating Co.

80 Temple Street

New Haven, CT 06506

CT03 Hartford Electric Light Co.

F.O. Box 2370

New Haven, CT 06506

CT04 Connecticut Light & Fower

King Street

Enfield, CT 06082

FLOl Florida Fower Corp.

F.O. Box 33733

St. Fetersburg, FL 33152

FL02 Florida Fower &

F.O. Box 529100

9520 W Flager

Miami, FL 33152

Light Company

FL03 Florida Fower &

F.O. Box 341608

Light Company

Coral Gables, FL 33134

FL04 City of Gainesville Utilities

200 E. University Ave. Rm 402

Gainesville, FL 32602

81
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: AUXSUPPLIER (Continued)

Interactive File Where Used: MASTER

FLOS Florida Public Utilities Co.

Drawer C

West Palm Beach, FL 33406

GAOl Coweta/Fayette, Inc.

P . 0 . Box 488

Newnan, GA 30264

GA02 Atlanta Gas Light

89 Annex

Atlanta, GA 30389

GA03 Georgia Power Company

1790 Montreal Circle

Tucker, GA 30084

GA04 Georgia Power Company

96 Annex

Atlanta, GA 30396

GAOS Georgia Power Company

Duluth, GA 30246

GA06 Buford Gas Company

30 Garnett Street

Buford, GA 30S18

GA07 Georgia Power Company

P . 0 . Box 3 2 7 Lawr enceville , GA 30246

GA08 Georgia Power Company

P . 0 . Box 271

Canton, GA 30114

GA09 Jefferson Electric Company

1001 Peachtree Street

Louisville, GA 30434

HIOl Hawaiian Electric Co., Inc.

P . 0 . Box 3978

Honolulu, HI 96813

INOl Public Service of Indiana

lOS S. Madison

Greenwood, IN 46142

82
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: AUXSUPPLIER (Continued)

Interactive File Where Used: MASTER

MAOl Bay State Gas Co.

2025 Roosevelt Avenue

Springfield, MA 01101

MA02 Boston Edison Company

P.O. Box 488

Boston, MA 02199

MAO 3 Bay State Gas Company

120 Royall Street

Canton, MA 02021

MA04 Bay State Gas Company

995 Belmont Street

Brocton, MA 02401

MDOl Baltimore Gas St Electric

1508 Woodlawn Drive

Baltimore, MD 21207

Co .

MIOl Berrien City Farm Bureau

M-140 &M-62

Eau Claire, MI 41911

Oil Co.

MNOl Minnegasco/Minnesota Gas

626 Nicollet Mall

Minneapolis, MN 55402

Co

MN02 Northern States Power

414 Nicollet Mall

Minneapolis, MN 55401

MOOl The Gas Service Co

2460 Pershing Rd

Kansas City, MO 64108

M002 Kansas City Power St Light

13330 Baltimore Avenue

Kansas City, MO 64145

: Co .

NCOl Duke Power Company

Drawer A D Salem Station

Winston-Salem, NC 27108

NEOl Cengas /Minnesota Gas Co.

1201 N Street

Lincoln, NE 68512

83
\

APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name; AUXSUPPLIER (Continued)

Interactive File Where Used: MASTER

NHOl Public Service Co. of New Hampshire

Crystal Avenue

Derry, NH 03038

NH02 Public Service Co. of New Hampshire

370 Amherst Street

Nashua, NH 03061

NH03 New Hampshire Elec. Cooperative, Inc.

Red 2 Tenney Mt . Hwy

.

Plymouth, NH 03264

NMOl Gas Co. of New Mexico

P.O. Box 1692

Albuquerque, NM 87103

NM02 Public Service Co. of New Mexico

414 Silver Ave. N.W.

Albuquerque, NM 87103

NM03 Public Service Co. of New Mexico

124 E. Marcy

Santa Fe, NM 87501

NYOl New York State Electric & Gas

5655 South Park Ave.

Hamburg, NY 14075

NY02 National Fuel Gas

455 Main Street

Buffalo, NY 14203

NY03 Orange & Rockland Electric & Gas Co.

One Bluehill Plaza

Peael River, NY 10965

NY04 Niagara Mohawk Power

383 Broadway

Saratoga Springs, NY 12866

NY05 Moore Oil Company

Charlton Road

Ballston Spa, NY 12020

OHOl Cincinnati Gas & Electric Company

139 E. 4th

Cincinnati, OH 45201

84
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: AUXSUPPLIER (Continued)

Interactive File Where Used: MASTER

OH02 Ohio Power Company

Box 630

Canton, OH 44701

OH03 Columbus & Southern Ohio Electric Co.

215 North Front Street

Columbus, OH 44701

OROl Pacific Power & Light Co.

300 W. Anderson Avenue

Coos Bay, OR 97420

OR02 Ashland Municipal Electric

20 E. Main

Ashland, OR 97420

PAOl Philadelphia Electric Co.

230 Market Street

Philadelphia, PA 19101

SCOl Palmetto Elec Cooperative, Inc.

Box 1218

Hilton Head, SC 29928

SC02 Piedmont Natural Gas Co., Inc.

P .0 . Box 1905

Greenville, SC 29602

SC03 South Carolina Electric and Gas

P . 0 . Box 764

Columbus, SC 29218

TNOl Memphis Light, Gas & Water Co.

P . 0 . Box 430

Memphis, TN 29218

TXOl El Paso Electric Co.

P . 0 . Box 982

El Paso, TX 79999

TX03 Lone Star Gas

301 Harwood St.

Dallas, TX 75201

TX04 Dallas Power & Light Co.

1506 Commerce Street

Dallas, TX 75201

85
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: AUXSUPPLIER (Continued)

Interactive File Where Used: MASTER

TX05 West Texas Utilities

106 S. Chadbourne

San Angelo, TX 76901

TX06 Lone Star Gas Company

P . 0 . Box 4 71

San Angelo, TX 76902

UTOl Utah Power & Light Company

1407 West North Temple St.

Salt Lake City, UT 84116

UT02 Logan Power & Light Co.

61 W. 100 N.

Logan, UT 84321

UT03 Mountain Fuel

45 E. 200 N.

Logan, UT 84321

VAOl Appalachian Power Company

523 Main Street

Lynchburg, VA 24506

WIOI Wisconsin Power & Light Co.

401 Oak Street

Baraboo, WI 53913

WI02 Northern States Power Company

P . 0

.

Box 1147

Eau Claire, WI 54701

WI03 Wisconsin Electric

231 W. Michigan Street

Milwaukee, WI 53201

86
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: BPERPROB

Interactive Files Where Used; MASTER, MIS (61, 72)

A NONE

B BLDG. DEPT. CODE PROHIBIT SOLAR

C CODES DON’T ADDR SOLAR CAN'T ISSUE

D BLDG. DEPT. REQ. REDESIGN OF SOLAR

E WILL NOT ISSUE NON SOLAR CAUSE

F PERMIT NOT REQ. RETROFIT

G PERMIT NOT REQ.

H 100% COMPLETION REQ. TO ISSUE

I BLDG. DEPT. SHOWED INTEREST

J OTHER SEPARATE PERMITS REQ'D.

K ADDS/CHANGES TO BLDG. REQ'D.

L OBTAINED BY OTHER THAN GRANTEE

Z MORE INFO. IN FILES

87
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Names; CFINPROB

Interactive Files Where Used: MASTER, MIS (60, 72)

A NO PROBLEM

B FIN. ORG. NEG ON SOLAR

C FIN. ORG. HAS TECH CONCERNS

D FIN. ORG. HAS MARKET CONCERNS

E FIN. ORG. NOT MAKING CONST. LOANS

F INCR. INT. RATE DUE TO SOLAR

G CONST. /MORTGAGE COMBINED

H HUD FINANCED

I RETROFIT INTERNAL FIN.

J APPRAISAL PROBLEMS

K LOAN LESS THAN APPR. VALUE

L COND. COMMIT. NON SOLAR

M COND. COMMIT. SOLAR CAUSED

N PENDING FHA/VA APPROV

.

0 REVOLVING CREDIT LINE

P INTERNAL FUNDING

Q RETROFIT NO FIN. REQ.

R CONST. & PERMANENT FIN.

S GRANT AMT. INCL. IN SALES PRICE

T STATE FUNDS

U LOW INC. HSG LOAN ONLY

Z MORE INFO. IN FILES

88
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: CPROBBRK

Interactive Files Where Used: MASTER, MIS (62, 72)

A NONE

B IMPROPER HANDLING DEL. OR ON SITE

C EQUIP. TOO FRAGILE

D FAULTY MANUFACTURE

E OPERATIONAL FAILURE

F DAMAGED OR INSTALLED INCORRECTLY

G FAULTY EQUIP REPLACED

H DEFECTIVE HOSE S /DAMPERS / FAN

S

I INST. MANUALS NOT PROVIDED

J MALFUNCTIONING CONTROLS

K ALL COLLECTORS/PANELS REPLACED

L LEAKAGE PROBLEMS

M MISC. COLLECTOR BREAKDOWNS

N STORAGE PROBLEMS

0 DAMAGED IN TRANSIT

Z MORE INFO. IN FILES

89
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: CPROBDEL

Interactive Files Where Used: MASTER, MIS (62, 72)

A NONE

B TEMP. PROD. DELAY

C MAJOR PROD. DELAY CHANGE OF EQUIP.

D DEL. DELAY DUE TO WEATHER

E DEL. DELAY CAUSE UNSPECIFIED

F COMPANY OUT OF BUSINESS

G MORE LEAD TIME REQ'D ON ORDERS

H HUD/BOEING INSTR. PACKAGE DELAYED

I INCOMPLETE ORDER

J DELAYED AT CUSTOMS

K DISPUTE CONTRACTORS & MFG.

L LOCAL SUPPLIER OUT OF MATERIALS

M MISC. PARTS REORDERED

N MISC. MATERIALS UNAVAILABLE

0 ORDER REC’D W/WRONG COMPONENTS

P PLANT SHUTDOWN/STRIKE

Q REORDER/DAMAGED PARTS REC’D

S SUPPLIER UNABLE TO SHIP PER SCHED.

T TRANSPORTATION RELATED DELAY

U MAJOR PARTS REORDERED

V FABRICATION DELAY

Z MORE INFO. IN FILES

90
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: CPROBINTF

Interactive Files Where Used: MASTER, MIS (62, 72)

A NONE

B MAJOR STRUCTURAL CHANGES

C MINOR STRUCTURAL CHANGES

D WEATHER

E AESTHESTIC PROBLEMS

F FURTHER CONST. AFTER COMPL.

G ADD’L MAT. /COMPONENTS REQD.

H IMPROPER DESIGN ROOF OR COLL.

I INSULATION RELATED

J ACQUISITION OF MATERIALS

K ADD'L DUCT WORK REQD.

L LEAKS

M MULTIPLE INTERFACE PROBLEM

N NEW DESIGN DEV. & INSTALLED

0 ROOF DESIGN CREATED PROBLEMS

P SOLAR MFG. RECOMMENDS CHANGE

Q ROOF DESIGN CREATED PROBLEMS

R SOLAR PLUMB. /WIRING RELATED

S SENORS OMITTED

T TRUSS DESIGNS ADDED

U STORAGE TANK MODS.

V SCHEDULING OF OTHER SUBCONT.

W WATERPROOFING

Y SOLAR INSTALL. PROBLEMS

Z MORE INFO. IN FILES

91
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: CPROBLAB

Interactive Files Where Used: MASTER, MIS (62, 72)

A NONE

B NO INTEREST WILL NOT WORK SOLAR

C LACK OF SKILL

D JURISDICTIONAL DISPUTE

E POOR WORKMANSHIP

F LACKS TECH. COMPETANCE

G WEATHER RELATED

H HAD TO TRAIN CO. PERSONNEL

I INTITAL CONTR. TERMINATED

J SLOW PYMNT SLOW LAB. RESPONSE

K EXTRA SUPERVISION REQ.

L INSTALLATION COSTS OVER ESTIMATE

M MORE INSTR. FROM SOL. MFG

N NOT AVAIL TO COMPL. WORK

0 SUBCONTR. BEHIND SCHEDULE

P LAB. PRODUCTION DEL. UNSPECFIED

Q ACQUIRING QUALIFIED LABOR

R UNSKILLED PROSPECTIVE OWNERS

s HIGH LABOR COSTS

z MORE INFO . IN FILES

92
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: CPROBOTH

Interactive Files Where Used: MASTER, MIS (62, 72)

A NONE

B PROB. W/GEN. CONTR. & SUBCONTR.

C RELATED TO COSTS

D SUBCONTR. WORKING OTHER JOBS

E ROOFING COORDINATION

F MISC. WEATHER RELATED

G VANDALISM/THEFT

H MODIFICATIONS AFTER COMPL

I OBTAINING GEN. MATERIALS

J ROCK BOX/FILL/STORAGE

K INSTRUMENTATION INSTALLATION

L CONSTRUCTION START DELAY

M INSTALL. TIME UNDERESTIMATED

N MAJOR CONSTRUCTION PROBLEMS

0 UNFAMILIAR W/SOLAR COMPONENTS

Z MORE INFORMATION IN FILES

93
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: EVENTS

Interactive File Where Used: MASTER (67)

GENE

AIRE

DMBY

DMBYl

DMBYll

DMBY12

DMBY2

DMBY3

DMBY4

DMBY41

DMBY42

DMBY5

DMBY6

DMBY7

DMBY71

DMBY72

DMBY8

DESC

FLOP

FLOPl

FL0P2

FL0P3

FLOP4

FLOP7

FL0P6

FLOPS

FLOPS

FLBO

FLBOl

FLB02

FLB03

FLB04

OPIM

OPIM6

OPIMl

OPIMll

OPIMlll

OPIM112

OPIM12

OPIM13

OPIM14

OPIM15

OPIM16

OPIM4

OPIM2

OPIM21

OPIM22

OPIM23

0 P T M 2 4

OPIM25

GENERAL

AIR ENTRAPMENT

DAMAGED

ACCIDENT

IN TRANSIT

DURING INSTALLATION

FREEZING OF LIQUID

LEAKAGE OF MOISTURE OR RAIN

LEAKAGE OF SYSTEM FLUIDS

BETWEEN COMPONENTS

FROM COMPONENTS

LIGHTNING

MAINTENANCE ACTION

SOIL EROSION

OVERFLOW PROVISIONS INADEQUATE

STORM DRAINS INADEQUATE

VANDALISM

DESIGN CHANGE

FAILED TO OPERATE

BROKEN

BURNED OUT

BURST

CLOGGED OR BLOCKED

FAULTY

INCOMPATIBLE

MALF-OTH COMPO

WORN OUT

FAILED TO OPERATE BECAUSE OF OUTAGE

ELECTRICITY

GAS

OIL

WATER

OPERATING, BUT IMPROPERLY

CONTINUOUSLY

DEPOSITION OF

CONDENSATION PRODUCT

MOISTURE

SOLID

DUST OR DIRT ON EXTERIOR SURFACES

DUST OR DIRT ON INTERIOR SURFACES

GUM OR VARNISH

PRECIPITATED MATTER

SEDIMENTATION

ELEMENT INADEQUACIES

INCORRECT

ADJUSTMENT

ALIGNMENT

CAPACITY

INSTALLATION

MANUFACTURING

94
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: EVENTS (Continued)

Interactive File Where Used: MASTER

OPIM26 PART OR COMPONENT

OPIM3 LEAKAGE OF AIR

OPIM5 SOLAR SHADING

OPIM51 OFF-SITE OBSTRUCTION

OPIM52 ON-SITE OBSTRUCTION

RUBN RESTRAINS USE BECAUSE OF NOISE

RUBNl FLUID MOVEMENT

RUBN2 VIBRATION

RUBN3 WATER HAMMER

RULS RESTRICTS USE OF LIVING SPACE

RULSl ENCROACHMENT

RULS2 EXCESSIVE AIR MOVEMENT

RULS3 LEAKAGE OF AIR

RULS4 ODORS

RULS5 SOLAR REFLECTION

RULS6 THERMAL RADIATION

RUOS RESTRICTS USE OF OUTDOOR SPACE

RUOSl FLUIDS ESCAPING

RUOS2 SOLAR REFLECTION

RUOS3 THERMAL RADIATION

SCHD SCHEDULING INADEQUACIES

SHPM SHPMT/PARTS & MATERIALS INCOMPLETE

MECH MECHANICAL

FLIN FILTRATION INADEQUATE

FLRA FLOW RATE

FLRAl HIGHER THAN DESIGN

FLRA2 LOWER THAN DESIGN

FLRG FLOW REGULATION INADEQUATE

FLRGl CYCLING EXCESSIVE

FLSD FLOW SEQUENCING NOT ACCORDING TO DESIGN

FLSDl DIRECTION

FLSD2 SCHEDULING

FLUN FLOW UNBALANCED

FLVE FLUID VOLUME EXCESSIVE

FLVEl BOILING PROVISIONS INADEQUATE

FLVE2 THERMAL EXPANSION PROVISIONS INADEQUATE

FRIG FRICTION EXCESSIVE

FRICl FOREIGN MATTER

FRIC2 IMPROPER MATERIALS

FRIC3 INADEQUATE BEARING SURFACES

FRIC4 INADEQUATE CLEARANCE

FRIC5 INADEQUATE LUBRICATION

INST INSTALL DIF

INSTl HARDWARE INADEQUATE

INST2 INSTRUCTIONS INADEQUATE

INST3 BUILDING INADEQUATE

LGRU LEAKAGE RUNOFF PROVISIONS INADEQUATE

LEAK LEAKING

OPIN OVERFLOW PROVISIONS INADEQUATE

OVLD OVERLOADED

95
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name; EVENTS (Continued)

Interactive File Where Used; MASTER

OVLDl ELECTRICALLY

0VLD2 MECHANICALLY

PASS PASSAGE SIZE

PASSl LARGER THAN DESIGN

PASS2 SMALLER THAN DESIGN

PBHD PRESSURE BUILDUP HIGHER THAN DESIGN

PBHDl DURING NO FLOW CONDITIONS

PBHD2 DURING NORMAL OPERATING CONDITIONS

PROP PRESSURE DURING OPERATION

PROPl HIGHER THAN DESIGN

PROP2 LOWER THAN DESIGN

PRIN PRESSURE REGULATION INADEQUATE

PREF PRESSURE RELIEF INADEQUATE

SUPI SUPPORT INADEQUATE

SUPIl CAUSING IMPROPER DRAINAGE

SUPI2 CAUSING JOINT FAILURE

SUPI3 LOW SPOTS OR SAGGING

TMOV THERMAL MOVEMENT

TMOVl CONTRACTION EXCESSIVE

TMOV2 DIFFERENTIAL DISPLACEMENT EXCESSIVE

TMOV3 EXPANSION EXCESSIVE

VHDE VACUUM HIGHER THAN DESIGN

VHDEl BECAUSE OF INADEQUATE RELIEF

VLDE VACUUM LOWER THAN DESIGN

VLDEl BECAUSE OF OUTGASSING

VLDE2 BECAUSE OF LEAKAGE

VIBE VIBRATION EXCESSIVE

VIBEl INADEQUATE/NO VIBRATION ISOLATORS

VIBE2 INADEQUATE/NO WATER HAMMER ARRESTORS

VLIN VOLUME INSUFFICIENT

VLTL VOLUME TOO LARGE

MAIN MAINTAINABILITY

ACRE ACCESS FOR REPAIRS INADEQUATE

ACRU ACCESS FOR ROUTINE MAINTENANCE INADEQUATE

BYPA BY PASSES OR SHUT-OFFS INADEQUATE

FAMA FACILITIES FOR MAINTENANCE INADEQUATE

FAMAl USE OF ELECTRICAL MAINTENANCE EQUIPMENT

FAMA2 WASTE DISPOSAL

MAST MAINTENANCE INSTRUCTIONS

MASTl INADEQUATE

MAST2 NOT AVAILABLE

MAEP MAINTENANCE EQUIPMENT

MAEPl INADEQUATE

MAEP2 NOT AVAILABLE

RERP REMOVAL AND/OR REPLACEMENT DIFFICULT

RPDR REPAIR PROCEDURES

RPDRl ARE CUMBERSOME

RPDR2 REQUIRES UNAVAILABLE SKILLED PERSONNEL

RNAV REPLACEMENT NOT AVAILABLE

RSNP ROUTINE SCHEDULED MAINTENANCE NOT PERFORME

96
APPENDIX C

CODES/;VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name; EVENTS (Continued)

Interactive File Where Used: MASTER

TCHP TEST CHECK POINTS

TCHPl INACCESSIBLE

TCHP2 LACKING

DURA MATERIALS DURABILITY/RELIABILITY

ANTF ANTIFREEZE DETERIORATION

ATAC ATTACK BY

ATACl AIRBORNE POLLUTANT OF

ATACll HYDROGEN CHLORIDE [HCL]

ATAC12 NITROGEN OXIDES [NOX]

ATAC13 OZONE

ATAC14 SALT SPRAY

ATAC15 SULPHUR DIOXIDE

ATAC16 OTHER

ATAC2 FUNGI

ATAC3 SOIL

ATAC4 ULTRA VIOLET RADIATION

ATAC5 VERMIN

CBCB CORROSION , • CBCBl DECOMPOSITION PRODUCT AND METAL

CBCB2 DISSIMILAR METALS

CBCB3 FLUID + DISSIMILAR METALS

CBCB4 FLUID AND METAL

DETR DETERIORATION

DETRl BLOATING

DETR2 BOND FAILURE

DETR3 DEPOSITION OF OUTGASSED VOLATILES

DETR4 EMBRITTLEMENT

DETR5 LOSS OF HOMOGENEITY

DETR51 PRECIPITATION

DETR52 SEGREGATION

DETR53 SHRINKAGE

DETR6 MOISTURE BUILDUP

DETR7 PH CHANGE

DETR8 PLASTIC FLOW

DETR9 SOFTENING

EROD EROSION

ERODl BY AIRBORNE PARTICULATE

EROD2 BY FLUID

EROD3 BY FOREIGN MATTER

FAIL FAILED

FAILl CREEP RUPTURE

FAIL2 EXCESSIVE DIMENSIONAL CHANGE

FAIL3 FREEZING

FAIL4 MOISTURE DEGRADATION

FAILS THERMAL CYCLING

FAIL6 THERMAL DEGRADATION

FAIL? THERMAL SHOCK

FAIL71 COLD FLUID ON HOT SURFACE

FAIL72 HOT FLUID ON COLD SURFACE

FAIL73 VIOLENT BOILING

97
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: EVENTS (Continued)

Interactive File Where Used; MASTER

FAILS

FAIL9

SRDG

SRDGl

SRDG2

SRDG3

SRDG4

SRDG5

Vise

SAFE

EGEM

EGEMl

EGEM2

EGEN3

EXED

FIRE

FIREl

FI RE 2

FIRE3

FIRE4

FIRES

FIRE51

FIRE52

FIRE6

PRSL

PRSLl

PRSL2

PRSL3

PRSL4

PRSL5

PRSL6

PRSL7

PRSL8

PRSN

PRSNl

PRSN2

PRSN3

SARD

SAHDl

SAHDl

1

SAHD12

SAHD13

SAHD2

SAHD21

SAHD22

SAHD23

SAHD231

SAHD232

SAHD233

SHEM

WET-DRY CYCLING

OUTGASSING OF VOLITALS

SURFACE DEGRADATION

BLISTERING

CRACKING

DISCOLORATION OR STAINING

PITTING

PEELING

VISCOSITY CHANGE

SAFETY

EGRESS, EMERGENCY

BLOCKED

INADEQUATE

LACKING

EXPOSED SHARP EDGES

FIRE POTENTIAL FIRE DAMAGE

AUTO IGNITION TEMPERATURE EXCEEDED

ELECTRICAL ARCING AND/OR SHORT

FIRE STOPS INEFFECTIVE OR MISSING

FLASH POINT TEMPERATURE EXCEEDED

INADEQUATE CLEARANCE

BETWEEN COMBUSTIBLES + HOT HARDWARE

BETWEEN FLAMMABLE FLUID AND SPARK SOUR

OVERHEATED EQUIPMENT

PERSONAL INJURY

ALLERGY

BROKEN BONE

BURN

CUT

ELECTRIC SHOCK

POISONED

SCRATCH

STRAIN

PERSON INJURED

OCCUPANT

MAINTENANCE PERSON

PASSER BY

SAFETY HAZARDS [OTHER THAN FIRE]

ACCESS, EMERGENCY

BLOCKED

INADEQUATE

LACKING

CONTACT POSSIBLE WITH

HOT FLUIDS

HOT SURFACES

TOXIC SUBSTANCE

INHALATION

DRINKING

SKIN CONTACT

SHUTOFFS, EMERGENCY

98
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: EVENTS (Continued)

Interactive File Where Used: MASTER

SHEMl

SHEM2

SHEM3

CNSL

SLRA

CNSW

CNSWl

CNSW2

CNSW3

CNSW4

MPPR

STRU

DEFL

DEFLl

DEFL2

DCHG

DCHGl

DCHG2

DCHG3

DCHG4

DCHG5

FDLB

FDLBl

FDLB2

FDLB3

FDLB4

FDLB7

FDLB5

FDLB51

FDLB52

FDLB6

FDLB61

FDLB62

LLOD

LLODl

LL0D2

LLOD3

LLOD4

LL0D5

LLOD6

LLOD7

LLOD8

LLOD81

LLOD82

LLOD83

LL0D84

LLOD9

LOBY

LOBYl

LOBYll

INACCESSIBLE

INCONSPICUOUS

LACKING

SOIL CONTAMINATION

SOLAR RADIATION CONCENTRATION

WATER SUPPLY, POTABLE, CONTAMINATION

DIRECT CONTACT WITH TOXIC MATERIAL

LACK OF SEPARATION OF CIRCULATION LOOPS

IMPROPER DESIGN OF TOXIC FLUID DISCHARGE

TOXIC FLUID LEAKAGE OR OVERFLOW

MOVING PARTS INADEQUATELY PROTECTED

STRUCTURAL

DEFLECTIONS WERE EXCESSIVE

HORIZONTALLY

VERTICALLY

DIMENSIONAL CHANGES EXCESSIVE

CREEP

DIFFERENTIAL SETTLEMENT

DRYING/SHRINKAGE

MOISTURE EXPANSION

THERMAL EFFECTS

FAILURE

BENDING

BUCKLING

BULGING

FATIGUE

FLOTATION

FRACTURE

BRITTLE

DUCTILE

YIELDING

AXIAL

TRANSVERSE

LIVE LOADS

EQUIPMENT [SOLAR HARDWARE]

HAIL

ICE

MAINTENANCE EQUIPMENT OR ACTIONS

PONDING OF WATER

SNOW

VEHICLE

WIND

BUFFETING

HORIZONTAL

UPLIFT

VORTEX SHEDDING

INSTALLATION PERSONNEL

OVERLOADED

ACCIDENTAL LOADS

ANIMAL

99
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: EVENTS (Continued)

Interactive File Where Used: MASTER

L0BY12 DEBRIS, FALLING

L0BY13 DEBRIS, WIND BLOWN

L0BY14 HUMAN

LOBY15 VEHICLE

LOBY2 DEAD LOADS

L0BY3 EXTREME ENVIRONMENTAL LOADS FROM

LOBY31 EARTHQUAKE

LOBY32 FLOOD

LOBY33 HURRICANE

LOBY34 TORNADO

THER THERMAL

TCAP CAPACITY

TCAPl TOO SMALL

TCAP2 MISMATCHED

TCIR CIRCULATION OF AIR, INDOOR SPACE

TCIRl TOO HIGH

TCIR2 TOO SMALL

TCON CONDUCTION, THERMAL

TCONl TOO HIGH

TCON2 TOO LOW

TCLG COOLING INADEQUATE

TERA ENERGY EXCHANGE RATE

TERAl TOO HIGH

TERA2 TOO LOW

TSIR ENERGY, SOLAR

TEAX ENERGY USE, AUXILIARY, TOO HIGH

TEOH ENERGY USE, OPERATING, TOO HIGH

TSIRl CONTRIBUTION TO LOAD TOO LOW

TSIR2 CONVERSION EFFICIENCY TOO LOW

TSIR3 DISSIPATION RATE TOO LOW

HGIN HEATING INADEQUATE

HWSP HOT WATER SUPPLY IS INADEQUATE

HWSPl DRAW RATE TOO HIGH

HWSP2 RECOVERY RATE TOO LOW

HUMD HUMIDITY, INDOOR AIR

HUMDl HIGHER THAN DESIGN VALUE

HUMD2 LOWER THAN DESIGN VALUE

OCIM OCCUPANT USE IMPROPER

OCIMl INEFFICIENT SCHEDULING OF LOAD DEMANDS

OCIM2 THERMOSTAT SET POINT

OCIM21 TOO HIGH

OCIM22 TOO LOW

OPTP OPTICAL PROPERTIES INADEQUATE

OPTPl ABSORPTANCE

OPTPll TOO HIGH

OPTP12 TOO LOW

OPTP2 EMITTANCE TOO HIGH

OPTP3 REFLECTANCE, SOLAR, TOO HIGH

OPTP4 TRANSMITTANCE TOO LOW

ORAN ORIENTATION ANGLE

100
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name; EVENTS (Continued)

Interactive File Where Used: MASTER

ORANl TOO FAR EAST

ORAN2 TOO FAR WEST

RSLR RADIATION, SOLAR

RSLRl EXCESSIVE

RSLR2 INADEQUATE CONTROL

RSLR3 INSUFFICIENT

RTHL RADIATION, THERMAL

RTHLl TOO HIGH

RTHL2 TOO LOW

THPG TEMPERATURE, HARDWARE OPERATING,

THPGl DURING NOCTURNAL OPERATION

THPGll TOO HIGH

THPG12 TOO LOW

THPG2 DURING NO FLOW CONDITION

THPG21 TOO HIGH

THPG22 TOO LOW

THPG3 DURING NORMAL OPERATION

THPG31 TOO HIGH

THPG32 TOO LOW

THPG4 DURING FILL

THPG41 TOO HIGH

THPG42 TOO LOW

TAIR TEMPERATURE, OUTDOOR AIR

TAIRl HIGHER THAN DESIGN VALUE

TAIR2 LOWER THAN DESIGN VALUE

TSTP TEMPERATURE SET POINTS,

TSTPl DIFFERENTIAL

TSTPll TOO HIGH

TSTP12 TOO LOW

TSTP3 HIGHER THAN DESIGN VALUE

TSTP4 LOWER THAN DESIGN VALUE

TLTA TILT ANGLE

TLTAl TOO HIGH

TLTA2 TOO LOW

THMOSY THERMOSYPHONING

101
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Lata element Name; HARDELEM

Interact ive File Where Used; MASTER

SBLD SITE/BUILDING

SITE SITE

SUDR SURFACE DRAINAGE

UTIL UTILITIES

WATR WATER

ELEC ELECTRIC

SV7ER SEWER

FUEL FUEL

SOIL SOIL

PLTR PLANTS/TREES

ADST ADJACENT STRUC

BLDG BUILDING

ROOF ROOF

ROFG ROOFING

INSU INSULATION

STRE STRUCTURE

CEIL CEILING

WALL WALL

INTR INTERIOR

EXTR EXTERIOR

FLOR FLOOR

BSHT BASEMENT

0 P W G OPENINGS

DOOR DOOR

WNDVJ WINDOW

OTER OTHER

SHSY SIIS-II/C/HW-ACT/PASS

ACSD T W/DISC SHS

COLA COLLECTOR ARRAY

COLU COLLECTOR UNITS

COVA COVER ASSY

HTRP HEAT TRAP

ABAS ABSORBER ASSY

TERM THERMAL INSUL

DESA DESICCANT

IN UR I NT UNIT REF

CASA CASE ASSY

HCON HEADERS-CONNECTORS

AIRD AIR DUCT ASSY

LPIP LIQUID PIPE ASSY

EXRA EXTR REF ARRAY

REFA REFLECTOR ARRAY

RINS INSULATION

MTGS MOUNTING STRUC

SUPS SUPTG STRUC

FIXM FIXED MOUNT

SADJ SEASON ADJ MOUNT

( 67 )

102
APPENDIX C

CODES/VALUES .FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: HARDELEM (Continued)

Interactive File Where Used: MASTER

TKCM

ENCL

THST

TKCU

SMCV

VSLC

CASK

THIA

STEL

INRT

STMD

STLQ

STRK

IITEX

CLST

STLD

ENTP

LISY

HTRS

PIAS

PUMP

LFIL

VALV

ELIN

AIRS

DUCA

BLOW

AFIL

DAMP

EAIN

TRACKING MOUNT

ENCLOSURE

THERMAL STORAGE

TANK/CONTN UNITS

STOR MED CONTN VL

VESSEL LIN/COAT

GASKETS/SEALANTS

INSULATION ASSY

STRUC ELEMENTS

INT RACKS/TROUGHS

STORAGE MEDIUM

LIQUID

ROCK

HEAT EXCHANGERS

COLLECTOR TO STOR

STORAGE TO LOAD

ENERGY TRANSPORT

LIQUID SYSTEMS

HEAT TRANSFER LIQ

PIPING ASSY

PUMPS

FILTERS

VALVES

INSULATION

AIR SYSTEMS

DUCT ASSY

BLOWERS

FILTERS

DAMPERS

INSULATION

CO NT

LSMC

LCLS

LSEN

LADV

CSFL

CDTC

CSEN

CADV

ETOR

EPRG

CONTROLS

LLD SUP MODE CONT U CONTROL LOGIC SELECTOR

SENSORS (L S)

ACTUATED DEV (L S)

COL/STOR FLOW CONT U DIFF THERMOSTAT CONT

SENSORS (T C)

ACTUATED DEV (T C)

ENERGY TRANS OPRN REGS

PRESSURE REGULATORS

EFRG

SFSC

SPRV

STRV

SEOP

SVRV

FLOW REGULATORS

SSVS FAIL-SAFE CONT

PRES RELIEF VALVES

TEMP RELIEF VALVES

ELEC OVERLOAD PROTEC

VACUUM RELIEF VALVES

103
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: HARDELEM (Continued)

Interactive File Where Used: MASTER

SCVA CHECK VALVES

SADV AUTO DRAINDOWN VALVES

SWHA WATER HAMMER ARRES

SABV AUTO BACKFILL VALVES

SBFP BACK FLOW PREVENTORS

CMPC COMPONENT OPRN CONTS

TMDC TRACKING MOUNT DRIVE CONT!

STHT STOR HEATER THERMOSTAT

AUXE AUXILIARY ENERGY

ARHT INTERNAL W/STORAGE

ITWS RESISTANCE HEATER

ILWS IN LINE W/STORAGE

ILFR FURNACE

ILHP HEAT PUMP

ILBR BOILER

ILRH RESISTANCE HEATER

ILAC AIR CONDITIONER

ILWH HOT WATER HEATER

IPST IN PARALLEL W/STOR

IPFR FURNACE

IPHP HEAT PUMP

IPBR BOILER

IPRH RESISTANCE HEATER

IPAC AIR CONDITIONER

IPDE DEHUMIDIFIER

IPHW HOT WATER HEATER

DIST DISTRIBUTION

CENA CENTRAL AIR TYPE

CSND SINGLE DUCT

CDUD DOUBLE DUCT

CMUL MULTIZONE

CVAV VAR AIR VOLUME

HYDR HYDRONIC/AIR TYPE

HFAN FAN COIL

HIND INDUCTION

HRAD RADIATION

ECON ENERGY CONSER TYPE

EHRL HEAT RECOVERY

EHRC HEAT RECLAIM

EHES ENERGY STORAGE

EHDL DEMAND LIMITER

EHVC VENTILATION CONT

PSYS T SYS INTG W/BLDG

PCSA COL/STOR ARRAY

PCPA COVER PLATE ASSY

PINS COL HT INSUL ASSY

PABS ABS/THER STOR UNIT

104
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: HARDELEM (Continued)

Interactiv,e File Where Used: MASTER

PCON

PACC

PCOL

PAUX

PADI

PSEP

PDIS

PDUC

PDAM

CONTROLS

AIR CIR CONTROLS

COL HT INSUL ASSY

AUXILIARY ENERGY

INTG INTO DIST

COMP SEP CONVN SYS

distribution'

DUCTS

DAMPERS

105
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: MKTPROB

Interactive Files Where Used: MASTER, MiS (64, 72)

A NONE

B MINOR REPAIRS

C MAJOR REPAIRS

D REPLACED MISC. PARTS

E NO MARKETING RETROFIT

F SOLAR FAILED TO MEET EXPECTATIONS

G NUMEROUS SYSTEM SHUTDOWNS

H CONTROL MALFUNCTION

I MINOR ADJUSTMENTS

J REPLACED A MAJOR PART

K OPERATIONAL FAILURE

L HOUSE SOLD FROM MODEL

M SYSTEM INOPERATIVE AT OPEN HOUSE

N INSTALLED AUXILIARY SYSTEM

0 SOLD DURING CONST. NO MKTG

P PRE SOLD NO MKTG

Q HOUSE IS MODEL/TO BE SOLD LATER

R LACK OF INFO AVAILABLE

S HOUSE/BLDG OCCUPIED DURING RETROFIT

T PUBLIC UNFAMILIAR WITH SYSTEM

U INTEREST RATES TOO HIGH

Z MORE INFO IN FILES

106
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: MKTPUBLIC

Interactive Files Where Used: MASTER, MIS (64, 72)

A FAVORABLE, ENTHUSIASTIC

B FAVORABLE, BUT SKEPTICAL

C HOME NOT AESTHETICALLY PLEASING

D PRICE TOO HIGH

E DONT CARE FOR DEVEL/NEIGHD

F NONE TAKEN

G POSITIVE

H NEGATIVE^

I CURIOUS

J MIXED

K SKEPTICAL

L LACKED SOLAR KNOWLEDGE

M CAUTIOUS W/ COST CONCERNS

N CONCERN WITH MAINTENANCE

0 HAD SOLAR KNOWLEDGE

P WANT PERFORMANCE ASSURANCE

Q WANT MORE INFORMATION

R LEERY OF SOLAR

S INTERESTED BUT MONEY NOT AVAILABLE

Z MORE INFO IN FILES
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: MTGPROB

Interactive Files Where Used: MASTER, MIS (63, 72)

A NONE

B HUD 235 LOAN

C HUD COLLEGE HSG LOAN

D HUD LOW INCOME HSG

E RETROFIT

F LOW INCOME PUB. HSG.

G NO MORTGAGE CASH

H HOUSE RENTED/LEASED AT THIS TIME

I HUD SEC. 8 ELDERLY HOUSING

J SELF HELP HOUSING LOAN/HUD FINANCED

K NO MORTGAGE USED UNIVERSITY FUNDS

L MORTGAGE OBTAINED PRIOR TO GRANT , , M GRANTEE HOLDS MORTGAGE

N INT. RATE HIGH/MONEY NOT AVAIL.

Z MORE INFO. IN FILE

108
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: OPERPROB

Interactive Files Where Used: MASTER, MIS (61, 72)

A NO PROBLEM

B WILL NOT ISSUE NON SOLAR CAUSE

C PENDING COMPL. OF CONST.

D PENDING ISSUED WHEN SOLD

F PERMIT NOT REQ . RETROFIT

G PERMIT NOT REQ.

K ADD’L BLDG. MODS REQ.

I INSPECTION VERBAL APPROVAL

Z MORE INFO. IN FILES

109
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Names: SYSMFGR-A, SYSMFGR-G

Interactive Files Where Used; GRANT, MASTER, MIS

ACRN

AIRC

ALBQ

ALSN

ALIB

ALHE

ASFE

AMTH

ASHS

ASKC

AMS I APOL

ARKL

AZTC

BDPC

BEAS

BRAD

BRWN

CDVA

CJAS

CALM

CPTL

CARO

CASA

CBLR

CHBL

CHPN

COLE

COLT

COLU

CNSL

CONS

COEN

CTEM

CREP

CSIS

DAYS

EKSC

ERSB

ENAL

ENCO

ENDY

ENRG

ELTD

FASC

FERN

ACORN STRUCTURES INC

AIR COMFORT INC

ALBUQUERQUE WESTERN

ALL SUN POWER INC

ALLEN IRA BASS

ALTERNATIVE HEAT SYS

AMERAUS SYS/FLEETWOO

AMERICAN HELIOTHERM

AMERICAN SOLAR HEAT

AMERICAN SOLAR KING

AMERICAN SUN IND.

APOLLO SOLAR SYSTEMS

ARKLA INDUSTRIES

AZTEC SOLAR CO

BDP COMPANY

BEASLEY COMPANY

BRADLEY LOREN CO

BROWN MANUFACTURING

C AND D VALVE

C J ASSOCIATES INC

CALMAC MFG

CAPITAL

CAROLINA SOLAR EQUIP

CASAGRANDE CONST CO

CENTRAL BOILERS LTD

CHAMBERLAIN MFG

CHAMPION HOME BLDRS

COLE SOLAR SYSTEMS

COLT INC OF SO CAL

COLUMBI CHASE SOL EN

CONSOLAR INC

CONSOLIDATED WESTERN

CONSUMER ENERGY CORP

CONTEMPORARY SYSTEMS

CREIGHTON SOLAR CONC

CSI SOLAR SYSTEMS

DAYSTAR

E AND K SERVICE CO

EDWIN R SANDERS BLDR

ENERGY ALTERNATIVES

ENERGY CONSERV ENG

ENERGY DYNAMICS CORP

ENERGY RESEARCH GRP

ENGINEERS LTD

FASCO INC

FERN ENGINEERING CO

( 56 , 58 , 71 )

110
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Names: SYSMFGR-A, SYSMFGR-G (Co

Interactive Files Where Used: GRANT, MASTER,

FILN FILON DIVISION

FLAG FLAGALA CORP

FLET FLETCHER MYERS

FLPR FLOW PRODUCTS INC

FOXS FOX STEEL CO

FRED FRED RICE PROD

FRON FRONTIER DEVELOPMENT

FUSY FUTURE SYSTEMS INC

GENE GENERAL ELECTRIC

CEDE GENERAL ENERGY DEVIC

GNSO GENERAL SOLARGENIC

GSUN GENERAL SUN

GNSS GNS SOLARWALL

GRIP GRIEP HEATING

GRUM GRUMMAN ENERGY SYS

GULF GULF THERMAL

HALS HALSUN SOLAR ENG

HEFR HEFRON SOLAR SYSTEMS

HLIO HELIO THERMICS

HDYN HELIODYNE

HELP HELIOPHASE

HTRM HELIOTHERM INC

HECL HEX CELL

HYPE HYPERION INC

ILSE ILSE ENGINEERING INC

ITEC INTERTECHNOLOGY

lENV INTL ENVIRONMENT

ISOL INTL SOLARTHERMICS

JACK JACKSON

KALW KALWALL

KENN KENNECOTT COPPER

KENW KENWALL CORPORATION

KTAC KTA CORP

LARG LARGO SOLAR SYS INC

LENX LENNOX-HONEYWELL

LOFC LIBBY OWENS FORD CO

MIRO MIROMIT

NENG NATIONAL ENERGY CORP

NESC NATIONAL ENERGY SYST

NSOL NATIONAL SOLAR CORP

NUTS NATURAL ENERGY CORP

NENW NATURAL ENERGY WKSHP

NORT NORTHRUP

NRGL NRG LTD

NRGM NRG MANUFACTURING

NPTD NTL PATENT DEVELOP

ntinued)

MIS

111
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Names: SYSMFGR-A, SYSMFgR-G (Continued)

Interactive Files Where Used: GRANT, MASTER, MIS

OCON OCON INDUSTRIES INC

OLIN OLIN BRASS

OVER OVERLY MANUFACTURING

OWEN OWENS ILLINOIS

PARK PARK ENERGY

PAYN PAYNE AIR CONDITION

PION PIONEER ENERGY PROD.

PIPR PIPER HYDRO INC

PLIN PLEIAD INDUSTRIES

PPGI PPG INDUSTRIES

PPIE PPG/INT ENVIR

PRSH PRACTICAL SOLAR HEAT

RMPR R M PRODUCTS

RALS RALEIGH SOLAR SYSTEM

RAYP RAYPAK

REFR REFRIGERATION RESERC

REPC RESEARCH PRODUCTS

REVE REVERE

REYN REYNOLDS

RICK RICKER MANUFACTURING

ROCK ROCKY MOUNTAIN PROD

ROMA ROM-AIRE

SATL SCIENTIFIC-ATLANTA

SEEN SEECO BINKLEY

SMSP SEMCO SOLAR PRODUCTS

SHAL SHALLA CORP

SHEL SHELDAHL

SITE SITE BUILT

SKYT SKYTHERM

SOFA SOLAFERN LTD

SOHT SOLAHART

SLAP SOLAPAK

SACC SOLAR ACCESS INC

SLCN SOLAR CENTRAL

SCOM SOLAR COMFORT INC

SDVL SOLAR DEVELOPMENT

SDEV SOLAR DEVICES

SELI SOLAR ELECTRI C INTL

SENC SOLAR ENERGY CORP

SENI SOLAR ENERGY INC

SEPR SOLAR ENERGY PROD

SERC SOLAR ENERGY RESEARCH

SEST SOLAR ENERGY STRUCT

SEEQ SOLAR ENERGY & EQUIP

SNGY SOLAR ENERGYTICS INC

SENG SOLAR ENGINEERING

112
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Names: SYSMFGR-A, SYSMFGR-G (Continued)

Interactive Files Where Used: GRANT, MASTER,

SENT SOLAR ENTERPRISES

S F RM SOLAR FARMS

SLUG SOLAR HEAT CORP

SLHT SOLAR HEAT INC

SHST SOLAR HEATING SYST

SHOM SOLAR HOMES INC

SliSG SOLAR HOUSING INC

SLHY SOLAR HYDRO INC

SINC SOLAR INC

SIOF SOLAR IND OF FLORIDA

SINN SOLAR INNOVATIONS

SLfCN SOLAR KINETICS CORP

SKIN SOLAR KING

SHFG SOLAR MANUFACTURING

SOLI SOLAR ONE

SPAS SOLAR PACKAGE STRUCT

SPST SOLAR PROD SUN TANK

SORE SOLAR RESEARCH

SLRM SOLAR ROOM CO

SSEV SOLAR SEVEN IND

SSHL SOLAR SKELTER

SSTR SOLAR STOR

SUNS SOLAR SUN

SSVA SOLAR SYST OF VA

SSSD SOLAR SYST SUNDANCE

SSEN SOLAR SYSTEM EKTERP.

SSII SOLAR SYSTEMS INT

SOTri SOLAR THERM

SOUL SOLAR UNLIMITED INC

SOLA SOLARA

SRAY SOLARAY

SCEL SOLARCELL

SCOA SOLARCOA INC

SLIN SOLAREIN

SGEN SOLARGENICS

SRI3 SOLARIS

SLMR SOLARMASTER

SMAT SOLARMaTIC

SROL SOLAROLL

SRON SOLARON

SOTC SOLARTEC

SOTR SOLARTRONICS INC

SAIR SOLAR-AIRE

SLR A SOLA-RAY

SOLC SOLCAN

SRGY SOLERGY INC

113
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Names; SYSMFGR-a, SYbliFUR-o (Continueu;

Interactive Files Where Used: GRANT, iiASTi:.R, nib

SLOP

SOLP

SOLW

SWET

SPEC

SRWI

SSSI

SSPA

SSCO

STIN

STOR

SCFT

SUDS

SNFL

SIIAR

SUPC

SUPO

SPIN

SPSY

SURE

SSYS

SNBL

SBUR

SNLL

SEAR

SPOW

SUFO

SLPO

SUMA

SNSV

SNSR

SNUT

SSTN

SNST

SNTP

SUNW

SWAT

SWOR

SUIIE

TREK

TESO

TECH

TOMS

TRAN

TRSI

UNCO

SOLOP CORP

SOLPOWER INDUSTRIES

SOLWIN INDUSTRIES

SOUTH WEST ENER-TECh

SPECTRA ENERGY SYS

SRW INC

SS SOLAR INC

SSP ASSOC

STANDARD SOLAR COLL

STATE INDUSTRIES

STORAGE ONLY

SUN CRAFT

SUN DESIGN

SUN FLOW

SUN HARVESTER CORP

SUN PAC

SUN POWER CORP

SUN POWER INDUSTRIES

SUN POWER SYSTEMS

SUN RAY SOLAR EQUIP

SUN SYSTEMS INC

SUNBLAZER SOLAR FURN

SUNBURST

S Li N C E L L

SUNEARTH

SUNENERGY POWER LTD

SUNFLOWER SOLAR INC

SUNLIGHT & POWER CO

SUNMASTER CORP . SUNSAV INC

SUNSAVER

SUNSHINE UTILITY CO

SUNSTONE

SUNSTREAM

S UNTAP INC

SUNWALL INC

SUNWATER

SUNWORKS

SUN-HEET

TECHNITREK CORP

TELLURIDE SOLAR WORK

THERMAL TECH

THOMASON

TRANTER

TRITEC SOLAR INDUSTR

UNION CO CORRECTIONL

114
appendix c CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Names; SYSMFGR-A, SYSMFUR-G (Continued)

Interactive Files Where Used: GRANT, MASTER, hid

USSC

UNSP

USIN

VEST

WEAT

WEST

WSDl

WHIT

WILX

WILC

WYSO

YING

ZIEN

ZORK

ZZZZ

UNITED STATES SOLAR

UNSPECIFIED

US INSTALLATIONS

VALMONT ENERGY SYSTE

WEATHER KING

WESTERN ENERGY INC

WESTERN SOLAR LEVEL

WHITE LINE INC

WILCOX MFG & DISTR

WILSON CORPORATION

WYOMING SOLAR

YING Manufacturing

ZIEN

ZOMEWORKS

ZZZZZZ - end OF LIST

115
APPENDIX C

CODES/VALUES FOR CERTAIN DATA ELEMENTS (Continued)

Data Element Name: ZONPROB

Interactive Files Where Used; MASTER, hIS ('(SI. 72)

A NO PROBLEM

B DOES NOT CONFORM SOLAR CAUSE

C DOES NOT CONFORM NON SOLAR CAUSE

D "SUN RIGHTS"

F PERMIT NOT REQ. RETROFIT

G PERMIT NOT REQ.

H ADD'L BLDG. MODS REQ.

I PREVIOUSLY ZONED

Z MORE INFO. IN FILES

116
APPENDIX D

MIRADS COMPUTER SESSIONS

Introduction

Appendix D contains actual MIRADS computer sessions. Each

example shows how MIRADS commands, discussed in chapters 3

and A of the text, are used in the context of actual MIRADS

queries*'; Data elements from the MIS (Management Information Summary) File were used in these examples.

Examples 1 through 13 are discussed in chapter 3 and

examples 14 through 17 are discussed in chapter 4 of the

text. Page numbers in the right margin of each example

reference the page of text that discusses the variation

of the MIRADS command being illustrated in the example.

Each computer session, was produced directly at a 300 baud.

Anderson Jacobson AJ832 terminal

"daisy" print wheel and a carbon

using an interchangeable

ribbon.

117
APPENDIX D

MIRADS COMPUTER SESSIONS

Example 1« Simple QUERY Command a4)

READY

>Q ENDSALEPRICE P

READY

>P PJNO ENDSALEPRICE

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

[

FILE CONTAINS 678 RECORDS

QUERY SELECTED 505 RECORDS

ENTER OUTPUT REPORT SITE ID

>PRINT 5

Q ENDSALEPRICE P

P PJNO ENDSALEPRICE

This is a warning message

only and can be ignored.

One of the data elements

queried was not designated as "indexed" and

therefore a sequential

search through the file

for matches is necessary.

PJNO ENDSALEPRICE

21501 102000

21502 72000

21504 0

21505 78500

21507 76000

Refer to Example 14, " Processing

a Query and Saving a Query Set ",

for computer sign-on procedure.

Example 2

QUERY Command with Alpha Qualifier (16)

READY

> Q PJCITY EQ BALTIMORE

READY

>P PJNO PJCITY

READY

>RUN

QUERY NOW PROCESSING

FILE CONTAINS 678 RECORDS

QUERY SELECTED 2 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q PJCITY EQ BALTIMORE

P PJNO PJCITY

PJNO PJCITY

23098 BALTIMORE

24043 BALTIMORE

118
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 3. QUERY Connnand With Numeric Qualifier ( 16)

READY

>Q COLSQFT-G GE 10000

READY

>P PJNO COLSOFT-G

READY

>RUN

QUERY NOW PROCESSING

FILE CONTAINS 678 RECORDS

QUERY SELECTED 3 RECORDS

ENTER OUTPUT REPORT SITE ID

>Q COLSQFT-G GE 10000

P PJNO COLSQFT-G

PJNO COLSQFT-G

22041 11270

24115 10206

28106 10080

Example 4. QUERY Command Using Data Element Qualifier (16)

READY

>Q CFIN-YM = *MTGAPP-YM AND GT 0

READY

>P PJNO CFIN-YM MTCAPP-YM

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 14 RECORDS

ENTER OUTPUT REPORT SITE ID

>PRINT 4

Q CFIN-Ylvf = *MTGAPP-YM Al\iD GT 0

P PJNO CFIN-YM MTGAPP-YM

PJNO CFIN-YM MTGAPP-YM

21511 7 508 7508

21548 7606 7606

22001 7704 7704

22003 7005 7005

119
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 5. QUERY Command Using ^AND'* Connector

READY

>Q PJSTATE EQ VA AND COLSQFT-G GT 500 AND LT 10000

READY

>P PJNO PJSTATE COLSQFT-G

READY

>RUN

QUERY NOW PROCESSING

FILE CONTAINS 678 RECORDS

QUERY SELECTED 6 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q PJSTATE EQ VA AND COLSQFT-G GT 500 AND LT 10000

P PJNO PJSTATE COLSQFT-G

PJNO PJSTATE COLSQFT-G

21510 VA 640

23133 VA 2743

24034 VA 5713

24153 VA 674

28182 VA 826

28230 VA 508

( 17 )

120
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 6. Descending SORT Command (18)

READY

>Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

READY

>S ENDSALEPRICE D

READY

>P PJNO CONST-YM ENDSALEPRICE

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 24 RECORDS

ENTER OUTPUT REPORT SITE ID

>PRINT 10

Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

S ENDSALEPRICE D

P PJNO CONST-YM ENDSALEPRICE

PJNO CONST-YM ENDSALEPRICE

23087 7908 119900

24153 8001 106703

24040 8002 105000

24032 7904 92185

24143 7905 89400

24136 7906 78500

24196 7908 76000

24025 7908 71900

24192 7906 64500

23147 7905 59500

121
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 7. Compound SORT Command ( 18 )

READY

>Q PJSTATE EQ MD OR VA OR DC

READY

>S CYCLE A PJNO D

READY

>P CYCLE PJNO PJSTATE

READY

>RUN

QUERY NOW PROCESSING

FILE CONTAINS 678 RECORDS

QUERY SELECTED 39 RECORDS

ENTER OUTPUT REPORT SITE ID

>PRINT 18

Q PJSTATE EQ MD OR VA OR DC

S CYCLE A PJNO D

P CYCLE PJNO PJSTATE

CYCLE PJNO PJSTATE

PI 28231 VA

PI 28230 VA

PI 28227 VA

PI 28205 VA

PI 28182 VA

PI 28173 VA

PI 28123 MD

PI 28114 VA

PI 28113 VA

1 21536 VA

1 21533 VA

1 21510 VA

2 22092 VA

2 22085 DC

2 22063 MD

3 23137 MD

3 23133 VA

3 23098 MD

122
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 8. COMPUTE Command Using ’NONE* Break-Field (IS'

READY

>Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

READY

>C NONE $TOTPRICE = Sum ENDSALEPRICE.

READY

>P PJNO CONST-YM ENDSALEPRICE $TOTPRICE

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 21 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

C NONE $TOTPRICE = SUM ENDSALEPRICE.

P PJNO CONST-YM ENDSALEPRICE $TOTPRICE

PJNO CONST-YM ENDSALEPRICE TOTPRICE

21530 7903 32000

22071 7905 51930

23008 7909 25900

23060 7907 26325

23071 7903 29600

23087 7908 119900

23098 7901 47646

23147 7905 59500

24006 7903 17133

24021 7903 20800

24025 7908 71900

24031 7902 22575

24032 7904 92185

24037 7905 24000

24122 7909 42000

24136 7906 78500

24137 7903 21600

24139 7906 46600

24148 7905 51900

24153 8001 106703

24196 7908 76000 1064697

123
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 9. COMPUTE Command Using '^ALl!.'* Break-Field (l 9

)

READY

>Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

READY

>C ALL $AVGESTCOS = SYSCOSTEST/GRSYS

READY

>S CYCLE

PEADY

>P CYCLE PJNO CONST-YM SYSCOSTEST GRSYS SAVGESTCOS

READY

>RUN

QUERY NOW PROCESSING

WAP13ING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 24 RECORDS

ENTER OUTPUT REPORT SITE ID

>PRINT 15

Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

C ALL $AVGESTCOS = SYSCOSTEST/GRSYS.

S CYCLE

P CYCLE PJNO CONST-YM SYSCOSTEST GRSYS $AVGESTCOS

CYCLE PJNO CONST-YM SYSCOSTEST #SS AVGESTCOS

1 21530 7903 12210 3 4070

2 22071 7905 7500 5 1500

3 23008 7909 18198 8 2275

3 23060 7907 38000 5 7600

3 23071 7903 6422 2 3211

3 23087 7908 169453 2 84727 . 3 23098 7901 95810 15 6387

3 23147 7905 89859 6 14977

4 24006 7903 35496 4 8874

4 24021 7903 8874 1 8874

4 24025 7908 11746 1 11746

4 24031 7902 4241 1 4241

4 24032 7904 27106 2 13553

4 24037 7905 8874 1 8874

4 24040 8002 14875 1 148 75

NOTE

The 'All ' Break-Field element has no real value when using

the SUM er COUNT options since the subtotal or CGUN'i woul(

reported and reinitialized for each record processed.

124
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 10. COMPUTE Conunand Using Name Break-Field (19)

READY

>Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

READY

>C CYCLE $TOTPRICE = SUM ENDSALEPRICE.

READY

>S CYCLE

READY

>P CYCLE PJNO CONST-YM ENDSALEPRICE $TOTPRICE

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 24 RECORDS

ENTER OUTPUT REPORT SITE ID

>PRINT 15

Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

C CYCLE $TOTPRICE = SUM ENDSALEPRICE.

S CYCLE

P CYCLE PJNO CONST-YM ENDSALEPRICE $TOTPRICE

CYCLE PJNO CONST-YM ENDSALEPRICE TOTPRICE

1 21530 7903 32000 32000

2 22071 7905 51930 51930

3 23008 7909 25900

3 23060 7907 26325

3 23071 7903 29600

3 23087 7908 119900

3 23098 7901 47646

3 23147 7905 59500 308871

4 24006 7903 17133

4 24021 7903 20800

4 24025 7908 71900

4 24031 7902 22575

4 24032 7904 92 185

4 24037 7905 24000

4 24040 8002 105000 353593

125
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 11. COMPUTE Conmand UsinR Algebraic Express!

READY

>Q CONST-YM GE 7901 AND ENDSALEPRICE GT 0

READY

>C NONE $TOTPRICE = SUM ENDSALEPRICE.

READY

>C NONE $CNTPRICE = COUNT ENDSALEPRICE.

READY

>C NONE $AVGPRICE = $TOTPRICE/$CNTPRICE.

READY

>P $CNTPRICE $T0TPRICE $AVGPRICE

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 24 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q CONST-YM GE 7901 AliD ENDSALEPRICE > 0

C NONE $TOTPRICE = SUM ENDSALEPRICE.

C NONE $CNTPRICE = COUNT ENDSALEPRICE.

C NONE $AVGPRICE = $TOTPRICE/$CNTPRICE.

P $CNTPRICE $TOTPRICE $AVGPRICE

CNTPRICE TOTPRICE

24 1323597

( 20 )

AVGPRICE

55150

126
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 12. PRINT Command Using Numeric Output Ligiit (21)

READY

>Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

READY

>P 10 PJSTATE PJNO CONST-YM ENDSALEPRICE

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 10 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

P 10 PJSTATE PJNO CONST-YM ENDSALEPRICE

PJSTATE PJl^O CONST-YM ENDSALEPRICE

CA 21530 7903 32000

NC 22071 7905 51930

CO 23008 7909 25900

WI 23060 7907 26325

NY 23071 7903 29600

IL 23087 7908 119900

MD 23098 7901 47646

NE 23147 7905 59500

OK 24006 7903 17133

OK 24021 7903 20800

127
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 13. PRINT Command Using 'SUM* Output Limit- (21)

READY

>Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

READY

>C CYCLE $CNTPRICE = COUNT ENDSALEPRICE.

READY

>C CYCLE $TOTPRICE = SUM ENDSALEPRICE.

READY

>S CYCLE

READY

>p sum; cycle $cntprice $totprice

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 24 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q CONST-YM GE 7901 AND ENDSALEPRICE > 0

C CYCLE $CNTPRICE = COUNT ENDSALEPRICE.

C CYCLE $TOTPRICE = SUM ENDSALEPRICE.

S CYCLE

P SUM CYCLE $CNTPRICE $TOTPRICE

CYCLE CNTPRICE TOTPRICE

12

34

4A

1

16

79

32000

51930

308871

353593

577203

NOTE: The 'SUM' option in the PRINT command' above is used in

conjunction with the COMPUTE commands calculating

$ CNTPRICE and $TOTPRICE. This option will suppress the

printing of all records except the record at a time when

a new-variable is to be printed ($CNTPRICE or $TOTPRICE)

Both $ CNTPRICE and $ TOTPRICE were computed on the 'Name'

break-field, CYCLE, therefore they were computed for each

CYCLE only.

128
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 14. Processing a Query and Saving a Query Set ( 25

)

PLEASE ENTER HOST ID(I/B)>

OMNUS PORT 46. PARITY (E/O/N) ? > ENTER USERID /PAS SWORD:

*DESTROY USERID/PASSWORD ENTRY

*UNIVAC 1100 OPERATING SYSTEM VER. 33R3A (RSI)*

The valid userid/

password has been

obscured to maintain

privacy.

LAST RUN AT: 060480 140801

DATE: 060480 TIME: 141606

>(aMIRADS,NB

ENTER QUALIFIER*FILENAME

>SOLAR*MIS

READY

>Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

READY

>SAVEC PRICERANGE

READY

>S ENDSALEPRICE D

READY

>C NONE $TOTPRICE = SUM ENDSALEPRICE.

READY

>C NONE $CNTPRICE = COUNT ENDSALEPRICE.

READY

>C NONE $AVGPRICE = $TOTPRICE/$CNTPRICE.

READY

> PPJNO CCNST-Yl-1 ENDSALEPRICE $T0TPRICE $CNTPRICE $AVGPRICE

READY

>SAVE AVGPRICE

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 8 RECORDS

ENTER OUTPUT REPORT SITE ID

>

NOTE:

RUN NUMBER 83

129
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 14 (continued)

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

S ENDSALEPRICE D

C NONE $TOTPRICE = SUM ENDSALEPRICE.

C NONE $CNTPRICE = COUNT ENDSALEPRICE.

C NONE $AVGPRICE = $TOTPRICE/$CNTPRICE.

P PJNO CONST-YM ENDSALEPRICE $TOTPRICE $CNTPRICE $AVGPRICE

PJNO CONST-YM

AVGPRICE

ENDSALEPRICE TOTPRICE CRTPkICE

23087 7908 119900

24032 7904 92185

24136 7906 78500

24196 7908 76000

24025 7908 71900

23147 7905 59500

22071 7905 51930

24148 7905 51900 601815 8

75227

130
(9

APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 15. Editing and Processing a Saved Query Set (26)

READY

>DI SPLAY AVGPRICE

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

S ENDSALEPRICE D

C NONE $TOTPRICE = SUM ENDSALEPRICE.

C NONE $CNTPRICE = COUNT ENDSALEPRICE.

C NONE $AVGPRICE = $TOTPRICE/$CNTPRICE.

P PJNO CONST-YM ENDSALEPRICE $TOTPRICE $CNTPRICE $AVGPRICE

READY

>EDIT AVGPRICE

ENTER EDIT COMMAND

>T

000:

>N

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

001 : >C /50000/70000/

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 70000

001

:

>EXIT

READY

>DO AVGPRICE

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 5 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 70000

S ENDSALEPRICE D

C NONE $TOTPRICE = SUM ENDSALEPRICE.

C NONE $CNTPRICE = COUNT ENDSALEPRICE.

C NONE $AVGPRICE = $TOTPRICE/$CNTPRICE.

P PJNO CONST-YM ENDSALEPRICE $TOTPRICE $CNTPRICE $AVGPRICE

PJNO CONST-YM

AVGPRICE

ENDSALEPRICE TOTPRICE CNTPRICE

23087 7908 119900

24032 7904 92185

24136 7906 78500

24196 7908 76000

24025 7908 71900 438485 5

87697

131
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 16. Adding a Saved Fragment (31)

READY

>ADD PRICERANGE

READY

>S ENDSALEPRICE D

READY

>P PJNO PJSTATE ENDSALEPRICE CONST-YM

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 8 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

S ENDSALEPRICE D

P PJNO PJSTATE ENDSALEPRICE CONST-YM

PJNO PJSTATE ENDSALEPRICE CONST-YM

23087 IL 119900 7908

24032 CT 92185 7904

24136 MN 78500 7906

24196 IN 76000 7908

24025 MA 71900 7908

23147 NE 59500 7905

22071 NC 51930 7905

24148 GA 51900 7905

132
APPENDIX D

MIRADS COMPUTER SESSIONS (Continued)

Example 1/. Addins To a Saved Fragment (31)

READY

>ADD PRICERANGE

READY

>AND LE 95000

READY

>S ENDSALEPRICE D

READY

>P PJNO PJSTATE ENDSALEPRICE CONST-YM

READY

>RUN

QUERY NOW PROCESSING

WARNING - QUERY FORCES SEQUENTIAL SEARCH

FILE CONTAINS 678 RECORDS

QUERY SELECTED 9 RECORDS

ENTER OUTPUT REPORT SITE ID

>

Q CONST-YM GE 7901 AND LE 7912 AND ENDSALEPRICE > 50000

AND LE 95000

S ENDSALEPRICE D

P PJNO PJSTATE ENDSALEPRICE CONST-YM

PJNO PJSTATE ENDSALEPRICE CONST-YM

24032 CT 92185 7904

24143 IL 89400 7905

24136 MN 78500 7906

24196 IN 76000 7908

24025 MA 71900 7908

24192 AR 64500 7906

23147 NE 59500 7905

22071 NC 51930 7905

24148 GA 51900 7905

133
REFERENCES

1. Computer Sciences Corporation, MIRADS User’s Manual

Prepared for the National Aeronautics and Space

Administration, MA-010-001-2H (Marshall Space Flight

Center, Alabama, May, 1977).

Available from:

Computer Services Division

Room A-22, Administration Building

National Bureau of Standards

Washington, D.C. 20234

2 . User's Manual for Online Retrieval of Grant Applica - tion Data , Institute for Computer Sciences and

Technology, National Bureau of Standards, Planning

Report Number 5 (Washington, D.C., August, 1977).

3 . User's Manual for Online Retrieval of Grantee Report

Data , Solar Data Center, National Bureau of Standards

Report Number 3 (Washington, D.C., October, 1978).

4. Christopher, Patricia M. and Krzewick, Joan E.,

Residential Solar Data Center Data Resources and

Reports , National Bureau of Standards Interagency

Report 79-1762 (Washington, D.C.: National Bureau

of Standards, June, 1979).

5. Christopher, Patricia M. and Aronoff, Martin J.,

Residential Solar Data Center Grant Reports , National Bureau of Standards Interagency Report

79-1923 (Washington, D.C.: National Bureau of

Standards, issued October, 1979).

6. Christopher, Patricia M. , So3.ar Data Dictionary / Directory , National Bureau of Standards, NBSIR 80-

(Draft), Prepared for the United States Department

of Housing and Urban Development, October, 1980

(anticipated)

.

7. Computer Sciences Corporation, MIRADS Implementation

Manual , Prepared for the National Aeronautics and

Space Administration,

134
NBS-H 4A I R fc. V. .1 7b)

U.S. DEPT. OF COMM.

BIBLIOGRAPHIC DATA

SHEET

1. PUBLICATION OR REPORT NO. NBSIR 80-2144

2.Gov’t. Accession No. 3. Recipient's Access ipn No.

4. TITLE AND SUBTITLE

Residential Solar Data Center MIRADS User's Guide

5. Publication Date October 1980

6. Performing Organization Code

7. AUTHOR(S) Patricia M. Christopher i tt 1

1

Michael Vogt

Hall

8. Performing Organ. Report No.

9. PERFORMING ORGANIZATION NAME AND ADDRESS

NATIONAL BUREAU OF STANDARDS

DEPARTMENT OF COMMERCE

WASHINGTON, DC 20234

10. Project/Task/Work Unit No.

11. Contract/Grant No.

12. SPONSORING ORGANIZATION NAME AND COMPLETE ADDRESS rsrreer. cuy, state, ZIP)

Department of Housing and Urban Development

Division of Energy, Building Technology and Standards

Washington, D.C. 20410

13. Type of Report & Period Covered

Final

14. ^jopsoring Agency Code

15. SUPPLEMENTARY NOTES

r 1 Document describes a computer program; SF-185, FIPS Software Summary, is attached.

16. ABSTRACT (A 200-word or less (actual summary of moat significant information. If document includes a significant bibliography or

literature survey, mention it here.^

The Residential Solar Data Center Project staff in the Center for Building

Technology, National Bureau of Standards, maintains a computerized data base

containing non-ins trumented residential data from the DoE/HUD Solar Heating and

Cooling Demonstration Program. Data contained in the solar data base are accessible

online to users of the NBS Center Computer via remote terminals with a data base

retrieval software package called MIRADS (Marshall information Retrieval ^nd Msplay

System). This document is a self-teaching user’s guide to the solar data base. It

is complete with the basic MIRADS language rules, examples of use, and a step-by-step

walk-through of a typical interactive session. Appendices contain all the data

element names and coded values needed to use the solar data with MIRADS, as well as many examples of actual computer sessions.

17, KEY WORDS (six to twelve entries; alphabetical order; capitalize only the first letter of the first key word unless a proper name;

separated by semicolons)

Automatic data processing; computer retrieval; data base retrieval; residential

buildings; solar data base; solar energy system; solar heating and cooling.

18. AVAILABILITY [^Unlimited

For Official Distribution. Do Not Release to NTIS

I Order From Sup. of Doc., U.S. Government Printing Office, Washington, DC

20402, SD Stock No. SN003-003-

[X] Order From National Technical Information Service (NTIS), Springfield, VA. 22161

19. SECURITY CLASS

(THIS REPORT)

UNCLASSIFIED

20. SECURITY CLASS

(THIS PAGE)

UNCLASSIFIED

21. NO. OF

PRINTED PAGES

143

2?. Price

$ 10.00

USCOMM-DC
W'.'

* r :

- m»«>

< tr/-‘ f

, ...?,r J'xa»3.4 j

r’i

jvVj’J'' I .fcluC-3 '•li T’VSO .f.V At/>0 7(H1A^00U<IS

Ti3H;

-4

. •« ttO 4 ' wfc',',

‘

i

3Jf\

.' '^*•5 ^ .'».iT(T

« ' ‘iff-y.' t'*3c»Cf lA- ’•

r».« ;v n.'A

,'i i •T—"' ^ j3^“' ''SisUf '^4

/

• wA r 2 no <jA3*ui.'' -• 'io'it4

^ DW3#(W*»'^0 to ^

it.t ':<t; r>o ,>?o' ,i*it

'

. v.iXrJ'

Jf ‘ luQ'sf’’ 'Nj -*',rvl -fti 21

C..: ;:j V :A

.... : n^or-A

••'

' <W«^ Ilf d‘ »

' g% jiff ^

- h !ut* v:v3 lc«i/t{>«l jAibl )'.»'d , v:ftX#»2^Tto n —»>1

. »T s c i »!»«!' A

/J C Anc ii t mA

V*: i j

«.' f , V .1.

•. •; '.iaH tol 'V«5.':V:.'' itti ft* 1 ‘iJKSV TtS^v •••*aaw tiJwJ tr ;

^3xi:^J.5a.^c. 4. ,tt&iafc0«5E 'lo uBft.w- ^f"

''

.M,,- -C'®;. a r:iM, hlKU.Alri fcW

^ rfj < ««•'

•Uxu‘

* A ikio'd uft':? C3 '"'.liJ;ii t

. ’ aw

'’ 30! .40Wii-*5Xs.!« • - - «iriT *J

ai .^t a/tkaru i^^ff .^rt 1

, Z, ^ I' ‘

.

•* •>• * W '— »4 ^ V -* i. V

-.4 ' * *' ^

'

•'-r.'r,t-i '. fy^di to r-.XQB>.av.5» » 613X4;^. BGA^IM 9lA^ ' *.^4

.'J .. •,".? !, '..A.R.t?J.

foiAAfii**- 1A jth'fl'C i *« .>CloQ 4.i ;

“. 'i».k /ot.,|f: v 3

':^> . f .«

..'A

1 » I !

.

. ,: .VI t u jkts [

. .. j '.. : .x" j » t ^ sT,; V * I « ti J f l,h # : ' I,. ;.. in? ,1 :: v, t ? i

‘ '. . ti ’•) r 1 to .. ;•*» J

<>

., .1 . li t ,

" » .'.X, u 1

';y

- :i - 'ft

lAiJrib^iaS'S' ; t.'"'

. ^ ;'X*« .' :s

.<> r„, fv.yt 'V'tw ^>t»k k<... * ' •' ’!'<• - •’ *‘'’' ' •' ^

' ' ;, '• 4 if'^ '1 1. . ‘\ A 4 .' 1

•..-f. ; .sjiAi- 0.|Fb-“siti3.'.

rAiya ,,rta3«\;« vjxsiTs ‘spIcb J ej^. . 1 -

0

~ 3W . / '^’*

> (

i

4)|l^

.-/a* > yfF^Ti ' ,!

'i. nO'X'i>’

t . ( I , .1

T'-'’.j.o V

I

( j».' • ^

j..''

.

. 'YTUieM.'^s|A Jf

i. I T H a! ' fX' i-iJi fart oO rtBtfwJf<>« rtJ lu otftO

I ,'.. vs** .J .‘i0 »^»i.*'<(’'‘^ lir.wiMt'1..

~', "t ‘I ,. a«9 >0 .t>»^ WV' I