Generate an equipment evidence pack

Build a verified ZIP package for selected equipment, check certificate integrity, and verify the checksum manifest.

Audit readiness For Owner, Administrator, Quality manager, Calibration manager

Generate an equipment evidence pack

Evidence files upload in short-lived secure batches, with up to two files at a time. The progress bar shows the full batch.

Metra checks each file first. If a file group is interrupted, Metra keeps the already-uploaded files and metadata and only retries unfinished work.

An equipment evidence pack is a private ZIP you can download. It contains a selected equipment-focused snapshot for an audit or customer review.

The pack is derived from application data. The source records, revisions, certificates, and audit history in Metra remain the official source.

Prerequisites

Permission to create exports and download the completed file.
Choose 1 to 100 equipment records.
Ensure required certificates are available and pass integrity checks.
Ensure any pre-Metra evidence packs are verified and not superseded.
Decide optional scope values: date range, site, and equipment status.
Review Upload or replace a calibration certificate before fixing certificate issues.

Owners, administrators, and quality managers normally have export access. Operational calibration roles do not get organisation-wide export permissions by default.

Select equipment and request the pack

Open Quality > Exports.
Select Equipment evidence pack (ZIP) as the Export type.
Enter Date from and Date to when only a defined inclusive period is required.
Select a Site and Equipment statuses when needed.
Under equipment selection, enter Search equipment text and select Search.
Select each required equipment record. The selection summary shows how many of the 100-item maximum are selected.
Recheck the selected site, period, statuses, and equipment.
Select Request export.

If the equipment list is empty, the page shows Search for equipment to build the evidence pack. Search again or change the site and status scope. A search error does not create an export.

The request locks the selected equipment record IDs and filters. A fixed cut-off snapshot is used, so later changes are not included.

What the ZIP contains

The generated archive contains:

manifest.json
summary.html
equipment.csv
calibration-events.csv
calibration-requirements.csv
measurement-points.csv
procedure-evidence.json
uncertainty-evidence.json
conformity-decision-evidence.json
reference-standard-usage.csv
traceability-chains.csv
out-of-tolerance-cases.csv
audit-trail.csv
certificates/
historical-evidence/

Certificate files are grouped under equipment and calibration-event folders. The readable summary.html file lists the organisation, requester, generation time, scope, record counts, and file contents. It also labels the pack as a point-in-time export.

Detailed investigation evidence only includes the selected equipment and date period. Internal storage paths are not included.

historical-evidence/ contains verified, customer-supplied pre-Metra documents for each equipment item and date period. A historical pack appears only when that pack belongs to the selected equipment and its period overlaps the export period. Draft, awaiting-approval, superseded, and voided packs are excluded.

For events with structured evidence, uncertainty data is included. It uses the exact budget and policy version saved with the event, plus point and stage results, components, observations, findings, acknowledgement history, and checksums. Externally reported uncertainty values stay marked as supplied values.

procedure-evidence.json stores the exact procedure revision and checksum for each event, including step definitions, execution revision, step outcomes, any approved deviations, users, and timestamps. If these links are inconsistent, generation stops instead of creating an incomplete export.

Certificate and checksum behavior

Only certificates tied to the selected calibration events are copied. Certificate metadata and content use the same private storage and integrity checks as the main application.

Before adding a certificate, Metra validates it against the stored SHA-256 checksum. If a required certificate is missing or does not match, generation stops. Unverified evidence is not silently omitted.

manifest.json records the organisation snapshot, requester, request/completion times, selected filters, record counts, and each file path, size, and SHA-256 checksum.

Use the manifest to check for accidental corruption. It is not a digital signature or proof of who created the file.

Monitor, download, and verify

In Export history, select Refresh until the job is completed or failed.
If completed, review the record count, file size, and File expires time.
Select Download while signed in with the required organisation permission.
Open summary.html and confirm the organisation, requester, scope, dates, and counts.
Recalculate SHA-256 checksums for the files listed in manifest.json using your organisation's approved verification tool.
Compare the calculated values with the manifest before relying on or transferring the pack.

The ZIP is available for seven days by default. Download is authenticated and limited to the current organisation; there is no public storage URL.

Failure handling

A failed job shows a safe failure code; internal implementation details are not shown.
Correct missing or corrupt certificate evidence through the controlled certificate workflow, preserving previous versions.
Correct historical evidence by superseding the complete dated pack; do not replace an individual file inside a verified pack.
Confirm every equipment record ID belongs to the selected organisation and the date range is valid.
Request a new pack after source records are corrected; failed and expired artifacts are never edited in place.
If a downloaded checksum differs, stop using that copy and download or regenerate the pack.

Expected result

You get a private, equipment-scoped ZIP. You can verify included files against the checksum manifest. Export metadata and audit history remain after the file expires; the application records stay the source of truth.

Warnings and next steps

A matching checksum confirms file integrity; it is not a certificate of regulatory approval or authorship.
Do not use a pack to conceal later corrections; generate a new point-in-time artifact.
Apply your organisation's retention and secure-transfer rules after download.

Next steps:

Reference-standard evidence

When the selected equipment is a reference standard, the pack includes its profile revisions, capability bands, restrictions, calibration-validity details, accreditation snapshots, standard usage, and traceability records from the correct certificate revisions.

Measurement uncertainty evidence

Pack generation writes out retained evidence only. It does not recalculate historical work with newer budgets, reference profiles, or policies.

Conformity-decision evidence

For events with controlled decisions, the pack includes decision evidence: exact rule revision and checksum, measurement and uncertainty provenance, acceptance limits, point and overall outcomes, reason codes, findings, acknowledgements, actors, timestamps, and evaluation hashes.

Generation renders the stored decision without applying a newer rule or recalculating historical work. See Calculate and review conformity decisions.