Controller truth
PLC and OPC data can be safety-relevant, but only if the tags, states, and timing are interpreted carefully.
Verification Method
From messy site signals to governed verification truth.
AviRob starts where industrial reality actually starts: mixed source families, ugly raw signals, and requirements that already exist before verification begins. The hard part is not just ingestion. It is inspecting raw source truth, assigning meaning carefully, and keeping that meaning governed as the site evolves.
- AviRob sits after risk assessment and safety-function definition. It does not author the original safety concept.
- PASS or FAIL is only allowed when explicit evidence dependencies are satisfied. Missing proof stays NOT_VERIFIABLE.
- The same lane supports FAT/SAT, release handoff, and recurring revalidation after robot, site, or config change.
Installed and on-prem deployment patterns are supported for industrial environments where source data needs to stay local.
Source families first, polished abstractions later
Industrial edge truth is rarely clean. AviRob starts from the sources teams actually have, not the sources they wish they had.
Fleet truth
VDA/FMS and orchestration streams add mission and coordination context, but they do not replace direct proof.
File truth
Folders, mixed exports, MCAP, rosbag, CSV, and text logs are often the fastest realistic entry point.
Identity truth
Aliases, partial IDs, code tables, and register values often need review before anyone should treat them as canonical.
Diagnostic truth
Some inputs explain or correlate behavior, but they are not strong enough on their own to justify a verdict.
Derived truth
Derived or synthetic views can accelerate review, but AviRob keeps them explicit so reviewers know what they depend on.
Why mapping and governance matter
- Raw industrial signals are often ugly, inconsistent, or only partially labeled.
- The same field can mean different things across vendors, sites, or software versions.
- Trustworthy verification needs inspectable mapping decisions, not invisible normalization.
- Those mapping decisions need review, versioning, and auditability over time.
Governed mapping lane
- Inspect the raw signal: bit, register, event code, alias, or partial identifier.
- Define the canonical meaning that a reviewer can understand and challenge.
- Review and version the mapping so changes stay visible over time.
- Use that governed meaning as the basis for checks, evidence, and gap reporting.
Evidence lanes stay explicit
AviRob keeps direct, diagnostic, derived, and synthetic evidence distinct so weaker lanes are not silently upgraded into verdict truth. If a required dependency is missing, the result stays NOT_VERIFIABLE.
Direct evidence
Use the strongest available source when a requirement needs direct proof from the safety-relevant layer.
Diagnostic evidence
Diagnostics can explain what happened, but they are not silently upgraded into direct proof.
Derived evidence
Derived views stay tied to their source dependencies so reviewers can see what the claim rests on.
Synthetic evidence
Synthetic or simulated views can accelerate workflow, but they stay explicit and are not mistaken for direct proof.
Built for the maintain phase, not only the first deployment
FAT/SAT is an entry point. The maintain-phase wedge is what makes the lane durable.
Recurring revalidation
Rerun checks after robot updates, site changes, fleet growth, or changed operating assumptions.
Stale evidence visibility
See when an old proof package no longer matches the site reality you are now operating.
Operational drift review
Find repeated issues, hotspots, and drift without dropping back to raw-log archaeology every time.
Installed deployment reality
- AviRob can fit installed, on-prem, and isolated deployment patterns.
- Controlled import and export workflows matter because industrial sites are not always cloud-friendly.
- Diagnostics, backup-minded operations, and admin control are part of product credibility here.
- The goal is software that reads like industrial infrastructure, not just a pilot landing page.
Lifecycle position
- Risk assessment and safety-function definition stay upstream.
- AviRob helps teams verify against those already-defined requirements.
- It is not a certifier and not a control or safety function.
- Its job is governed evidence, explicit gaps, and reviewable truth.
Start with one governed mapping and one real verification question.
Bring one representative source bundle, one trust boundary, and one deployment question you want answered without hand-waving.