Scratch file - Osd4.com

15 February 2008

OSD4W ON-SITE STORMWATER DETENTION SYSTEM DESIGNER For Windows

USER GUIDE Program version 1.07.3 Userguide revised 15/02/08

Boffinz.com Pty Ltd trading as ..... Bowditch Group

VERSION 1.07.3 OSD4W and this user guide are works in progress. Version 1.06.5 was issued as a “pre-release” version to some new users to allow their installations to be updated seamlessly to version 1.07 – see note below. Version 1.07.3 provides the full utility of earlier versions but provides some user friendly enhancements and additional features. New features include: PSD and storage volume calculations make provision for the runoff from portions of the site to be: - captured 100% (C=1.0) - uncontrolled (C=0) the session file (osd4w.ini) is now written to the user‟s „home folder‟ - the file is now user accessable even if the program‟s „.exe‟ file is stored on a remote drive users can choose to use multiple folders of their choice to store and retrieve jobfiles and jobnotes the contents of the Notesbox may be saved as a text file to any user selected folder a text file may be retrieved from any folder and displayed in the Notesbox users may customise the field name labels displayed in the Job Details form - the revised labels are: - saved in the „user folder‟ as a file named JobLabels.txt - are recalled at program startup - replace the default labels when reports are generated reports may now be printed to any print destination known to the user‟s computer Users of OSD4 and OSD4W should be able to run the current release of OSD4W intuitively. New users may need to refer to portions of this userguide and the help buttons and notes that are provided on some screens. See Appendix A of this userguide for more information about new features. IF YOU ARE UPGRADING FROM AN EARLIER VERSION OF OSD4W 1. Users of versions 1.05.2 or earlier will need to relocate their userkey file – see installation procedures. 2. The format of the userkey file was changed in February 2008. Updated copies of OSD4W may require an updated userkey. These are issued free upon request.

3. The format of the jobfile has been expanded to allow the additional site data to be saved for later recall. Version 1.07 can read jobfiles written by earlier versions of OSD4W DEMONSTRATION MODE All versions of OSD4W will run in demonstration mode if a valid userkey file cannot be found - see „Delivery‟ on page 5 for more information. The demonstration version is the full product with two exceptions – it is unregistered and it includes a substitute file for zone data. The zones file included in the demonstration version includes data for three fictional zones that are identified as NORTH, MIDDLE and SOUTH. These could be very loosely identified as localities that are somewhere in southern Queensland, somewhere in central New South Wales and somewhere in southern Victoria. Output generated by the demonstration version is similarly fictional and must not be adopted for real world design projects. OSD4W „knows‟ the details of the zone-ARI data sets included in DemoZones.txt. If the demonstration zone file is missing or corrupted or the coefficients have been edited, OSD4W will not calculate the PSD or storage volume. It is possible that some other functions may be disabled. The display flags may be edited in DemoZones.txt to demonstrate the zone display features. In general, the installation notes in the body of this user guide refer to the licensed program. If separate installation notes may be issued for the demonstration version, they will be provided as a text file. KNOWN ISSUES No issues have been reported for earlier version. We wish to thank users who submitted „wish list‟ items. Some of these have been included in version 1.07.3.

OSD4W was written by Bruce Bowditch and is distributed and supported by: BOWDITCH GROUP 1 Buckingham Ave Bentleigh 3204 Contact Bruce Bowditch if you would like to discuss OSD4W, the MC2 MultiCell flow control device or any aspect of OSD theory and application: Office 03 9557 7183 (Phone/Fax) Mobile 0407 955 744 Email [email protected] Please note: 1. 2.

Fax facilities may be switched off for extended periods (because the voice mail facility trashes faxes) Mobile phone facilities may also be switched off for extended periods

The preferred options are: 1. Attach scanned documents to emails – this option is always available. 2. If you need to send a fax, phone beforehand to ensure that fax facilities will be available.

