What is the Process for Re-certifying Flight Hardware?Why use water tanks from a retired Space Shuttle?What...
How should I push back against my job assigning "homework"?
California: "For quality assurance, this phone call is being recorded"
Why does a helium balloon rise?
GFCI Outlet in Bathroom, Lights not working
If a problem only occurs randomly once in every N times on average, how many tests do I have to perform to be certain that it's now fixed?
Is American Express widely accepted in France?
Sucuri detects malware on wordpress but I can't find the malicious code
How can I add depth to my story or how do I determine if my story already has depth?
When leasing/renting out an owned property, is there a standard ratio between monthly rent and the mortgage?
What happens if you do emergency landing on a US base in middle of the ocean?
Is there a practical difference between different types of Berachos?
Is it a problem that pull requests are approved without any comments
Does Peach's float negate shorthop knockback multipliers?
What does it mean by "d-ism of Leibniz" and "dotage of Newton" in simple English?
What's the correct term for a waitress in the Middle Ages?
Unorthodox way of solving Einstein field equations
How can I offer a test ride while selling a bike?
Restoring order in a deck of playing cards (II)
Does any lore text explain why the planes of Acheron, Gehenna, and Carceri are the alignment they are?
Word for a small burst of laughter that can't be held back
Setting extra bits in a bool makes it true and false at the same time
Strange math syntax in old basic listing
How can Iron Man's suit withstand this?
Did thousands of women die every year due to illegal abortions before Roe v. Wade?
What is the Process for Re-certifying Flight Hardware?
Why use water tanks from a retired Space Shuttle?What is the purpose of the Dream Chaser carry test?Falcon 9 1.1 demo flight (flight 6) - Was the second stage burn meant to test deorbit?Through what mechanisms would SpaceX test and examine the returned CRS-5 first stage?Does every liquid-fueled rocket engine get a test run before its actual flight operation?What will the Falcon Heavy maiden flight launch as its payload?Why is there any launch window at all for the Falcon Heavy test flight?Testing flight characteristics before actual flight in model rockets?What is the surrogate liquid for LOx during the preliminary testing of injectors?Why is a purging process necessary for static firing test of liquid rocket engines?Purging process of a rocket engine
$begingroup$
I was reading about how we reused the water tanks because they were still within their certified life-time and had two questions:
- When would a certification become VOID?
- I'd assume if the water tanks accidentally took a fall they'd not be certified still.
- What are some other examples of events that can void a certification?
- When an event occurs altering the suitability of flight hardware how is it re-certified?
- I'd assume there's some sort of inspection, could someone outline what it'd be?
- You may use the example of the water tanks being dropped, what would NASA do?
You may also consider the toppled NOA satellite as a case study too if you wish. I'd like to know what all they had to do to consider it as "certified" again after the incident.
reuse testing
$endgroup$
add a comment |
$begingroup$
I was reading about how we reused the water tanks because they were still within their certified life-time and had two questions:
- When would a certification become VOID?
- I'd assume if the water tanks accidentally took a fall they'd not be certified still.
- What are some other examples of events that can void a certification?
- When an event occurs altering the suitability of flight hardware how is it re-certified?
- I'd assume there's some sort of inspection, could someone outline what it'd be?
- You may use the example of the water tanks being dropped, what would NASA do?
You may also consider the toppled NOA satellite as a case study too if you wish. I'd like to know what all they had to do to consider it as "certified" again after the incident.
reuse testing
$endgroup$
add a comment |
$begingroup$
I was reading about how we reused the water tanks because they were still within their certified life-time and had two questions:
- When would a certification become VOID?
- I'd assume if the water tanks accidentally took a fall they'd not be certified still.
- What are some other examples of events that can void a certification?
- When an event occurs altering the suitability of flight hardware how is it re-certified?
- I'd assume there's some sort of inspection, could someone outline what it'd be?
- You may use the example of the water tanks being dropped, what would NASA do?
You may also consider the toppled NOA satellite as a case study too if you wish. I'd like to know what all they had to do to consider it as "certified" again after the incident.
reuse testing
$endgroup$
I was reading about how we reused the water tanks because they were still within their certified life-time and had two questions:
- When would a certification become VOID?
- I'd assume if the water tanks accidentally took a fall they'd not be certified still.
- What are some other examples of events that can void a certification?
- When an event occurs altering the suitability of flight hardware how is it re-certified?
- I'd assume there's some sort of inspection, could someone outline what it'd be?
- You may use the example of the water tanks being dropped, what would NASA do?
You may also consider the toppled NOA satellite as a case study too if you wish. I'd like to know what all they had to do to consider it as "certified" again after the incident.
reuse testing
reuse testing
asked 9 hours ago
Magic Octopus UrnMagic Octopus Urn
3,49011550
3,49011550
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
$begingroup$
From what I've observed, the general process works like this:
A Non-Conformance Report (NCR) is generated. These are applicable for everything from an unexpected scratch or tool mark on a surface to a system-level failure. The NCR identifies the "is" vs. "should be" state of a component.
A Material Review Board (MRB) convenes. This is a group of engineers and managers who make decisions in a structured way regarding NCRs. From here, it's case-dependent. It may involve specific analysis, or it may just be a series of discussions. It all depends on the specific nonconformance.
The NCR is dispositioned. Again, case dependent. The disposition is determined by the MRB. Typical disposition outcomes:
Use as is. Analysis shows the nonconformance does not affect safety or mission success -- no corrective action is necessary to certify the part for flight.
Rework the part. Case dependent. Could be as simple as redrilling a hole in the right location, buffing out scratches, etc.
Use as is, issue drawing rev. In the case of a misdrilled hole, for example, create a drawing rev showing where the hole was drilled so that there is traceability between the drawing and what was manufactured.
Scrap. The component is too far gone. Toss it out and build a new one. Depending on the source of the NCR, it may be a build to print, or there may be a redesign.
$endgroup$
$begingroup$
+1, A couple of things to add: A) the MRB is usually given total authority over the future of the part and may direct the project office to examine, test, repair etc. B) there is usually a distinction drawn between "re-work" such as your first example and "repair" which is closer to your second example of buffing to remove a scratch. The difference lies in that "re-work" is re-application of the same processes used in the original build whereas "repair" uses additional (authorised) processes that were not needed for an original build.
$endgroup$
– Puffin
5 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "508"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fspace.stackexchange.com%2fquestions%2f36486%2fwhat-is-the-process-for-re-certifying-flight-hardware%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
From what I've observed, the general process works like this:
A Non-Conformance Report (NCR) is generated. These are applicable for everything from an unexpected scratch or tool mark on a surface to a system-level failure. The NCR identifies the "is" vs. "should be" state of a component.
A Material Review Board (MRB) convenes. This is a group of engineers and managers who make decisions in a structured way regarding NCRs. From here, it's case-dependent. It may involve specific analysis, or it may just be a series of discussions. It all depends on the specific nonconformance.
The NCR is dispositioned. Again, case dependent. The disposition is determined by the MRB. Typical disposition outcomes:
Use as is. Analysis shows the nonconformance does not affect safety or mission success -- no corrective action is necessary to certify the part for flight.
Rework the part. Case dependent. Could be as simple as redrilling a hole in the right location, buffing out scratches, etc.
Use as is, issue drawing rev. In the case of a misdrilled hole, for example, create a drawing rev showing where the hole was drilled so that there is traceability between the drawing and what was manufactured.
Scrap. The component is too far gone. Toss it out and build a new one. Depending on the source of the NCR, it may be a build to print, or there may be a redesign.
$endgroup$
$begingroup$
+1, A couple of things to add: A) the MRB is usually given total authority over the future of the part and may direct the project office to examine, test, repair etc. B) there is usually a distinction drawn between "re-work" such as your first example and "repair" which is closer to your second example of buffing to remove a scratch. The difference lies in that "re-work" is re-application of the same processes used in the original build whereas "repair" uses additional (authorised) processes that were not needed for an original build.
$endgroup$
– Puffin
5 hours ago
add a comment |
$begingroup$
From what I've observed, the general process works like this:
A Non-Conformance Report (NCR) is generated. These are applicable for everything from an unexpected scratch or tool mark on a surface to a system-level failure. The NCR identifies the "is" vs. "should be" state of a component.
A Material Review Board (MRB) convenes. This is a group of engineers and managers who make decisions in a structured way regarding NCRs. From here, it's case-dependent. It may involve specific analysis, or it may just be a series of discussions. It all depends on the specific nonconformance.
The NCR is dispositioned. Again, case dependent. The disposition is determined by the MRB. Typical disposition outcomes:
Use as is. Analysis shows the nonconformance does not affect safety or mission success -- no corrective action is necessary to certify the part for flight.
Rework the part. Case dependent. Could be as simple as redrilling a hole in the right location, buffing out scratches, etc.
Use as is, issue drawing rev. In the case of a misdrilled hole, for example, create a drawing rev showing where the hole was drilled so that there is traceability between the drawing and what was manufactured.
Scrap. The component is too far gone. Toss it out and build a new one. Depending on the source of the NCR, it may be a build to print, or there may be a redesign.
$endgroup$
$begingroup$
+1, A couple of things to add: A) the MRB is usually given total authority over the future of the part and may direct the project office to examine, test, repair etc. B) there is usually a distinction drawn between "re-work" such as your first example and "repair" which is closer to your second example of buffing to remove a scratch. The difference lies in that "re-work" is re-application of the same processes used in the original build whereas "repair" uses additional (authorised) processes that were not needed for an original build.
$endgroup$
– Puffin
5 hours ago
add a comment |
$begingroup$
From what I've observed, the general process works like this:
A Non-Conformance Report (NCR) is generated. These are applicable for everything from an unexpected scratch or tool mark on a surface to a system-level failure. The NCR identifies the "is" vs. "should be" state of a component.
A Material Review Board (MRB) convenes. This is a group of engineers and managers who make decisions in a structured way regarding NCRs. From here, it's case-dependent. It may involve specific analysis, or it may just be a series of discussions. It all depends on the specific nonconformance.
The NCR is dispositioned. Again, case dependent. The disposition is determined by the MRB. Typical disposition outcomes:
Use as is. Analysis shows the nonconformance does not affect safety or mission success -- no corrective action is necessary to certify the part for flight.
Rework the part. Case dependent. Could be as simple as redrilling a hole in the right location, buffing out scratches, etc.
Use as is, issue drawing rev. In the case of a misdrilled hole, for example, create a drawing rev showing where the hole was drilled so that there is traceability between the drawing and what was manufactured.
Scrap. The component is too far gone. Toss it out and build a new one. Depending on the source of the NCR, it may be a build to print, or there may be a redesign.
$endgroup$
From what I've observed, the general process works like this:
A Non-Conformance Report (NCR) is generated. These are applicable for everything from an unexpected scratch or tool mark on a surface to a system-level failure. The NCR identifies the "is" vs. "should be" state of a component.
A Material Review Board (MRB) convenes. This is a group of engineers and managers who make decisions in a structured way regarding NCRs. From here, it's case-dependent. It may involve specific analysis, or it may just be a series of discussions. It all depends on the specific nonconformance.
The NCR is dispositioned. Again, case dependent. The disposition is determined by the MRB. Typical disposition outcomes:
Use as is. Analysis shows the nonconformance does not affect safety or mission success -- no corrective action is necessary to certify the part for flight.
Rework the part. Case dependent. Could be as simple as redrilling a hole in the right location, buffing out scratches, etc.
Use as is, issue drawing rev. In the case of a misdrilled hole, for example, create a drawing rev showing where the hole was drilled so that there is traceability between the drawing and what was manufactured.
Scrap. The component is too far gone. Toss it out and build a new one. Depending on the source of the NCR, it may be a build to print, or there may be a redesign.
answered 8 hours ago
TristanTristan
11.5k13858
11.5k13858
$begingroup$
+1, A couple of things to add: A) the MRB is usually given total authority over the future of the part and may direct the project office to examine, test, repair etc. B) there is usually a distinction drawn between "re-work" such as your first example and "repair" which is closer to your second example of buffing to remove a scratch. The difference lies in that "re-work" is re-application of the same processes used in the original build whereas "repair" uses additional (authorised) processes that were not needed for an original build.
$endgroup$
– Puffin
5 hours ago
add a comment |
$begingroup$
+1, A couple of things to add: A) the MRB is usually given total authority over the future of the part and may direct the project office to examine, test, repair etc. B) there is usually a distinction drawn between "re-work" such as your first example and "repair" which is closer to your second example of buffing to remove a scratch. The difference lies in that "re-work" is re-application of the same processes used in the original build whereas "repair" uses additional (authorised) processes that were not needed for an original build.
$endgroup$
– Puffin
5 hours ago
$begingroup$
+1, A couple of things to add: A) the MRB is usually given total authority over the future of the part and may direct the project office to examine, test, repair etc. B) there is usually a distinction drawn between "re-work" such as your first example and "repair" which is closer to your second example of buffing to remove a scratch. The difference lies in that "re-work" is re-application of the same processes used in the original build whereas "repair" uses additional (authorised) processes that were not needed for an original build.
$endgroup$
– Puffin
5 hours ago
$begingroup$
+1, A couple of things to add: A) the MRB is usually given total authority over the future of the part and may direct the project office to examine, test, repair etc. B) there is usually a distinction drawn between "re-work" such as your first example and "repair" which is closer to your second example of buffing to remove a scratch. The difference lies in that "re-work" is re-application of the same processes used in the original build whereas "repair" uses additional (authorised) processes that were not needed for an original build.
$endgroup$
– Puffin
5 hours ago
add a comment |
Thanks for contributing an answer to Space Exploration Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fspace.stackexchange.com%2fquestions%2f36486%2fwhat-is-the-process-for-re-certifying-flight-hardware%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown