GSFC-STD-7000 REV A-2013 GENERAL ENVIRONMENTAL VERIFICATION STANDARD (GEVS).pdf

《GSFC-STD-7000 REV A-2013 GENERAL ENVIRONMENTAL VERIFICATION STANDARD (GEVS).pdf》由会员分享，可在线阅读，更多相关《GSFC-STD-7000 REV A-2013 GENERAL ENVIRONMENTAL VERIFICATION STANDARD (GEVS).pdf（203页珍藏版）》请在麦多课文档分享上搜索。

1、Check the GSFC Technical Standards Program website at http:/standards.gsfc.nasa.gov or contact the Executive Secretary for the GSFC Technical Standards Program to verify that this is the correct version prior to use. GSFC-STD-7000A 4/22/2013 Supersedes GSFC-STD-7000 GENERAL ENVIRONMENTAL VERIFICATIO

2、N STANDARD (GEVS) For GSFC Flight Programs and Projects Approved By: NASA GODDARD SPACE FLIGHT CENTER Greenbelt, Maryland 20771 Original Signed by: Director of Applied Engineering and Technology Goddard Space Flight Center Original Signed by: Director of Flight Projects Goddard Space Flight Center O

3、riginal Signed by: Director of Safety and Mission Assurance Goddard Space Flight Center Original Signed by: Chief Engineer Goddard Space Flight Center Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Check the GSFC Technical Standards Program website

4、at http:/standards.gsfc.nasa.gov or contact the Executive Secretary for the GSFC Technical Standards Program to verify that this is the correct version prior to use. ii GEVS Changes to GENERAL ENVIRONMENTAL VERIFICATION STANDARD Change No. Date Nature of Change Baseline April 2005 A 4/22/2013 Major

5、update - STS references removed; Reference to Office of Mission Success removed; Added definition of anomaly; Significant updates to the following sections: 1.13; 2.2.5; 2.4.1.2; 2.4.1.4.1; 2.4.2.2; 2.4.2.6; 2.4.4.1; 2.4.4.2; 2.6.2.4; Section 1.14 added; Section 2.5 rewritten; Section 2.7 rewritten

6、CCR Number CCR-D-0071 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Check the GSFC Technical Standards Program website at http:/standards.gsfc.nasa.gov or contact the Executive Secretary for the GSFC Technical Standards Program to verify that this

7、is the correct version prior to use. iii TABLE OF CONTENTS Paragraph Page SECTION 1 - GENERAL INFORMATION 1.1 PURPOSE . 1-1 1.2 APPLICABILITY AND LIMITATIONS 1-1 1.3 THE GSFC VERIFICATION APPROACH. 1-1 1.4 OTHER ASSURANCE REQUIREMENTS 1-2 1.5 RESPONSIBILITY FOR ADMINISTRATION 1-2 1.6 GEVS CONFIGURAT

8、ION CONTROL AND DISTRIBUTION . 1-2 1.7 APPLICABLE DOCUMENTS 1-2 1.7.1 Spacecraft Tracking and Data Network Simulation 1-2 1.7.2 Deep Space Network (DSN) Simulation . 1-3 1.7.3 NASA Standards . 1-3 1.7.4 Military Standards for EMC Testing 1-3 1.7.5 Military Standards for Non-Destructive Evaluation .

9、1-3 1.8 DEFINITIONS 1-3 1.9 CRITERIA FOR UNSATISFACTORY PERFORMANCE 1-8 1.9.1 Failure Occurrence 1-8 1.9.2 Failures with Retroactive Effect . 1-8 1.9.3 Failure Reporting . 1-8 1.9.4 Wear Out . 1-8 1.10 TEST SAFETY RESPONSIBILITIES 1-8 1.10.1 Operations Hazard Analysis, Responsibilities For 1-9 1.10.

10、2 Treatment of Hazards 1-9 1.10.3 Facility Safety 1-9 1.10.4 Safety Responsibilities During Test 1-9 1.11 TESTING OF SPARE HARDWARE . 1-9 1.12 TEST FACILITIES, CALIBRATION . 1-10 1.13 TEST CONDITION TOLERANCES 1-10 1.14 TEST MEASUREMENT CONSIDERATIONS 1-12 SECTION 2 - VERIFICATION PROGRAM SECTION 2.

11、1 - SYSTEM PERFORMANCE VERIFICATION 2.1 SYSTEM PERFORMANCE VERIFICATION . 2.1-1 2.1.1 Documentation Requirements 2.1-1 2.1.1.1 System Performance Verification Plan . 2.1-1 2.1.1.1.1 Environmental Verification Plan . 2.1-1 2.1.1.2 System Performance Verification Matrix 2.1-2 2.1.1.2.1 Environmental T

