Feature scope

See what works. Know what still needs testing.

The core work-order-to-PDF workflow has passed a synthetic browser demonstration. Other modules are at different stages; a visible screen is not evidence of a complete, production-ready feature.

Early accessSynthetic demonstrationValidation before production

Selected record flows tested

Clients, facilities and instruments

Client, facility and instrument records were created and retrieved during testing. Customer-owned and internal instruments do not yet behave consistently across all modules.

  • Evaluate your asset types and required history before migration.
  • Bulk import, exports, labels, custom fields and production data volumes still need end-to-end validation.

Synthetic demonstration passed

Manual calibration worksheets

A procedure-defined five-point workflow saved manual readings and environmental values and produced a draft record. No physical instrument was connected in this test.

  • Your procedures, tolerances, uncertainty calculations and decision rules need independent verification.
  • Hardware capture, Beamex imports and automatic environmental feeds have not been validated.

Core synthetic path tested

Review, signing and PDF output

A draft was reviewed, approved, signed after password verification, downloaded as a PDF and opened through public verification. The same demo administrator performed and reviewed the test.

  • Independent reviewer permissions and separation of duties are not validated.
  • Public verification does not establish measurement validity or accreditation.
  • DCC export and digital signing have not passed end-to-end validation.

Selected workflow tested

Work orders and release conditions

The test linked a client instrument, procedure and work order through execution and release. Completion was blocked until approval and issuance in the tested path.

  • Customer scenarios, parallel activity, exceptions and all permissions require additional testing.
  • Live collaborative review is currently not usable because its connection does not stay established.

Partially tested

Scheduling and record history

One internal-instrument schedule flow was tested. Date/status inconsistencies and differences for customer-owned instruments remain open.

  • Notification and email delivery have not been demonstrated; outgoing email is not configured.
  • Predictive interval recommendations have not been validated.

Selected examples checked

SPC and measurement analysis

One synthetic SPC example and one range-method Gage R&R example were checked. These checks do not validate every method or establish metrological suitability.

  • Some dashboard and report counts disagree and need correction.
  • RBI, uncertainty budgets and advanced reporting require fuller validation.
  • The drift-analysis insufficient-history guard was tested; successful predictive analysis was not.

Limited workflow coverage

Quality and supporting records

Selected training-record, non-conformance/CAPA and manual environment-record flows were tested. A saved training record does not establish technician competence.

  • Document upload/download, traceability, notifications, teams and other supporting modules need further workflow testing.

Important open gaps

Integrations, mobile and audit controls

Integration health currently returns an error. No external connector or mobile field workflow has been validated. Ten historical audit-hash mismatches remain, although selected new entries passed checks.

  • Do not treat the audit history as fully verified or tamper-proof.
  • The Android APK is available for evaluation only.
  • Read Product status before planning an operational deployment.

Evaluate the fit before operational use.

Use synthetic data first. Production use depends on resolving relevant gaps, validating your procedures and controls, and agreeing acceptance and commercial terms. A demo does not establish metrological validity, compliance or security certification.