LIVEdataset aec-bench@releasetasks 552models 18disciplines 5last submission … · built …

electricalwith-tool

Poe Power Budget

Calculates total Power over Ethernet demand from device count and per-device power draw, then compares it with the switch PoE budget. The deterministic check reports utilization, available headroom, required headroom allowance, and remaining headroom margin.

with-tool: The model is given an executable Python calculator script.

Standards

IEEE 802.3at IEEE 802.3bt

Tags

deterministic electrical network poe power-budget

How this task is generated

One template produces many comparable benchmark tasks while keeping the scoring contract fixed.

01
Template
The reusable contract shown on this page.
02
Scenario
An archetype and site context are sampled.
03
Difficulty tier
Inputs may be hidden at harder tiers.
04
Task prompt
The model responds with the declared outputs.

Parameters

Inputs the model receives, and the outputs it is scored on.

Inputs

4 inputs

Always given

Included directly in every task prompt.

3

Device count
device_count
Number of PoE powered devices
1 – 96
Power draw per device
power_draw_per_device_w
Power draw per device
1 – 90 W
Switch poe budget
switch_poe_budget_w
Available switch PoE budget
30 – 3000 W

Hidden at higher difficulty

Visible in easier tasks and withheld in one or more harder tiers.

1

Required headroom pct
required_headroom_pct
Required headroom as a percentage of connected PoE load
Hidden at hard difficulty.
0 – 50 %

Scored outputs

5 outputs

Total power requirement w

total_power_requirement_w

Total PoE power requirement

Scores if within ±3% of the reference value.

Utilization pct

utilization_pct

PoE budget utilization

Scores if within ±3% of the reference value.

Available headroom w

available_headroom_w

Unused PoE budget

Scores if within ±3% of the reference value.

Required headroom w

required_headroom_w

Required headroom allowance

Scores if within ±3% of the reference value.

Headroom margin w

headroom_margin_w

Margin after required headroom

Scores if within ±3% of the reference value.

Difficulty

Each template is sampled at three tiers. Harder tiers may hide inputs, forcing the model to infer them from the scenario description.

easy

All inputs given

Small access switch budget

medium

All inputs given

Access or high-power PoE switch

hard

Some inputs hidden

Headroom allowance hidden in design context

Hidden inputs

Required headroom pctrequired_headroom_pct

Prompt replacement text

Use the required power reserve implied by {{ archetype.description }}.

Required headroom pct restricted to: 20

Task bundle

The exact instruction and parameter contract used to generate this task, pinned to the published library source.

/workspace

instruction.md
poe-power-budget_calc.py

Teal lines show Jinja input conditions, not task visibility policy. A line renders only when that input or tool is visible.

1You are a senior electrical and communications engineer checking a PoE switch power budget.2 3## Given4 5| Parameter | Value | Unit |6|-----------|-------|------|7| Powered devices | {{ device_count }} | count |8| Power draw per device | {{ power_draw_per_device_w }} | W |9| Switch PoE budget | {{ switch_poe_budget_w }} | W |10{% if required_headroom_pct is defined %}11| Required headroom | {{ required_headroom_pct }} | % |12{% endif %}13 14## Constraints15 16- Total PoE demand equals device count times per-device draw.17- Utilization equals total demand divided by switch PoE budget.18- Available headroom equals switch budget minus total demand.19- Required headroom equals total demand times the headroom percentage.20- Headroom margin equals available headroom minus required headroom.21 22## Output Format23 24Include a JSON block with exactly these keys:25 26```json27{28  "total_power_requirement_w": <numeric_value>,29  "utilization_pct": <numeric_value>,30  "available_headroom_w": <numeric_value>,31  "required_headroom_w": <numeric_value>,32  "headroom_margin_w": <numeric_value>33}34```35 36Write your complete solution to `/workspace/output.md`.37

Scenario archetypes

Each generated task is drawn from one of these realistic scenario bands.

Site contexts ground each scenario in a real locale the model can use to infer hidden values.

Access switch

access_switch

Access switch serving cameras and wireless access points

station-comms-roomcampus-access-switch

Parameter ranges

device_count: 4 – 48
power_draw_per_device_w: 7 – 30
switch_poe_budget_w: 180 – 1200
required_headroom_pct: 10 – 25

High power switch

high_power_switch

High-power PoE switch serving PTZ cameras or field devices

roadside-cabinetsecurity-headend

Parameter ranges

device_count: 8 – 96
power_draw_per_device_w: 20 – 75
switch_poe_budget_w: 740 – 3000
required_headroom_pct: 15 – 35

Example task

roadside-cabinet-high-power-switch-preview — hard difficulty, some inputs hidden.

High-power PoE switch serving PTZ cameras or field devices. roadside-cabinet. Required outputs: total_power_requirement_w, utilization_pct, available_headroom_w, required_headroom_w, headroom_margin_w

The model sees

Scenario context and visible inputs.

device_count: 8 to 96
power_draw_per_device_w: 20 to 75 W
switch_poe_budget_w: 740 to 3000 W

Executable tool: poe-power-budget_calc.py

The model must infer

Inputs withheld at this difficulty.

Required headroom pct
required_headroom_pct

Stand-in text in the prompt

Use the required power reserve implied by {{ archetype.description }}.

The model must produce

The scored JSON answer schema.

{
  "total_power_requirement_w": <number>,
  "utilization_pct": <number>,
  "available_headroom_w": <number>,
  "required_headroom_w": <number>,
  "headroom_margin_w": <number>
}

total_power_requirement_w · scored within ±3%
utilization_pct · scored within ±3%
available_headroom_w · scored within ±3%
required_headroom_w · scored within ±3%
headroom_margin_w · scored within ±3%