12、est Matrix . 2.1-2 2.1.1.3 Environmental Verification Specification 2.1-3 2.1.1.4 Performance Verification Procedures 2.1-3 2.1.1.5 Verification Reports 2.1-3 2.1.1.6 System Performance Verification Report . 2.1-3 2.1.1.7 Instrument Verification Documentation 2.1-4Provided by IHSNot for ResaleNo rep

13、roduction or networking permitted without license from IHS-,-,-Paragraph Page Check the GSFC Technical Standards Program website at http:/standards.gsfc.nasa.gov or contact the Executive Secretary for the GSFC Technical Standards Program to verify that this is the correct version prior to use. iv SE

14、CTION 2.2 - ENVIRONMENTAL VERIFICATION 2.2 APPLICABILITY . 2.2-1 2.2.1 Test Sequence and Level of Assembly 2.2-1 2.2.2 Verification Program Tailoring 2.2-1 2.2.3 Qualification if Hardware by Similarity 2.2-3 2.2.4 Test Factors/Durations . 2.2-4 2.2.5 Structural Analysis/Design Factors of Safety . 2.

15、2-4 SECTION 2.3 - ELECTRICAL FUNCTION and b. All space flight hardware, including interface hardware that is developed by GSFC or any of its contractors and that is provided to another NASA installation or independent agency as part of a payload that is not managed by GSFC. The provisions herein are

16、 generally limited to the verification of ELV payloads and to those activities (with emphasis on the environmental verification program) that are closely associated with such verification, such as workmanship and functional testing. The standard is written in accordance with the current GSFC practic

17、e of using a single protoflight payload for both qualification testing and space flight (see definition of hardware, 1.8). The protoflight verification program, therefore, is given as the nominal test program. 1.3 THE GSFC VERIFICATION APPROACH Goddard Space Flight Center endorses the full systems v

18、erification approach in which the entire payload is tested or verified under conditions that simulate the flight operations and flight environment as realistically as possible. The standard is written in accordance with that view. However, it is recognized that there may be unavoidable exceptions, o

19、r conditions which make it preferable to perform the verification activities at lower levels of assembly. For example, testing at lower levels of assembly may be necessary to produce sufficient environmentally induced stresses to uncover design and workmanship flaws. These test requirements should b

20、e tailored for each specific space program. For some projects, tailoring might relax the requirements in this standard; however, for other projects the requirements may be made more stringent to demonstrate more robustness or greater confidence in the system performance. Provided by IHSNot for Resal

21、eNo reproduction or networking permitted without license from IHS-,-,-GENERAL INFORMATION _ GENERAL INFORMATION Check the GSFC Technical Standards Program website at http:/standards.gsfc.nasa.gov or contact the Executive Secretary for the GSFC Technical Standards Program to verify that this is the c

22、orrect version prior to use. 1-2 Since testing at the component (or unit) level, or lower level of assembly for large components, often becomes a primary part of the verification program, all components should be operating and monitored during all environmental tests if practicable. Environmental ve

23、rification of hardware is only a portion of the total assurance effort at GSFC that establishes confidence that a payload will function correctly and fly a successful mission. The environmental test program provides confidence that the design will perform when subjected to environments more severe t

24、han expected during the mission, and provides environmental stress screening to uncover workmanship defects. The total verification process also includes the development of models representing the hardware, tests to verify the adequacy of the models, analyses, alignments, calibrations, functional/pe

25、rformance tests to verify proper operation, and finally end-to-end tests and simulations to show that the total system will perform as specified. Other tests not included herein may be performed as required by the project. The level, procedure, and decision criteria for performing any such additiona

26、l tests shall be included in the system verification plan and system verification specification (section 2.1). 1.4 OTHER ASSURANCE REQUIREMENTS In addition to the verification program, the assurance effort includes parts and materials selection and control, reliability assessment, quality assurance,

27、 software assurance, design reviews, and system safety. 1.5 RESPONSIBILITY FOR ADMINISTRATION The responsibility and authority for decisions in applying the requirements of this standard rest with the project manager. The general/environmental requirements are intended for use by the flight project

28、managers, assisted by the systems assurance managers, and systems engineering in developing project-unique performance verification requirements, plans, and specifications that are consistent with current NASA program/project planning. 1.6 GEVS CONFIGURATION CONTROL AND DISTRIBUTION This document is

29、 controlled and maintained by the GSFC Institutional Support Office and is available through the Goddard Document Management System (GDMS). 1.7 APPLICABLE DOCUMENTS The following documents may be needed in formulating the environmental test program. The user must ensure that the latest versions are

