ML19308B762
| ML19308B762 | |
| Person / Time | |
|---|---|
| Site: | Crane  |
| Issue date: | 05/30/1977 |
| From: | Kuffner A EG&G, INC. |
| To: | |
| References | |
| TASK-TF, TASK-TMR ERDA-76-45-10, SSDC-10, NUDOCS 8001170256 | |
| Download: ML19308B762 (38) | |
Text
ERDA 76-45/10 ssDC-10 O
SAFETY INFORMATION SYSTEM CATALOGING SYSTEM SAFET /
PEVELOPMENT CENTER b
T J
0
& ERDA 94 EGsG l"$ $1;[
P00R~0RIGlHAL l
MAY 1977 UNITED STATES i
ENERGY RESEARCH AND DEVELOPMENT ADMINISTRATION f
O l
DIVISION OF OPERATIONAL AND ENVIRONMENTAL SAFETY l
8001170 2.5g
i
}
4 4
(
i9 j
ERDA 76-45/10 i
ssoc-10 UC-41 i
l i
l SAFETY INFORMATION SYSTEM CATALOGING l
l l
Prepared By I
A. R. Kuffner i
Work Performed At EG&G IDAHO, INC.
i IDAHO OPERATIONS OFFICE
-Under Contract No. EY-76-C-07-1570-l l
l l
I j
May 1977 l
!O i
i
O\\
ACKNOWLEDGMENT Special acknowledgment is due to Dr. Robert J. Nertney for his helpful guidance, to Della T. Kellogg' for her editorial assistance, and to Joann Walker for drafting the logic tree.
l O
ii 1
O GLOSSARY Catalog: A list of vocabulary words which are systematically grouped.
Computer Stores:
Information recorded in the computer which can be drawn from as needed.
Data: Detailed information of any kind.
Data Base: The accumulation of data on which an information system is built.
Hardware: The electronic equipment used in association with data processing.
Input:
Information fed into a computer.
Key Word: A word affording a means of access to a particular part of the total data base.
Output:
(1) The information fed out of a computer; (2) The recording or printing device or its product to which such information is transferred.
Software: Any of the written programs, flow charts, etc., that may be inserted in computer programs.
Taxonomy: The systematic classification of vocabulary within a subject field.
Vocabulary: The set of words employed by a language, group, individual, or work, or in relation to a subject.
l i
l s
l iii
CONTENTS O
ACKNOWLEDGMENT...........................
ii GLOSSARY.............................. iii 1
I.
INTRODUCTION II. THE CATALOGING TREE......................
4 1.0 DETERMINE THE DESIRED OUTPUTS OF THE SYSTEM 4
1.1 Determ.ne Desired Output to ERDA and 4
ERDA C(ntractors A.1 Survey Needs of Entire Range of 4
Perconnel A.2 Assign Priorities to Results of Survey.....................
10 A.3 Select Needs Which Can and Should Be Addressed..................
12 1.2 Determine Desired Output to External Organizations......
12 2.0 DETERMINE THE VOCABULARY REQUIRED TO PRODUCE THE DESIRED OUTPUT................
13 2.1 Specify Individual Output..............
13 2.2 Identify Vocabulary Requirements 14 of Specified Output...
14 2.2.1 Topic 2.2.2 Vocabulary and Key Words...........
15 2.2.3 Audience.
15 2.2.4 Format....................
15 j
2.2.5 Location ( f Input Da ta............
15 2.2.6 Retrieva' of Input Data 16 2.2.7 Analytical Procedures 16 2.2.8 Compilation of Output 16 2.2.9 Communication of Output 16 iv
(-
CONTENTS (cont.)
2.3 Include Selected Elements in System 17 Vocabulary 3.0 CATALOG THE REQUIRED VOCABULARY 17 B.1 Survey / Utilize Existing Vocabulary As Applicable....................
17 B.l.1 Survey....................
17 i
B.l.2 Select Applicable Terms and Classifications 18 J
B.1.3 Include in System Taxonomy.........
18 B.2 Develop New Segmen.c.s of Taxonomy 18 Where Needed B.2.1 Select Terms Not Included in Existing Catalog...............
18 4
B.2.2 Arrange Under General Headings........
18 B.2.3 Add to Existing Vocabulary and s--
Classifications 18 B.3 Impose Desired Logical Arrangement on Vocabulary and Catalogs...............
19 B.3.1 Key Words 19 B.3.2 Thesaurus 19 B.3.3 General Classifications 19 i
B.3.4 Hardware Requirements 20 B.3.5 Software Requirements 20 B.4 Prepare Written Taxonomy on Procedures fo r General Us e...................
20 B.4.1 Prepare a Draft 20 B.4.2 Distribute Draft for Review by Selected Personnel..............
20 i
i B.4.3 Prepare Revision...............
20 f
v i
t
CONTENTS (cont.)
8.4.4 Publish Taxonomy...............
21 B.4.5 Distribute to Appropriate Personnel 21 4.0 APPLY TAXONOMY TO EXISTING AND INCOMING DATA STORES 21 4.1 Train Appropriate Personnel in the Use of Procedures and Taxonomy 21 4.1.1 Advertise Availability of System....
21 4.1.2 Provide Training, Contacts, Etc........
21 4.2 Apply Taxonomy to Existing Data Stores 21 l
c.1 Provide Access to External Computer Stores 22 c.2 Computerize Internal Data 22 4.3 Apply Taxonomy to New Data Stores..........
22 III. REFERENCES 22 APPENDIX A - CLASSIFICATIONS FOR USE IN ERDA SAFETY INFORMATION NETWORK TAXONOMY 23 FIGURES 1.
Data base, design 2
2.
Safety information system cataloging tree...........
5 3.
Needs survey matrix....
11 O
l v,
1 l
OV I.
INTRODUCTION l
Information is an important tool in the performance of any job.
In order to do a job well, you need to know how to do it, what rules to follow, what other tools (besides information) can be used, etc.
This information may be found in several places, making it necessary to locate information sources, identify the useful portions of the avail-able information, collect the information, and reduce it to a usable form.
Ideally, however, this process will have been completed prior to the time when your need for the information arises. That is, the information will have been systematized for your use. While information is a tool, an information system 's a refinement of that tool, and is therefore more valuable to the user.
The Energy Research cnd Development Administration (ERDA) has made a strong commitment to safeti in its activities.
ERDA's safety mission is to make ERDA and ERDA contractor safety programs as effective as possible. An essential element of the overall ERDA safety program that will achieve that goal is a comprehensive safety information system.
This comprehensive system will serve two general purposes:
(1) To provide personnel at all management levels with the n
information they need to facilitate evaluation of risk (j}
/
and allocation of resources in all facets of ERDA's opera tion.
(2) To provide personnel engaged in all of ERDA's different functions, or disciplines, with the information they need to do their jobs safely.
The management levels within an organization form a horizontal struc-ture, as shown in Figure 1(a). The different functions form a vertical structure within the same organization [ Figure 1(b)]. When the two structures are combined, the result is a complex structure, as shown in Figure 1(c).
In order to fully serve the organization made up of that complex structure, an information system must be designed so that the needs of each of the potential users within the structure are considered.
In addition to safety personnel, the potential users of a safeA infor-mation system could include personnel involved in such disciplines as administrative work, program management, dissemination of information to the public, construction, research, etc. The data base which supports this information system will serve all of those needs by including internally and externally produced data relating to past, present, and predicted events [ Figure 1(c)]. Further guidance on the development of Guidell)ionsystemscanbefoundinSSDC-9,SafetyInformationSystem_
- .'forg)a t (O!
v i
O Top Management
/
Middle Management Lower Operating Management (a)
W M
4 e
8
'/
6 f
0,'0 s
0, C2 w
+
(b)
O Data Base Internal Data External Data Past l Present l Future Past l Present l Future
+
+
e Events l Events l Events Events l Events ! Events EGG A-198 -
l Fig.1 Data base design.
(
O 2
l
The ERDA safety information " system" being developed is actually a network of sj:+ ems. This development effort is being scaled to an ERDA-wide level. Many cf the aspects of such a large scale network, such as accessibility of compt.ter facilities, accessibility of other systems and information, the necessary funding that guarantees that accessibility, etc., are also being developed on an ERDA-wide level.
Most of the systems which will be part of the network will be applicable ERDA-wide, or at least at several locations within the ERDA organization. The ideas presented here are, in general, intended as guidance for the development of such systems. However, many of these ideas can also be scaled down to the level of an individual contractor developing an infor-mation system intended for internal use only.
For example, although computerization of the information system is referred to here, the individual contractor may not have the facilities available to develop a computerized system.
In that case, the contractor can scale down the ideas presented here to the appropriate level.
Because it is very likely that a system developed by one ERDA con-tractor may also be of use to other ERDA contractors, the system would probably be incorporated into the ERDA-wide network at some later date.
The ideas presented here should be utilized in the development of such a system, so that its incorporation into the ERDA network will be an easy process.
As stated above, a primary objective of an information system is p) that it should meet the needs of the users within the organization to
- V be served. To achieve that objective, one of the basic aspects of the system's development should be the use of a widely understood and usable vocabulary. The use of a standard vocabulary would also insure the compatibility of the individual systems to be used in the ERDA network.
Because English is the language that is most widely understood and used by the potential users of the individual systems and the network, it makes sense to use English as the basis for their operation. The network's use of the English language will include colloquial and slang terms as well as standard use of the language. One project that must be begun in the initial stages of development, then carried through the entire life of the network, is the development of a taxonomy or catalog for the network. The taxonomy will systematically classify the English vocabulary (including colloquial and slang terms) to be used in the net-work and therefore in each of the systems.
Some important considerations throughout the development of any information system are the legal constraints placed on such systems by the Freedom of Information Act of 1967 (5 USC Section 552) and the Privacy Act of 1974 (P.L.93-579). The Freedom of Information Act allows individuals to request any information recorded about them by the Federal government, and allows individuals to change any record which may be incorrect. The Privacy Act restricts the release of infor-mation kept on individuals by the Federal government.
Those requesting such information must show a "need-to-know".
1 N) 3-
Obviously, we don't want to violate these constraints in the develop-ment of new information systems, especially where reports on accidents, personal injuries, etc., are involved.
In addition, we don't want to create information systems in such a way that requests for information under the provisions of these laws result in an overly large work load.
Of particular concern in developing a taxonomy are such areas as communication of system outputs and exchange of information between systems.
The vocabulary and taxonomy may have to be structured in such a way as to avoid violation of these laws.
In any case, it is recom-mended that legal personnel be consulted on these constraints during the early stages of system development.
As shown by the cataloging tree in Figure 2, there are four basic steps involved in developing a taxonomy:
1.0 Determine the Desired Outputs of the System 2.0 Determine the Vocabulary Required to Produce the Desired Output 3.0 Catalog the Required Vocabulary 4.0 Apply the Taxonomy to Existing and Incoming Data Stores The following discussion develops these steps in detail.
II. THE CATALOGING TREE 1.0 DETERMINE THE DESIRED OUTPUTS OF THE SYSTEM The outputs of each system can be divided into two groups:
those that will remain inside ERDA, and those that will be disseminated to outside agencies, organizations, etc.
1.1 Determine Desired Output to ERDA and ERDA Contractors Internal outputs will probably cover a much wider range of infor-mation needs than external outputs.
The process of determining what l
both types of outputs will be is virtually the same, however.
A.1 Survey Needs of Entire Range of Personnel. To meet the objec-tive of a system that is really useful to all potential users, one approach is simply to ask those potential users what they would need from the system. That is, conduct a survey of the potential users to determine what types of information they would like to be able to get from a safety information system.
O 4
m -.
m
-__...._mam_..
..-o
.~.m.__
_u_.m..
E i
\\
V i.
l J
5 i
I
?
(
l D8JECTIVE:
Usable by All I
Develop Taxonomy for Discipitnes and 4
- g Cornuterized ERDA 54fet)
Organtr,ational Information System g,,
g,
t
'I l
4.0 l
3.0 l
1,0 l
2.0 l Catalog Required Apply Taaonomy to Deteretne Vocabulary l Determined Desired Vocabulary (alsting and Output of system Required to Produce
'ncoming Data Stores
}
Desired Output Q
6 pI i
i_i i
- 1. 2 3
8l 3
4'2 I
43
[
> Batermine Desired Determine Destred Output to ERDA 4 Dutput to f aternal Train Appropriate Apply Tasonomy to Apply Taaonomy to 1
(MA Contractors Organizattons Personnel in use of eistina Data Stores ww Data Stores Procedures & Taaonomy 1
~ '
A A
I 2.1 2.2 l
- 2. 3 I
5pecify l
Identify Vocabulary Incinde Selected I 4.1.1 I a 1_ ?
l Indietdual Output i Requirements of Elemeits in System Advert t se Provide Spectf ted Output Vocabulary Availability Training.
t of System Contacts, etc.
(
I c.l I
c.?
L
)
. 2.1
.2.3 2.2.5 2. 2. 7 F29 Provide Access
[ Computertre l
to [aternal i Internal Data l L
r 2.2.g Communicatto
- 2. 2. 6 Procedures of Output Topic (s)
'. 2. 2 Audience 2.2.4 Input Data 0
I I
I c. Z.1 I c.2.2 i
etrieval of Compilation Vocabulary pg j
& Key Words Input Data of output provide Key Word Computer Internal
-r 1
FacilIttes Data Stores 2.
Fig. 2 Safety information system cataloging tree.
l f
I f
i s
W L',
r termire Desiredi rDetermine Desiredt 03e g
tbtput to ERDA andt goutput to ExternallI I ERCA Contractorsl
( _ Organizations J t_ _ _ _
___J y
A 6
l A.1 A2 l
A.3 Survey Needs of Entire Assign Priorities to Select Needs Which Can Ranqe of Personnel Results of Survey and Should Be Addressed I
A I.1 I A.I.?
IA.I.3 i A.I.4 i
A.3.1 h A. 3.2 l
A.J.3 Determine Appropriate Develop Method Conduct Sumarize Include High
[AClude low include Medium Disciplines and Of Survey Survey Survey Priority Items Prio-ity items Priciity items Organizational Levels To Be Surveyed L
- Technical Personnel A.I.2.1 l
A.2.1 A.2.2 l A.2.3
- Contractor Management dQuestionnairel Identify Range Review Assign Priority of Priorities Individual Needs_
to I idual and Supervision 3)7g
- Field Organization q Interview l Management
- High
- Feasibility A.I.2.3
. Field Organization
. Medium
. Priority Assigned Safety Management d Combination l by Participant
.to,
. Program Management
. Relative Merit
- Headquarters Safety Management
- 0verlap
. Headquarters Management Fig. 2 (cont.)
O O
O
.,_...._m
. - -. _ _ _. _. _. _.. _.... _ = - -. _ _
T 1
c i
4 l
L i -
4 i
e
.t
}'
I i
3.0 f
l r-l j
a Catalog Required L_
vx a bula rr _ __;
l p.5 t
B t
I i
l B.3 l
B.i I
l B.1 l
8.2 SurveyAltilize Existing Develop New Impose Desired Logical Prepare Written Vocabulary and Catalogs Segments of Taxonomy Arrangement on Taxonomy & Proced. ires j
As Applicable Where Needed Vocabulary and Catalogs for General Use
[
i l
y i
F.4.1 i
B.4.3 i
B.4.5 i
R.I.i I
8.1.t f
E.f.3 y
Prepare Prepare Distribute To i
Select Include In Su #
Draft Revision Appropriate j
Applicable Terms
_S.25 tem Taxonnmy Personnel t
& Classifications j.
s.4.2 B.4.4 i
Publish --
1 B.2.1 8.2.2 l
B.2.3 Distribute Draft Ta xonomy For Review By Select Terms Arrange Under Add to Existing Selected Personnel Not Included In General Headings Vocabulary 1
Existing Catalogs Classifications t
1 t
4'
}
i B.3.1 l B. 3. 2 B.3.3 l
B.3.4 l B.3.5 t.
g
{
Key Words Thesaurus General Topics Re r nts Requ r ts f
i i
Fig. 2 (cont.)
I 1
1 I
i-l
'?
],
t i
(
A.l.1 Determine Appropriate Disciplines and Organizational Levels To Be Surveyed. To a large extent, the appropriate disciplines and organizational levels to be surveyed will be determined by the type of operation conducted by the particular organization and by the way that the organizaticn is arranged.
For example, a primary responsibility of an ERDA field organization is to monitor and appraise the activities of the contractors under its jurisdiction.
Typically, responsibility for the safety aspects of this function is assigned to a safety division within the field organization. The director of that division then delegates the responsibility for each safety discipline (industrial safety, health protection, environmental protection, etc.) to an indi-vidual on his staff who has some expertise in the field.
These indivi-duals therefore need safety information on a continual basis.
Obviously, the safety division director and his staff should participate in the survey.
At the other end of the spectrum, let's look at the needs of, for example, a heavy equipment operator.
Individuals involved in operating heavy equipment encounter a wide variety of situations in which they need to know the limits within which they can work safely.
These individuals and/or their supervisors should also have the oppor-tunity to express their safety information needs as survey participants.
The message here is that, when determining which personnel should participate in the survey, all of the following possible sources should be taken into consideration:
. Technical Personnel in All of the Disciplines Concerned
. Contractor Management and Supervisory personnel
. Field Office Management
- Field Office Safety Management
- Program Management
. Headquarters Safety Management
- Headquarters Management A.l.2 Develop Method of Survey. The choice of a method for the survey will depend on several constraints. The amount of time
~
and the number of personnel available to conduct the survey will have an effect on how extensive it is.
If a lot of travel funds would be required to conduct personal interviews, perhaps the survey should be in the form of a questionnaire.
The types of personnel chosen to participate in the survey may effect the choice of methods and the development of the survey itself. For example, top management people may have little time for an interview and not much more for a lengthy questionnaire.
Another point to keep in mind is that questions for either an interview or a questionnaire should be formulated on the basis of the factor (s) the participants have in common.
For example, a survey ques-tionnaire for a participant group trained ir. the Management Oversight and Risk Tree (MORT) was formulated on the basis of the MORT tree itself[2],
8
(
The discussion below suggests s ne methods for conducting surveys and describes advantages and disadvantages of each method.
A. l. 2.1 Questionnaire. This' method is useful when participants are some distance away, or when you have decided to use a large number of participants.
Either of those conditions or both can make interviewing an impractical alternative.
Questionnaires can backfire, though.
Even the most willing participant won't have the time to answer a 10-page questionnaire.
Also, if questions are worded in the wrong way, participants may not understand what information you want, or they may think they understand and give answers that won't really help you. Another point to watch out for is wording questions or posing types of questions that result in the answers you want to see or hear. That is, your survey may lose its independence depending on what questions you ask.
In summary, if you plan to use a questionnaire, keep it as short and as uncomplicated as possible.
A.l.2.2 Interview. The interview technique is useful if you have the time and personnel available to conduct a series of interviews. The interviews may be made more effective and efficient if your participants are notified of the interview topics in advance.
If the participant is uncertain about what is meant by a particular ques-tion, an explanation can easily be given.
If the participant isn't p) already sold on the idea of an information system, you can do a little sU public relations work while you conduct the interview.
This may result in more information received than a questionnaire.
An uninterested participant can very easily throw away a questionnaire.
Unlike interviews conducted in accident investigations, it might be helpful to conduct interviews which include several parti-cipants simultaneously. This allows for more discussion. What one participant suggests or comments on may trigger a new thought for other participants. The warnings against biasing the results of your survey apply here as well as to questionnaires.
A.l.2.3 Combination of Questionnaire and Interview.
The idea here is to prepare your participants in advance of the interview by first distributing a questionnaire. The questionnaire should include an explanation of the purpose of the survey, or you may want to give an oral explanation at the time of distribution. This method gives the participant an opportunity to think about his or her responses before the interview is conducted. Any questions the participant may have can be answered during the interview.
A.l.3 Conduct the Survey. After you've decided on a survey method and have done the advance preparation required on your part, you I
can proceed with the survey. As a part of the survey, you should ask l
the participants to assign priorities to their needs. This will assist
!(n) you later in determining which needs the information system should fill.
G 9
m 3
A.l.4 Summarize the Survey. Before making any attempt to do anything with the results of the survey, it helps to summarize the results.
If you have conducted interviews, prepare some sort of summary as soon as possible. No matter how complete your notes are, you can lose some of the information you gained from the interview if too great a time elapses between the interview and the time at which the summary is done.
The summary of a pilot survey conducted by the System Safety Development Center (SSDC) resulted in a good matrix representation.
The matrix was very helpful in preparing for further surveys, as well as in determining which types of information were most desirable across the board. Figure 3 shows the general format of the matrix.
A.2 Assign Priorities to Results of Survey. There will be some needs expressed by the participants which you won't be able to incor-porate into the system for any one of a number of reasons (e.g., hardware constraints, sof tware constraints, funding constraints, etc.). You will therefore have to assign priorities to help in making the decision as to which of the needs should be included in the system.
A.2.1 Identify Range of Priorities.
This is simply a matter of establishing some range according to which you will rank each of the needs requested. The range you develop can be very simple or more complex.
A simple range would be high-medium-low.
A more complex range would develop the three categories a little further.
Developing too complex a range may result in problems later on when you're trying to select the needs to be addressed.
There may not be enough differentiation between the needs to make selection of one or the other possible.
A.2.2 Review Individual Needs. Each system output that has been requested by your survey participants will have to be reviewed on the basis of several factors before a priority can be assigned to it.
The review should be made on the basis of such factors as the following:
(1)
Feasibility - Does the requested output fit with the other outputs of the system as far as hardware and software requirements go? Will it make the system too expensive?
(2) Priority Assigned by Participant (s) - What priority l
did the participant assign to the need? If top management personnel assign a high priority to a need, perhaps this should carry more weight than high priority assigned to a need by personnel on lower tiers.
(3)
Relative Merit - Will you gain more if this output is fitted into the system than you will gain if another output is fitted in? What will you lose if you do not include this output?
10
)
(Q le c f l%
e5,f /
hs**f e
% rh
,J $
Off$
e $. e
.x ir f
ta
- gy m
y
$.,sf evr
/*
us s
t d
[N.
e*
ee h
N 5.s 3
N g
i
/
F
~/$
Of;%
4g
%M*$
s a
y e
l r
y t
n l
f a a
t l
oi r
s n
o y
t e
e eo n
r s
l g c
e r
t e
f i
vr o
D ne ys ao i
em et e
f a
g it i
E ot ce cr s
ve vn f
a S
y tn t
E ia nn iP y
ig io a
S H
co c
aC e
tl ed g
h t a tC S
y l
o t
t f
f a
ge oe P
cn c
l t
t e rr l c aa an r
a i
a i n o
do r
E rv ea on h
oM oo a
i l
i i a t
i ii e
r a
r ai P
i oi mp r
I pt Ee dt l
de dt l
t c
t rt L
sc r
as a
at au c
s i
s nu e
P na P
Ri e
Rs Rl lu u
t u
ol r
I ao s
H a
l f
d i
d l
i l
f C
ri s
W o
n r
n o
F S
Td A
P I
C I
P I
a D
R
)
~
t
(4) Overlap - Does the need expressed by personnel in one discipline overlap similar needs expressed by those in other disciplines?
If several disciplines or organizational levels request a type of infor-mation, perhaps the need should be given higher priority than the individual needs have separately.
For example, if several management groups request a recordkeeping function, perhaps it should be made part of the system.
A.2.3 Assign Priority to Individual Need.
Each need should be assigned a priority on the basis of your evaluation of the outputs individually and in comparison with one another.
A.3 Select Needs Which Can and Should Be Addressed.
This process may not be as clear-cut as the text would indicate.
In some cases, lower priority needs may be selected over higher priority ones because they are more feasible or they have greater applicability, or for a similar reason.
However, in general, the selection process below can be followed:
A.3.1 Include High Priority Items.
If you have assigned a high priority to a particular need, you had a good reason for doing so.
Obviously, the output should be included in the system.
A.3.2 Exclude Low Priority Items.
Outputs that have been assigned low priorities may be items for which there is little need or which can be easily accomplished outside of the system, or which are outweighed by other outputs. Such items can be sacrificed for higher priority outputs.
A.3.3 Include Medium Priority Items _. This part of the selection process will require a lot of judgment on your part.
You may, in fact, find that a few medium priority items will have to be excluded from the system. Some trade-offs may be necessary.
For the most part, however, those needs which are the most feasible, are the most applicable, have the highest merit, etc., will be the most logical selections.
1.2 Determine Desired Output to External Oraanizations This is essentially the same process as is used in the determi-nation of internal outputs. The exception is that the needs of all disciplines and organizational levels for external outputs will not be as extensive as they are for internal outputs.
It is expected that technical personnel and contractor middle management and supervisory personnel will have little or no need for outputs from the system to go to external organizations. Therefore, the determination of appro-priate personnel to be surveyed (as in A.l.1) would probably exclude those groups.
O 12
V 1
Higher management personrel, on the other huu, may have to report more extensively and more frequently to other organizations.
For example, contractor management may have to repo;' to their parent com-pany, and ERDA management frequently reports to other Federal agencies, the Congress, etc.
It is important to note that while the number of required reports to a few external organizations may be somewhat limited, the avenue for exchange of information with many external organizations must be kept open. This information exchange can be valuable both for EEA and the other organizations involved, as well as for the safety profession in general.
2.0 DETERMINE THE VOCABULARY REQUIRED T0 PRODUCE THE DESIRED OUTPUT The combined output of all of the systems with the network will have quite an extensive vocabalarv. Because of the nature of energy research and development, some pt. ts of that vocabulary will be unique.
Other parts will be ordinary English language. All aspects of each output should be covered to make the vocabulary as complete as possible.
O)
The determination process will not necessarily be broken into the separate steps described here. The process will instead be a continuous
('
one. That is, for each output and its requirements, you will pick out the items that should be included in the system vocabulary and see that they are included. Since the requirements are all related to the same output, they overlap a great deal and are difficult to separate completely.
This makes separation into the " steps" shown here a difficult task. By separating them, our intention is to assure that none of these elements are lef t out of the process.
To help clarify the description of the process, let's look at a pos-sible output of the system and 'illow it through the process.
- Suppose, for example, that the desired output is an accident risk assessment report for a particular organization.
2.1 3pecify Individual Output By singling this step out, our intention is simply to make the point that the process of determining the vocabulary required to produce the output must be completed for each output that has been selected for the system.
The example desired output has already been specified - an accident risk assessment report.
n v
13 l
2.2 Identify Vocabulary Requirements of Specified Output Each output will make certain demands of the system vocabulary.
Different topics, audiences, report formats, etc., will have some effect on the vocabulary and its structure. One way to make sure the vocabulary can meet the demands is to examine each output on the basis of those demands. The identification process is, in effect, a review of each element (i.e., topic, audience, report format, etc.) of the output.
The review should search out such items as the following:
(1) Basic vocabulary.
(2) Vocabulary unique to the output topic and/or disciplines involved.
(3) Synonyms (including abbreviations, trade names, slang, etc.).
(4) Cross-references to other outputs, other topics, other disciplines, etc.
I The elements to be reviewed are discussed below.
2.2.1 Topic. The topic that the output will cover is a good place to start the examination.
Each topic will encompass one, or possibly several, disciplines.
This will give us a wide range of vocabulary to examine for possible inclusion in the system vocabulary.
For example, a typical risk assessment report might summarize the organization's accident costs, and then provide a statistical estimate of the current annual accident risk from the organization's activities.
To provide as complete an accident risk assessment as possible, the system should include vocabulary associated with such areas cs the following:
(1) Risk methodology.
(2) Riskquantification(dollars, days, people,etc.).
(3) OSHA injury and illness classifications.
(4) Energy classifications (if the assessment is to be in keeping with the MORT concept of energy vs. barriers).
(5) Monetary factors associated with accidents and incidents (direct and indirect costs, normalizing factors, multi-pliers,etc.).
(6) Types of operations conducted by the organization (including hardware and materials involved in those opera tions).
O 14
2.2.2 Vocabulary and Key Words. Once the disciplines associated
(
with a particular topic have been determined, they can then be examined on the basis of their vocabulary. The vocabulary from each discipline that will be needed to make the output complete must be identified.
Thi:, doesn't necessarily mean that the entire vocabulary asso-ciated with each discipline is needed. Only the parts of the vocabulary that are necessary to make the desired output understandable should be included.
For example, the statistical theory behind the risk metho-(
dology may be quite complex. Since the objective is to make the metho-dology understandable to those who receive the output, rather than to teach them a probability and statistics course, only those terms which will aid in their comprehension of the risk methodology need to be used.
In identifying the vocabulary needed to meet the output demands, you must also be sure to include any synonyms for the selected vocabulary, if they are likely to be used.
In addition, you will want to identify any key words associated with the discipline at this time, since entry into the system will be based on their use.
2.2.3 Audience. The audience that will receive the output will determine the technical nature of the vocabulary to be used and the aspects of the topic to be emphasized. The accident risk assessment
(
report will most likely be used by the organization's own management.
An internal report would probably be less formal, but more specific on 3
facilities, processes, management systems, etc., than an external report would be. An external report might require comparison with other organi-zations. These factors would have an effect on what vocabulary would be used.
2.2.4 Format. The format of the output will structure the voca-bulary to a certain extent. A report that uses a lot of text and a few figures may have a much more extensive vocabulary than one that uses a lot of numerical tables. Our risk assessment example would be a combina-tion of text and tables, so the extent of its vocabulary would be some-where between the two extremes.
In addition, reports which are periodic will probably have a stan-dard format and an established vocabulary.
Outputs produced as a result of special requests may require a specialized vocabulary to conform to the desired format.
2.2.5 Location of Input Data. The source of your input data may have some effect on the vocabulary you build into the system.
Input data located within your organization will probably not cause too many problems. For the risk assessment report, for example, the raw data will probably be stored in one location, possibly even within a single computer system.
v 15 i
However, data located outside your organization may provide some difficulties.
External data that are not computerized may be more easily manipulated to fit the existing system vocabulary than data that are computerized. To make the transition between computer systems easier, some additional vocabulary and key werding may be necessary.
2.2.6 Retrieval of Input Data _.
The process required to retrieve the input data may place additional constraints on the vocabulary.
If a manual system for retrieval is used, the input data can be restated to fit into your existing vocabulary.
If an automated process is used for retrieval, it may impose some constraints on your vocabulary.
For example, some form of data base management system may be available for use in conjunction with the safety information system, allowing different methods of manipulation of your data base for the purposes of data retrieval, updating, changing the structure of the data base itself, etc. The logic and computer language used by the data base management system may shape the vocabulary you use to a certain extent.
2.2.7 Analytical Procedures.
The process by which the input data will be reduced to a usable form may have an effect on the vocabu-lary needed. A simple example of t. 's is the data reduction process used in the risk methodology. As s.ted above, there is no need to go into the vocabulary of the theory of probability and statistics too deeply.
However, some_of the vocabulary is needed to help in the analysis of the raw data. Since risk is a combination of the proba-bility and the consequence of occurrence of an accident, the general methods for deriving these two elements must be understood.
Therefore, the system should include only the vocabulary necessary to achieve that understanding.
2.2.8 Compilation of Output. Once the input data have been reduced to a usable form, the output must be organized within the framework of the format that has been selected. The instructions required to accom-plish that end may produce some additional vocabulary.
For example, in compiling the risk assessment report, the text should be organized in a certain way, the tables should be presented in a comprehensible form, abbreviations may be necessary, special symbols may be required, etc.
Or in some cases, you may simply need to instruct the computer to print out a particular report that has already been programmed into the system.
2.2.9 Conmunication of Output. A particular output may be communi-cated in a number of ways. A very informal output might consist of a simple phone call. The example, a risk assessment report, will most of ten be an internal document " communicated" to others via a transmittal letter.
The method of communication may require additional vocabulary.
In cases where the output is to be disseminated to a large and varied group of recipients, it is important that the output is under-standable in itself, without needing any additional explanation.
If the vocabulary required for this purpose has not already been identified in the previous steps of the procedure, now is the time to do so.
16
n 2.3 Include Selected Elements in System Vocabulary This " step" is simply a transfer process. For each output that the system will provide, you have gathered a vocabulary.
Now those individual vocabularies will need to be assembled into one overall system vocabulary.
3.0 CATALOG THE RE0UIRED VOCABULARY The vocabulary required to produce the desired output will probably be rather large in volume. To make it useful, the vocabulary must now be subjected to some form of organization. A typical method of organizing vocabulary for an information system is to create a somewhat arbitrary coding system. A more useful form of organization is to produce a taxo-nomy for the information system. This will ensure that the vocabulary is systematically classified.
A good taxonomy should be based on an appropriate combination of set classifications, new or in existence. The American National Standards Institute, in its Standard Z16.2[3], presents a set of classifications of hardware and materials. These classifications are currently used only to classify sources of occupational injuries, agencies of accidents resulting in injury, etc., and are easily adaptable for use in the o
taxonomy for an overall safety information system network.
Another set of classifications is the classification of energy types found in MORT.
The combination of these two can easily be expanded to cover all the areas that most taxonomies would require. Appendix A contains the two lists.
B.1 Survey / Utilize Existing Vocabulary As Applicable Within the ERDA/ERDA contractor group, there are already several safety information systems in existence [NSIC (Nuclear Safety Informa-tion Center, REIRS (Radiation Exposure Information Reporting System, ERIS (Emergency Resources Information System), etc.].
These systems are good examples of bases for the ERDA network, and their vocabularies can be the basis for the network taxonomy. The existing network voca-bulary and taxonomy should be taken into consideration when a new system is being developed.
In addition, there may be information systems in existence outside of ERDA's jurisdiction which could be adapted to our use.
1 B.1.1 Survey. A survey of existing systems can be conducted on several levels.
Inside ERDA, the Technical Information Center is the primary source for information systems. Other information on existing systems can be obtair.ed from technical information personnel, other federal or state agencies, libraries, information system consultant OG l
17 l
etc. A good resource for the survey is the Sources of Expertise firms (4J, available for use at your ERDA field organization safety Index office. liaving selected existing systems which may be of use, the next step is to examine their vocabulary and catalogs for possible incorporation into our system.
B.l.2 _ Select Applicable Terms and Classifications.
You may decide to use existing vocabulary and/or classifications as they are, or you may only want to use parts of them.
In any case, you will want to review the existing catalogs and select those parts that you want to use.
Their applicability will depend on the requirements of the system outputs.
For example, the flSIC catalog would probably be incorporated into the ERDA network taxonomy as a whole, based on the nature of its content (and depending on how compatible it is with other vocabulary and cata-loging to be used). On the other hand, if some personnel information is included in the network as a basis for recordkeeping, only small parts of any existing personnel systems may be used.
B.1.3 Include in System Taxonomy.
The terms and the parts of the existing catalogs you have selected as being applicable to the system should be collected. They will provide a basis for the develop-ment of the rest of the system's taxonomy.
B.2 Develop flew Segments of Taxonomy Where fleeded There are likely to be gaps between the vocabulary / cataloging you need and what has been provided by existing system catalogs.
If so, you will have to develop the missing segments, based on the output requirements.
B.2.1 Select Terms flot Included in Existing Catalog. This will require a comparison between the vocabulary provided by the existing systems and the vocabulary selected on the basis of your examination of the output requirements. Where gaps exist, select terms from the output requirement vocabulary.
B.2.2 Arrange Under General lieadings. The selected terms may fit into the general structure already established, or they may require that entire new sections (i.e., classifications) of the structure be developed.
In any case, make sure that the selected terms do fit into the structure.
B.2.3 Add to Existing Vocabulary and Classifications. The new vocabulary segments are now structured so they will fit into the esta-blished structure. They should now be added to the existing vocabulary and classifications to form the basis from which the taxonomy will be developed.
O 18
p B.3 Impose Desired Logical Arrangement on _ Vocabulary and Catalogs
,(
To a certain extent, the vocabulary and catalels will already be logically arranged. This is especially true in those cases where cata-loging from an existing system is being used.
However, now you'll want to go a step further and impose an overall arrangement according to the following constraints.
B.3.1 Key Words. Choosing key words is an important task.
These words will be used to enter the system. That is, users will call one key word, or a combination of several key words, from the system or network in order to retrieve the desired output. To facilitate use of the system, the key words should therefore be well-known, obvious choices for each particular discipline.
B.3.2 Thesaurus. This is another important item closely related to key words. The development of the thesaurus can solve several problems that arise in understanding the system vocabulary.
For one thing, different organization levels tend to use different types of vocabulary. Technically-oriented people will use technical terms much more frequently than management-oriented people will, and yet they need to understand one another. For example, a fire protection engineer may be advocating the purchase and installment of a particular type of fire suppression system. His procurement people are interested primarily in how much the system will cost and if it's worth the investment. The
\\
(h engineer and the procurement specialist have a common interest, but if they don't understand each other's vocabulary, there may be such a communications gap that the system may never be purchased. The voca-bulary used must eliminate those communications problems.
Another problem that arises is that different people may use different terms to mean the same thing. This can take several forms.
Some people use a colloquial or slang term for a particular piece of equipment, while others use a standard technical term.
Different organizations may use different terms for the same items or procedures.
Some people use the full chemical name for a compound, while others use a trade name.
To eliminate these problems, the thesaurus must be established so that key words are properly associated with all of their synonyms.
Each system should produce the desired information whether a key word is called out or a synonym of the key word is called out.
B.3.3 General Classifications. Once the key words and the thesaurus are established, more general classifications should become fairly obvious. All that needs to be done here, then, is to select appropriate classifications and organize the key words and synonyms by i
the classifications.
v l
19 l
f B.3.4 Hardware Requirements.
In many cases, the system being developed will be intended for computer use.
When this is the case, anything about the equipment being used that might affect the logical structure of the vocabulary and/or the system itself should be taken into consideration.
In addition, interfaces with other systems on different equipment may involve logical difficulties.
When such transfers between systems are anticipated, the possible difficulties should be considered during the development of the systems.
B.3.5 Software Requirements. The type of computer language that the system uses may place some constraints on the vocabulary and its logical arrangement. The way the computer program itself is structured will also have some effect.
In addition, if a data base management system of some sort is applied, structuring the data base so that dif-ferent segments and combinations thereof are more easily retrievable, the logic structure of the vocabulary will be affected.
These factors should all be kept in mind during the development of the taxonomy.
B.4 Prepare Written Taxonomy and Procedures for General Use I
The taxonomy must be made available to system users in order to complete its development process.
In addition, the taxonomy should be accompanied by some self-explanatory procedures for its use.
Although this formalizes the taxonomy to a certain extent, you must remember to keep the written taxonomy and procedures as uncomplicated as possible.
If the taxonomy is well done but the procedures are not, the purpose of the whole process can be defeated.
B.4.1 Prepare A Draf t.
By now, the vocabulary and classifications should be well-organized. All that needs to be done is to present them in a format that will be suitable for the system users.
In addition, you will need to prepare some simple, step-by-step instructions that will allow a wide range of users to obtain the information they need from the system.
B.4.2 Distribute Draf t for Review by Selected Personnel. The draf t taxonomy and procedures should now be reviewed by some appropriate personnel. Select people from various organizational levels and dis-ciplines who are potential users of the system, people who may have developed similar systems, professional computer people, etc.
This will provide two important results: you will have had some objective review of the taxonomy and procedures, and they will have been validated.
B.4.3 Prepare Revision.
Based on the comments and suggestions you receive from the reviewers, revise the taxonomy and pro::edures. As further development of the system is conducted, the taxonomy will be subject to continuing revision. The format of the taxonomy should take that possibility into account.
O 20
B.4.4 Publish Taxonomy. Have the taxonomy printed, or at least reproduced in a legible form, and in as great a quantity as you will need. This may entail a survey of potential users so that you can develop a mailing list.
B.4.5 Distribute to Appropriate Personnel.
Distribute the taxonomy to those on your mailing list. K;ke it available for widespread use.
The system will never be cost effective if people don't use it.
4.0 APPLY TAXONOMY TO EXISTING AND INCOMING DATA STORES Applying the taxonomy to the system's input data will not be a difficult task, but it will be time-consuming.
A good way to break down the work load is to have your system's users do some of the work.
4.1 Train Appropriate Personnel in the Use of Procedures and Taxonomy This process can be started in conjunction with the publishing and distribution of the taxonomy.
4.1.1 Advertise Availability of System.
If no one knows that an information system is available, no one is going to use it.
The public
[N relations work for such a system can be started in the early stages of 3
, (
i the system's development. For example, some work in this area can be done while your needs surveys are being conducted.
This sales work will help gain support for the system, provided it is done properly.
It may even provide incentive to get the system into operation faster, if people know of the proposed system in advance.
Once people know the system is available, they will want to know what it consists of and how to use it.
4.1.2 Provide Training, Contacts, Etc.
One of the purposes of providing procedures with the taxonomy is to eliminate the need for an extensive training program.
If such a need is anticipated, however, you should be prepared to handle it.
Even af ter users are trained, they will have questions at times.
You should have knowledgeable personnel available to assist users when problems arise.
4.2 Apply Taxonomy to Existing Data Stores This part of the application will be the most time-consuming, but it's a necessary process. The system's users will be able to assist here, to a certain extent, by applying the taxonomy to input data and I
data stores in their jurisdiction.
l fT
! !w,/
21
c.1 Provide Access to External Computer Stores.
External data stores will be much more difficult to manipulate than internal stores.
To begin with, external stores must be compatible with the taxonomy.
Hopefully, this will have been taken care of by the cataloging process.
If external stores are to be used, all that can be done internally is to provide the taxonomy and provide access to the stores through some type of interface arrangement.
c.2 Computerize Internal Data.
Internal data stores will be much easier to handle than external stores. Most organizations already have the capacity to do so.
c.2.1 Provide Computer Facilities. Most organizations within the ERDA/ERDA contractor group have computer facilities of their own.
It is at least a fairly easy task to get access to facilities of some sort. Ready access will be an important factor in how much the system will be used.
c.2.2 Key Word Internal Data Stores.
Provided that you already have access to computer facilities, the first step toward computerization will be to " key word" the data based on the taxonomy.
Depending on the volume of data, this may or may not require a lot of time.
4.3 Apply Taxonomy to New Data Stores This will be a much less time-consuming job than applying the catalog to existing data stores. The procedure is the same.
It can possibly be done by the users, to a certain extent.
The only difference is that the catalog can be applied to new data stores as they become available, and will therefore be a continuous process.
III.
REFERENCES
[1]
M. G. Bullock, Safety Information System Guide, ERDA 76-45/9, SSDC-9 (March 1977).
[2]
W. G. Johnson, MORT - The Management Oversight and Risk Tree, SAN 821-2 (February 1973).
[3] ANSI Zl6.2, American National Standard Method of Recording Basic Facts Relating to the Nature and Occurrence of Work Injuries (Approved October 4, 1962).
[4] Sources of Expertise Index, NASA CR-121206, NASA CR-134929, NASA CR-121149, NASA CR 134754.
O 22
.m.
a-a_m_m__
mm.a.2a-_m a*--aa- - -
u.aa m
__m._
A a
2a ma a
a w.a a-a
--a.--
m l
l 4
k 4
l, 1
i i
1 i
I i
i APPENDIX A CLASSIFICATIONS FOR USE IN ERDA SAFETY INFORMATION NETWORK TAXONOMY 4
i 1
b h
,i t
i, 4
l k
t
(
9 1-23
-. <- u i..ta.! ;
i
1.
ANSI Zl6.2 AGENCY OF ACCIDENT CLASSIFICATIONS A1,6.2 Alternase, Detailed Agency of Acci.
Code dena Claselfeasjon CAemicals, cArmiral compends (solida, liquids, gasee) (centm.ed)
Code 0950 llelogensted compounds, NEC (trichlorethy.
lene, perchlorethylena, methyl chloride, refris-0100 Asr pressure tabnormal, environmental)
,,,,m 0101 llish pressure (as in caisson work, deep div.
0955 Metallic compounde, NEC (lead, mercury, aine, ing, etc) brass, cadmium, chromiuro, etc)
)
0120 14w pressure (rarefied air as at entreme ele-0960 Osides of nitrogen (nitros fumes) watsone) 0999 Chemicals and cliemical compounds, NEC 0200 Ansmals, sosects, birds, repssles (live) 1000 Clorhing. epparel, sAces 0201 Animals 2001 Boots, shoes, ete 0230 Birds 1010 Glove.
0250 Insui' 1020 if ats, head coverings 0270 Reptiles g o3o o,,,,,,,,,,,,;,,,,,,
1010 Shirts, blouses, sweaters, costs 0300 Animal prodecra (not food) 1050 Suits, pants, coveralls, dresses 0301 Bones S'h"8r'**I' N
0310 Feathere Underwea 1070 0320 Fur, hair, wool, etc (raw) 1099 A pparel, N EC 0330 Hides, lestber (1199 Animal products, NEC ggon c,,y,,g
,,,oleum products p
0500 Boilers, pressure sessels 0"I'"
1120 Crude oil, fuel cil 0510 Pr uurized containers (for gases or liquida)
I 1130 Casoline and liquid hydrocarl.on compounde 0530 Preuure lines (hose or pipe-for pressurised g
g bquids, gases, or vapore) 1140 Hydrmerbon snes (methane. ethane, ethyl ne.
0599 Prenure semela, NEC propane, butane, isobuiene, bu ylene, isobviy-e 0600 Bones, barrels, ceermners, pacAages (empty or full) lene, L P sas, etc) 0601 Barrels, kegs, drums 11 % Kerosine 0630 Bones, crates, cartons 1160 1 ubiscating and cutting oile end greases 0650 Bottica, juge, desks, etc 1170 Manuf actured gasee 0670 Tanks, bins, eic teot pressurized) 1180 Naphtha sol ents s petralcum ether, mineral 0699 Contuners, N EC spirais, cleaners naphtha, rubber solvent, Stod-dard solvent, eramatic solvents, etc) 0700 Buildings and irrverares (not Roors, working sur 11 % Petroleum asphalts and road oile faces, or walk =an. See " working surf aces ** clasedi-1199 Coal and petroleum products, NEC cation) 0701 Buildings, oMice, plant, residential, etc 1300 Conreyors 0710 Bridges 1301 Gravity con,eyore 0720 Dams, socks, etc 1350 Powered conicyors 0730 Crandeiands, stadia, etc 1400 Drugs and medico c 0740 SceSolds, staging, etc 1101 Biologic prducis (sera, toains, andtonine, vac; 0750 To=ers, poles, etc cines, plasma, etc) 0760 11 barf s, doc ks, etc 0799 Buildings and situctures, NEC 3490 g,g,,,,g;,g,g, 0800 Cerarve items. NEC 1500 Electric apparatus 0801 Brick 1501 Motors
\\
0810 China 1505 Cenerators 0820 Drain tile, sewer pipe,8ue lining, etc 1510 Transformers, converters 0830 Cla2ed tile (decorative not load bearing; me-1515 Conductors seic tile, etc) 1520 Sw;tchboard and bus structures, switches, cir-0840 Pottery cuit breakers, fuses 0850 Structural tile (stared or plain) 1530 Rheostats, starters, and control apparatus; ca.
0899 Ceramic items, N EC pacitars; rectifiers, storage batteries
'I I ' ' E P '"'
0000 CAemicals, cArmical compounds (solida, liquida, 88 I
gma) 1599 Electrical apparatus, NEC 0901 Acids 0#5 Alcohola 1600 Escamrions, trearAes, runnels, ere 0910 Alk alies 1610 bravati,sne (for buildinae, roads, etc) 0915 Aromainc compounds (bensol, toluene, sylene, 1620 Mine shafts, entries, drifts, etc aniline, etc) 1630 Trenches 0920 Arsenic compounds 1680 Tunnels 09:5 Carbon bisulphide 1699 Escasations, NEC (wcils, pita, etc) 0930 Carbon dioside 0935 Carbon monoxide 1800 Food products (includies animal foods) 09:0 Carbon tetrachloride 1810 Fruits and fruit product.
0945 Cyanides or cyanogen compounds 1820 Crains and grain products P00R~0R M
(N f
\\
V Agency of Accident-Alternate Detailed Clasal.
Code s
Gestion (Condnued)
Hosising apparaiss (conunad) 2640 Other hoisting apparatua Code 2641 Air hoi.:
Toed prod. css hneluding imal foods) (censinnedi 2642 Chain hoist, chaia blocks 2643 Electric beist 1840 Meats and mest products 2644 Gia pole 1850 Milk and milk products 2645 Jacks (mechanical, hydrsulic, sir, 1870 Vegetables and segetable products
,,, )
1890 Food producis, NEC 2666 Jammer (legginal 1900 furniture, parures /urnishings (not need parts of 2647 Mine buckets buildings or structures) 2699 Iloisung apparatus, NEC 1901 Cabinets,6te cases, bookcases, etc UOO Merm and presse sa ars, NEC (bacterie, fungi, 1910 Chairs, benches, etc paras. tic organisms, site es, ete-not chemicals, 1
Counters, work I,enches, etc dm pmerd mdseinal items, or food infesta-
I 1950 Hoor coverings, carpets, rugs, mais, etc 1960 Lighting equipment, lamps, bulbs, etc 2800 Ladders (6:cd or portable) 1970 Tables 2810 Fixed ladders 1999 Furniture, natures, furnishings, NEC 2830 Moosble ladders 2831 Emiension ladders 2000 Class seems, NEC (glassware, glan 6bers, sheets, etc I bicp a de
-not bottles, jern, flasks, or glaw cloth) g,,,
2P 79 Ladders, N EC 2200 /Isad tools, nor powered 220I A"
2900 liquids. NEC 2205 Blow forch 2910 Water 2210 Chisel 2999 Other liquids, NEC 2215 Crowber, pry bar 2220 Fi'e 30:10 Mer 4ines 2225 Fork 3001 Asusiors, miners, tumblers, ete 2230 flammer, s: edge, mellet 3050 Agewultural rnachines NEC 2235 Ifatchet 300 Buffers, polishers, sanders, grinders CN 2240 lloe 3150 Casting, forging, and melds a machines
(
)
2245 Knife 3200 Crushing, pulveruing, cic, machines
/
2250 Pick 3250 Drilling, boring, and turning machines 3V 2255 riane 3300 Farth moving and high=sy construction ma.
2260 Pliers, tongs diacs, N EC 2265 Punch 3350 Mir. sg and tunnell ng machinn, NEC 2270 Rye, chain 3400 05~ machinea 2275 Saw 3450 Pac aging and wrapping machines 22a0 Scis. ors, shears 3500 Pic! :ng, carding, and combing machines 2285 Scre= driver 3550 Pts.ers, shapers, e,ioiders 2290 Shovel, spade 3600 P. sees (not printii presses) 2295 Wrench 3650 Prinung machines 2299 liend tools, not powered, NEC 3:00 Rolls -
3750 Saws 2300 llend svols, powered 3300 Se,,,,;ng and separating machines 2301 Abrsu.e store or wheel grinde' 38'io Shears, sharers, sheers 2305 Buner, pohsher, waser 3900 Stitching and me ing machines 2310 Chisel 3950 we,s;ng, kniiiing, spinning machi es 2315 Drill 3999 Machines, NEC 2320 llammer, tamper 2325 Irnner 4000 Mechanical pouer tren.smis. ion apparates 2330 Knife Nort: Tran mission equipment includes a!! me.
2335 Powder actuated tools chanical means of transmiinns pe=ct from a prime D40 Punch meer up to, but not including, a shaft (oe any put.
2345 Riveter leys er gears on the shafel, the bearings of which integral part of a machine. Directly con.
2350 Sandblasier form an 2355 Saw nected pr.me m.ners are dc6ned as having no trans-23r 0 $cre= driver, bolt setter mnuon apt aratus.
2370 Welding tools 4010 Belts 2399 Iland tools, pe=ered, NEC 4020 Chains, rapes cables 4030 Itrums pullets, sheases 2500 lie rees egmpaient, NEC tlurnaces, retorts, space
.tolo Friction r'utclics 1,raier, s:oir., ranges, etc-not electric) 4W,0 Gears 4099 Methanical pe=cr transmission apparatus.NEC 2600 limtsng apparetus t
2r10 Crancs, derricks 4100 Mesal stents, MC (plates, rods, wire, shapes, nuts, 2620 Eles si. r.
holes, nails, ete-includes molien metal, ingots, and 2f 30 Shmels, dredges melting scrap, but not ores or other raw minerals) i C E00R~0RIGINAL
..5-25
~
Agency of Accialent-Alternate, Detaiteil Classi-Code fication (Continued) yon n,ti,,,,u,beces (in wie as suppuris for people) 5801oor (of a building, a scaffold, a staging, a mine, a schicle, etc) Code Salo Ground (oundoors) 4200 Mmeral items metallic, AEC (produci, of niining; 5H11 ILimps M20 Hools raw or semi processcJ. such as cres and ere concen. 582i Hun =an or platforms a permanent elesated tretes) surf aces) 4300 Af. >,4 items, nonmerathe, NEC (products of rnin. 5830 Side =alks. paths, walkways (outdoor) in.c. s asanng, landshdes, etc, such as dirt, clay, 5810 Stairs, steps 5315 Street, road sa.w. gi svel, pone, etc ) 5899 Workmg surfaces, NEC eiOO Vaper e id pulp item s, NEC 59uo Work erca or ennironment, NEC E00 Parricles (unidentified) 8800 Aliscellaneous, NEC 4700 Plea rs, siccs, s egerarien sin natural or unprocessed 9800 Un4aone n, unidents/ icd (other than particles) . ond.no n --doc, not inclu.te threshed grains, har-sested frusis, hmbed loss, cic) ,y,99 y,,p..,q,f,,,,g,,, 4800 Plastic arems, NEC Iro=ders, sheets, rods, shapes, cic, but not uncombined chemkale or components Al,7 Agency of Accialent Part Classification need in plastic manuf acturing) The agency parts clasu6catian should be especially de-4%0 famps and prime moiers signed to meet the parucular needs for detad in each analy-4910 Eng6nes (sicam, internal combusnon, etc) ., program. les most important function is to preside speci6e 4930 Pumps detail for the special analy6s of accidenis insolving selected For thn purriac, it shauld be highly deisited and 49i0 Turbines (hydraube, sir, etc ) agent s. d,rectiv related to 'he agency under stuJ). 5000 Alurt.ng subirences and equipment t use'this code in man anal >+is programa, homescr. the introduction of only i > <a es of radiation injunes) esii n..se br.ak,l.,= n, in ibe a;ency pari, clas66 canon would 5010 footopes and uradiated sulaiances for indu+ rc= ult in esien6sc ial utanans which would be impracncable trial or medical use for rre ntah"n in sabular form. The general classi6 cation 5020 Hadmm perwnied 1 clam, there fore, is merely a skeleton clas 4 canon 5030 Reactor f uel, raw or processed which should meet all needs for ma s anaissis. hut w hich SMO Hem ter mastes should be substantially amphfied for detailed sindy pregisms. 50iG Sun Sar,0 l'lirasiolet equipment Code 5070 % elding e.juip, 'ent, elect ric are OW Tarts c/ hm/crs and pressure sensels 5080 X-ray and IInoroscope equipment 0510 Fire door "iN Ihr", sabe, controls Soaps, drier cars, cleanias compoundi, MC $100 s O',r.o Shell m Tubes 5300 Scrap, debns, waste matena!s, NEC 0:m l'.ns, NEC 5500 Test.!c oces, AEC (includes animal Elers after Erst n;oo p,rs of huddings and structures (not working sur. scouring and rienning, segetabic and annibene fiber
- f ac es-s e rule 3 6 2 3 6 e
tearept glass), yern, thread, y.ird goods, felts, and 0710 Ceihngs tentale products) 0720 Doors. door frames, door openings 0730 Foun Jations $6CC l'ckles t ccc rule 3 3 2 4 regarding injuries esperi-pan p,p., enred sihile occupiing a seh.cle) 0750 Walls and supporting members (joints, beams, 5601 Animal drawn girders refiers. framing, erci 5610 Aircraft 0770 Window s, win.fow frames, window openings 5620 thshway schiiles, pe=cred 0799 Other parts of buildings and structures, NEC 5630 Plant or industrial schicles $632 lla ndn uc k s. Jolhes, and other non-1300 parts of conacyor, powered schwie, 1110 Ita,kets, containers 5635 } eekhfr, stackers, lumber carriers, and 13 3 Grats, l.chs, chuns cables, pullen, abeases either powered carriers leo it,,oks 5638 Stules. t r actor s, and other po cred 1350 Holt, sowieg schicles 1399 NEC 5640 Rail schicle, $650 Sled *, snan sad ice schicles 2200 Parts of Aand tools, not pourred 5660 Water schicles 2210 Cutung edge 5699 Vehicles, N EC 2220 llandle 2230 llead 5700 rood items, NEC (legs lumber, slabs poles, chips, 2240 Point 2299 NEC and wood product,y O 500DRWL ~
Agency of Accident Part Closelfica: Ion (Continuorri) Code l 2300 Perss of knod tools, powered 2310 Cutting edge 2320 Controls 2330 Drive shaft 2310 Frame 2350 llcad or impact unit 23(,0 %:or or power unit 2399 NEC' 2600 Parts el heuting apparatus 2603 Bed, frame 2610 Doe.m, poles 2611 Conirols 2G20 Cears, Letts, rhains, cables, pull ys, shesies 2625 flooks 2f,30 ior or engine 2633 Tr a< k 2699 NEC 3000 Parts of machines 3005 Bed, frame 3010 Car riage 3015 Chuck 3020 Controle 3025 Dies 3030 Gears. belis, chains, cables, pulleys, shcases 3033 % tors 3480 Point of operation 30L5 Tool rest 3030 Safety desices, guards 3099 NEC 5600 Paris cf ichicles 5th5 A nte M10 Controls, siecring. braking rnechanism 5615 Doors 5610 Frame M25 llull 5630 l ights %)5 %ior l 5640 Propeller %:i 4 heels and aires %',0 Wind.hiclJ, mindows '655 Transmisuon, drne shaft, differential h? NEC PGDR. 9800 Yo egeno cars indiretcJ 9999 % e, egeart part l 27
O 2. ENERGY CLASSIFICATIONS AND TYPICAL EXAMPLES OF ENERGY SOURCES _ Electrical Mass, Gravity, Height Battery Banks Human Effort Diesel Units Stairs High Lines Lifts Transformers Cranes Wiring Bucket and Ladder Switchgear Trucks Underground Wiring Slings Cable Runs Hoists Service Outlets and Fittings Elevators Pumps Jacks Motors Scaffolds and Ladders Heaters Crane Cabs Power Tools Pits Small Equipment Excavations Elevated Doors Nuclear Canals Vessels Vaults Temporary Storage Areas P res s u re-V ol ume/ K-Co n s ta n t-Di s ta n ce Receiving Areas Shipping Areas Boilers Casks Heated Surge Tanks Burial Ground Autoclaves Storage Racks Test Loops and Facilities Canals and Basins Gas Bottles Reactor In-Tank Storage Areas Pressure Vessels Dollies Coiled Springs Trucks Stressed tiembers Hand Carry Gas Receivers Cranes Kinetic-Rotational Li f ts < - Commercial Shops Centrifuges Hot Cells Motors Assembly Areas Pumps Inspection Areas Cooling Tower Fans Test Rigs Cafeteria Equipment Reactors Laundry Equipment Critical Facilities Gears Subcritical Facilities Shop Equipment (Grinders, Saws, Laboratories Brushes,etc.) Pilot Plants Floor Polishers O 28
(3 i Kinetic-Linear Flammable Materials Cars Packing Materials Trucks Rags But.es Gasoline (Storage and in Vehicles) Fork Lifts Lube Oil Carts Coolant Oil Dollies Paint Solvent Railroad Diesel Fuel Surfaces Buildings and Contents Obstructions Trailers and Contents Shears Grease Presses Hydrogen (Incl. Battery Banks) Crane Loads In Motion Gases - Other Pv Blowdown Spray Paint Power Assisted Driving Tools Solvent Vats Corrosive Thermal Radiation Acids Furnaces Caustics Boilers " Natural" Chemicals, (Soil, Steam Lines Air, Water) Lab and Pilot Plant Equipment 4 Decon Solution Solar V Explosive Pyrophoric Electromagnetic and Particulate Radiation Caps Primer Cord Canals Dynamite Plug Storage Powder Metallurgy Storage Areas Dusts Storage Buildings Hydrogen (Incl. Battery Banks) Radioactive Sources and Water Decomp.) Waste and Scrap Gases-0ther Contamination Nitrates Irradiated Experimental and Electric Squibbs Reactor Equipment Peroxides-Superoxides Electric Furnace Blacklight (e.g., Magniflux) Thermal (Except Radiant) Laser Medical X-ray Convection Radiography Equipment and Sources Heavy Metal Weld Preheat Welding Exposed Steam Pipes Electric Arc - Other (High Electric Heaters Current Circuits) Fire Boxes Electron Beam Leading Melting Pot Electric Wiring and Equipment Furnaces 29 l
O Acoustical Radiation Equipment Noise Ultrasonic Cleaners Toxic Pathogenic Acetone Fluorides Carbon Monoxide Lead Ammonia and Compounds Asbestos Trichlorethylene Dusts and Particulates Pes ti ci des-He rbi cides-I ns ec ti ci de s Bacteria Beryllium and Compounds Chlorine and Compounds Decon Solutions Sandblast Metal Plating Asphyxiation-Drowning 9 30
O OTHER SSDC PUBLICATIONS IN THIS SERIES SSDC-1 Occupancy-Use Readiness Manual SSDC-2 Human Factors in Design SSDC-3 A Contractor Guide to Advance Preparation for Accident Investigation SSDC-4 MORT User's Manual SSDC-5 Reported Significant Observation (RS0) Studies SSDC-6 Training as Related to Behavioral Change SSDC-7 ERDA Guide to the Classification of Occupational Injuries and Illnesses SSDC-8 Standardization Guide for Construction and Use of MORT-Type Analytic Trees SSDC-9 Safety In.or mation System Guide P00R~0 RENAL o ,}}