JSC_NS-OSH-003_Training_and_Functions_of_Test_Safety_Officers.pdf

NS-OSH-003

Revision C

Training and Functions of Test Safety Officers NS/Safety and Test Operations Division

October 17, 2018 Revision C

Verify this is the correct version before use

National Aeronautics and Space Administration Lyndon B. Johnson Space Center Houston, Texas

Unique Work Instruction Training and Function of Test Safety Officers Document No.: NS-OSH-003 Revision: C Date: 10/17/2018 Page 2 of 16

VERIFY THIS IS THE CORRECT VERSION BEFORE USE

Training and Functions of Test Safety Officers

October 17, 2018

Approved by

Stacey A. Menard, Chief

Safety and Test Operations Division

Date: 10/17/2018 Page 3 of 16

Change Record

Revision Date Originator/Phone Description Baseline 03/26/2001 Robert W. Woyan

244-1283 Baseline release

• Transferred from NT as a result of

SR&QA reorganization occurring February, 2001.

• Renumbered from NT-TSF-007, PCN-1 to NS-OSH-003 Baseline.

PCN-1 03/13/2002 Robert D. (Doug)

Harris 483-7101

NS MLC Action:

Author changed to Doug Harris

A 07/12/2002 Robert D. (Doug) Harris 483-7101

Rewrite. Revision bars not used.

B 02/12/2010 Author:

Larry Barnwell 483-2011

Process Owner:

Chris Counts, Lead Analysis and Investigation Team

(NS23)

483-0794

Technical/Process Changes:

Section 1 and 2:

• Clarified Scope and Purpose.

Section 3:

• Updated and added new definitions.

Section 4:

• Clarified

Section 10.1.1.b:

• Added physiological training.

Section 10.1.2.c

• Added ‘letter’ as a notification of satisfactory completion of training plan.

Section 10.2.2

• Clarified recertification

Section 10.2.3

• Clarified recertification

Section 10.3.2.c

• Clarified test plans

Section 10.3.7

• Revised section to address EVA safety notification of testing or training...

Section 10.4.3.a

• Clarified TSO actions.

Section 10.4.3.b

• Removed TREB

Section 10.5.1

• Clarified monitoring of tests

Section 10.5.4.d

Date: 10/17/2018 Page 4 of 16

• Removed pager and added ‘home or cellular phone’.

Section 10.5.7.b

• Clarified TSO actions.

Editorial Changes:

• Approval signatory changed from Wayne

Gremillion to David Loyd.

• Process Owner changed from Wayne

Gremillion to Chris Counts.

• References to NS changed to Safety and

Test Operations Division/NS or STOD) throughout the document.

B with

PCN-1

12/30/2011 NS MLC Editorial Change Clarified records section

C 10/17/2018 Author: Chris Counts

• Section 3: Added ORC, Record, and Records Custodian.

• Section 3: Removed apostrophe ‘s’ on RID’s and Changed User Readiness Review (URR) to Use Readiness Review.

• Section 4: Moved records into a table format and added retention schedules.

• Section 6: Added JPR 1281.9.

• 10.3.3 : Removed wording “test safety officer” after TSO.

• Section 10.6: Added for Measurement and

Verification.

Date: 10/17/2018 Page 5 of 16

1 PURPOSE

The purpose of this procedure is to establish the criteria for an individual to train and function as a Test Safety Officer (TSO). Test Safety is a Johnson Space Center core function of the Safety and Test Operations Division (S&TOD). Test Safety supports S&TOD with routine management and office support, preventive and corrective actions, internal audits, process control, personnel management, record keeping, document and data control, preliminary mishap investigations, test documentation assessment, test readiness review participation, and test operations monitoring.

2 SCOPE

This procedure applies to all hazardous testing and training at JSC, all hazardous testing or training performed for JSC at other locations, JSC sponsored or funded hazardous testing activities, and testing or training involving JSC personnel.

3 DEFINITIONS, ACRONYMS AND TERMS

ATIS: Action Tracking Information System CDR: Critical Design Review Certification: The authorization by appropriately signed document a candidate has satisfactorily completed qualification and training.

