I
|
|
|
15.3.1. Lift Truck Standards
|
I
|
|
|
15.3.1.1. Lift trucks shall be in accordance with ANSI/ASME B56.2, Type Designated Area, Use Maintenance, Operator, and ANSI B56.3, Electric Battery-Powered Industrial Trucks, safety standards.
|
C
|
|
|
15.3.1.2. Lift trucks to be used in locations classified as hazardous by the NEC Article 500 shall meet the requirements of NFPA 505, Fire Safety Standard for Powered Industrial Trucks Including Type Designations, Areas of Use, Conversions, Maintenance, and Operation. Replacement tires and other components shall be those approved for the specific application and/or environment.
|
C
|
|
|
Battery powered equipment and its use shall comply with OSHA and NFPA standards. Type EX rated battery powered equipment is the only equipment approved for use in specifically named Class I, Group D or Class II, Group G hazardous locations.
|
I
|
|
|
15.3.1.3. Lift trucks used to transport explosives and propellants or operate in explosive and propellant locations shall also meet the requirements of NASA-STD 8719.12, AFMAN 91-201, and DoD 6055.9-STD.
|
C
|
|
|
15.3.2. Lift Truck General Design Requirements
|
C
|
|
|
15.3.2.1. Lift trucks shall be equipped with shoulder-high wing safety seats with seatbelts.
|
C
|
|
|
15.3.2.2. Personnel platforms attached to lift trucks shall be designed and tested in accordance with 6.3 of this volume.
|
C
|
|
|
15.3.2.3. Critical loads shall not exceed 75 percent of the lift truck rated capacity.
|
C
|
|
|
15.3.3. Lift Truck Tests. Lift trucks shall be tested in accordance with ASME/ANSI B56 Series Safety Standards.
|
C
|
|
|
15.3.4. Lift Truck Data Requirements. Initial and recurring data requirements shall be submitted in accordance with the requirements of Attachment 1, A1.2.5.17 of this volume.
|
C
|
|
|
COMPUTER SYSTEMS AND SOFTWARE |
I
|
|
|
General |
I
|
|
|
16.1.1. NPR 7150.2, NASA Software Engineering Requirements, provides requirements for project computer systems and software. The payload project shall follow the requirements of NASA-STD-8719.13, Software Safety Standard, and NASA-STD-8739.8, Software Assurance Standard for project computer systems and software. The requirements for computer systems and software that are used to control and/or monitor operations identified as safety critical by NASA-STD-8719.13 are described in NASA-STD-8719.13 and below. The term software, as used in this publication, includes firmware and software that is executed on processors in operations within complex electronics. Software requirements do not apply to the design or hardware description language for complex electronic devices. Firmware is software stored in nonvolatile memory and it does not represent complex electronic devices.
Note: Complex electronics encompasses programmable and designable complex integrated circuits. “Programmable” logic devices can be programmed by the user and range from simple chips to complex devices capable of being programmed on-the-fly. “Designable” logic devices are integrated circuits that can be designed but not programmed by the user.
|
C
|
|
|
These requirements are not intended to be used as a checklist; instead, they are to be used in conjunction with safety analyses performed in accordance with applicable standards and directives.
|
I
|
|
|
16.1.2. The requirements shall be tailored to the system or system type under development. Unless specifically excluded by the PSWG and Range Safety, these requirements shall apply to all computer systems and subsystems that perform safety critical functions during the assembly, handling, checkout, test, and launch of payloads.
|
C
|
|
|
These systems and subsystems include ground support equipment (such as test equipment, battery charging/monitoring equipment), and spaceflight hardware systems supplied by the payload project. The payload project should assess all such equipment for possible safety critical computer system functions in software and firmware use.
|
I
|
|
|
16.1.3. In addition to contractor-developed computer systems and software, these requirements shall apply to programmable logic controllers (PLCs), firmware such as erasable programmable read only memory (EPROM), commercial off-the-shelf (COTS) and government off-the-shelf (GOTS) products, and reused code. These requirements shall apply to software that is executed on processors (where applicable) on Complex Programmable Logic Devices (CPLDs), Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), and System on a Chip (SOC) applications, but not to the devices themselves or the hardware description language logic or text.
|
C
|
|
|
Chapter 16, in its entirety, applies to all forms of software and firmware; however, special attention should be paid to the following:
(1) EPROMs or EEPROMs should contain unique version identifiers and be validated via checksum or some other method before installation and use.
(2) COTS, GOTS, and re-use software should be examined and evaluated as to their appropriateness for the intended new use. Unused portions of re-use software should be removed.
|
I
|
|
|
| |
