SOLUTIONS

One evidence model. Different operating pressures.

Laboratories, plants, regulated operations, aerospace programs, manufacturers and service organizations prioritize different risks. METRAXIOM changes workflow emphasis without changing what a measurement, source, uncertainty, decision, review or authority state means.

Open Calibration Studio Explore product Discuss a pilot

WORKFLOW-SPECIFIC, NOT WALLPAPER

Open an operating lane. See the problem, workflow, proof and limitation together.

The collapsed row shows the workflow immediately. Deeper evidence and the authority boundary appear only when the visitor chooses to inspect the lane.

01LAB / FIELDCalibration laboratoriesReceive → identify → qualify method and references → acquire → evaluate → review → package → deliver → preserve recall paths.Inspect

OPERATING PROBLEM

Receiving, work authorization, standards, multi-discipline execution, uncertainty, review, certificates, recall, and customer delivery often live in separate systems.

PRODUCT EVIDENCE / ARCHITECTURE

Calibration Studio, the Universal Calibration Workspace architecture, candidate work-package manifests, as-found/as-left lineage, and controlled procedure authority.

BOUNDARY

METRAXIOM does not itself establish laboratory competence, accreditation scope, authorized signatories, or metrological traceability.

WORKFLOW

Receive → identify → qualify method and references → acquire → evaluate → review → package → deliver → preserve recall paths.

02GXP CONTEXTPharmaceutical and GMP operationsAsset/program authority → controlled execution → exception/OOT route → independent review → immutable release package → QMS/CAPA linkage.Inspect

OPERATING PROBLEM

Instrument status, controlled procedures, deviations, electronic records, signatures, data integrity, and QMS ownership must remain aligned without slowing bench work.

PRODUCT EVIDENCE / ARCHITECTURE

Fail-closed production gates, versioned authority, audit/event controls, role separation, explicit electronic-record boundaries, and validation-oriented release evidence.

BOUNDARY

References to GMP, GxP, FDA, Part 11, or Annex 11 describe supported control patterns, not regulatory approval or validated customer use.

WORKFLOW

Asset/program authority → controlled execution → exception/OOT route → independent review → immutable release package → QMS/CAPA linkage.

03MISSION-CRITICALAerospace and defense metrologyConfiguration identity → exact method/specification authority → reference qualification → controlled measurement → decision/review → portable proof → dependency recall.Inspect

OPERATING PROBLEM

Multi-function equipment, customer flow-downs, configuration, offline constraints, reference adequacy, decision risk, and long-lived evidence require stronger reconstruction than a spreadsheet can provide.

PRODUCT EVIDENCE / ARCHITECTURE

Versioned measurement context, exact procedure bindings, uncertainty and decision-rule separation, DUEPROOF reliance edges, proof-package architecture, and planned offline profiles.

BOUNDARY

No CUI, FCI, ITAR, EAR, CMMC, DFARS, DoD, program approval, or air-gapped availability is implied without a specifically authorized deployment.

WORKFLOW

Configuration identity → exact method/specification authority → reference qualification → controlled measurement → decision/review → portable proof → dependency recall.

04PRODUCTIONManufacturing qualityInstrument/program → scheduled work → controlled point evidence → conformity decision → OOT impact → CMMS/QMS handoff → closure proof.Inspect

OPERATING PROBLEM

Production decisions can depend on instruments, standards, specifications, process context, and prior calibrations that are difficult to reconstruct after an OOT event.

PRODUCT EVIDENCE / ARCHITECTURE

Calibration programs, due-state architecture, deterministic calculations, append-only evidence, review queues, and dependency-based impact analysis.

BOUNDARY

METRAXIOM supports measurement-resource and quality workflows; it is not a replacement for every MES, ERP, CMMS, LIMS, or QMS function.

WORKFLOW

Instrument/program → scheduled work → controlled point evidence → conformity decision → OOT impact → CMMS/QMS handoff → closure proof.

05OEM / SERVICEEquipment manufacturers and service organizationsControlled procedure and device profile → authorized service order → guided acquisition → review → certificate/evidence package → API or portal delivery.Inspect

OPERATING PROBLEM

Procedures, device profiles, service orders, certificates, revisions, compatibility, and customer evidence must remain consistent across products and technicians.

PRODUCT EVIDENCE / ARCHITECTURE

Procedure catalog, Device Bridge architecture, commercial-work-order model, certificate lineage, compatibility-register requirement, and versioned APIs.

BOUNDARY

Compatibility is declared by tested model, profile, firmware, and connection path—not by vendor name alone.

WORKFLOW