Certifying Official: The Safety and Test Operations Division Chief, or authorized delegate, is the certifying official for all TSO candidates.

DR: Discrepancy Report DTP: Detailed Test Procedure HA: Hazard Analysis Hazardous Test: A test wherein any test subject, test team member, observer, or member of the public is exposed to, or has the potential to be exposed to, a hazardous condition.

Potential loss of high-value equipment/facilities or impact to mission is also considered hazardous testing

Hazardous Training: A training profile subjecting the crewmember or test subject to hazardous conditions. Potential loss of high-value equipment/facilities or impact to mission is also considered hazardous training.

IT: Information Technology NBL: Neutral Buoyancy Laboratory OJT: On the Job Training ORC: Organizational Records Coordinator ORI: Operational Readiness Inspection PDR: Preliminary Design Review PSMO: Pressure Systems Manager’s Office QA: Quality Assurance QE: Quality Engineer Qualification: Criteria a candidate must meet to qualify for certification.

Record: 44 US Code §3301: all books, papers, maps, photographs, machine readable materials, or other documentary materials, regardless of physical form or characteristics, made or received by an agency of the United States Government under Federal law or in connection with the transaction

Date: 10/17/2018 Page 6 of 16 of public business and preserved or appropriate for preservation by that agency or its legitimate successor as evidence of the organization, functions, policies, decisions, procedures, operations, or other activities of the Government or because of the informational value of data in them.

Records Custodian: Individual responsible for maintaining Federal records.

RID: Review Item Disposition S&TOD: Safety and Test Operations Division (NS) S&MA: Safety and Mission Assurance Directorate (NA) SATERN: System for Administration, Training, and Education Resources for NASA TD: Test Director Test Safety Manager: The person who has management responsibility for the TSO candidate.

Test Safety Officer (TSO): Certified representative of the S&TOD for hazardous tests and hazardous training.

Test Safety Officer Candidate: An individual who has met the qualification requirements and is in training for certification to be a TSO.

TPS: Task Performance Sheet TR: Test Requestor TRRB: Test Readiness Review Board URR: Use Readiness Review

4 RECORDS

The following records created by this work instruction are maintained by the records custodian per JPR 1440.3, JSC Records Management Procedural Requirements:

Record Record Custodian NASA Retention Schedule

