Skip to content

Arc Skills / Technical management and design reviews

Review technology readiness evidence

Use Arc Skills to compare a claimed technology readiness level with the evidence from actual experiments and demonstrations. The output shows which level criteria are supported, which conditions are missing and what demonstration would address the gap.

Use this skill

Use Arc Skills to review this technology readiness claim.

Inputs:
- Claimed level and governing level definitions
- Demonstration reports and exact hardware/software configuration
- Intended environment, scale, loads and integration dependencies

Return a criterion-to-evidence table with supported findings, missing conditions and next demonstration. Distinguish analytical prediction, laboratory evidence and relevant-environment evidence. Do not assign a level from a label alone.

Set up the toolkit · Read the skill instructions

What you provide and what you get

Inputs and outputs
What you haveHow it is usedWhat you get
Claim and controlled level definitionsEstablish the actual maturity criteriaA bounded assessment basis
Experiment reports and configurationsCheck what was demonstratedCriterion-level findings
Intended application and environmentIdentify gaps in fidelity and conditionsA targeted maturation demonstration

A laboratory sensor demonstration does not settle the flight claim

Illustrative engineering example.

A supplier describes its sensor as TRL 6. The available demonstration uses a laboratory unit, a bench supply and simulated data. The target application uses revised electronics and a different environment.

Claim: TRL 6 under NASA definitions.
REP-LAB: breadboard B1, room conditions, bench supply, simulated recorder.
Target: hardware C2, flight power interface, thermal/vibration environment and real recorder timing.
No relevant-environment demonstration report or B1 → C2 comparison supplied.
A laboratory sensor demonstration does not settle the flight claim
Assessment dimensionAvailable evidenceSupported conclusionGap / next demonstration
Basic functional behaviorREP-LAB shows B1 outputs under stated laboratory conditionsSome laboratory function evidence existsInspect report criteria and repeatability before assigning a lower level
EnvironmentRoom conditions onlyTarget environment not demonstrated by this reportDefine relevant thermal, vibration and electrical conditions from the intended application
Fidelity and scaleBreadboard B1 versus intended C2Representativeness unresolvedCompare design changes and demonstrate the appropriate prototype
IntegrationSimulated recorder and bench supplyActual endpoint behavior not establishedExercise real or justified representative power/data interfaces
Claimed levelTRL 6 label without criterion mappingClaim cannot be substantiated from this packetProvide a criterion-linked demonstration report under the governing definitions

NASA’s Appendix E describes level-specific evidence and environments. This example does not mechanically award a lower level: the report detail is insufficient for a complete criterion-by-criterion judgment even at a lower claim.

A technology can have useful laboratory evidence and still lack the conditions needed for its intended application. A part’s heritage in another product also needs a configuration and use comparison; technology maturity does not settle qualification or delivery acceptance.

Compare the demonstration with the intended use

  1. Inspect the exact level definitions the claim uses.
  2. Map each criterion to experiment conditions, fidelity, scale and configuration.
  3. Identify missing environments, integration dependencies and unresolved anomalies.
  4. Describe the demonstration that would close each gap without confusing readiness, qualification and acceptance.

Questions about this task

Does the same part number preserve a heritage maturity claim?

It is useful identity evidence, but compare design modifications, duty cycle, loads, environment and interfaces. A changed application can require new demonstrations.

Sources and further reading

References inspected on 3 October 2026. The worked output is an authored example using the stated inputs.