Focused on Asia Pacific · Connected to global practice
← Back to topic toolsPROJECT DELIVERY & EVIDENCE TOOLS · 1.0.0

Dispatch and settlement sensitivity

Import interval CSV and reconcile requested versus measured reduction, contractual receipts, costs and a transparent downside scenario.

Inputs, calculation and explicit draft saves remain in this browser. JSON backups contain the complete register or CSV, so review them before sharing. Local history records explicit saves only, retains 30 save records and is editable; it is not a tamper-proof audit trail or multi-user database.

Restore from a JSON backup

Paste the complete JSON backup from this tool. Loading replaces the current inputs; export them first if needed.

1. Define the explicit contractual scenario

This model is for consumption curtailment. The baseline and actual MW share one boundary and interval. A consumption increase is negative delivery, retains its sign and receives no curtailment payment. This is not a battery power dispatch or programme settlement engine.

2. Supply non-overlapping interval CSV

Paste comma, semicolon or tab-separated UTF-8 CSV, up to 5,000 intervals / 2 MB. Use every template header. Times need Z or ±HH:mm. Durations are minutes; powers are MW; recharge quantities are MWh; service/recharge rates are currency per MWh; wear and foregone value are total currency per row. Rows may be sorted on calculation.

The second sample interval consumes more than baseline and must fail to deliver its requested reduction. Do not extrapolate these two intervals to annual earnings. All initial contract/scenario references remain blank.

Learn the method and continue the project

Open the related technical lessonReview the project data requestReturn to all topic tools