Training History in SATERN database (Training Plan, Training Record, and Written Test Results

Training Focal Point/Coordinator

3/33C

DESTROY OR DELETE 5 YEARS AFTER

SEPARATION OF EMPLOYEE OR WHEN

NO LONGER NEEDED, WHICHEVER

COMES FIRST

Qualifications Experience Date (see paragraph 8.2)

Test Safety Office, Manager

3/33C

DESTROY OR DELETE 5 YEARS AFTER

SEPARATION OF EMPLOYEE OR WHEN

NO LONGER NEEDED, WHICHEVER

COMES FIRST

Record of Class III physical and/or Physiological Training Certification, where required

Test Safety Office, Manager

3/33C

DESTROY OR DELETE 5 YEARS AFTER

SEPARATION OF EMPLOYEE OR WHEN

NO LONGER NEEDED, WHICHEVER

COMES FIRST

Date: 10/17/2018 Page 7 of 16

5 SAFETY PRECAUTIONS AND WARNING NOTES

TSO Job Hazard Analysis NS-STO-WI03

6 REFERENCES

JPR 1281.9, Process Control JPR 1700.1, JSC Safety and Health Handbook JPR 1440.3, JSC Records Management Procedural Requirements NPR 8715.3, NASA Safety Manual NS-STO-W103, TSO Job Hazard Analysis

7 TOOLS, EQUIPMENT, AND MATERIALS

TSO Job Hazard Analysis NS-STO-WI03

8 PERSONAL TRAINING AND CERTIFICATION

8.1 Personnel Training and Certification

NASA Certification to perform as a Test Safety Officer Proof of Specialized Training and successful completion of certification examination.

Maintained by Employee

8.2 Qualifications

The TSO candidate must meet one of the following levels of experience:

• Five years practical engineering experience.

• Three years system safety engineering experience or three years test operations experience.

• Two years of practical engineering experience and 18 credit hours of college level safety courses.

• Two years practical experience in system safety or in test operations safety.

• One year of on-the-job (OJT) training in a specific test area or test discipline qualifies the TSO for a specific area where the OJT occurred The S&TOD may waive any of the above requirements by documenting the rationale in the certification document.

9 RESPONSIBILITIES

• The TSO Manager ensures training and certification of TSO candidates.

• The TSO is responsible for providing support to the Test Directors (TD), and facility managers to assist them in assuring the safety of test subjects, test team personnel, test hardware, operations, and support facilities and equipment.

Date: 10/17/2018 Page 8 of 16

• The TSO assures all applicable safety requirements and specifications are met and all the necessary analyses are complete and adequate to provide a thorough understanding of the risks involved.

• When safety problems are noted, the TSO is responsible to bring them to the attention of the test organization.

• Significant safety concerns which cannot be resolved with the testing organization must be brought to the attention of the S&TOD.

10. Procedure

10.1 Certification

10.1.1 The TSO Manager will:

a. Direct the TSO candidate through the process using the TSO training plan and mentoring process.

b. Provide records of the candidate’s training completion and recommend certification to the certifying official. Records must include the completed training plan, training record, written test results, and where required, the certification of a class III physical and/or physiological training.

c. Actively monitor TSO certification status, and direct recertification, as required. The TSO scheduler will verify work assignments are only given to TSOs currently certified in the respective test area.

d. Ensure the candidate is aware of his/her responsibilities as outlined in JPG 1700.1 and

NPG 8715.3.

10.1.2 The certifying official will:

a. Approve the training plan.

b. Monitor the TSO training program.

c. Issue a certification card or letter upon satisfactory completion of training plan.

10.1.3 Once certified, the TSO is responsible for carrying out the assigned functions and tasks specified in the applicable parts of this procedure. The TSO will not accept work assignments for which they are not certified.

10.2 Continuation of Certification

10.2.1 Recertification is required every three years. Recertification is comprised of a performance assessment by the TSO Manager.

10.2.2 Limited recertification is required for a TSO after six months without performing TSO duties in a specific area. (Exception: TSO Reduced Gravity Certification required recertification after 12 month of no activity.) Limited recertification comprises a performance assessment by the TSO Manager or Lead, and the monitoring of one test under the supervision of a TSO certified in the specific area.

Date: 10/17/2018 Page 9 of 16

10.2.3 Full recertification will be required for a TSO after one year without performing TSO duties in a specific area (Exception: TSO Reduced Gravity Certification required recertification after 18 month of no activity). Full recertification is comprised of a performance assessment by the TSO Manager and a retake of the certification exam. Additionally, one test will be monitored while under the supervision of a TSO certified in the area.

10.3 Test Documentation

10.3.1 Responsibilities. The S&TOD or their representative will provide safety reviews of test documentation to assure implementation of NASA and OSHA safety requirements.

10.3.2 Document Review Requirements

a. Documentation Review. The TSO must review all documentation pertinent to the safety of tests. Safety related comments should be resolved between the TSO and test organization. Significant safety concerns which cannot be resolved with the test organization will be brought to the attention of the S&TOD. The following paragraphs list documents which may be needed for adequate control of safety issues throughout the test life cycle. Based on system, facility, or test complexity, the test organization (with TSO concurrence) will determine which documents are needed for a specific test.

b. Test Request/Requirements Documents. Test request/requirements documents should be reviewed as early in the life cycle of the test as possible. This will allow the cognizant test safety personnel to research the safety requirements for the test prior to other test documentation reviews. The TSO can specify any safety analyses required for the test.

c. Test Plans. Test plans (or test objectives) should be reviewed prior to completion of the Test Readiness Review Board (TRRB). This review will look for data pertinent to the safety and health of the test personnel, high value hardware/facilities, potential impact to mission, and all associated test work place environments. If discrepancies exist in the test plan, they should be called to the attention of the TD prior to the TRRB. If the discrepancies have not been resolved before the TRRB, then these items will be entered into the TRRB record as test constraints.

d. Test Procedures. Test procedures should be reviewed prior to completion of the TRRB.

If there are discrepancies, they must be brought to the attention of the TD prior to the TRRB. If the discrepancy cannot be resolved prior to the TRRB, then the discrepancy will be entered into the TRRB record as a test constraint.

e. Emergency, Contingency and Backout Procedures. These procedures are used to modify the test/training in case of an emergency. Emergency, contingency and backout procedures should be reviewed prior to completion of the TRRB. These procedures may be a part of the detailed test procedures or may be a separate document. Test personnel should be familiar with these procedures prior to the start of the test. In some cases, this may require dry runs for these procedures.

f. Pressure System Documentation. Proof Pressure Certification is evidence the pressure system is adequate for the test requirements. Proof pressure tests should be valid at the time of test. These tests are performed by the test personnel and reviewed by the Pressure Systems Manager’s Office. The TSO should verify all required proof pressure tests and pressure systems certifications are current prior to the start of the test. If it has not been completed prior to the TRRB, the proof pressure test or other applicable

Date: 10/17/2018 Page 10 of 16 pressure systems documentation will be a test constraint and will be entered into the TRRB record.

g. Cleaning Procedures. Cleaning procedures are required for equipment which must be maintained to a specific cleanliness standard. In some cases, where the test is manned or if the test is performed in an atmosphere where the oxygen concentration has been altered, cleaning procedures should be reviewed prior to completion of the TRRB. If there are discrepancies, they will be brought to the attention of the TD prior to the TRRB.

If the discrepancy cannot be resolved prior to the TRRB, then the discrepancy will be entered into the TRRB record as a test constraint. Cleaning (including recleaning if necessary) per the approved procedures must be completed prior to the start of test.

h. Buildup Procedures. Buildup procedures are performed prior to testing to accommodate a particular design requirement. If buildup procedures are separate from the detailed test procedures, then they should be reviewed prior to the start of the buildup of the test article and facility.

i. Technical Hardware Information. TSOs must review applicable technical information to verify and assure appropriate safety protection. This type of information may include:

Blueline drawings (electrical, mechanical, and structural) Pressure, flow, leak rate, stress, vibration, thermal, and load calculations Compatibility studies Failure history of system Safety factor calculations Previous test reports

j. Hazard Analyses. Hazard analyses are normally performed by the test organization and reviewed for adequacy by the TSO. Hazard analyses must be reviewed prior to the completion of the TRRB. If the TSO comments are not incorporated prior to the TRRB completion, then hazard analysis approval will be entered into the TRRB record as a test constraint. The TSO must assure hazard analyses are coordinated between the Test Manager and the test article Subsystem Manager (or Test Requester) to assure all applicable hazards are addressed in the test integrated hazard analysis.

1. The hazard analysis may be performed by the TSO in some situations. When the test organization requests the TSO perform an analysis, it must be coordinated between the TSO, the test organization, the test article Subsystem Manager (or TR), and the S&TOD. The S&TOD will authorize the analysis through an Action Item assignment to the TSO Manager or Lead, who will assign it to the appropriate TSO. The S&TOD must approve analyses performed by the support contractor TSO.

2. The TSO must assess the level of risk associated with each test to determine the level of analysis required. Formal and informal risk assessments are performed on a routine basis for test facilities and systems using the hazard analyses as reference. Risk levels are assigned based on probability and severity potential.

10.3.3 Review Records. The cognizant TSO must keep detailed review records of all test documentation. These records may be in the form of a test log, e-mail message, etc.

10.3.4 Review Checklist. The use of a test documentation review checklist is not required.

However, the TSO may find checklists to be useful aids in the review of test

Date: 10/17/2018 Page 11 of 16 documentation. The use of any checklist does not relieve the TSO from the responsibility to verify test documentation complies with all requirements of this procedure.

10.3.5 Activity Logging

a. The TSO will document any pertinent information in a searchable database at the completion of each test event. This will be a central database searchable by every TSO and S&TOD, not a personal database housed on an individual TSOs PC.

b. The TSO must assure pertinent information is disseminated to other TSOs and test organizations in order to prevent recurrence of similar hazardous situations in the future.

10.3.6 Weekly Activity Report. The TSO will prepare a weekly report of activities and significant events. It will include the name of the activity, a description, and any other pertinent information.

10.3.7 EVA Safety Notification of Testing or Training Issues with Potential Flight Implications.

A TSO must coordinate with EVA Safety to ensure notification of a flight or flight-like equipment concern during testing or training when EVA Safety support is not present.

10.3.8 S&MA Issue Communication

a. The TSO must initiate an anomaly report via e-mail when a nonconformance on flight or flight-like equipment occurs during testing or training and quality assurance support is not present and for items which could be a generic problem for flight hardware.

b. The anomaly report will be submitted to the appropriate NASA S&MA Managers listed on the TSO distribution list.

10.3.9 NASA Form 1627 Mishap Report

a. The TSO must assure a Mishap Report is completed for all mishaps occurring during a test. S&TOD must be notified of the mishap as soon as possible after it occurs.

b. The test organization is responsible for the actual investigation and completion of the forms, unless the S&TOD determines an independent mishap investigation board should be formed.

10.4 Participation in Meetings

10.4.1 Introduction

a. The NASA/JSC Safety Manual requires the S&TOD support all JSC hazardous ground testing/training operations. Part of the fulfillment of these requirements is the attendance at all meetings relating to test safety. Examples of meetings which typically require test safety support are: Preliminary Design Reviews (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), hardware buildup meetings, and as needed Test Requirements Evaluation Board (TREB), and Operational Readiness Inspections (ORI).

b. The S&TOD ensures safety requirements are identified by the test organization and appropriate hazard controls are implemented. Because of high hazard and complex systems, some of the most dangerous operations are in the test areas. The TSO is obligated to fully understand each system and its operating environment. The technical support provided by the TSO to test related meetings is critical to assist in the assurance

Date: 10/17/2018 Page 12 of 16 of a safe test. Included as part of each test or training operation, will be a Test Readiness Review (TRR). A TSO (or S&TOD representative) will be a board member of the Test Readiness Review Board (TRRB).

10.4.2 Responsibilities

a. The certified TSO is responsible for attending and supporting all test support meetings listed above, unless instructed otherwise by the S&TOD.

b. The safety support contractor certified TSO will have signature authority at all meetings.

When an NS representative is in attendance, the safety support contractor TSO will act as a consultant to the NS representative. Attendance by an S&TOD representative does not relieve the safety support contractor TSO from any responsibilities contained in this procedure.

c. The safety support contractor certified TSO is responsible for reporting meeting status to the S&TOD.

10.4.3 Meeting Participation

a. TRRB. The TSO is a board member representing the S&TOD at the TRRB. Once the

TRRB agenda is completed and all open items listed, the TSO will concur on the test readiness. If the TSO feels safety issues have not been fully addressed, then the TSO has two courses of action. First, the TSO may list the issue as an open item and constrain the test on the TRR sheet, or the TSO may decline from signing altogether. It is suggested refusing to concur on a test should be used as a last resort. After signing, the TSO will receive a copy of the completed TRRB summary sheet. The TSO must report any unresolved safety items to the S&TOD as soon as it is determined the issue will impact the test.

b. PDR, CDR, ORI, and Hardware Buildup. The TSO will represent the S&TOD in support of other meetings, such as PDR, CDR, ORI, and hardware buildup meetings. The TSO has full signature authority and will respond to all safety related action items. The TSO may present safety concerns verbally, or if more critical, through Review Item Dispositions (RID’s). The TSO must participate fully in these meetings and pursue any safety concerns which may arise.

10.5 Monitoring of Tests

10.5.1 Introduction. JSC conducts many operations involving hazards to test personnel, test team members, observers, or in some cases the general public, and can include potential for high value hardware/facilities loss, and mission impact. The TSOs responsibility in these operations includes more than the review of test plans, safety analysis, and detailed test procedures. In some cases, real time monitoring of hazardous tests is also included in the TSOs responsibilities.

The duties and responsibilities of the TSO are varied and must follow the entire test life cycle including pre-test, test, and post test.

a. Pre-Test Inspections and Evaluations

b. The TSO is responsible for being aware of all test activities in the TSOs assigned area.

The TSO must assure they are on distribution for organizational activity schedules and a close liaison is maintained with technical representatives, test directors, and engineers.

Date: 10/17/2018 Page 13 of 16

c. The TSO is responsible for coordinating with the QA division on all tests to assure full cooperation exists and the SR&QA organization functions as a unit. Coordination with Quality is necessary to assure problems are addressed fully and every available information source is utilized. On many engineering evaluation tests and tests involving uncontrolled hardware, there are no quality assurance personnel in attendance. In these situations, the TSO represents all S&MA functions and will notify QA in the event Quality Assurance support is needed.

1. The TSO must inspect the test facility and test article prior to initial test operations to assure all hazard closure actions have been accomplished and controls are in place and active.

2. The TSO must coordinate with Quality to assure the test article configuration has been approved and all quality assurance requirements have been met prior to test startup.

3. The TSO must monitor pre-test emergency drills, dry runs, and dry functional tests as needed to assure validation of design and procedural safety measures.

d. The TSO serves as a member of the TRRB and must attend all applicable pretest activities, such as emergency drills, buildup meetings, open items reviews, etc. TSOs have the responsibility to advise the TD to discontinue any pretest, test, or post-test operation deemed to be unsafe. After being advised to stop any test activity, the TD should stop the test or redirect it to a safe position. This is at the TD’s discretion. At no time is the TSO to take direct control of the test team. The TSO always works through the TD. If the TD does not accept the advice of the TSO, the TSO must notify the S&TOD of the event and their rationale for recommending a test hold or test terminate.

e. The TSO is not required to be present during all test activities. The amount of physical attendance required is a function of the hazard level, hardware cost, and program impact.

The TSO will exercise judgment in allocating test coverage time and inform the S&TOD project support personnel of manpower requirements. If the physical presence of a TSO is not required, the amount of time given to a test is at the discretion of the TSO. With regard to attending and monitoring tests, priority will be given to tests involving human subjects, hazardous materials, high cost hardware, etc. In some special cases TSO monitoring may be requested for special tests. TSO support must be coordinated through the S&TOD.

f. The TSO may develop and use checklist as an aid in repeat situations.

g. Certified TSOs have signature authority for the S&TOD for situations requiring safety approval. The support contractor TSO normally serves as advisor to S&TOD at TRRB for manned tests. The S&TOD representative attending the TRRB may sign on the TRRB record as TSO, upon recommendation of the support contractor TSO assigned to the test. The support contractor TSO is a TRRB member for Neutral Buoyancy Lab (NBL) and unmanned test programs. As such, the support contractor TSO has signature authority during these test life cycles. The test organization may alter support contractor signature authority with S&TOD concurrence.

10.5.2 Responsibilities. The S&TOD, or its designated representative, is responsible for real time monitoring of all hazardous or high cost hardware tests as designated by the S&TOD. This monitoring includes, but is not limited to review of applicable documentation, real time monitoring of the test, and emergency action if necessary.

Date: 10/17/2018 Page 14 of 16

10.5.3 Pretest Activities. Pretest activities include:

a. Inspection of the test setup.

b. Evaluation of deviation sheets, open Discrepancy Reports (DR), Task Performance

Sheets (TPS), Material Review Board (MRB) actions, waiver requests, open items, Hazard Analyses, Detailed Test Procedures, and other test related requirements.

Significant safety concerns which cannot be resolved with the testing organization must be brought to the attention of the S&TOD

c. Participation in test readiness review board meetings. See paragraph 10.5.a.4.

d. Provide safety support to the Test Director. See paragraph 10.5.a.4.

e. In the absence of S&TOD support, the TSO may perform certain quality assurance functions, such as:

1. Inspect equipment configuration and documentation

2. Verify instrument calibration and proof test currency

3. Verify the quality of consumables (air, water, etc.)

10.5.4 Test Activities

a. TSOs must advise the TD of any unsafe conditions prior to testing. If an unsafe condition is developing due to testing procedures, the TSO must notify the TD of the condition and recommend a resolution.

b. TSO functions during tests must include:

1. Monitoring the test. The TSO may find it useful to maintain a log of significant events throughout the test. If generated, the log is to be filed, along with other test documentation pertinent to safety, in a TSO maintained file.

2. Advising the TD on all matters relative to unsafe test completion.

3. Ensure test procedures are followed.

c. If the TSO determines the continuation of the test presents a clear, present, and unwarranted danger to the subject, test team members, or NASA property, the TSO must advise the TD to abort or terminate the test. The TSO may request the TD to place the test on hold or back out to a safe position while the hazardous condition is corrected or a discussion is held about the continuation of the test. Further test termination guidance is provided in section 10.5(f) of this procedure.

d. If physical TSO presence is not required, the TSO must be available during off duty hours by leaving their home or cellular phone number with the TD, for any problems occurring during off duty hours.

e. Monitoring of certain crew training activities. The selection of which training activities to monitor will be based on the type of training and the nature of the test, but includes as a minimum all emergency drills. Procedural demonstrations must be monitored by a TSO when:

1. The TSOs review of the test procedures indicates possible procedural hazards.

2. Verification of procedural adequacy is required.

10.5.5 Post Test Activities. After completion of test activities the TSO must perform the following functions:

a. Observe egress operations

Date: 10/17/2018 Page 15 of 16

b. Ensure post-test operations are conducted safely during the disassembly and disposition of the test hardware.

c. Participate in debriefing if a safety issue arose during the test life cycle.

d. Assure corrective action is taken on significant hardware or procedure anomalies. A written report of the anomaly must be submitted to the S&TOD. For hardware anomalies, S&TOD will forward a copy of the report to the NASA Flight Systems Safety and Mission Assurance branch responsible for the hardware.

e. The TSO may conduct daily spot checks of manned test areas prior to daily test runs to assure the continuing safety of the test.

10.5.6 TSO Recommended Termination of a Hazardous Test

a. Criteria for recommending the termination of a test. The TSO must advise the TD to terminate a test if either of the following two conditions is present:

1. There is a clear and present danger to the subject, test team personnel, or high cost hardware.

2. The test procedures are not being followed as approved by the TRRB, or as modified by an approved test deviation.

b. The following steps will be taken in terminating a test. The TSO can take the following steps in any order necessary. However, if a clear and present danger exists, the TSO is to advise the TD to terminate the test immediately. The TSO may substitute “hold” or “back out to a safe position” for “terminate” as deemed appropriate.

1. Consult with support personnel (e.g., suit engineer or technician, data acquisition personnel, medical personnel, or test conductor)

2. Consult with TD

3. Enter communication loop and advise the TD to terminate the test and state the reason(s)

4. If the TD fails to terminate the test, inform the S&TOD a TD has not complied with the TSOs advice to terminate a test

c. As soon as conditions permit, the TSO must make a verbal report to the S&TOD of a safety related test termination, hold, or back out. This must be followed with a written report within five (5) working days. This must be done in all cases, whether the TD complied with the TSOs advice or not.

10.5.7 Incident Reporting

a. In the event of a serious anomaly or incident (i.e., death, injury, or major property damage), the TSO must immediately inform the appropriate point of contact within

S&TOD.

b. An appropriate written report will be submitted to the S&TOD. While on station, the TSO will do the following:

1. Awareness. If not already cognizant of the situation, notify the TD and advise as requested.

2. Stabilize. Ensure the test is brought to a safe, stable condition to prevent further injury or damage.

3. Secure the scene. Ensure the conditions at the time of the incident are maintained as much as possible. Conditions may have to be altered due to rescue operations.

4. Safeguard evidence. Ensure voice, video, and other evidence are impounded.

Date: 10/17/2018 Page 16 of 16

5. Reporting. Advise the TD and test organization management on Mishap and Close Call reporting requirements.

6. If the TSO is not physically present, and is informed of an incident, the TSO will use their judgment as to whether to go to the test location or not. The TSO will notify NS or NA as soon as possible. If the TSO chooses to go to the test location, steps 1 through 4 of Section 10.5.7(b) will be followed.

10.6 Measurement and Verification

This process is measured and verified as prescribed by JPR 1281.9, Process Control, as follows:

Success will be measured by signature of the Test Safety Officer certification letter by the Safety and Test Operations Division Chief or their designee.

11 FLOW CHART

None