1、CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE MWI 1280.5 REVISION H EFFECTIVE DATE: February 3, 2009 EXPIRATION DATE: February 3, 2014 MARSHALL WORK INSTRUCTION QD01 MSFC ALERT PROCESSING Provided by IHSNot for R
2、esaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction QD01 MSFC ALERT Processing MWI 1280.5 Revision: H Date: February 3, 2009 Page 2 of 34 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT
3、 VERSION BEFORE USE DOCUMENT HISTORY LOG Status (Baseline/ Revision/ Canceled) Document Revision Effective Date Description Baseline 5/14/99 Document converted from MSFC-P14.2-C01 to a Directive. Previous history retained in system as part of canceled or superseded ISO Document files. Revision A 8/2
4、0/99 Document changed to match revised MSFC organization and to eliminate MMI 5310.2 Revision B 4/8/02 Revised to eliminate reference to specific S Change name of records retention document; Revise applicability Revision E 11/21/2003 Add 7-day announcement, delinquent announcement, and 30-day extens
5、ion features Revision F 10/15/2004 Revised to bring document in compliance with the HQ Rules Review Action (CAITS: 04-DA01-0387). Changes were also made to reflect S Incorporated DCB review comments corrections; Split paragraphs with multiple “shall” statement; Deleted Section 2.3 as redundant; Chan
6、ged traceability comments to match MPR 8040.2; Deleted non-used documents from Applicable Documents; Translated some acronyms; Incorporated various non-technical formatting and wording changes; Added definitions for certain job titles/tasks; Updated ALERT data system URL; Updated Appendix C for upda
7、ted form and data field descriptions Added MPR 1440.2 as an Applicable Document and referenced it in Section 9. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction QD01 MSFC ALERT Processing MWI 1280.5 Revision: H Date: February
8、 3, 2009 Page 3 of 34 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 1. PURPOSE 1.1 The purpose of this Marshall Work Instruction (MWI) is to establish Marshall Space Flight Center (MSFC) responsibilities and inst
9、ructions for Acute Launch Emergency Restraint Tip (ALERT) and ALERT-type notification processing for government hardware described in MPD 1280.1. 1.2 The MSFC system for processing ALERTs and ALERT-type notifications is designed to: (1) prevent occurrence on MSFC-controlled products of nonconformanc
10、es documented in the Government-Industry Data Exchange Program (GIDEP), NASA ALERT processing systems, or similar notification systems; (2) provide the impact of identifying and correcting ALERT and ALERT-type product problems on MSFC-controlled products when requested; (3) prevent occurrence on oth
11、er government products of product supplier problem issues which are found on MSFC government products; and (4) satisfy requirements of NSTS 5300.4 (1D-2), NPD 8720.1, NPD 8730.2, NPR 8735.1, and NPD 1280.1. 2. APPLICABILITY 2.1 This MWI applies to the personnel, programs, projects, and activities at
12、 MSFC and MSFCs Michoud Assembly Facility (MAF), including contractors and resident agencies to the extent specified in their respective contracts or agreements. (“Contractors,” for purposes of this paragraph, include contractors, grantees, Cooperative Agreement recipients, Space Act Agreement partn
13、ers, or other agreement parties.) 2.2 This MWI shall be applicable to all MSFC organizations and programs which use, develop, or provide products for the Government or Government entities when the product requires identification and traceability per MPR 8040.2. This includes flight hardware, ground
14、support equipment, test equipment, and other products as defined by the design control process owner and program/project manager/customer/user. For flight projects, the reporting response is required as defined in NPR 8735.1, Figure 1 “Decision Points for Discontinuing Closed-Loop GIDEP Reporting fo
15、r Flight Systems.” 3. APPLICABLE DOCUMENTS 3.1 NPD 1280.1, “NASA Management System Policy” 3.2 NPD 2110.1, “Foreign Access to NASA Technology Transfer Materials” 3.3 NPD 8720.1, “NASA Reliability and Maintainability (R typical titles include Office Manager, Directorate Director, Project Manager. 5.1
16、2 Problem Advisory (PA). (1) Preliminary information on a suspected problem or (2) A Government-Industry Data Exchange Program document reporting a problem with parts, components, materials, manufacturing processes, specifications, software, facilities, or test equipment having an unknown or low pro
17、bability of causing problems for other users. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction QD01 MSFC ALERT Processing MWI 1280.5 Revision: H Date: February 3, 2009 Page 6 of 34 CHECK THE MASTER LIST at https:/repository.m
18、sfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 5.13 Safe-ALERT (SA). A notice of defective or nonconforming items, products, or conditions that create a safety hazard for personnel or equipment. 5.14 S&MA Project Representative. Individual, Team or Branch S
19、&MA person assigned with coordinating, leading and/or performing safety-related tasks for a specific project. 6. INSTRUCTIONS Actionee Section Perform all actions MSFC Organization Lead 6.1 Including ALERT Processing in Organization Plans/Contract Requirements. Each applicable MSFC organization shal
20、l include ALERT participation as a part of its operation by doing the following: MSFC Organization Lead 6.1.1 Stating ALERT processing in the Project Plan, the Reliability Plan, a task agreement, operating instructions, or the contract, modeling their requirements after the sample requirements state
21、ment referenced in Appendix A, Standard (STD) Reliability and Maintainability (RM) Data Requirement Description (DRD) STD/RM-ALERT, MSFC ALERT System Documentation. MSFC Organization Lead 6.1.2 Appointing organization ALERT Coordinators to serve as prime points of contact for ALERT notification, tra
22、cking, review, and response. MSFC Organization Lead 6.1.2.1 The Organizational Lead shall inform the MSFC ALERT Coordinator of these appointments. MSFC ALERT Coordinator 6.1.3 The MSFC ALERT Coordinator shall add organization ALERT Coordinators to distribution for ALERTs MSFC ALERT Coordinator 6.1.3
23、.1 The MSFC ALERT Coordinator shall provide training materials and/or instruction in ALERT processing to all new organization ALERT Coordinators. S&MA Project Representative 6.1.4 If a flight hardware project is involved, the S&MA Project Representative shall assure that adequate parts traceability
24、is specified in keeping with the requirements of MPR 8040.2. 6.2 According to the “GIDEP Operations Manual,” generation of an ALERT is the obligation of the organization that Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction Q
25、D01 MSFC ALERT Processing MWI 1280.5 Revision: H Date: February 3, 2009 Page 7 of 34 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Actionee Section Perform all actions initially discovers product nonconformance.
26、Therefore, ALERT submittal processing shall consist of the following steps: Organization ALERT Coordinators 6.2.1 The Organization ALERT Coordinators shall follow the rules for generating and submitting ALERTs as stated in the “GIDEP Operations Manual. MSFC ALERT Originator 6.2.1.1 The MSFC ALERT Or
27、iginator shall initiate the ALERT not more than 60 days from time of discovery of the nonconforming or defective item. MSFC ALERT Originator 6.2.2 The MSFC ALERT Originator shall complete GIDEP Form 97-1 (shown and explained in Appendix B). MSFC ALERT Originator 6.2.3 The MSFC ALERT Originator shall
28、 provide a copy of the Form 97-1 draft to the MSFC ALERT Coordinator for review, approval, and distribution within the NASA community. (See 6.3.) MSFC ALERT Originator 6.2.4 The MSFC ALERT Originator shall send the draft ALERT information to the product supplier to provide them an opportunity to res
29、pond. MSFC ALERT Originator 6.2.5 The MSFC ALERT Originator shall transmit the official form and supplier response (if any) to GIDEP after MSFC approval and at least 15 but not more than 30 working days after supplier notification. MSFC ALERT Coordinator 6.3 Receiving and Distributing ALERTs. Receip
30、t and distribution of ALERTs and ALERT-type notifications for MSFC shall be performed by the MSFC ALERT Coordinator. MSFC ALERT Coordinator 6.3.1 The MSFC ALERT Coordinator shall receive ALERTs and ALERT-type notifications from GIDEP, other NASA Centers, and within MSFC, usually by electronic mail o
31、r facsimile transmission, and sometimes hardcopy. MSFC ALERT Coordinator 6.3.2 The MSFC ALERT Coordinator shall screen the information for potential aerospace applicability. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction QD
32、01 MSFC ALERT Processing MWI 1280.5 Revision: H Date: February 3, 2009 Page 8 of 34 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Actionee Section Perform all actions MSFC ALERT Coordinator 6.3.2.1 If information
33、 is potentially applicable, the MSFC ALERT Coordinator shall: MSFC ALERT Coordinator 6.3.2.1.1 Determine whether it is new or updated information. MSFC ALERT Coordinator 6.3.2.1.2 Assign an MSFC tracking number. MSFC ALERT Coordinator 6.3.2.1.3 Enter the ALERT information into the receipt log. MSFC
34、ALERT Coordinator 6.3.3 6.3.3.1 6.3.3.2 6.3.3.3 6.3.3.4 6.3.3.5 When one or more ALERT-type notifications are received (not to exceed 2 work days from receipt of the oldest notification, except for 2 days prior to launch in which notifications are held until after launch unless specifically authoriz
35、ed for release by the S&MA Shuttle Assurance Department Manager or his designated representative as critical for mission safety), the MSFC ALERT Coordinator shall prepare the MSFC ALERT Notification, Tracking, and Response Data System for ALERT distribution, by: Entering basic ALERT data into an ALE
36、RT record. Downloading the image file to an MSFC Web-accessible location. Saving the monthly distribution summary sheet for Web call up. Updating the MSFC ALERT Web page. Updating the MSFC ALERT archive for the new ALERT distribution. MSFC ALERT Coordinator 6.3.4 The MSFC ALERT Coordinator shall dis
37、tribute information through the database and associated e-mail to all Organization ALERT Coordinators for response and to others, as requested, for information purposes only. NOTE: S&MA historical ALERT-type data (distributed at MSFC from April 1997 forward) is available from the Provided by IHSNot
38、for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction QD01 MSFC ALERT Processing MWI 1280.5 Revision: H Date: February 3, 2009 Page 9 of 34 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CO
39、RRECT VERSION BEFORE USE Actionee Section Perform all actions ALERT application, Reporting option, Historical ALERTs report that is accessible through URL: https:/safety.msfc.nasa.gov/apps/tps/tps_main.asp. MSFC ALERT Coordinator 6.3.5 The MSFC ALERT Coordinator shall record the organizations that r
40、eceived the distribution using the data system to track responses. Organization ALERT Coordinator 6.4 Evaluating and Responding to ALERTs. When an MSFC ALERT distribution is received by an Organization ALERT Coordinator, the coordinator shall: Organization ALERT Coordinator 6.4.1 Perform ALERT evalu
41、ation by comparing each hardware ALERT item against hardware used within or stocked by the organization. Organization ALERT Coordinator 6.4.1.1 For each ALERT for which the hardware is NOT used or stocked by the organization, submit a NO IMPACT indication into the MSFC ALERT data response data recor
42、d. (See Appendix D.) Organization ALERT Coordinator 6.4.1.2 6.4.1.2.1 6.4.1.2.2 If a part identified in an ALERT involves organization hardware, Record an IMPACT in the MSFC ALERT Response data record, along with the first half of an ALERT Impact Response page (Appendix D) to include an assessment o
43、f the significance of the issue for that organizations sphere of responsibility, and Coordinate development of an appropriate response to the potential discrepant condition including, but not limited to, generation of nonconformance correction documentation. (See MPR 8730.3.) Organization ALERT Coor
44、dinator 6.4.2 6.4.3 Within the required initial response time (21 workdays or prior to launch), submit the initial impact information through data record update to the MSFC ALERT Coordinator. Initiate a one-time 30-day response extension by selecting the option from the electronic system menu, speci
45、fying the Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction QD01 MSFC ALERT Processing MWI 1280.5 Revision: H Date: February 3, 2009 Page 10 of 34 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.
46、htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Actionee Section Perform all actions ALERT involved, and entering justification for the extension if: The response is from 7 days before becoming delinquent through not more than 30 days after becoming delinquent. The hardware is not applicable
47、to a mission/use occurring within 30 days of the Response Due Date. There is a legitimate justification for needing a 30-day extension, NOTE: This causes the due date to be extended to 30 days beyond the original Response Due Date. Organization ALERT Coordinator 6.4.4 6.4.4.1 6.4.4.1.1 6.4.4.1.2 If
48、an impact was identified, submit a completed ALERT Impact Response field information into the MSFC ALERT data system record within 21 workdays or prior to launch as stated in the initial notification, including a description of any countermeasure implemented to address the problem. For international
49、 partners, the Organization ALERT Coordinator shall: Provide summary information only (as shown in Appendix C: MSFC ALERT Problem Summary Chart) to the international partner (per GIDEP regulations and NPD 2110.1) and Coordinate potential impact evaluations with information provided by the international partner. 6.5 Tracking/Evaluating ALERT Responses. The MSFC ALERT
