space-rha.comShort courseChapter 5 · BOM scrub and parts review

Chapter 5 · Lesson 6 of 6 · about 12 minutes

Findings, owners and the handoff package

For each finding, write down what the evidence supports, what is still open, what the consequence would be and what you propose to do about it. Store the evidence with the configuration it applies to, so a later engineer can follow the reasoning.

Every finding needs a next step and an owner.

For each finding, write down what the evidence supports, what is still open, what the consequence would be and what you propose to do about it. The review can ask for an analysis, a test, a replacement part or a documented decision by the project. Store the evidence alongside the configuration it applies to, so a later engineer can follow the reasoning without reconstructing it.

A finished review is a set of findings with owners and next steps. A column of colors in a spreadsheet does not carry that information.

Close actions with evidence and with the right authority.

Each finding links the BOM revision, the drawing and firmware configuration, the requirement, the source report, the reasons the report applies to this use, the verification of any mitigation, the owner and the disposition. Keep radiation findings separate from parts-quality and procurement approvals, which answer different questions. Decide in advance what reopens a finding: a substitution, a supplier change, a new lot, a change in how the part is used, a mission extension or new information about a failure.

The record built during the scrub supports the review; it is not itself a release approval.

Leave the review with a handoff package someone can work from.

Take U4, the optocoupler on the demonstration board. The handoff entry for it identifies the exact construction, the receiver threshold, the LED drive current, the proton spectrum at its location, the degradation data that already exist and the minimum transfer ratio the circuit needs. With those in hand, decide what additional information would settle the question that matters, which is whether the command path still works at end of life.

The next chapter takes objectives like these and chooses the evidence strategy and the facilities to meet them.

Turn a gap into a test or analysis objective.

A usable objective states the mechanism in question, the population the result has to cover, the flight operating envelope, the parameter to be measured, the exposure the test is based on, how events will be detected and how the part will be recovered, and the decision the result will feed. Ask for samples that represent the flight lot and for measurement conditions that match the application. Line the schedule up with procurement and design, so that the result arrives while it can still change the implementation.

A beam species or a target dose is one line of the objective. The rest of it is what makes the result usable.

Exercise on the demonstration board

Write up the findings for the demonstration board as one entry per part and effect, with an owner and a next action for each, and then read the list back as if you were the designer or the test lead. Check that each entry says what was supported, what is open and what would reopen it, and that nothing depends on a conversation that is not written down.

Going deeper

Preserve the dependencies of the conclusion.

An argument under configuration control states the population it covers, the conditions, what was observed, how the consequence was modeled and what uncertainty remains. A change usually breaks only some of these links. Reopen the findings that depend on the changed link and keep the evidence that still applies. Any exception someone proposes has to be reconciled with the system requirement it was allocated from, through the decision process the project has authorized.

Track the revision of the evidence and the revision of the application separately. A change to either one can invalidate a disposition.

Make the acceptance argument reviewable before the test.

Before the test, write down how the response data and their uncertainty will be applied to the circuit criterion and to the system allocation, and how the modes the test cannot see, the sampling, the equivalence of the test source to the flight environment, the transport, any censoring and the verification of mitigations enter that argument. If the planned test cannot resolve the uncertainty that controls the decision, keep the alternative actions on the table.

Choose the facility to fit the question. Booking the convenient facility and then reshaping the question to fit its capabilities produces a result that answers the wrong question.

The common mistake

An action marked done closes the action. It does not authorize flight use; that takes the acceptance argument and the project's decision. The handoff from the scrub is a draft objective, and the test results and the acceptance decision are still ahead.

Takeaway

  • Close an action with evidence, and write down what would reopen it.
  • Define the engineering question before you choose the experiment.

Check yourself

The review ends with a spreadsheet whose last column colors each part green, yellow or red. Why does the course say that is not a finished review?

A finished review is a set of findings with owners and next steps: for each finding, what the evidence supports, what is still open, what the consequence would be and what is proposed. A column of colors does not carry that information, and each finding has to link the BOM revision, the drawing and firmware configuration, the requirement, the source report, the reasons the report applies to this use, the verification of any mitigation, the owner and the disposition, stored with the configuration it applies to so that a later engineer can follow the reasoning without reconstructing it.

The test report arrives, the action on a finding is marked done, and the designer takes that as approval to fly the part. What is wrong?

An action marked done closes the action; it does not authorize flight use, which takes the acceptance argument and the project's decision. The record built during the scrub supports the review and is not itself a release approval, and radiation findings are kept separate from the parts-quality and procurement approvals because those answer different questions. The handoff from the scrub is a draft objective, and the test results and the acceptance decision are still ahead.

Why does the course ask you to decide in advance what reopens a finding, and what kinds of change belong on that list?

An argument under configuration control states the population it covers, the conditions, what was observed, how the consequence was modeled and what uncertainty remains, and a change usually breaks only some of these links; deciding in advance lets you reopen the findings that depend on the changed link and keep the evidence that still applies. The list includes a substitution, a supplier change, a new lot, a change in how the part is used, a mission extension and new information about a failure. Track the revision of the evidence and the revision of the application separately, because a change to either one can invalidate a disposition.

Write the test or analysis objective for U4, the optocoupler, from its handoff entry. What does the entry hold, and what question does the objective have to answer?

The entry identifies the exact construction, the receiver threshold, the LED drive current, the proton spectrum at its location, the degradation data that already exist and the minimum transfer ratio the circuit needs. The question that matters is whether the command path still works at end of life, so the objective states the mechanism (displacement damage of the LED and the receiver), the population the result has to cover, the flight operating envelope (the minimum drive and the cold and hot cases), the parameter to be measured (CTR at the flight drive), the exposure it is based on (the mission proton fluence through the damage curve of the LED material, lesson 5.2), how events will be detected and the part recovered, and the decision the result will feed. Ask for samples that represent the flight lot and line the schedule up with procurement and design; a beam species or a target dose is one line of the objective, and the rest is what makes the result usable.

A proton facility has beam time available soon, so the team books it and plans to adjust the open question on U3, the bipolar amplifier, to what protons can answer. What does the course warn against?

Choose the facility to fit the question; booking the convenient facility and then reshaping the question to fit its capabilities produces a result that answers the wrong question. U3's open question is TID with ELDRS, which a lot-specific exposure at high and low dose rate addresses (lesson 6.2), not a proton run. Before any test, write down how the response data and their uncertainty will be applied to the circuit criterion and the system allocation, including the modes the test cannot see, the sampling, the equivalence of the test source to the flight environment, the transport, any censoring and the verification of mitigations; if the planned test cannot resolve the uncertainty that controls the decision, keep the alternative actions on the table.

Further reading