Develop a roadmap for running operational scenarios
Tender ID: 567083
Tender Details
Tender Description
This Tender is invited by the Issuer.
The MDBA is in the process of adoption the Source model to support river operations. A key requirement is defining how the MDBA is best to run scenarios with the Source Operations Model (SOPS) and how this connects to the ROWs system. There is a complex workflow that exists, where data is prepared by the ROWS workflow system, this data is exported into a text file, the SOPS loads this data, and the user can then run and view the results (Figure 1). This workflow is okay when the operator is only testing one scenario. However, a key output from adopting SOPS is the ability to run multiple scenarios with the aims of:
Allowing the operator to test decisions against a range of inflows and demand conditions and providing a mechanism for producing likelihood results (i.e. what is the likelihood of flow downstream of Yarrawonga exceeding a certain amount). Currently, the SOPS takes approximately 4 min to load, 0.5 min to run. We are looking at providing the ability to run scenarios in two ways. A number of predefined scenarios (8 scenarios as a starting point) ensemble runs (1000 scenarios). For these scenario runs to assist operators, they must be able to run efficiently and not take too long.
The workflow undertaken by the operator is summarised in Figure 1. Running multiple scenarios can be undertaken in different ways. This project will explore the options for undertaking this scenario analysis; including consideration of Minimise operator workload and be simple as possible, Efficiency of run time: Load time and run time Parallelization Etc. Where to run scenarios from, ROWS Source Command line (server/cline) Veneer, Etc. their considerations include Scenarios would ideally be able to be run standalone (external to ROWS for testing/debugging and development purpose) as well been driven from ROWS Assuming ROWS is the best way for running scenarios, we would want consistency in code between ROWS and standalone running to enable ongoing development/maintenance (can both approaches use a common script).
If using client/server approach, can we update model through guide and start parallel run or do we need to reload model each time we change something in model. This impacts on overall run time. Business continuity and disaster recovery options. Current MDBA initiatives including: The current state/target state work being as part of the Joint Venture work. The scenario testing tool being developed by the EEWD project. Please see attachment.
Location
Victoria : Barwon South West : Gippsland : Grampians : Hume : Loddon Mallee : Melbourne
South Australia : Adelaide : Eyre & Western : Far North : Fleurieu & Kangaroo Island : Limestone Coast : Murray & Mallee : York & Mid North
Australian Capital Territory
