STP stands for Scenario Tables Pool. The idea is, that all modelling results for resources and demands are stored in the STP, which is a part of the central ORACLE database. From there, the data are available for balancing.
Data are stored as monthly volumes in m³.
The STP contains both historic data and projected data. The months are counting from the start of the hydrological year: Month 1 means October. The years are the hydrological years, year 1998 would be year 1997/98, from October 1997 to September 1998.
Note: currently, each year in the STP tables contains 15 months, from October to December and again from January to December.
The projected data are for the years 2005, 2010, 2015, 2020, 2025, 2030, 2035 and 2040. As opposed to the irrigation module, different hydrological conditions are not applied in the pre-processing module.
According to the individual sub-modules, the following 6 STP tables are used by the pre-processing module:
A typical example for a STP Table is the Table STP_MUNICIPAL (only a very small selection of records is shown):
Please note, that the results for all locations (= SETT_ID ), scenarios (1, 2 or 3), months (1, 2 ... ) and years (both historical and projections) are stored in the same database table. Historical years have scenario 0. SALINITY indicates the salinity class.
The LOG_SESSION is needed to recall the parameters that were used to calculate that demand.