SCOPE The OSD4W USER GUIDE is designed to acquaint users with the basic operation of the software. It is assumed that users have a basic understanding of the Swinburne OSD Methodology. This user guide does not attempt to familiarise users with the Swinburne Methodology. Copies of the One-day OSD Workshop Notes may be accessed at: http://www.swinburne.edu.au/corporate/knowledge/ventures/licences.htm The download link is embedded in the text on the last line of the page: look for ….. Dr D I Phillips and Bruce W Bowditch The programmer is prepared to discuss all aspects of OSD4W and the Swinburne methodology. LIABILITY LIMITATION The author and the program distributors will not be liable for any claims beyond the value of the original license fee. In no event will the author or the distributors be liable for additional damages including but not limited to any loss of profits or savings or other consequential or incidental damages arising out of the use or the inability to use this program even if they have been advised of the possibility of such damages or claims. WARRANTY The author warrants that the program substantially conforms to the specification in the associated user documentation and the order leaflet. The exclusive remedy of the Customer and the sole obligation of the author and the supplier under this warranty shall be for the author to use reasonable efforts to remedy any failure to so conform to such specifications which is reported in writing to the supplier within 90 days from the date of dispatch of the software program or at the author's sole election to refund the licence fee paid by the customer. Any refund will only be made after the Customer has been notified of the decision to refund the fee and the Customer returns the software and the documentation or destroys same if so agreed with the distributor and in addition provides a written undertaking, in a form that the distributor has advised as being acceptable to the distributor, to refrain from using the software for commercial or any other purposes. The licence to use the software will be cancelled upon the completion of this exchange. NON-ACCEPTANCE OF LICENCE CONDITIONS IF THE LIABILITY, WARRANTY OR USER LICENCE PROVISIONS ARE UNACCEPTABLE TO THE USER, THE PRODUCT SHOULD BE RETURNED TO THE DISTRIBUTOR WITHIN 7 DAYS OF RECEIPT. THE PURCHASE PRICE WILL BE REFUNDED IN FULL AND ALL LICENCE AGREEMENTS WILL BE CANCELLED. The specification for OSD4W is subject to change without notice.

WHY OSD4 The OSD4 project was commenced because the author did not feel comfortable with some aspects of the OSD software packages that were available in 1993. These packages were not user friendly or were based upon superseded or incorrectly interpreted OSD theory. There was a need to provide hydraulic designers and controlling authorities with a comprehensive, fast and convenient OSD design and reporting tool which was based upon up-to-date technology. OSD4 was designed and written by a single author with a view to satisfying those needs.

WHY OSD4W To permit expansion of the program‟s feature set Microsoft announced that Vista would not support 16-bit programs WHO OSD4 solved the equations developed for the Swinburne methodology by: Dr. Donald I. Phillips Senior Lecturer, Water Engineering Swinburne University of Technology OSD4 and OSD4W were written by: Bruce W. Bowditch B.E.(Civil) ACKNOWLEDGEMENTS: The hydrograph and stepped head logos were designed by Bruce Bowditch. They are the copyright of S.V.C Products and are reproduced with its permission. S.V.C is the sole Victorian manufacturer of the flow control device known as the MULTI-CELL and is licensed to distribute MULTI-CELL products to all Australian States. The MULTI-CELL device was invented by Dr. Donald I. Phillips - Australian and U.S. patents have been granted. The patent describes two versions of the Multi-Cell device. The sealed version can handle relatively high heads. The commercial expression of the sealed version was developed by Bruce Bowditch and is known as the MC2. Manufacture commenced in 1993 and field experience has demonstrated that it is the only commercially available product that provides blockage-free control of discharges from redeveloped residential sites.

ABOUT THE AUTHOR Bruce Bowditch purchased his first microcomputer in 1979. Since then, he has gained considerable experience with a wide range of business and technical packages including the beta testing of high-end CAD, database and payroll products. He has also written many utilities for business and personal use. These day to day hands-on experiences have made him very aware of the need for programs to be functional and user friendly. He has also been a member of a number of user groups and was the founding president, convenor and contributing editor for a national CAD user group. Bruce believes that support is a two way street and that the utility of most programs is a function of the feedback provided by the users - every question builds the knowledgebase. This source of ideas always ceases to flow when programmers do not support their users. Bruce joined the precasting operations of the S.V.C Group of Companies in 1959. He subsequently became deeply involved in all aspects of the group's activities including design, estimating, research, production of prestressed and reinforced concrete structural and architectural elements, IR and IT. In the early 1980s Bruce became Managing Director of the Group. He retired in July 2001 but continues as a Director. Bruce convened the first meeting of Stormwater Industry Association of Victoria and was subsequently elected as the founding Secretary. He retired from that position after completing three terms but continues as a Committee member of SIA Victoria and as a Director of Stormwater Industry Association Ltd.

