Protected Website Forms
HTTPS, antiforgery validation, input limits, and reCAPTCHA protect public form submissions. Review the safeguards.
Reading MTConnect Validation Evidence
Interpret validator and auditor findings in the context of the implementation, MTConnect version, and test scope.
Know the evidence source
- Online validator findings reflect the response documents and options submitted for that validation run.
- Auditor findings reflect the streams, rules, and monitoring period configured in the deployed environment.
- Supporting records should identify the MTConnect version, equipment, endpoint, test time, and scenarios in scope.
Review findings consistently
- Confirm the evidence source, MTConnect version, device, endpoint, and tested response or time window.
- Group findings by schema, model, vocabulary, sequence, or observed data-quality issue.
- Trace each finding to the affected document element, component, DataItem, or observation.
- Record the owner and corrective action, then rerun the same scenario after the change.
- Retain the before-and-after evidence with the release or deployment record.
A clean result applies only to the material and scope evaluated. It does not establish coverage for untested equipment states, endpoints, versions, or future configuration changes.
Looking for the Data Item workbook?
The MTConnect Data Item Reference Workbook is a separate terminology and planning asset. It is not generated validation evidence for an implementation.
Request the reference workbook