NASA-LLIS-3757
Lessons Learned - Importance of Tracking and Verification of Space Flight Electrical Connectors During Ground Processing at Kennedy Space Cente
Year: 2011
Abstract: Description of Driving Event:
The Shuttle Connector Analysis Network (SCAN) system developed by the Space Shuttle Processing organization consisted of a user interface software and database system accessed by workstations throughout KSC to track an orbiter's connector configuration (mated or demated) and system retest verification. By using SCAN, the orbiter system engineers and test conductors could quickly determine the status of orbiter connector configurations. SCAN provided current listings of all demated connectors prior to system power-up. Often connector configurations would change between orbiter power-ups as a result of system troubleshooting or rework that could only be performed while the orbiter was powered down. SCAN also recorded the work authorization document that was used for performing the connector test verification after the mating of the flight hardware. The system engineer would record the system checkout for each active connector pin after the connector was mated for flight. The same process was followed if a connector was demated during ground processing (postflight mate). Ares I-X did not have a SCANtype system, and tracking of the connector configurations before power-up was difficult. There was also no good way to verify that connector testing had been performed on a flight-mated connector.
The Shuttle Connector Analysis Network (SCAN) system developed by the Space Shuttle Processing organization consisted of a user interface software and database system accessed by workstations throughout KSC to track an orbiter's connector configuration (mated or demated) and system retest verification. By using SCAN, the orbiter system engineers and test conductors could quickly determine the status of orbiter connector configurations. SCAN provided current listings of all demated connectors prior to system power-up. Often connector configurations would change between orbiter power-ups as a result of system troubleshooting or rework that could only be performed while the orbiter was powered down. SCAN also recorded the work authorization document that was used for performing the connector test verification after the mating of the flight hardware. The system engineer would record the system checkout for each active connector pin after the connector was mated for flight. The same process was followed if a connector was demated during ground processing (postflight mate). Ares I-X did not have a SCANtype system, and tracking of the connector configurations before power-up was difficult. There was also no good way to verify that connector testing had been performed on a flight-mated connector.
Subject: Configuration Change Control
Show full item record
| contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
| date accessioned | 2017-09-04T16:54:31Z | |
| date available | 2017-09-04T16:54:31Z | |
| date copyright | 03/30/2011 | |
| date issued | 2011 | |
| identifier other | WYXKMEAAAAAAAAAA.pdf | |
| identifier uri | https://yse.yabesh.ir/std/handle/yse/118042 | |
| description abstract | Description of Driving Event: The Shuttle Connector Analysis Network (SCAN) system developed by the Space Shuttle Processing organization consisted of a user interface software and database system accessed by workstations throughout KSC to track an orbiter's connector configuration (mated or demated) and system retest verification. By using SCAN, the orbiter system engineers and test conductors could quickly determine the status of orbiter connector configurations. SCAN provided current listings of all demated connectors prior to system power-up. Often connector configurations would change between orbiter power-ups as a result of system troubleshooting or rework that could only be performed while the orbiter was powered down. SCAN also recorded the work authorization document that was used for performing the connector test verification after the mating of the flight hardware. The system engineer would record the system checkout for each active connector pin after the connector was mated for flight. The same process was followed if a connector was demated during ground processing (postflight mate). Ares I-X did not have a SCANtype system, and tracking of the connector configurations before power-up was difficult. There was also no good way to verify that connector testing had been performed on a flight-mated connector. | |
| language | English | |
| title | NASA-LLIS-3757 | num |
| title | Lessons Learned - Importance of Tracking and Verification of Space Flight Electrical Connectors During Ground Processing at Kennedy Space Cente | en |
| type | standard | |
| page | 4 | |
| status | Active | |
| tree | NASA - National Aeronautics and Space Administration (NASA):;2011 | |
| contenttype | fulltext | |
| subject keywords | Configuration Change Control | |
| subject keywords | Configuration control and data management | |
| subject keywords | Configuration Management | |
| subject keywords | Ground Operations | |
| subject keywords | Planning of requirements verification processes |

درباره ما