Build an OPC UA Equipment Acceptance Checklist Reconciler
Process simulated open62541 server telemetry to audit factory equipment against site acceptance specifications. Flag missing telemetry nodes and compile acceptance sign-off packets.
What you are building
The core problem, expected build, and operating context for this challenge.
Process simulated open62541 server telemetry to audit factory equipment against site acceptance specifications. Flag missing telemetry nodes and compile acceptance sign-off packets.
Factory Integration Specialist
Parse node ID structures and value definitions from simulated open62541 server snapshots.
Compare exposed node definitions against contract equipment acceptance checklists.
Evaluate telemetry sampling jitter and sensor error flags across commissioning tests.
Construct a standardized acceptance packet highlighting missing or out-of-spec node definitions.
Browser-based commissioning checklist view with node discovery statuses and sign-off export controls.
Construct mock JSON node dumps mimicking open62541 information models with status codes and engineering units. Starter examples below are synthetic. They are not downloaded records.
open62541 OPC UA Uses open62541 architecture principles where OPC UA nodes and server information models define equipment capabilities.
mastra-ai, typescript, zod. Mastra AI provides deterministic workflow orchestration to walk complex hierarchical information models. Fast reasoning API capable of reconciling tabular schema checklists against observed telemetry nodes.
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.
Flags missing mandatory nodes according to the site acceptance checklist.
Detects invalid OPC UA StatusCode values during test runs.
Generates a verified acceptance packet with sign-off recommendations.
```json [ { "input": { "equipment_tag": "PUMP-SKID-04", "mandated_nodes": [ "ns=2;s=InletPressure", "ns=2;s=DischargeFlow", "ns=2;s=MotorAmps" ], "observed_nodes": [ { "node_id": "ns=2;s=InletPressure", "status": "Good", "value": 4.2, "unit": "bar" }, { "node_id": "ns=2;s=DischargeFlow", "status": "Good", "value": 110, "unit": "m3/h" }, { "node_id": "ns=2;s=MotorAmps", "status": "Good", "value": 24.1, "unit": "A" } ] }, "expected_output": { "equipment_tag": "PUMP-SKID-04", "checklist_conformance": true, "missing_nodes": [], "handover_recommendation": "SIGN_OFF" } }, { "input": { "equipment_tag": "PUMP-SKID-05", "mandated_nodes": [ "ns=2;s=InletPressure", "ns=2;s=DischargeFlow", "ns=2;s=MotorAmps" ], "observed_nodes": [ { "node_id": "ns=2;s=InletPressure", "status": "BadSensorFailure", "value": 0, "unit": "bar" } ] }, "expected_output": { "equipment_tag": "PUMP-SKID-05", "checklist_conformance": false, "missing_nodes": [ "ns=2;s=DischargeFlow", "ns=2;s=MotorAmps" ], "handover_recommendation": "REMEDIAL_ACTION_REQUIRED" } } ] ```
Read-only inspection of static node dumps; no live OPC UA method invocations. Use mock external writes. Require human review before any real deployment.
Participation guide
Read-only inspection of static node dumps; no live OPC UA method invocations. Use mock external writes and human review.
How work is evaluated
Flags missing mandatory nodes according to the site acceptance checklist. Detects invalid OPC UA StatusCode values during test runs. Generates a verified acceptance packet with sign-off recommendations.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Parse node ID structures and value definitions from simulated open62541 server snapshots. Compare exposed node definitions against contract equipment acceptance checklists. Evaluate telemetry sampling jitter and sensor error flags across commissioning tests. Construct a standardized acceptance packet highlighting missing or out-of-spec node definitions.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Flags missing mandatory nodes according to the site acceptance checklist. Detects invalid OPC UA StatusCode values during test runs. Generates a verified acceptance packet with sign-off recommendations.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Browser-based commissioning checklist view with node discovery statuses and sign-off export controls.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Read-only inspection of static node dumps; no live OPC UA method invocations.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Parse node ID structures and value definitions from simulated open62541 server snapshots.
Compare exposed node definitions against contract equipment acceptance checklists.
Evaluate telemetry sampling jitter and sensor error flags across commissioning tests.
Construct a standardized acceptance packet highlighting missing or out-of-spec node definitions.
Reference links and supporting material
Construct mock JSON node dumps mimicking open62541 information models with status codes and engineering units. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
Mastra AI
TypeScript agent framework.
Evaluated output
No output checks are configured.
- Parse node ID structures and value definitions from simulated open62541 server snapshots. Compare exposed n...
- Flags missing mandatory nodes according to the site acceptance checklist. Detects invalid OPC UA StatusCode...
- Browser-based commissioning checklist view with node discovery statuses and sign-off export controls.
- 2 public reference cases
- 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
- Mastra AI · Optional
- Mastra AI · 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.