Introduction OSD4 was released in 1993 as the sole user friendly program that supported the Swinburne OSD Methodology. In particular, OSD4 solved the OSD equations developed by Dr Don Phillips of Swinburne University. Some of the Phillips Equations for flow (PSD) could only be solved by iteration. Irrespective of the storage system adopted, the calculation of minimum storage volumes could only be established by iteration. OSD designers were spending hours solving problems that OSD4 resolved in a similar number of seconds. Because it was uniquely focussed on the Swinburne Methodology, OSD4 provided a tool that was equally usable by OSD designers and municipal engineers. Being a program of its time, OSD4 was a DOS program that could also operate in a window (full screen or otherwise) in a MS Windows environment. It was tweaked from time to time but, apart from the introduction of printers that accommodated USB ports, it retained its status of an up-to-date program. The introduction of USB ports was a non-event because OSD4 already had a „print reports to file‟ facility that provided a simple workaround. When Microsoft announced the imminent release of their Vista operating system, they declared that it would not support programs designed for 16-bit environments. That meant that OSD4 would not run under Vista. OSD4W is written in Borland Delphi Studio 2006 for the WIN32 environment. It will run under Vista. OSD4W continues the user friendly tradition established by OSD4. This tradition dictates that system and program crashes and hang-ups are not acceptable. This can only be achieved if all input variables are primed with valid data and all user input is monitored and validated. If a user attempts to enter invalid data, OSD4W will reject it.

Windows Registry OSD4W is a stand-alone program. It does not seek to access the Windows registry and OSD4W and its subfolders may be relocated at the user‟s discretion at any time – just make sure you edit your shortcuts accordingly. Stand-alone programs are also identified in computer literature as “Portable applications”.

Delivery The program is currently delivered by 2 emails with attachments. Email 1 delivers the program as a zip file complete with all files and folders apart from two important working files – the rainfall zones data file (zones.txt) and the registration key file (W7-?????.osd). The inclusion of DemoZones.txt provides data sets for some fictional rainfall zones and enables the program to be run in full demonstration mode. Email 2 delivers the registration key and zones.txt. OSD4W looks for the registration key file at startup, confirms that the installation is registered and extracts the registrant's details. Zones.txt provides real world data for a number of localities.

Installation of Registered and Demonstration Copies of OSD4W 1.

Create a folder at a suitable location of your choice and name it osd4w – that name is convenient but it is not mandatory. Given that the distribution zip file identifies the version and that OSD4W is a portable application, the „home directory could be named „osd4w1073‟.

2.

Unzip the Email 1 distribution file into this new folder. NOTE: When you unzip the distribution file, elect to create all sub-folders included in the zip file. e.g. For Winzip, this requires the "Use folder names" box to be checked. If you don't create the sub-folders, all files will be extracted to a single folder and the program will not be able to find some of the components.

3.

The standard folder structure is shown adjacent.

4.

Two folders are particularly important. a.

The „osd4w‟ folder contains one principal file - the „.exe‟ program file - but it may contain two additional files. The name of the program file, as distributed, reflects the version number. The program file distributed for version 1.07.3 is named osd4w1073.exe. The OSD4W folder may also contain files named folders.txt and osd4w.ini. The function of folders.txt is explained by the contents of that file but feel free to contact the programmer if you need further information. The „.ini‟ is simply a record of the

settings of the session that were current when the program was last shut down. This „last session file‟ may be recalled by the user. OSD4W will run normally if either or both of these files are missing. b.

5.

The „user‟ folder will usually contain a copy of demoZones.txt – but registered users will need to copy zones.txt from Email 2 to this folder – see step 5 below – otherwise, the program will run in demonstration mode. The structure of the zones files are indicated in the picture of Screen 4 shown later in this user guide. The folder may also contain two user configuration files – preferences.osd and JobLabels.txt. If these files are missing, the program will adopt some default settings.

Copy your registration key file from Email 2 to the user folder and rename it ‘user.osd’. OSD4W looks for this file at startup. If it is not found, the program will start in a demonstration mode. If the program is running in demonstration mode it will look for DemoZones.txt. If that file is not found or has been edited by the user, the Calculation button will be disabled. NOTE: Some earlier versions of OSD4W required the user.osd file to be located in the same folder as the application file - osd4w1073.exe.

6.

