Skip to content
M2M TECH — Code AI

Arc Vision

Powered by MEA

10
Open cases
10
Awaiting review
5
Open work
1
Overdue
0
Awaiting verification
1
Valid readings
180/191
Synthetic · analytics not connected
About this demo

All machine data is invented. This is a demo starting point for the Hitachi Challenge Europe Theme 3 direction — not a Hitachi integration, not a validated diagnostic product and not a production deployment. Workflow state is synchronized to an isolated guest Cloud workspace when available; photos remain local. This is not a tamper-proof audit log. Planner/Technician are view presets, not authorization roles.

Arc VisionWorkspace

Demo scenarios

Three synthetic walkthroughs. Opening never resets your work; restarting asks for confirmation and affects only that case.

Scenarios
3
Verified
0
In progress
3

Confirmed bearing fault (synthetic)

Needs decision
  1. 1. Observation: Drive-end vibration rises 3x over three weeks with a temperature rise.
  2. 2. Evidence: Data available, comparable with a human-declared baseline, 21/21 samples.
  3. 3. Reason: Trend and spectrum suggest a possible outer-race defect — a hypothesis, not a finding.
  4. 4. Human decision: Approve the inspection, assign a technician and due date.
  5. 5. Outcome: The technician explicitly records a finding. See CASE-1006 for a completed repair with post-intervention evidence to verify.
Walk through CASE-1001

Telemetry gap (synthetic)

Needs decision
  1. 1. Observation: No samples for 9 days.
  2. 2. Evidence: Sensor disconnected; 12/21 samples. A gap is not a healthy reading.
  3. 3. Reason: Condition diagnosis is withheld; restore data collection first.
  4. 4. Human decision: Approve a data-restoration task (or defer until a fresh reading).
  5. 5. Outcome: A validated fresh reading returns the case to review — no bearing finding is invented.
Walk through CASE-1002

Changed operating context (synthetic)

Needs decision
  1. 1. Observation: Amplitude stepped up at the same time as a documented duty-point change.
  2. 2. Evidence: Not comparable with the part-load baseline (speed and load outside tolerance).
  3. 3. Reason: The operating context explains the step; no bearing conclusion is drawn.
  4. 4. Human decision: Approve acquiring comparable evidence at the current duty point.
  5. 5. Outcome: A named engineer may declare the new reading as the baseline; otherwise it stays a reference only.
Walk through CASE-1003