NASA ENGINEERING NETWORK
Follow this link to skip to the main content
+ Contact LLIS
Go
ABOUT NASALATEST NEWSMULTIMEDIAMISSIONSMyNASAWORK FOR NASA

+ NASA Home
FIND ENGINEERING RESOURCES BY
LLIS HOME
NASA CENTERS
MISSION DIRECTORATE
TOPICS
BY YEAR


Public Lessons Learned Entry: 1098

Lesson Info:

  • Lesson Number: 1098
  • Lesson Date: 1999-05-26
  • Submitting Organization: JSC
  • Submitted by: Mark Woloshin / Ronald Montague

Subject:

Establishing common policies and rules for multi-organizational processes

Description of Driving Event:

There were a number 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 that 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 the 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 need

Recommendation(s):

The 2A team established standard work policies to ensure consistent processing of the flight hardware.

  • 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 the hardware. Documented under the team instruction were tool control in and around the flight hardware, access to the flight hardware, contamination and foreign object debris (FOD) control methods, test readiness review and constraint review processes, configuration control procedures, red streamer and mate/demate log procedures, etc.
  • Team Instructions have been established for other missions; however, it is recommended that a consistent set of Team Instructions be established for all Space Stations hardware. In addition, the methods and process learned should be applicable to all other ISS segments.
  • Discipline should continue to be maintained by the facility host or responsible prime contractor.

Evidence of Recurrence Control Effectiveness:

N/A

Documents Related to Lesson:

N/A

Mission Directorate(s):

  • Exploration Systems
  • Science
  • Space Operations
  • Aeronautics Research

Additional Key Phrase(s):

  • External Relations
  • Facilities
  • Flight Operations
  • Ground Operations
  • Industrial Operations
  • Policy & Planning
  • Range Operations
  • Risk Management/Assessment
  • Test Facility

Additional Info:

    Approval Info:

    • Approval Date: 2002-02-12
    • Approval Name: Ronald Montague
    • Approval Organization: JSC
    • Approval Phone Number: 281-483-8576


    FirstGov - Your First Click to the US Government
    + 2004 Vision for Space Exploration
    + FY 2005 Budget Request
    + 2003 Strategic Plan
    + Freedom of Information Act
    + The President's Management Agenda
    + FY 2003 Agency Performance and Accountability Report
    + NASA Privacy Statement, Disclaimer,
    and Accessibility Certification

    + Freedom to Manage
    NASA
    Curator:Manson Yew
    NASA Official: Gregory Robinson
    + Contact LLIS