A number of readme and miscellaneous files may be found in the other folders. The „hold‟ and „archive‟ folders have been included to encourage users to move older files out of their working folders.

7.

Installation is complete. HINT: Click the Preferences button on Screen 2 as soon as possible to establish some „permanent‟ settings - e.g. You may have purchased an OSD4W licence through company XYZ Associates P/L but your clients and the controlling authorities may know you by a more personable business name You may also want to changes some of the report labels to suit your office practice - Click the Job Details button on Screen 2 and read the notes dislayed on Screen 6

Entering Data These notes are IMPORTANT - they apply to most of the OSD4W screens. User friendliness requires that invalid input is not accepted. If invalid input were accepted, the outcomes would be uncontrolled - invalid outputs and system crashes could be expected. OSD4W collects the user‟s input as text and, where appropriate, converts the entries to the variable types that the program requires to develop valid outcomes. Most of the conversions are from text to integer or floating point numeric variables. For example, if the user intended to enter an area as „1000‟ but hit an adjacent top row key and entered „100-‟, OSD4W would discard the non-numeric key and interpret the entry as 100. BUT MORE: – OSD4W requires the user to confirm that their entries are complete by hitting the ENTER key. Fields requiring ENTER KEY confirmation are identified on most screens by blue captions. The fields on Screen 3 are a little more difficult to identify but almost all of them require the ENTER KEY to be pressed to complete the data entry for any field – see the blue note on that screen. On some screens, a red message is displayed when OSD4W detects that a field has been edited. This message disappears when the ENTER key is hit. If OSD4W detects an invalid entry or is waiting for the user to edit an entry field, it will generally substitute a valid entry. As an example of the latter, toggle the „Calculate PSD‟ and „Nominate PSD‟ radio buttons on Screen 2 and observe the changes in the PSD Calc. And PSD Nom. fields. Substituted values are placeholders. In particular, the substitution ensures that „divide by zero‟ and other calculation errors do not occur. In some instances, if an edited entry has not been confirmed, the entry will revert to its prior value when the cursor is moved away from the edit field. If additional characters are entered after the mouse had been moved away, the reversion may be seen if the mouse is moved across the edit field. This behaviour may not be consistent from screen to screen.

Getting Started Having installed OSD4W, create a shortcut to the „.exe‟ file in any convenient location and hit it.

Screen 1 – The Opening Screen

From top to bottom, left hand side first, the screen elements are: 1.

The name and version of the program.

2.

The name of the licensee and the serial number of the licence.

3.

RELEASE NOTES button

4.

Commercial identifications – who can do without them?

5.

CONTINUE button – let‟s get on with it!

6.

WISH LIST button – here is your chance to fire up the programmer

7.

ABOUT button – the contents are brief

8.

EXIT button – did you say “let‟s get out of here” ?

Screen 2 – The Design Screen - the OSD business centre

Even though there are only a few opportunities to enter data on the Design Screen, it really is the business centre of OSD4W. Data Entry Fields Tc – min

Time of concentration of the catchment in minutes.

Tso – min Travel time from the site outlet to the catchment outlet in minutes. This parameter was established by Bowditch. In his derivations of the Swinburne method, Phillips was concerned with „Tcs‟ which he defined as the travel time from the head of the catchment to the site outlet. This did not present problems with lenticular catchments (think – shaped like a bay leaf) but presented some confusion when the catchment was shaped like a liquidamber leaf and the site was located on one of the minor branches. Tso is the travel time from the „site outlet‟ to the „catchment outlet‟. Tc = Tcs + Tso. PSD NOM – L/s the Nominated PSD The Swinburne Method seeks to establish the maximum site discharge that can be tolerated without increasing the peak catchment discharge. Phillips identified this discharge as the Permissible Site Discharge (PSD). Circumstances arise that enable or require the PSD to be nominated rather than calculated. The most frequent example we are aware of concerns existing reaches which have limited capacity. Examples include „private drains‟ through neighbouring properties that cannot be upgraded (the „new owners‟ of the downstream property just say NO to any request to upgrade the drain even though your client‟s are very willing to meet all expenses and pay „compensation‟). On the other hand, proposed enhancements for downstream infrastructure or the

