Skip to main content
Challenge

Build a Plant Equipment Commissioning Acceptance Audit Packager

Cross-reference factory acceptance test checklists with simulated Sparkplug B device birth data and sensor ranges. Assemble audit-ready commissioning documentation for client handover.

EngineeringHosted by Vera
Challenge brief

What you are building

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

Cross-reference factory acceptance test checklists with simulated Sparkplug B device birth data and sensor ranges. Assemble audit-ready commissioning documentation for client handover.

Industrial Project Engineer

Parse NBIRTH payloads and device metric definitions from simulated Sparkplug B streams.

Verify that instrument engineering units and metric ranges meet acceptance criteria.

Flag unannounced or missing device metrics required by contractual commissioning specs.

Synthesize a client-ready equipment commissioning acceptance summary packet.

Web view showing contractual commissioning criteria, live metric bindings, and acceptance packet download button.

JSON dumps representing Sparkplug B NBIRTH templates, metric properties, and contract specification tables. Starter examples below are synthetic. They are not downloaded records.

Eclipse Sparkplug Implements Sparkplug B NBIRTH metric metadata and property fields (e.g., engineering units, min/max limits).

pydantic-ai, fastapi, jinja2. Pydantic AI cleanly validates Sparkplug metric property types against contractual commissioning schemas. Local or hosted LLM with strong schema enforcement and contract parsing capabilities.

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 metric range definitions that do not match project specification sheets.

Validates presence of all mandatory Sparkplug B birth metadata properties.

Outputs a valid equipment acceptance certificate in JSON format.

```json [ { "input": { "contract_id": "CTR-9012", "device_id": "CHILLER-EDGE-01", "required_metrics": [ { "name": "SupplyTemp", "unit": "degC", "min": -10, "max": 50 } ], "nbirth_payload": { "metrics": [ { "name": "SupplyTemp", "properties": { "eng_unit": "degC", "eng_min": -10, "eng_max": 50 } } ] } }, "expected_output": { "contract_id": "CTR-9012", "device_id": "CHILLER-EDGE-01", "acceptance_passed": true, "discrepancies": [], "certificate_status": "READY_FOR_SIGNATURE" } }, { "input": { "contract_id": "CTR-9012", "device_id": "CHILLER-EDGE-02", "required_metrics": [ { "name": "SupplyTemp", "unit": "degC", "min": -10, "max": 50 } ], "nbirth_payload": { "metrics": [ { "name": "SupplyTemp", "properties": { "eng_unit": "degF", "eng_min": 14, "eng_max": 122 } } ] } }, "expected_output": { "contract_id": "CTR-9012", "device_id": "CHILLER-EDGE-02", "acceptance_passed": false, "discrepancies": [ "Unit mismatch on SupplyTemp: expected degC, found degF" ], "certificate_status": "REJECTED" } } ] ```

Audit compilation only; does not transmit actuation or write commands to edge controllers. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Audit compilation only; does not transmit actuation or write commands to edge controllers. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Flags metric range definitions that do not match project specification sheets. Validates presence of all mandatory Sparkplug B birth metadata properties. Outputs a valid equipment acceptance certificate in JSON format.

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

Parse NBIRTH payloads and device metric definitions from simulated Sparkplug B streams. Verify that instrument engineering units and metric ranges meet acceptance criteria. Flag unannounced or missing device metrics required by contractual commissioning specs. Synthesize a client-ready equipment commissioning acceptance summary packet.

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

Flags metric range definitions that do not match project specification sheets. Validates presence of all mandatory Sparkplug B birth metadata properties. Outputs a valid equipment acceptance certificate in JSON format.

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

Web view showing contractual commissioning criteria, live metric bindings, and acceptance packet download button.

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

Audit compilation only; does not transmit actuation or write commands to edge controllers.

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

  • Parse NBIRTH payloads and device metric definitions from simulated Sparkplug B streams.

  • Verify that instrument engineering units and metric ranges meet acceptance criteria.

  • Flag unannounced or missing device metrics required by contractual commissioning specs.

  • Synthesize a client-ready equipment commissioning acceptance summary packet.

Resources and assets

Reference links and supporting material

Dataset notes

JSON dumps representing Sparkplug B NBIRTH templates, metric properties, and contract specification tables. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Pydantic AI

Typed Python agent framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Parse NBIRTH payloads and device metric definitions from simulated Sparkplug B streams. Verify that instrum...
  • Flags metric range definitions that do not match project specification sheets. Validates presence of all ma...
  • Web view showing contractual commissioning criteria, live metric bindings, and acceptance packet download b...
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
  • Pydantic AI · Optional
Orchestration
  • Pydantic 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.

Frequently Asked Questions about Build a Plant Equipment Commissioning Acceptance Audit Packager