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 District Cooling Thermal Handover Compliance Reviewer

Format
Code-aware
Lines
70
Sections
11
Linked challenge
Build a District Cooling Thermal Handover Compliance Reviewer

Prompt source

Original prompt text with formatting preserved for inspection.

70 lines
11 sections
No variables
1 code block
## Build
Analyze tenant chilled water building connection submittals in Arabic and English against district cooling standards. Detect insufficient temperature differential designs that cause low delta-T syndrome.

## User
District cooling customer connection managers and MEP technical compliance auditors

## Workflow
1. Extract tenant energy transfer station submittal specifications from bilingual PDF technical schedules.
2. Evaluate coil flow rates and design supply-return temperatures using EnergyPlus heat exchanger definitions.
3. Detect low delta-T risks that threaten central cooling plant distribution efficiency.
4. Synthesize a bilingual connection compliance scorecard and remediation notice for the property developer.

## Interface
Bilingual document inspection interface highlighting extracted design variables and delta-T compliance status.

## Data
Use mock bilingual Arabic-English tenant MEP submittal manifests paired with EnergyPlus heat exchanger schema snippets.
Starter examples below are synthetic. They are not downloaded records.

## Source
[EnergyPlus](https://raw.githubusercontent.com/NREL/EnergyPlus/develop/README.md)
Utilizes EnergyPlus epJSON heat exchanger and water coil object properties to calculate thermal transfer efficiency.

## Tools
haystack, pydantic-ai, pandas, fastapi.
haystack manages bilingual document parsing, text extraction, and clause retrieval across technical submittals.
Hosted multilingual LLM capable of high-accuracy English and Arabic technical translation and extraction.

## 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
- Parses bilingual Arabic-English submittal documents to extract design flow, supply temperature, and return temperature.
- Flags submittals failing to achieve the contractual 8.5°C delta-T threshold across heat exchangers.
- Generates bilateral compliance scorecards with itemized engineering discrepancies.
- Requires chief MEP engineer sign-off before official client rejection letters are dispatched.

## Starter Examples
```json
[
  {
    "input": {
      "submittal_id": "SUB-DXB-902",
      "document_language": "ar-en",
      "design_supply_temp_c": 5.5,
      "design_return_temp_c": 14.5,
      "design_flow_lps": 42,
      "building_type": "Commercial Office"
    },
    "expected_output": {
      "delta_t_c": 9,
      "status": "APPROVED",
      "contractual_threshold_met": true,
      "summary_en": "Meets 8.5C minimum delta-T design standard.",
      "summary_ar": "مطابق لمعيار فرق درجات الحرارة الأدنى 8.5 مئوية."
    }
  },
  {
    "input": {
      "submittal_id": "SUB-DXB-903",
      "document_language": "ar-en",
      "design_supply_temp_c": 6,
      "design_return_temp_c": 11.2,
      "design_flow_lps": 68,
      "building_type": "Residential Tower"
    },
    "expected_output": {
      "delta_t_c": 5.2,
      "status": "REJECTED",
      "contractual_threshold_met": false,
      "summary_en": "Deficient delta-T (5.2C vs 8.5C req); risk of low delta-T plant derating.",
      "summary_ar": "فرق درجات حرارة غير كافٍ (5.2 مئوية مقابل 8.5 مئوية مطلوبة)؛ خطر تدني كفاءة المحطة."
    }
  }
]
```

## Safety
Generates technical compliance audit reports only; contractual permissions remain subject to physical inspection.
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.