implementation of a stormwater harvesting facility may allow a higher PSD to be nominated. The „PSD Nom‟ field is only available when the appropriate radio button in the “OSD System Details” group has been hit. The field is disabled when you elect to calculate the PSD. The font style and colour of the PSD Calc. And PSD Nom. Buttons is determined by the state of the radio buttons in the OSD System Details section. JobFile/JobNotes Filename The text entered in this field forms part of the file name of “Job Files” and “Job Notes” files. Job Files record the data entered by the user – the file name is filename.osd. Job Notes save the contents of the Notes Box to a text file – the file name is filename.txt. By default, these files are saved in the Jobfiles folder when either of the nearby save buttons are clicked. If the filename is not changed, a warning message is displayed. Click the File Menu button for user selected save/load folder options.

Other Selection Options on Screen 2 The fields identified as “Zone-ARI Flow”, “Zone-ARI Store” and “Storage Type” are provided with drop-down selection boxes. Click the down arrow in the right of the box, then scroll through the drop-down list and click your selection to complete your entry for this field. The Zone-ARI selection options may vary from session to session: - more zones may have been added to the file – or some may have been deleted - the „Load All Zones‟ option may have been chosen - the file may have been rearranged by the user The consequence is that when „job files‟ or the „last session‟ file are recovered, there is no guarantee that the Zone/ARI pairs will be in the same position in the drop-down boxes. Solely for these reasons, OSD4W requires the user to reselect some items. The “Storage Type” entries coincide with the three options provided by the Phillips Equations. The Zone-ARI options are selected from a file named zones.txt. Click the “Show All Zones” button for more information. Navigation and Work Buttons The function of most of these buttons is generally self-evident. Click any one to have a look at the possibilities then click the “Back” button to return to Screen 2. Load All Zones The Zone-ARI buttons generally offer a sub-set of the data held in zones.txt – the Zone/ARI records where the display flag is set to „Y‟. This button makes all zones available for the current session. The limited set will be offered when OSD4W is exited and restarted. Show All Zones All available zones will be displayed but this is just a „viewing‟ option. Zones flagged „N‟ will not be available for selection unless zones.txt is edited or the „Load All Zones‟ button is hit. Calculate Hitting this button will cause the PSD, storage volumes and other outcomes to be generated. If the input data set is invalid or incomplete, this button will be disabled – it will be „greyed out‟. Save Jobfile, Load JobFile After you click the Calculate button, it is worthwhile saving the input data for later recall. Set the „Job and Notes Filename‟ field accordingly. You may save a number of jobfiles as templates that carry the customary entries for a variety of municipalities. Click the File Menu button more flexible save/load options. Report Menu You can print or file a report. The filename will be based upon the entry in the „Job and Notes Filename‟ field. Remember – hit the ENTER key to confirm every entry that you edit. Data Output Fields The outcome of calculations is displayed in the Flow Calculation and Storage Calculations fields located in the top-right portion of the screen. Site Details Click the Site Details button to access Screen 3.

Screen 3 – Site Details Enter the site characteristics at this screen.

Areas Enter area data downwards from the top of the screen. Enter the total area and hit the ENTER key - the first „Existing‟ and „Proposed‟ sub-areas will be populated automatically – all other sub-areas will be set to zero. Enter a decimal fraction or an area in either sub-area 1 and sub-area 2 will be populated. And so on. Prompts identify problems. The Calculations button on Screen 2 will be disabled if you exit this screen before problems are corrected. You can return to this screen to correct problems. Run-off coefficients Just enter the appropriate coefficients against the sub-areas. Remember – hit the ENTER key to confirm every entry that you edit. New to version 1.07.3 – Uncontrolled & Captured Runoff OSD4W enables user to specify that the runoff from portions of the will be captured 100% or uncontrolled. The notional runoff coefficients adopted for these options are 0.0 and 1.0 respectively. The algorithms for PSD and storage volume calculations have been adjusted to accommodate these new options. See Appendix A for Partial Site Control and Appendix B for 100% Capture.

Screen 4 – Zone Data Click the Show All Zones button on Screen 2 to access this screen.

The Zones File – zones.txt OSD4W expects to find this user-maintained file in the „user‟ folder. (When running in demonstration mode, OSD4W expects to find demozones.txt.) The current working version of zones.txt holds data for more than 560 zone/ARI combinations. Scrolling through all of these zone options on Screen 2 will probably be inconvenient. -

