Skip to main content
Challenge

Build a Multi-Zone Metrology Route Optimizer

Analyze normalized open62541 OPC UA analog measurement drift against calibration thresholds. Generate an optimized routing sequence for metrology technicians across large plant zones to efficiently address out-of-tolerance instrumentation.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Analyze normalized open62541 OPC UA analog measurement drift against calibration thresholds. Generate an optimized routing sequence for metrology technicians across large plant zones to efficiently address out-of-tolerance instrumentation.

Plant Metrology Engineer

Ingest open62541 OPC UA analog measurement nodes and historical calibration drift records.

Evaluate drift severity and classify sensors requiring immediate calibration checks.

Group flagged sensors by physical plant coordinates or layout zones.

Calculate an optimized transit path for the metrology technician between the identified zones.

Plant layout map displaying prioritized calibration points and the computed shortest-path technician route.

Construct 300 normalized records reflecting open62541 OPC UA instrumentation nodes with drift metrics, calibration thresholds, and physical plant zone coordinates. Starter examples below are synthetic. They are not downloaded records.

open62541 OPC UA Extracts OPC UA variable arrays and engineering units metadata structures to track analog instrumentation values based on open62541.

langgraph, pydantic, fastapi. LangGraph orchestrates multi-step decision graphs to process drift metrics, group by zones, and determine the optimal technician routing path. Requires logical pathfinding and structured schema adherence via local 7B+ or hosted lightweight models.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Correctly calculates and flags sensors exceeding their specific calibration drift thresholds.

Successfully groups flagged sensors by their designated plant zones.

Outputs a valid JSON technician route sequence that minimizes zone-to-zone transit steps.

```json [ { "input": { "sensors": [ { "node_id": "ns=2;s=Mixer.Temp1", "zone": "A1", "drift_percent": 4.5, "limit": 3 }, { "node_id": "ns=2;s=Reactor.Press", "zone": "C4", "drift_percent": 5.2, "limit": 2.5 }, { "node_id": "ns=2;s=Mixer.Temp2", "zone": "A1", "drift_percent": 1.1, "limit": 3 } ], "start_zone": "A0", "note": "Simplified synthetic app records." }, "expected_output": { "flagged_sensors": [ "ns=2;s=Mixer.Temp1", "ns=2;s=Reactor.Press" ], "optimized_route_zones": [ "A0", "A1", "C4" ], "route_rationale": "Proceed from start A0 to nearest zone A1, then traverse to C4." } }, { "input": { "sensors": [ { "node_id": "ns=2;s=Packager.Weight", "zone": "D2", "drift_percent": 0.5, "limit": 1 } ], "start_zone": "A0", "note": "Simplified synthetic app records." }, "expected_output": { "flagged_sensors": [], "optimized_route_zones": [ "A0" ], "route_rationale": "No sensors exceed calibration thresholds; remain at start zone." } } ] ```

Read-only analytics routing personnel safely without modifying live calibration offsets or PLC logic. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Read-only analytics routing personnel safely without modifying live calibration offsets or PLC logic. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Correctly calculates and flags sensors exceeding their specific calibration drift thresholds. Successfully groups flagged sensors by their designated plant zones. Outputs a valid JSON technician route sequence that minimizes zone-to-zone transit steps.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest open62541 OPC UA analog measurement nodes and historical calibration drift records. Evaluate drift severity and classify sensors requiring immediate calibration checks. Group flagged sensors by physical plant coordinates or layout zones. Calculate an optimized transit path for the metrology technician between the identified zones.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Correctly calculates and flags sensors exceeding their specific calibration drift thresholds. Successfully groups flagged sensors by their designated plant zones. Outputs a valid JSON technician route sequence that minimizes zone-to-zone transit steps.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Plant layout map displaying prioritized calibration points and the computed shortest-path technician route.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Read-only analytics routing personnel safely without modifying live calibration offsets or PLC logic.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest open62541 OPC UA analog measurement nodes and historical calibration drift records.

  • Evaluate drift severity and classify sensors requiring immediate calibration checks.

  • Group flagged sensors by physical plant coordinates or layout zones.

  • Calculate an optimized transit path for the metrology technician between the identified zones.

Resources and assets

Reference links and supporting material

Dataset notes

Construct 300 normalized records reflecting open62541 OPC UA instrumentation nodes with drift metrics, calibration thresholds, and physical plant zone coordinates. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

LangGraph

Runtime for stateful agent workflows.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest open62541 OPC UA analog measurement nodes and historical calibration drift records. Evaluate drift s...
  • Correctly calculates and flags sensors exceeding their specific calibration drift thresholds. Successfully...
  • Plant layout map displaying prioritized calibration points and the computed shortest-path technician route.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 2 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • LangGraph · Optional
Orchestration
  • LangGraph · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Multi-Zone Metrology Route Optimizer