30、procured and that the most recent changes and additions are included. 1.7.1 Spacecraft Tracking and Data Network Simulation - STDN No. 101.6, Portable Simulation System and Simulations Operation Center Guide for TDRSS it is subject to a design qualification test program; it is not intended for fligh

31、t. b. Flight Hardware: Hardware to be used operationally in space. It includes the following subsets: (1) Protoflight Hardware: Flight hardware of a new design; it is subject to a qualification test program that combines elements of prototype and flight acceptance verification; that is, the applicat

32、ion of design qualification test levels and flight acceptance test durations. (2) Follow-On Hardware: Flight hardware built in accordance with a design that has been qualified either as prototype or as protoflight hardware; follow-on hardware is subject to a flight acceptance test program. (3) Spare

33、 Hardware: Hardware the design of which has been proven in a design qualification test program; it is subject to a flight acceptance test program and is used to replace flight hardware that is no longer acceptable for flight. (4) Reflight Hardware: Flight hardware that has been used operationally in

34、 space and is to be reused in the same way; the verification program to which it is subject depends on its past performance, current status, and the upcoming mission. Level of Assembly: The environmental test requirements of GEVS generally start at the component or unit level assembly and continue h

35、ardware/software build through the system level (referred to in GEVS as the payload or spacecraft level). The assurance program includes the part level. Verification testing may also include testing at the assembly and subassembly levels of assembly; for test record keeping, these levels are combine

36、d into a “subassembly“ level. The verification program continues through launch, and on-orbit performance. The following levels of assembly are used for describing test and analysis configurations: Assembly: A functional subdivision of a component consisting of parts or subassemblies that perform fu

37、nctions necessary for the operation of the component as a whole. Examples are a power amplifier and gyroscope. Component: A functional subdivision of a subsystem and generally a self-contained combination of items performing a function necessary for the subsystems operation. Provided by IHSNot for R

38、esaleNo reproduction or networking permitted without license from IHS-,-,-GENERAL INFORMATION _ GENERAL INFORMATION Check the GSFC Technical Standards Program website at http:/standards.gsfc.nasa.gov or contact the Executive Secretary for the GSFC Technical Standards Program to verify that this is t

39、he correct version prior to use. 1-6 Examples are electronic box, transmitter, gyro package, actuator, motor, battery. For the purposes of this document, “component“ and “unit“ are used interchangeably. Instrument: A spacecraft subsystem consisting of sensors and associated hardware for making measu

40、rements or observations in space. For the purposes of this document, an instrument is considered a subsystem (of the spacecraft). Module: A major subdivision of the payload that is viewed as a physical and functional entity for the purposes of analysis, manufacturing, testing, and recordkeeping. Exa

41、mples include spacecraft bus, science payload, and upper stage vehicle. Part: A hardware element that is not normally subject to further subdivision or disassembly without destruction of design use. Examples include resistor, integrated circuit, relay, connector, bolt, and gaskets. Payload: An integ

42、rated assemblage of modules, subsystems, etc., designed to perform a specified mission in space. For the purposes of this document, “payload“ and “spacecraft“ are used interchangeably. Other terms used to designate this level of assembly are Laboratory, Observatory, Satellite and System Segment. Spa

43、cecraft: See Payload. Other terms used to designate this level of assembly are Laboratory, Observatory, and satellite. Section: A structurally integrated set of components and integrating hardware that form a subdivision of a subsystem, module, etc. A section forms a testable level of assembly, such

44、 as components/units mounted into a structural mounting tray or panel-like assembly, or components that are stacked. Subassembly: A subdivision of an assembly. Examples are wire harness and loaded printed circuit boards. Subsystem: A functional subdivision of a payload consisting of two or more comp

45、onents. Examples are structural, attitude control, electrical power, and communication subsystems. The science instruments or experiments are also included as subsystems of the payload. Unit: A functional subdivision of a subsystem, or instrument, and generally a self-contained combination of items

46、performing a function necessary for the subsystems operation. Examples are electronic box, transmitter, gyro package, actuator, motor, battery. For the purposes of this document, “component“ and “unit“ are used interchangeably. Limit Level: The maximum expected flight level (consistent with the mini

47、mum probability levels of Table 2.4-2). Margin: The amount by which hardware capability exceeds requirements. Module: See Level of Assembly. Nonconformance: A condition of any hardware, software, material, or service in which one or more characteristics do not conform to specified requirements. Prov

48、ided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-GENERAL INFORMATION _ GENERAL INFORMATION Check the GSFC Technical Standards Program website at http:/standards.gsfc.nasa.gov or contact the Executive Secretary for the GSFC Technical Standards Program to verify that this is the correct version prior to use. 1-7 Offgassing: The emanation of volatile matter of any kind from materials into a manned pressurized volume. Outgassing: The emanation of volatile materials under vacuum co