The number of files displayed in the drop-down selection boxes on Screen 2 can be reduced by setting the display flag of irrelevant entries to „N‟ Note: If a designer only works with sites in one rainfall zone, all other rainfall zones will be irrelevant.

-

The most frequently accessed entries may be duplicated at the head of the file. OSD4W is not disturbed by duplicated or unsorted entries. It builds the display arrays when Screen 2 is loaded and leaves it to the user to find what they are looking for in their user-maintained file when they hit the down arrow for the dropdown selection boxes.

-

If you only design projects for one municipality and the same ARI is specified for flow and storage calculations, place two copies of the relevant data line at the head of zones.txt. HINT 1

The original or master copy of zones.txt may be copied to the „hold‟ folder and a subset may be copied to the user folder as the working copy of zones.txt file. If you only design projects for one rainfall zone, you may only need 1 or 2 entries in zones.txt. If you only design for 5 rainfall zones, you will probably need less than 10 entries.

HINT 2

Set the display flag for all irrelevant zones to „N‟. You can always hit the „Load All Zones‟ button on Screen 2 to make the other zones temporarily available at any time.

NOTE OSD4 users will be familiar with a file named zones.idc. Zones.txt provides an identical function but adopts a different construction. The fields in zones.idc were „space delimited‟ whereas zones.txt is a „comma separated values‟ (csv) file. The zone field in zones.idc was limited to 10 characters and could not include spaces. This lead to some awkward abbreviations. Zones.txt also provides for a

display flag and a trailing text field that may refer to any relevant item e.g. clauses or tables in regulations. CAUTION - Rainfall Coefficients The rainfall coefficients included in the „zones.txt‟ file have been derived from BoM data sheets, ARR87 charts, other publications, OSD4 and OSD4W users and a variety of other sources. The file is offered in good faith but the contents are not guaranteed. Users should check a range of calculated intensities against the rainfall tables published for the localities they are working in. Please send an email to [email protected] if you discover any significant problems. If you have a set of coefficients for a zone not included in zones.txt – please send a copy to [email protected] Your data will be incorporated into zones.txt and you will receive a copy of the updated file.

Screen 5 – Preferences Click the Preferences button on Screen 2 to access this form.

OSD4W will look for a file named preferences.osd in the user folder at startup. If the file does not exist, the program loads a default set of values.\ The preference file records data that the users prefers to include consistently in reports. This screen should be accessed at an early time. The saved data will not be accessible until OSD4W is restarted.

Screen 6 – Job and Client Details Click the Job Details button on Screen 2 to access this form

In general, the data entered on this screen is job specific and is saved when a Jobfile‟ is saved - click the Save Jobfile button on Screen 2; or - click the File Menu button on Screen 2 to open Screen 9. The entries in the Job Reference and Job Name fields are echoed to Screen 2 but cannot be edited at that screen. New to version 1.07.3 – Edit Field Names Users may customise the field name labels displayed in the Job Details form. The revised labels are held in a file named JobLabels.txt which is saved in the user folder. The customised labels are recalled at program startup and are used in reports.

OSD4W will use a default set of labels if JobLabels.txt cannot be found.

Screen 7 – Reports Access this screen by clicking the Report Menu button on Screen 2.

The Reports screen enables the user to generate reports to accompany submissions. Click the Print Report button to print a report on your system printer. Click File Report to save an identical set of data to a reports file in the jobfiles folder. Both options expect that non-proportional fonts will be used for printing and display. If your default settings are for proportional fonts such as Times New Roman, the columnar alignment of the output will be inconsistent. In version 1.06.5, report printing and filing will be inhibited if the checkbox labelled Uncontrolled adjacent to Sub-area 4 is checked. A suitable message will be displayed. New to version 1.07.3 – Edit Field Names

Screen 9 – File Activity Access this screen by clicking the File Menu button on Screen 2.

Version 1.07.3 (rev 1) allows users to use additional folders to store files. If OSD4W offers a default file name for a selected File Type, it will be displayed above the group of radio buttons. The filename for Job Files and Job Notes entered in the JobFile/JobNotes Filename field on the previous screen is adopted as the initial filename. The filename may be edited on this screen. Press the ENTER key after editing the input field. The choices offered by the Activity and Folder set of radio buttons may be restricted for some File Types. All options that are temporarily unavailable are greyed out. When a JobFile is opened, data previously saved by the user will be retrieved and loaded into the relevant fields on the Design and Site Details screens and any fields that display program generated data will be cleared. The word Select will be displayed against the Zone-ARI Flow, Zone-ARI Store and Storage Type fields of the Design Screen. The Calculate button will not be enabled until these three fields have been confirmed and/or edited.

