ATS Workbench QA/QC desktop tools

Downloads

Release packages are private.

ATS installers and operator packages are distributed only through authorized channels. This page documents access status without exposing public installer links.

NDE request control

ATS NDT

ATS NDT helps authorized operators prepare, link, review, and control NDE request packages around register evidence and release-safe workflows.

Version
0.9.9.8
Access
Available to authorized users
Release channel
Distributed through private channels
Review status
Last reviewed for v0.1 public site release

Traceability review

ATS Trace

ATS Trace helps authorized QA/QC users review weld traceability evidence across workbook-backed records, register evidence, material and consumable checks, welder evidence, WPS context, and review reporting.

Version
0.9.8.4
Access
Available to authorized users
Release channel
Distributed through private channels
Review status
Last reviewed for v0.1 public site release

Welder evidence lookup

ATS Welder Lookup

ATS Welder Lookup helps authorized users search workbook-backed request history by welder and review RT, UT, WQR, WPS, process, and acceptance-criteria evidence.

Version
0.9.9.9
Access
Available to authorized users
Release channel
Distributed through private channels
Review status
Last reviewed for v0.1 public site release

Authorized access

What users should expect.

ATS Workbench release packages are available to authorized users through private distribution channels only.

  • The public website may describe product versions and access status, but it must not store release packages.
  • Authorized users should receive packages through a controlled internal path or future authenticated endpoint.
  • Version and release-channel instructions should be checked before installing or reporting an issue.

Windows trust

Install with version and source checks.

  • Confirm the product name, version, and sender before running an installer or operator package.
  • Windows trust prompts should be reviewed carefully and escalated if the package source is unclear.
  • Keep the original private package available for support comparison, but do not place it in public storage.

No public installer storage

Private files stay outside the static site.

  • No public installer storage is used in the v0.1 public site.
  • No source archives, package manifests, credentials, sensitive values, or release signing material are included.
  • Future private downloads should use Cloudflare Access or server-side authorization before reaching private R2 storage.

Future architecture

Controlled release delivery.

  • Cloudflare Access email OTP protects the future admin area.
  • A Worker or Pages Function authorizes release metadata and download requests.
  • Private R2 stores approved release artifacts outside the public static build.