Standard Practice for Human Engineering Program Requirements for Ships and Marine Systems, Equipment, and Facilities

SCOPE
1.1 This practice establishes and defines the requirements for applying human engineering to the development and acquisition of ships and marine systems, equipment, and facilities. These requirements are applicable to all phases of development, acquisition, and testing and shall be integrated with the total system engineering and development, and test effort. It is not expected nor intended that all of the human engineering activities should be applied to every marine program or program phase. Therefore, these activities shall be tailored to meet the specific needs of each program and the milestone phase of the program within the overall life cycle. This tailoring shall be performed by the procuring activity or by the contractor or subcontractor with the assistance and approval of the procuring activity in order to impose only the essential human engineering requirements on each program. Guidance for selection of only the essential requirements is contained in Appendix X1.

General Information

Status
Historical
Publication Date
14-Apr-1991
Current Stage
Ref Project

Relations

Buy Standard

Standard
ASTM F1337-91(2001) - Standard Practice for Human Engineering Program Requirements for Ships and Marine Systems, Equipment, and Facilities
English language
10 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
An American National Standard
Designation:F 1337–91 (Reapproved 2001)
Standard Practice for
Human Engineering Program Requirements for Ships and
Marine Systems, Equipment, and Facilities
This standard is issued under the fixed designation F 1337; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (e) indicates an editorial change since the last revision or reapproval.
1. Scope 3.1.2 critical activity—any human activity that if not ac-
complished in accordance with system requirements (that is,
1.1 This practice establishes and defines the requirements
time limits, specific sequence, necessary accuracy) will have
for applying human engineering to the development and
adverse effects on system or equipment cost, reliability, effi-
acquisition of ships and marine systems, equipment, and
ciency, effectiveness, or safety.
facilities. These requirements are applicable to all phases of
3.1.3 cultural expectation—the cause and effect relation-
development, acquisition, and testing and shall be integrated
ships (for example, red means stop or danger) that humans
with the total system engineering and development, and test
learn from their culture.
effort. It is not expected nor intended that all of the human
3.1.4 duty—a set of operationally related tasks within a
engineering activities should be applied to every marine
given job (for example, communicating, operator mainte-
program or program phase. Therefore, these activities shall be
nance).
tailored to meet the specific needs of each program and the
3.1.5 function—an activity performed by a system (for
milestone phase of the program within the overall life cycle.
example, provide electric power) to meet mission objectives.
This tailoring shall be performed by the procuring activity or
3.1.6 human engineering—a specialized engineering disci-
by the contractor or subcontractor with the assistance and
pline within the area of human factors that applies scientific
approval of the procuring activity in order to impose only the
knowledgeofhumanphysiologicalandpsychologicalcapabili-
essential human engineering requirements on each program.
ties and limitations to the design of hardware to achieve
Guidance for selection of only the essential requirements is
effective man-machine integration.
contained in Appendix X1.
3.1.7 human factors—the application of scientific knowl-
2. Referenced Documents edge about human characteristics, covering both biomedical
and psychosocial considerations, to complete systems, indi-
2.1 ASTM Standards:
vidual equipments, software, and facilities. This application is
F 1166 Practice for Human Engineering Design for Marine
through such specialized fields as human engineering, man-
Systems, Equipment and Facilities
ning, personnel selection, training, training devices and simu-
2.2 Other Standard:
lation, life support, safety, job performance aids, and human
SNAME Sample Model Specification for Human Engineer-
performance testing and evaluation.
ing Purposes—Technical and Research Bulletin 4–22
3.1.8 human interface—any direct contact (that is, physical,
3. Terminology
visual, or auditory) with a piece of hardware or software by a
human operator or maintainer.
3.1 Definitions of Terms Specific to This Standard:
3.1.9 job—the combination of all human performance re-
3.1.1 arrangement drawings—engineering design drawings
quiredforoperationandmaintenanceofonepersonnelposition
that provide plan, sectional, and elevation views of: (1) the
in a system.
configurationandarrangementofmajoritemsofequipmentfor
3.1.10 life support—that area of human factors that applies
mannedcompartments,spaces,orindividualworkstations,and
scientific knowledge regarding the effects of environmental
(2) within the work station, such as in a modular rack or on a
factors on human behavior and performance to items that
fiddleboard.
require special attention or provisions for health promotion,
biomedical aspects of safety, protection, sustenance, escape,
This practice is under the jurisdiction of ASTM Committee F25 on Ships and
survival, and recovery of personnel.
Marine Technologyand is the direct responsibility of Subcommittee F25.07 on
3.1.11 mission—a specific performance requirement im-
General Requirements.
posed on one or more systems (for example, unload cargo)
Current edition approved April 15, 1991. Published November 1991.
Annual Book of ASTM Standards, Vol 01.07. within the operational requirements.
Available from Society of NavalArchitects and Marine Engineers, 601 Pavonia
Ave., Jersey City, NJ 07306, Attn: Technical Coordinator.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
F 1337
3.1.12 operational requirements—requirements under 3.1.22 vendor drawings—design drawings prepared by the
which the platform, system, equipment, or software will be manufacturer of an individual piece of equipment which is
purchased for installation aboard a ship or other marine
expected to operate and be maintained (for example, day/night,
platform.
all weather operation, sea state, speed, endurance) while
completing a specific mission or missions.
4. Summary of Practice
3.1.13 panel layout drawings—detailed drawings that in-
clude such features as: a scale layout of the controls and 4.1 Human Engineering Program Plan—The human engi-
displays on each panel or an item of equipment such as a neering program plan, in accordance with the requirements of
this practice and the equipment or ship specification, shall
shipboardcommandconsole;adescriptionofallsymbolsused;
include the tasks to be performed, human engineering mile-
identification of the color coding used for displays and con-
stones, level of effort, methods to be used, design concepts to
trols; the labeling used on each control or display; and the
be used, and the test and evaluation program, in terms of an
identification of control type (for example, alternate action or
integrated effort within the total project.
momentary), also screen layouts for software generated dis-
4.2 Quality Assurance—Verification of compliance with the
plays.
requirements of this practice and other human engineering
3.1.14 platform—the major hardware (for example, ship,
requirementsspecifiedbythecontractwillbetheresponsibility
off-shore rig, barge, submarine) on, or in which, the individual
oftheprocuringactivity.Humanengineeringperformedduring
equipment, system, or software will be installed or added.
thedevelopmentprogrambyacontractororsubcontractorshall
3.1.15 spatial relationships—placement of multiple but
be demonstrated to the satisfaction of the procuring activity at
separate components of a system together, so it is visually
the scheduled design and configuration reviews and inspec-
obvious that the components are related and used together, or
tions, as well as during development test and evaluation
placementofidenticalcomponentsusedonmultiplesystemsto
inspections, demonstrations, and tests.
provide the user with a spatial clue as to where the components
4.3 Nonduplication—The efforts performed to fulfill the
are located.
human engineering requirements specified herein shall be
3.1.16 subtask—activities (perceptions, decisions, and re- coordinated with, but not duplicate, efforts performed in
sponses) that fulfill a portion of the immediate purpose within accordance with other requirements. Necessary extensions or
transformations of the results of other efforts for use in the
a task (for example, remove washers and nuts on the water
human engineering program will not be considered duplica-
pump).
tion. Instances of duplication or conflict shall be brought to the
3.1.17 system—a composite of subsystems, including
attention of the procuring activity.
equipment, communications, software, and personnel that ei-
4.4 Cognizance and Coordination—Thehumanengineering
ther independently, or in conjunction with other systems,
program shall be coordinated with maintainability, system
performs functions.
safety, reliability, survivability/vulnerability, and integrated
3.1.18 system analysis—a basic tool for systematically de-
logistic support, as well as other human factors functions, such
fining the roles of and interactions between the equipment,
as life support and safety, personnel selection, preparation of
personnel, communications, and software of one or more
jobaids,andtraining.Resultsofhumanengineeringanalysisor
systems. It is an iterative process, requiring updating. Used in
lessons learned information shall be incorporated into the
the early phases of design, it can be useful in allocating
logistic support analysis as applicable. The human engineering
assignmentoftaskstopersonnel,equipment,software,orsome
portion of any analysis, design and development, or test and
combinationthereof.Doneinlaterdesignstages,itcanserveas
evaluation program shall be conducted by, or under the direct
the basis for the arrangement of equipment and work stations.
cognizance of, personnel properly trained and experienced in
3.1.19 task—a composite of related activities (perceptions, human engineering and assigned the human engineering re-
decisions, and responses) performed for an immediate purpose, sponsibility by the contractor or subcontractor.
written in operator/maintainer language (for example, change a
5. Significance and Use
water pump).
3.1.20 task analysis—a method used to develop a time-
5.1 Intended Use—Compliance with this practice will pro-
oriented description of the interactions between the human
vide the procuring activity with assurance that the operator/
operator/maintainer and the equipment or software in accom- maintainer will be efficient and effective in the operation and
plishing a unit of work with a system or individual piece of maintenance of systems, equipment and facilities. Specifically,
it is intended to ensure that:
equipment. It shows the sequential and simultaneous manual
and intellectual activities of personnel operating, maintaining,
5.1.1 System performance requirements are achieved by
or controlling equipment, in addition to sequential operation of appropriate use of the human component,
the equipment.
5.1.2 Proper design of equipment, software and environ-
ment permits the personnel-equipment/software combination
3.1.21 task element—the smallest logically and reasonably
to meet system performance goals,
definable unit of behavior required in completing a task or
subtask (for example, apply counterclockwise torque to the
5.1.3 Design features will not constitute a hazard to person-
nuts, on the water pump, with a wrench). nel,
F 1337
5.1.4 Trade-offs between automated versus manual opera- 6.1.1 Operational Requirements (OR)—Operational re-
tion have been chosen for peak system efficiency within quirements (ORs) are established first to define the parameters
appropriate cost limits, within which the individual equipment, system, or total plat-
5.1.5 Application of selected human engineering design form shall be expected to perform. ORs shall be expressed in
standards are technically adequate and appropriate, such terms as the weather conditions under which it must
operate (for example, rain, snow, sea state limits); number of
5.1.6 Systems and equipments are designed to facilitate
required maintenance, days it must operate without being refueled or resupplied; and
maximumnumberofpersonnelthatwillbeavailabletooperate
5.1.7 Procedures for operating and maintaining equipment
and maintain the hardware. Human engineering shall be
are efficient, reliable and safe,
considered in the development of ORs, especially when the
5.1.8 Potential error-inducing equipment design features are
ORs include requirements on the number, type, or training of
eliminated, or at least, minimized,
operators or maintainers, or both.
5.1.9 Layouts and arrangements of equipment afford effi-
cient communication and use, and 6.1.2 Mission Requirements Analysis—Mission require-
5.1.10 Contractors provide the necessary, technically quali- ments define the performance parameters of the equipment,
fied manpower to accomplish the objectives listed. system, or total platform in greater detail than that provided by
5.2 Scope and Nature of Work—The human engineering the ORs, and in terms of specific activities the hardware/
effort shall include, but not necessarily be limited to, active software is supposed to accomplish. Human engineering shall
participation in three major interrelated areas of platform, be involved in establishing the mission requirements since the
system, and equipment development. human’s capabilities or limitations may well be a controlling
factor regarding whether or not the mission requirements can
5.2.1 Analysis—Starting with a mission analysis developed
within baseline operational requirements, the functions that be met.
must be performed by the system in achieving its mission
6.1.3 System Requirements Analysis—System requirements
objectives shall be identified and described. These functions
analyses define the specific systems that will be needed to
shall be analyzed to determine the best allocation to personnel,
successfully complete each of the missions delineated above.
equipment, software, or combinations thereof. Allocated func-
Human engineering shall be involved in establishing system
tions shall be further dissected to define the specific tasks that
requirements, since some systems can require greater numbers
mustbeperformedtoaccomplishthefunctions.Eachtaskshall
ofpersonnelandhigherskilllevelsforoperatorsormaintainers
be analyzed to determine the human performance parameters,
than others. Human engineering data from existing systems
the system/equipment/software capabilities, and the
similartothosebeingproposedforthenewdesignmaybeused
operational/environmentalconditionsunderwhichthetasksare
as a baseline in defining the new system requirements.
conducted. Task performance parameters shall be quantified,
6.1.4 Function Definition—The functions that must be per-
where possible, and in a form permitting effectiveness studies
formed by each system to achieve the desired mission objec-
of the crew-equipment/software interfaces in relation to the
tives shall be defined. This definition shall be done without
total system operation. Human engineering high risk areas
consideration as to whether the function will be performed by
shall be identified as part of the analysis.
a human, by a machine, or by a combination of the two.
5.2.2 Design and Development—Design and development
Functions shall be stated as a required action (for example,
of the equipment, softwar
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.