Health-monitoring equipment
Health-monitoring equipment qualification evidence review
This review examines the qualification evidence behind a health-monitoring unit and confirms it supports the claims the certification package will make. An engineer works through the DO-160G environmental results, the DO-178C software lifecycle artifacts, and the sensor and data-integrity substantiation, then ties each to the certification basis and the declared means of compliance. It is run during a qualification evidence review, before the data is committed to a submission. What you get is a gap list scoped to the equipment, a trace map from requirement to test result, and a closure order that keeps the qualification story consistent.
When this review is needed
- Qualification testing is complete and the results have to be checked before they anchor a submission.
- The unit was qualified against one platform's environment and is now proposed for another.
- Software verification and environmental testing were run by separate teams and no one has reconciled the two.
- A reviewer wants the qualification data validated internally before an authority reads it.
The problem
Qualification data for a health-monitoring unit accumulates as a stack of test reports rather than as an answer to a requirement set. The DO-160G results describe what conditions the box survived, the DO-178C data describes how the software was verified, and the sensor substantiation lives in yet another format. Whether those results actually cover the requirements the certification basis imposes is a question no single report answers, and it stays open until someone reads them together against the basis.
What gets reviewed
- DO-160G environmental categories checked against the equipment's intended operating conditions
- DO-178C lifecycle artifacts assessed against the declared software level and its objectives
- Sensor and data-integrity substantiation tied to the health-monitoring function's requirements
- Qualification test results mapped to the certification basis and means of compliance
- Consistency between the environmental, software, and sensor evidence sets
- The delivered evidence configuration confirmed against the current equipment build
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Every DO-160G category the basis requires has a corresponding test result at the correct severity
- The DO-178C objectives for the declared software level are each satisfied by a named artifact
- Sensor accuracy and data-integrity claims are supported by results rather than asserted in the plan
- Qualification results reference the equipment build that the certification package describes
- No requirement relies on a test run under conditions milder than the intended operating environment
Evidence normally required
- The certification basis and the applicant's compliance checklist
- DO-160G environmental test plan and full result set
- DO-178C software plans, verification records, and declared level
- Sensor characterization and data-integrity substantiation
- The equipment configuration list matching the qualified build
Common discrepancies
- A DO-160G category tested one severity below what the operating environment demands
- A DO-178C objective with no artifact satisfying it at the declared level
- Data-integrity claims stated in the plan but never demonstrated by result
- Test reports referencing a hardware build that differs from the one being certified
What is at stake
Qualification evidence that looks complete but does not map cleanly to the basis produces findings the moment an authority applies the requirements to it. A category tested for the wrong severity, or a software objective left unsatisfied, forces re-test or re-verification late, when schedule pressure is highest. The cost of catching it at review is a memo; the cost of catching it in the authority's response is a program slip.
How the work runs
Read the basis
Establish the environmental and software requirements the qualification evidence has to satisfy.
Check the results
Confirm each DO-160G and DO-178C result answers a requirement at the required severity and level.
Reconcile the sets
Verify environmental, software, and sensor evidence describe the same equipment build.
Order the gaps
Sequence any re-test or re-verification so the qualification story stays consistent.
What the buyer receives
- An equipment-scoped qualification gap list keyed to the basis
- A trace map linking each requirement to its qualification result
- A closure order that keeps the environmental, software, and sensor evidence consistent
Who uses the output
- Certification leads deciding whether the qualification data is ready to submit
- Test and software engineers who own the results each gap references
- Program managers weighing re-test cost against the submission schedule
How the work fits into the transaction or program
The review comes after qualification testing and before the data is locked into a compliance submission. It converts a stack of test reports into a checked answer to the certification basis, so the qualification evidence enters the submission already reconciled. Anything it flags feeds re-test or re-verification while there is still schedule to absorb it.
Start with a single asset
Confirm requirements map to substantiating evidence.
Jurisdiction-specific considerations
FAA and EASA acceptance of qualification data can differ in how much environmental and software substantiation each expects to see for the same function. The review marks where the existing results serve both authorities and where one will call for evidence the other treats as sufficient already.
Regulatory limits
The review assesses whether the qualification evidence is complete and consistent with the basis. It does not qualify the equipment, accept the test results on an authority's behalf, or determine airworthiness of any installation using the unit.
What this review does not cover
- Running or re-running the qualification tests
- Producing software verification or environmental substantiation
- Any acceptance or approval decision on the equipment
Specific to this review
- Reused units fail qualification review most often on environmental severity, because a box qualified for a mild platform is proposed for a harsher one without re-testing.
- DO-178C objective coverage is the hardest part of a qualification review to fake: a declared level that the artifacts do not support is visible on inspection.
- Data-integrity substantiation for a health-monitoring function is frequently asserted in the plan and never carried through to a demonstrated result.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
Frequently asked questions
How is this different from the STC installation evidence review?
This one examines whether the equipment's own qualification data holds up against the basis. The installation review checks whether that qualified equipment, once fitted, is supported by installation evidence. The qualification review comes first and feeds the installation package.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.