Skip to main content
Back to Prompt Library
implementation

Build the application

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: Build a Building Thermal Resilience and Grid Outage Simulator

Format
Code-aware
Lines
87
Sections
11
Linked challenge
Build a Building Thermal Resilience and Grid Outage Simulator

Prompt source

Original prompt text with formatting preserved for inspection.

87 lines
11 sections
No variables
1 code block
## Build
Evaluate commercial building passive survivability during extreme heat grid outages using EnergyPlus. Simulate indoor temperature drift across zones and formulate actionable, emergency occupancy relocation schedules to maintain human safety.

## User
Building sustainability engineer

## Workflow
1. Ingest building epJSON models, utility outage timeframes, and extreme heat weather files formatted for EnergyPlus.
2. Simulate indoor thermal drift across zones using EnergyPlus with active HVAC cooling systems disabled.
3. Identify specific thermal zones exceeding safe human occupancy thresholds, strictly defined as 30 degrees Celsius.
4. Generate a prioritized evacuation and temporary cooling center routing plan for human review.

## Interface
Thermal drift dashboard mapping building zones against simulated operative temperatures and required evacuation timelines.

## Data
Utilize reference commercial building epJSON files and historical extreme heat weather data formatted for EnergyPlus.
Starter examples below are synthetic. They are not downloaded records.

## Source
[EnergyPlus](https://raw.githubusercontent.com/NREL/EnergyPlus/develop/README.md)
Executes EnergyPlus thermal zone simulations to compute hourly operative temperature drift during mechanical cooling failures.

## Tools
pydantic-ai, pandas, numpy.
Enforces strict structured validation on thermal thresholds, evacuation logic, and zone occupancy data.
Fast cloud LLM with strong mathematical and structured reasoning capabilities.

## Deliverables
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.

## Acceptance
- Executes EnergyPlus simulations with HVAC systems disabled to accurately model passive thermal drift.
- Flags any thermal zone mathematically exceeding the 30 degrees Celsius safety threshold during the specified outage window.
- Generates a structured occupancy relocation plan prioritizing zones with the fastest thermal limit breaches.

## Starter Examples
```json
[
  {
    "input": {
      "building_id": "BLDG-OFFICE-12",
      "initial_zone_temp_c": {
        "Zone_South": 24,
        "Zone_Core": 22
      },
      "hourly_drift_c": {
        "Zone_South": 3.5,
        "Zone_Core": 1
      },
      "outage_duration_hours": 2,
      "occupancy": {
        "Zone_South": 45,
        "Zone_Core": 120
      }
    },
    "expected_output": {
      "peak_temps_c": {
        "Zone_South": 31,
        "Zone_Core": 24
      },
      "evacuation_required": [
        "Zone_South"
      ],
      "relocation_target": "Zone_Core",
      "record_type": "Simplified synthetic app record for testing"
    }
  },
  {
    "input": {
      "building_id": "BLDG-RETAIL-04",
      "initial_zone_temp_c": {
        "Main_Floor": 23
      },
      "hourly_drift_c": {
        "Main_Floor": 1.5
      },
      "outage_duration_hours": 4,
      "occupancy": {
        "Main_Floor": 300
      }
    },
    "expected_output": {
      "peak_temps_c": {
        "Main_Floor": 29
      },
      "evacuation_required": [],
      "relocation_target": "None",
      "record_type": "Simplified synthetic app record for testing"
    }
  }
]
```

## Safety
Recommends evacuation plans that must be reviewed by facility managers and emergency response personnel before execution.
Use mock external writes. Require human review before any real deployment.

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Hold the task contract and output shape stable so generated implementations remain comparable.

Tune next

Update libraries, interfaces, and environment assumptions to match the stack you actually run.

Verify after

Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.