Performance standards
MOPS compliance support for airborne equipment
MOPS compliance support helps an equipment supplier show that an article meets the minimum operational performance standard a TSO invokes by reference. It is used by teams whose bench, environmental, and analysis evidence was produced piecemeal and may not answer every performance requirement the standard sets. The work maps each MOPS requirement to the evidence that answers it and flags the requirements with no substantiation behind them. You receive a requirement-to-evidence map and a prioritized list of the performance data to close.
When this review is needed
- A TSO invokes a performance standard and the team needs to know which MOPS requirements still have no evidence.
- The article changed during development and the bench data no longer answers the requirement it was meant to.
- A later MOPS revision is being adopted and the delta against the prior performance data has to be understood.
- An accuracy or integrity figure was claimed by analysis where the standard sets a number that test was meant to demonstrate.
The problem
A performance standard expresses its bar as numbers: accuracy bands, integrity figures, time-to-alert limits, and operating ranges. Those numbers are demonstrated in bench runs and analyses produced at different points in development, and the article rarely stays fixed across them. When a sensor range narrows or an algorithm is retuned, the old run still sits in the file answering a requirement the article no longer meets the same way.
What gets reviewed
- The MOPS the applicable TSO invokes and the revision the program is committing to
- Bench and laboratory performance test evidence against the requirements it answers
- Accuracy, integrity, and time-to-alert figures against the limits the standard sets
- Analysis used in place of test where the standard permits it
- Requirements the article allocates to software or hardware behavior
- Open performance items and any deviations the program intends to carry
What gets validated
- Every MOPS performance requirement maps to test or analysis evidence that supports it
- The MOPS revision the evidence answers matches the revision the program commits to
- Accuracy and integrity figures in the evidence meet the limits the standard states
- Analysis substituted for test is permitted by the standard and is justified
- Behavior allocated to software is substantiated by the verification behind it
- Carried deviations against the standard are documented and traceable
Evidence normally required
- The MOPS document and revision the TSO invokes
- Bench, laboratory, and field performance test reports assembled so far
- Performance analyses used in place of or alongside test
- The accuracy and integrity budgets the design allocated
- The article configuration the performance data was generated against
Common discrepancies
- Requirements with no test or analysis evidence behind a claimed-met status
- Evidence answering a superseded MOPS revision rather than the one the program commits to
- Accuracy or integrity figures demonstrated on a build the article has since retuned
- Analysis substituted for test where the standard expects test, with no justification
- Behavior allocated to software with no verification evidence connecting the two
What is at stake
A claimed-met performance requirement with no run behind it draws a finding the moment an examiner asks for the data. Each gap pushes a bench re-run into the schedule, and re-runs against environmental conditioning are slow to stage, so a handful of unsupported numbers can move the submittal date by weeks.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Pin the standard
Confirm the MOPS and revision the TSO invokes and that the program commits to it.
Map the figures
Tie each performance requirement to the run or analysis meant to demonstrate it.
Check the numbers
Compare demonstrated accuracy, integrity, and timing to the limits the standard states.
List the closures
Flag requirements with missing, stale, or out-of-limit evidence and order them by review exposure.
What the buyer receives
- A requirement-to-evidence map across the invoked MOPS
- A figures check comparing demonstrated accuracy and integrity to the limits stated
- A list of performance requirements with missing or stale substantiation
- A prioritized closure list ordered by review exposure
Who uses the output
- Certification leads assembling the performance evidence for submittal
- Systems and test engineers staging the bench re-runs the gaps require
- Program management sequencing the closure against test-cell availability
How the work fits into the transaction or program
The work focuses on the performance bar a TSO inherits from the MOPS it invokes. It pairs with environmental category mapping when the same article also needs its qualification coverage checked against the installation.
Start with a single asset
Confirm requirements trace through verification.
Regulatory limits
Endeavor Elements supports the applicant's performance evidence against the invoked MOPS. It does not issue a TSO authorization, make compliance findings for the authority, or guarantee acceptance of the performance claims.
What this review does not cover
- Issuing any TSO authorization or approval
- Running the bench or environmental performance tests
- Approving deviations against the standard on the authority's behalf
Specific to this review
- A TSO often invokes a MOPS by reference, so the performance bar lives in the standard rather than the TSO text, and missing the invoked revision is a frequent finding.
- MOPS coverage and currency are checked separately: a requirement can have evidence yet answer the wrong revision of the standard.
- Performance is expressed as numbers, so a retune that quietly moves an accuracy or integrity figure can break a met claim without any document being deleted.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
Frequently asked questions
Why check the MOPS revision if the article already passed bench testing?
Bench evidence answers the revision it was written against. If the program commits to a later MOPS revision, the review confirms the existing runs still meet the figures the new revision sets rather than the ones the old runs assumed.
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.
Walk through your situation with an engineer who has done this work.