Appendix A Partial Site Control - Swinburne Method - OSD4W Controlling the discharge from the whole site may be very difficult on steep or stepped sites. In some cases, it may be feasible and economical to allow uncontrolled discharge from portion of the site. The Swinburne Method will be satisfied provided the site discharge at time Tcs from the onset of the storm event does not exceed Qp, the benchmark discharge. (We also describe this discharge as “the benchmark Qp,Tcs discharge”. That‟s because of the focus placed on flow rates. Using Cartesian coordinates, this benchmark discharge is usually plotted as Tcs,Qp.) The Swinburne Methodology requires the site outflow hydrograph to pass through or below the benchmark coordinate. (Bowditch introduced the Tso variable in 1993 to avoid some conceptual difficulties presented by branched catchments. Tcs = Tc - Tso) Version 1.07.0 of OSD4W fully implements the proposed Partial Site Control feature. Users of previous versions will note the additional fields and controls added to Site Details (3) screen. The formats used for jobfiles and „.ini‟ files needed to be changed to accommodate the additional variables used for the Partial Site Control feature. The Save Jobfile, Load Jobfile and startup routines were rewritten: to accommodate to accommodate the various file formats appropriately. Entering Data for Partial Site Control Version 1.07.x employs a simpler implementation than proposed in version 1.06.x. Element 4 of the proposed site details may be used to enter aggregated data for portions of the site that will not be controlled by the OSD installation. Enter the total uncontrolled area and the associated weighted runoff coefficient then check the adjacent “Uncontrolled” checkbox. The details are presented when you click the “Help – Uncontrolled sub-areas” button If a number of small elements will be uncontrolled, the user can use the facilities offered by the Site Details screen to calculate a weighted runoff coefficient. Just enter the sub-areas and associated runoff coefficients and note the calculated output. An example of data entry for partial site control follows.

Screen 3 – Site Details – version 1.07.0

The checkbox labelled „Uncontrolled‟ has been added to the Site Details screen. Three additional display items have been arranged below the checkbox. The last of these will be used to display the weighted fraction of the existing site configuration that will be uncontrolled. Let‟s assume that the total site area is 5000 sq.M and that 1000 sq.M will be uncontrolled. If we enter the total site area as 1000 sq.M and also assume that the uncontrolled area is split 750/250 as shown above, the weighted coefficient for that uncontrolled area is 0.75 – as shown at the bottom of the Proposed Site Elements group. Note these for later entry as ……. Sub-area 4 = 1000 sq.M …… Coefficient4 = 0.75 Now proceed to enter the total area and sub-element details of the site and click the „Uncontrolled‟ checkbox.

Sample data is displayed in the screenshot above. The fraction of the total runoff that will not be controlled, UP fraction, is calculated as: (1000x0.750) / (5000x0.420) = 0.357 Click the “Help – Uncontrolled sub-areas” to see more updated text.

Appendix B 100% Capture Stormwater has been traditionally viewed as a nuisance in urban precincts and its management has focused upon conveyance. In some circles, the mantra of best practice was “pass it downstream as quickly as possible”. As a direct consequence of recent climatic experiences, many more Australians now view stormwater as an asset and are motivated to harvest it. From an OSD perspective, harvesting stormwater helps to offset the extra loads that are placed upon infrastructure as a consequence of increased urban densities. OSD4W version 1.07.0 makes provision for 100% capture from portions of the site. The runoff coefficients for proposed sub-areas 3 and 4 will now accept an entry of zero. Click the “Help – 100% runoff” button on the Site Details screen for some additional comments.

Screen 2 – The Design Screen - the business centre – version 1.06.5 Data entry is now complete so we can simply the “Calculate” button to determine the PSD and the required storage volume.

