Scenario Explorer
Work through what a pricing change would have meant, before anything is published.
Inputs
What data is required?
- A base set of rates, fleet and demand assumptions
- The change you want to test, and the range you want to test it across
Outputs
What does it calculate, display or help you decide?
- The modelled effect of a change, with every assumption exposed
- A clear separation between a modelled scenario and a real result
Build prompt
Not yet written. This module is proposed and not scheduled. The purpose, inputs, outputs and operating complication above describe what it would do; the build prompt, setup steps, dependencies and tests will be added if it is taken forward.
The part that catches people out
A scenario is an assumption, not a forecast. Any modelled outcome depends on how demand is assumed to respond, and that assumption is usually the least certain part of the model. Show the assumption next to the result, allow it to be changed, and never present a scenario as something that happened.
Optional RME connection
To be defined. Any supported data connection would require approved interfaces and verified data rights.
Any connection to RateHighway services would require approved interfaces, authorisation, tenant isolation and verified data rights. Nothing about access or availability is approved.
Proposed, not scheduled
There is nothing to build from yet. Start with a module that has a written prompt, or read the playbook to decide whether this one is worth building at all.