In InfoWorks WS Pro, the modelling of the water supply system is divided into two main parts:
The physical network is the static geometry of the system. The InfoWorks model of the network is made up of nodes (reservoirs, customer supply points) and links (pipes, valves, pumping stations). To model the network, the user will need to gather information about the real network and then identify the nodes and links for the model. See Networks for more information.
New networks are created within a model group. Or you can import networks from an external system.
A network is a version controlled item. See Managing version controlled objects.
If you are maintaining a network over a period of time, it can be updated with additional asset or other data stored in CSV files.
When you open a network it is initially displayed using a GeoPlan window. The GeoPlan shows the network in its geographical context. You can then view or edit the network objects that make up the network.
Networks can also be exported in a variety of formats.
See Networks and Managing version controlled objects for full details on working with networks.
Networks are made up of network objects. These are:
Full details about working with network objects can be found in the Network objects section.
There are several different ways of viewing and editing network information:
Every water supply system must have a control policy. In InfoWorks WS Pro the network geometry and control data are split into separate but very closely related items. The control data describes the initial state of the water supply network at the start of a simulation and the policy for controlling the network during the simulation.
This separation simplifies the modelling process. Multiple control data sets can be associated with the same network to model variations in operation. The same control data can be associated with more than one network so physical changes in the network can be modelled.
Control data is also a version controlled item. Creating is the same process but importing is different because data is needed from other sources. Control data does not require validation before being used in a simulation. See Managing version controlled objects.
Control data can be updated from external CSV files.
The major difference is opening control data for viewing and editing. Control data cannot be viewed on its own. It can only be viewed or edited in the context of a network. You have to associate the control data with a network. It will be displayed in parallel with the network on the same grid views and property sheets.
See Control data and Managing version controlled objects for full details on working with control data.
It is beyond the remit of this on-line help to describe the general approaches to model making. Some excellent pointers can be found in Chapter 6 of Obradovic et al (1998), entitled Making a Model.