REG NASA-LLIS-1098--1999 Lessons Learned - Establishing common policies and rules for multi-organizational processes.pdf

1、Lessons Learned Entry: 1098Lesson Info:a71 Lesson Number: 1098a71 Lesson Date: 1999-05-26a71 Submitting Organization: JSCa71 Submitted by: Mark Woloshin / Ronald MontagueSubject: Establishing common policies and rules for multi-organizational processes Description of Driving Event: There were a numb

2、er of different organizations involved in the processing of the 2A hardware and each organization had its own set of work rules. This often caused confusion among the different organizations and KSC personnel that were required to work on the hardware. There were also policies and work practices tha

3、t were new to the organizations and were not documented for a consistent implementation. These policies and rules ranged from topics like tool control and access control to topics such as scheduling and test readiness reviews. The confusion with the rules and policies often led to work delays and th

4、e loss of a team atmosphere.Root cause: Integration of multiple players was not factored into program planning at the lowest levels.Lesson(s) Learned: Processes requiring the support and participation of multiple entities must be pre-established by the host facility prior to needRecommendation(s): T

5、he 2A team established standard work policies to ensure consistent processing of the flight hardware.a71 The policies and processes were documented in a “2A Team Instruction“ which was approved by all the effected organizations. The Team Instruction documented all approved processes for processing t

6、he hardware. Documented under the team instruction were tool control in and around the flight hardware, access to the flight hardware, contamination and foreign object Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-debris (FOD) control methods, test

7、 readiness review and constraint review processes, configuration control procedures, red streamer and mate/demate log procedures, etc.a71 Team Instructions have been established for other missions; however, it is recommended that a consistent set of Team Instructions be established for all Space Sta

8、tions hardware. In addition, the methods and process learned should be applicable to all other ISS segments.a71 Discipline should continue to be maintained by the facility host or responsible prime contractor.Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Di

9、rectorate(s): a71 Exploration Systemsa71 Sciencea71 Space Operationsa71 Aeronautics ResearchAdditional Key Phrase(s): a71 External Relationsa71 Facilitiesa71 Flight Operationsa71 Ground Operationsa71 Industrial Operationsa71 Policy & Planninga71 Range Operationsa71 Risk Management/Assessmenta71 Test

10、 FacilityAdditional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: a71 Approval Date: 2002-02-12a71 Approval Name: Ronald Montaguea71 Approval Organization: JSCa71 Approval Phone Number: 281-483-8576Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-