Arc Skills / Technical management and design reviews
Review a supplier technical deliverable
Use Arc Skills to review a supplier report or technical data package against the agreed deliverable list. The result separates contractual completeness, configuration mismatch and technical evidence gaps, with an owner and requested correction for each.
Use this skill
Use Arc Skills to review this supplier technical deliverable.
Inputs:
- Contracted deliverable list and acceptance criteria
- Submitted files, part numbers, serials and revisions
- Governing requirements, raw results and interface context
Return a review table with expected artifact, supplied evidence, finding, consequence and requested correction. Distinguish administrative omissions from technical defects. Check every claim against the delivered configuration.What you provide and what you get
| What you have | How it is used | What you get |
|---|---|---|
| Contracted artifact list | Define the required submission | Completeness findings |
| Reports and configuration records | Match article, revisions and coverage | Applicability findings |
| Original results and limits | Check technical claims and methods | Evidence gaps and specific correction requests |
A test summary omits the configuration it claims to support
Illustrative engineering example.
The contract calls for a qualification package for a converter. The supplier supplies a summary marked compliant but omits several contracted attachments.
Expected: report with serial and firmware, raw thermal results, calibration certificates, interface pin table and signed exception list.
Submitted: REP-22 rev A; article “prototype”; firmware absent; summary “all tests passed”; raw data absent.
Delivered converter: SN-08, hardware C, firmware F2. Pin table has a different chassis-bond instruction from buyer ICD-3.| Expected evidence | Supplied artifact | Finding class | Consequence | Requested correction |
|---|---|---|---|---|
| Article identity | REP-22 says prototype; no serial or firmware | Configuration gap | Applicability to SN-08 C/F2 unresolved | Supplier provides tested configuration and delivered/tested comparison |
| Thermal results | Pass summary only; raw data absent | Contract and evidence gap | Limits, excursions and reduction cannot be checked | Attach required raw data, method and acceptance comparisons |
| Calibration | No certificates | Required attachment absent | Measurement validity cannot be assessed | Identify instruments and provide applicable certificates |
| Pin table | Conflicting chassis-bond instruction | Technical interface mismatch | Buyer and supplier wiring contracts disagree | Both endpoint owners reconcile controlled revisions |
| Exception list | Unsigned sheet | Administrative completeness gap | Contracted attestation is missing | Request authorized signature; do not interpret it as a physical performance failure |
Five expected evidence groups were checked. The findings have different consequences: an unsigned list is not proof of technical failure, while contradictory bond instructions need an engineering compatibility decision.
The packet may contain useful results, but “all tests passed” does not resolve article identity, raw-result omissions or the interface disagreement. Ask for exactly the artifacts needed to assess those gaps.
Review completeness and technical adequacy separately
- Compare the submission with the contracted list, format and coverage.
- Match part, serial, hardware/software revision and test conditions.
- Inspect calculations, raw data, units, uncertainty and limits for material claims.
- Separate contractual and technical corrections, assigning the proper supplier, buyer or acceptance authority.
Questions about this task
How is this different from reviewing a supplier compliance claim?
This reviews the whole contracted data package and its technical adequacy. A compliance-claim review focuses on whether evidence supports a particular offered requirement and configuration.
Sources and further reading
- NASA Systems Engineering Handbook: configuration management: Background on identifying configurations and controlling baseline changes.
- NASA Systems Engineering Handbook: technical data management: Background on identifying, retaining and supplying technical data.
References inspected on 3 October 2026. The worked output is an authored example using the stated inputs.