The above screen has been calculated on the basis of the data entered and UP fract = 0.357. The Swinburne Method includes a variable identified as Qp. This is the discharge from the site that is included in the peak catchment discharge. For version 1.07.0 this parameter is identified as Qptot – the total contributed by the controlled and uncontrolled portions of the site. Qu is the contribution from the uncontrolled portion of the site and Qp is a the contribution from the balance of the site. Qu= (UP fraction)xQptot and Qp=Qptot-Qu For this example, Qptot, Qu and Qp are 38.77, 13.85 and 24.92 L/s respectively. The PSD and the required storage volume is calculated on the basis of Qp=24.92 L/s. If the total site area was controlled, the PSD would be much higher and the storage volume much lower than the values displayed in the screenshot.

Appendix C Rainfall Data File – zones.txt An extract from zones.txt is shown below. Each record is a single line of data arranged as eleven fields separated by commas. Similar data may be viewed when OSD4W is running by clicking the “Show All Zones” button on the Design Screen. The subsequent display is spread by inserting spaces and each record is preceded by the record or line number. The file is an ASCII file that may be edited with Notepad or any other “plain text” editor of your choice. Data for additional rainfall zones may be added. The first field is the name of the rainfall zone, the second is the ARI in years, and the next seven fields are the coefficients of the intensity/duration equation in power sequence. The display flag follows – if the flag is set to “N”, that record is not loaded by default when OSD4W starts to run. The last field in a zones.txt record is a free text field. As distributed, it echoes the zone name. It could be used to record information about the record e.g. the table number of the source reference. MELBOURNE,5,3.1953,-0.6283,-0.0388,0.01046,0.000477,-0.0001623,-0.0000263,Y,MELBOURNE MELBOURNE,10,3.3475,-0.63,-0.0432,0.00881,0.001072,-0.0000116,-0.0000694,Y,MELBOURNE ALEXANDRA,1,2.7484,-0.6265,-0.0357,0.0118,0.00012,-0.00032,0.0000079,N,ALEXANDRA ALEXANDRA,2,2.9915,-0.6275,-0.0353,0.01265,-0.00002,-0.0004001,0.0000261,N,ALEXANDRA ALEXANDRA,5,3.2325,-0.6266,-0.0348,0.01245,-0.000024,-0.0003765,0.0000214,N,ALEXANDRA ALEXANDRA,10,3.3584,-0.6268,-0.0345,0.01295,-0.000066,-0.0004333,0.0000283,N,ALEXANDRA ALEXANDRA,20,3.4902,-0.6267,-0.034,0.01309,-0.000139,-0.0004444,0.0000325,N,ALEXANDRA ALEXANDRA,50,3.637,-0.6261,-0.0337,0.01294,-0.000175,-0.0004327,0.000031,N,ALEXANDRA ALEXANDRA,100,3.7369,-0.6264,-0.0336,0.01337,-0.000191,-0.0004894,0.0000413,N,ALEXANDRA ALTONA,1,2.5972,-0.6195,-0.0428,0.00791,0.001617,-0.0002033,-0.0000493,Y,ALTONA ALTONA,2,2.8799,-0.6246,-0.0413,0.00845,0.001362,-0.0002538,-0.0000327,Y,ALTONA ALTONA,5,3.188,-0.6338,-0.0416,0.00713,0.001727,-0.0000793,0.0000744,Y,ALTONA ALTONA,10,3.3527,-0.6408,-0.04,0.00764,0.001474,-0.0001137,-0.0000608,Y,ALTONA

Calculating the Rainfall Intensity – the Intensity/Duration Equation The following equation enables the average rainfall intensity for any storm to be calculated. 2

3

4

5

ln(I) = A + B(ln(T)) + C(ln(T)) + D(ln(T)) + E(ln(T)) + F(ln(T)) + G(ln(T))

6

where I is the average rainfall intensity in mm/hr, T is the storm duration in hours, ln(I) is the natural log of the intensity and ln(T) is the natural log of the duration. At startup, OSD4W scans the file and builds an array that is made available to the user when populating the Zone-ARI Flow and Zone-ARI Storage fields on Screen 2. The order in which the records appear is optional because the user may traverse all data when populating these fields. If you only use a few zones or ARIs, placing copies of them at the head of the file will ensure that they are the first to be found. Duplicating selected entries leaves the bulk of the file in its original form. Any records with the display flag set to “N” will be ignored when the array is populated at runtime. The array may be rebuilt to include all records during runtime by Clicking the Load All Zones button. Users are requested to send copies of new zone data to the author.

Suggestions 1.

Hit the Wish List button on the opening screen

2.

Programmers think they know what users need but:

Users needs are established progressively as software products are used meaningfully.