NASA-LLIS-1274
Lessons Learned – Planning and Design of Test Series
Year: 1998
Abstract: Description of Driving Event:
Flight element testing is very necessary but expensive; program schedule pressures typically mandate performing the minimum set of tests possible. The paper/documentation process associated with troubleshooting problems and/or performing detailed investigations of unexpected test results can significantly add to the time required to perform detailed tests on flight hardware/elements.
In this particular event, a minimum amount of pre-planning (i.e. insufficiently defined test requirements) resulted in power quality test implementation at KSC on the ISS Flight Node 1 that required replanning/rescoping the tests "on the fly" at KSC. Compounding the event was unexpected test results from the Russian to American Converter Unit (RACU) that forced the onsite test team along with support personnel from Boeing Canoga Park to perform detailed troubleshooting which further delayed the formal testing progress. Due to the unplanned, excessive time spent on Node 1 Power Quality Testing, valuable schedule reserves for the Flight Node 1 were lost. In addition, the NASA & Boeing Power AIT were forced to fly technical personnel and hardware to and from KSC, JSC and Boeing CP in order to support the Node 1 testing. Further, at risk was the opportunity to obtain all of the necessary data to both verify the Node 1 power system and to validate the electronic models necessary to verify the end to end power system functionality.
Flight element testing is very necessary but expensive; program schedule pressures typically mandate performing the minimum set of tests possible. The paper/documentation process associated with troubleshooting problems and/or performing detailed investigations of unexpected test results can significantly add to the time required to perform detailed tests on flight hardware/elements.
In this particular event, a minimum amount of pre-planning (i.e. insufficiently defined test requirements) resulted in power quality test implementation at KSC on the ISS Flight Node 1 that required replanning/rescoping the tests "on the fly" at KSC. Compounding the event was unexpected test results from the Russian to American Converter Unit (RACU) that forced the onsite test team along with support personnel from Boeing Canoga Park to perform detailed troubleshooting which further delayed the formal testing progress. Due to the unplanned, excessive time spent on Node 1 Power Quality Testing, valuable schedule reserves for the Flight Node 1 were lost. In addition, the NASA & Boeing Power AIT were forced to fly technical personnel and hardware to and from KSC, JSC and Boeing CP in order to support the Node 1 testing. Further, at risk was the opportunity to obtain all of the necessary data to both verify the Node 1 power system and to validate the electronic models necessary to verify the end to end power system functionality.
Subject: Configuration Management
Show full item record
| contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
| date accessioned | 2017-09-04T18:27:43Z | |
| date available | 2017-09-04T18:27:43Z | |
| date copyright | 04/20/1998 | |
| date issued | 1998 | |
| identifier other | IOVEQCAAAAAAAAAA.pdf | |
| identifier uri | http://yse.yabesh.ir/std;jsery=autho47037D83FCDCAC42/handle/yse/209942 | |
| description abstract | Description of Driving Event: Flight element testing is very necessary but expensive; program schedule pressures typically mandate performing the minimum set of tests possible. The paper/documentation process associated with troubleshooting problems and/or performing detailed investigations of unexpected test results can significantly add to the time required to perform detailed tests on flight hardware/elements. In this particular event, a minimum amount of pre-planning (i.e. insufficiently defined test requirements) resulted in power quality test implementation at KSC on the ISS Flight Node 1 that required replanning/rescoping the tests "on the fly" at KSC. Compounding the event was unexpected test results from the Russian to American Converter Unit (RACU) that forced the onsite test team along with support personnel from Boeing Canoga Park to perform detailed troubleshooting which further delayed the formal testing progress. Due to the unplanned, excessive time spent on Node 1 Power Quality Testing, valuable schedule reserves for the Flight Node 1 were lost. In addition, the NASA & Boeing Power AIT were forced to fly technical personnel and hardware to and from KSC, JSC and Boeing CP in order to support the Node 1 testing. Further, at risk was the opportunity to obtain all of the necessary data to both verify the Node 1 power system and to validate the electronic models necessary to verify the end to end power system functionality. | |
| language | English | |
| title | NASA-LLIS-1274 | num |
| title | Lessons Learned – Planning and Design of Test Series | en |
| type | standard | |
| page | 3 | |
| status | Active | |
| tree | NASA - National Aeronautics and Space Administration (NASA):;1998 | |
| contenttype | fulltext | |
| subject keywords | Configuration Management | |
| subject keywords | Independent Verification and Validation | |
| subject keywords | Policy & Planning | |
| subject keywords | Research & Development | |
| subject keywords | Risk Management/Assessment | |
| subject keywords | Safety & Mission Assurance | |
| subject keywords | Test & Verification | |
| subject keywords | Test Article |

درباره ما