Controlled procedure and device profile → authorized service order → guided acquisition → review → certificate/evidence package → API or portal delivery.

SHARED CONTROL FOUNDATION

Context, authority, observation, model, decision, review, and proof remain separate.

That separation lets METRAXIOM support different industries without creating a different truth model for every customer. DUEPROOF supplies provenance, reliance, contest, correction, recall, and portable proof; metrology modules supply the discipline-specific meaning.

Serious use requires scoped validation.

Applicable law, contracts, quality procedures, personnel competence, method validation, security, data classification, and release authority remain customer- and deployment-specific.

Review current trust boundaries →

Automatic counts. No individual tracking.

TRACE counts approved public page requests worldwide without an analytics consent banner. No visitor identifiers, fingerprints, individual browsing histories or GPS locations are collected.

Analytics privacy update · October 29, 2026

TRACE automatically measures aggregate requests to approved public METRAXIOM pages worldwide to improve content, navigation and reliability. It runs at the first-party hosting proxy, before the hosting page cache, and works when JavaScript is disabled. No analytics consent banner or country-based opt-in selection is used.

The basic store contains separate hourly totals for approved pages, country and US-state labels, common referral domains, broad device/browser/operating-system families and unverified request categories. It contains no individual request ledger, full IP addresses, raw user agents, full URLs or queries, visitor identifiers, fingerprints, session histories or GPS coordinates. Country labels come from hosting network metadata and can describe a VPN or network exit. Missing geography is recorded as unavailable. No city, address or coordinates are collected. US-state labels come only from the trusted hosting header; other state/region labels remain unavailable. Software names are broad, spoofable claims, with no versions or cross-request fingerprint.

GPC, DNT and an explicit traffic objection stop collection. Earlier “Keep analytics off” choices saved only in browser storage are carried forward as objections when JavaScript runs on a public application page. They are not sent with the initial HTTP request: that request, JavaScript-disabled requests and static-only visits may contribute until an objection cookie or privacy signal is sent. Exclude this browser from traffic measurement without an account or JavaScript. The preference cookie uses the same value for everyone who excludes traffic (1) or explicitly restores basic measurement (0), lasts up to 180 days and does not identify you. Restoring basic measurement preserves the old local choice; it can apply again after the restore preference expires or is cleared. Restoring aggregate measurement does not override privacy signals or grant individual tracking permission. Earlier aggregate counts cannot be linked back to you or selectively removed.

When you choose a dashboard view, a separate functional reporting-preference cookie remembers only the preset or calendar dates for up to 30 days, scoped to /traffic. It is not used by the collection layer and contains no identifier or consent grant. Use Forget saved reporting view, including without JavaScript, to remove it. A failed refresh may display a clearly dated snapshot held briefly in page memory; it is never relabeled as current or replaced with fabricated zero counts.

Individual browser analytics is disabled in this aggregate-only rollout. The former optional browser collector is not loaded, its intake is retired, and no new tab/session events are accepted. Earlier consent records are not rewritten as new permission. Previously collected optional events follow their existing 30-day retention and integrity-checkpoint policy.

Page requests are separate from verified page rendering or unique people. Navigation requests, crawler claims, link previews, other automation and unknown requests remain separate. Estimated visitors and session histories are unavailable. Small labeled groups are combined in public reports. Counts are aggregate observations and do not establish identity, intent or endorsement.

Recognized health checks, HEAD requests, prefetches, server-component fetches and private/API/unapproved paths are excluded. Browser memory/disk cache, back-forward restores, client-only navigation, privacy objections, missing metadata and storage failures leave coverage gaps. Request retries and spoofed software labels can affect totals. The system does not extrapolate missed traffic or import historical Vercel Analytics counts.

Hourly counter buckets are retained for 30 days and pruned hourly in bounded runs; calendar reports exclude older hourly data even if maintenance is delayed. Separate cumulative marginal totals, with no event times or cross-dimension links, remain for the life of the site’s traffic record. Changing a date range, leaving the page or closing a browser does not erase those totals. Earlier uncollected state/software labels remain unavailable, not reconstructed. Vercel delivers the website and Supabase stores TRACE aggregates in the existing United States database. Provider security logs and backups have separate policies. TRACE adds no paid analytics feed or operator-computer dependency.

This October 29, 2026 supplement updates the analytics description in the September 7, 2026 Privacy Notice. It does not amend frozen agreement snapshots or claim that server-side processing is automatically exempt from privacy law. The assessment concerns this limited data flow and its controls; no universal regulatory approval is claimed. Privacy requests: ANDREWATTS23@gmail.com.