Customer Point Data Fields
Customer Points represent demand data that can be imported into the network. This demand can then be automatically allocated to appropriate nodes in the network using a set of rules. See Static Demand Allocation for more details on importing and allocating demand using customer points.
Information relating to customer points can be viewed and edited on the Customer Points Grid or on the Customer Point Property Sheet.
When Alternative Demand exists
for the object, additional pages are displayed on the property sheet.
Alternative Demand pages are marked 
.
Most data can be edited on the grid, but some fields cannot be displayed in the grid format. To view and edit all customer point data, use the property sheet.
The following table describes all the data that can be used to define a customer point.
Further information, including units details, about all the Network Object fields stored in the Master Database can be found in the data fields topics listed in the Network Data Fields topic.
Fields that are common to the majority of objects can be found in the Common Data Fields topic.
The Property Page column shows which page of the property sheet displays the data. The pages are:
-
Definition Page
-
Allocation Page
-
Demand Page
-
User Page - see Common Data Fields topic for details of user fields
-
Alternative
Demand Page
The Grid column shows if the data item is available for editing in the grid view.
Customer Point Data
Database Table Name: wn_address_point
|
Field Name |
Help Text |
Flag |
Grid |
Property Page |
Size |
Precision |
Database Field |
Default |
Error Lower Limit |
Error Upper Limit |
Warning Lower Limit |
Warning Upper Limit |
|||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Key |
A unique identifier for the Customer Point objects within the database. |
YES |
YES |
1 |
25 |
|
|
reference |
Text |
|
|
|
|
|
|||||||||||||||||||||
|
X |
X coordinate |
YES |
YES |
1 |
|
2 |
XY |
x |
Double |
|
|
|
|
|
|||||||||||||||||||||
|
Y |
Y coordinate |
YES |
YES |
1 |
|
2 |
XY |
y |
Double |
|
|
|
|
|
|||||||||||||||||||||
|
Elevation |
Elevation above datum of pipe invert. |
YES |
YES |
1 |
|
2 |
Z |
z |
Double |
|
-999 |
9999 |
|
|
|||||||||||||||||||||
|
Identifier |
For information. Any additional identifier you may have for the customer |
YES |
YES |
1 |
50 |
|
|
identifier |
Text |
|
|
|
|
|
|||||||||||||||||||||
|
Parent Key |
Parent Key |
YES |
YES |
1 |
50 |
|
|
parent_key |
Text |
|
|
|
|
|
|||||||||||||||||||||
|
Connection Point X |
The Connection Point X and Connection Point Y values describe the coordinates of the location at which the customer point is connected to the water distribution network. If these connection point fields are flagged as default (#D), the connection point coordinates will be calculated on allocation of customer point demand to the network. The coordinates of the connection point will be calculated as the nearest location (to the customer point) on the pipe to which the customer point is allocated. When allocating demand by use of the Demand Allocation Wizard, customer point demand can be allocated using connection point coordinates in preference to customer point coordinates. |
YES |
YES |
1 |
|
2 |
XY |
connection_point_x |
Double |
|
|
|
|
|
|||||||||||||||||||||
|
Connection Point Y |
See Connection Point X |
YES |
YES |
1 |
|
2 |
XY |
connection_point_y |
Double |
|
|
|
|
|
|||||||||||||||||||||
|
Category Type |
|
YES |
YES |
2 |
|
|
|
category_type |
Integer |
|
|
|
|
|
|||||||||||||||||||||
|
External Category |
You may have an external demand category name that does not match any of the categories in your Demand Diagram in InfoWorks. You can use this External Category name to map data onto InfoWorks demand categories during the import process on the Demand Allocation Wizard Special Review Page. |
YES |
YES |
2 |
30 |
|
|
external_category |
Text |
|
|
|
|
|
|||||||||||||||||||||
|
Demand Category |
The name of the InfoWorks Demand category |
YES |
YES |
2 |
30 |
|
|
category_id |
Text |
|
|
|
|
|
|||||||||||||||||||||
| Number of Equivalent Persons | The number of equivalent person associated with the customer point. See additional table below. | YES | YES | 2 | WN_QD | equivalent_persons | Double | ||||||||||||||||||||||||||||
|
Number Of Properties |
The number of properties associated with the customer point. See additional table below. |
YES |
YES |
3 |
|
|
|
no_of_properties |
|
|
0 |
|
|
|
|||||||||||||||||||||
|
Specific Consumption |
The daily consumption per property/person. See additional table below. |
YES |
YES |
3 |
|
2 |
WN_QD |
spec_consumption |
|
|
0 |
|
|
|
|||||||||||||||||||||
|
Average Demand |
The average demand per customer point. See additional table below. |
YES |
YES |
3 |
|
4 |
WN_DQ |
average_demand |
|
|
0 |
|
|
|
|||||||||||||||||||||
|
Direct Demand Factor |
A factor applied to a demand category created as Direct demand to adjust the demand category values. The factor will normally be 1.0. See additional table below. |
YES |
YES |
3 |
|
2 |
|
direct_demand |
|
|
0 |
|
|
|
|||||||||||||||||||||
|
Allocation Run |
The allocation run (using the Demand Allocation Wizard) that resulted in the current setting of the Allocated Pipe ID field |
YES |
YES |
3 |
|
|
|
allocation_run |
|
|
|
|
|
|
|||||||||||||||||||||
|
Allocated Pipe Id |
The pipe to which this point has been allocated after running the Demand Allocation Wizard. |
YES |
YES |
3 |
63 |
|
|
allocated_pipe_id |
Text |
|
|
|
|
|
|||||||||||||||||||||
|
Demand at From Node |
By default, InfoWorks allocates demand at the To node if the nodes at both ends of a link are available for allocation. Checking this box forces allocation at the From node if there is a choice |
YES |
YES |
3 |
|
|
|
demand_at_us_node |
Boolean |
|
|
|
|
|
|||||||||||||||||||||
|
Status |
The current status of the customer point with regard to allocation. The status field will be blank if the customer point has not yet been through the allocation process.
|
YES |
YES |
3 |
|
0 |
|
status |
Integer |
|
|
|
|
|
|||||||||||||||||||||
|
Saved |
This field indicates whether an address point has been allocated manually or by use of the Demand Allocation Wizard.
|
NO |
YES |
NO |
|
|
|
saved |
Boolean |
|
|
|
|
|
|||||||||||||||||||||
|
Key Customer |
Check this box to identify the customer point as a Key Customer. When importing data, if this field is blank, InfoWorks will generate a field name using the values in the X and Y fields. In order to ensure that points with generated keys do not overwrite existing points with the same key, use the Make Generated Keys Unique option on the Demand Allocation Wizard Acquisition Page. |
YES |
YES |
NO |
|
|
|
key_customer |
Boolean |
|
|
|
|
|
Demand falls into three basic types. Different values need to be included in the imported data depending on the demand type.
|
Average Demand |
Fill in the Average Demand box for the demand category. The Average Demand is the average consumption supplied over a time period to the customer point. |
|
Demand per Property |
Fill in the Specific Consumption and Number of Properties fields for the demand category. The Specific Consumption is the consumption defined as volume per property per day. This is multiplied by the Number of Properties to give total consumption per day |
|
Direct Demand |
Fill in the Direct Demand Factor box for the demand category. The Direct Demand Factor is a multiplier that is used to adjust the values in the demand category. The factor will normally be set to 1.0. 
Please Note
If the value is zero or blank, no direct demand will be applied. |
If the Number of Properties field is blank or zero, the value set for either Direct Demand. or Average Demand will be used. If the Number of Properties is non-zero, the Demand per Property value will be used.
Alternative Demand Page
Database Table Name: wn_alt_customer_demand
|
Field Name |
Help Text |
Flag |
Grid |
Property Page |
Size |
Precision |
Required |
Database Field |
Default |
Error Lower Limit |
Error Upper Limit |
Warning Lower Limit |
Warning Upper Limit |
|||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Key |
A unique identifier for the Customer Point object |
YES |
YES |
|
25 |
|
NO |
|
reference |
Text |
|
|
|
|
|
|||||||||||||||
|
Category Type |
|
YES |
YES |
|
|
|
NO |
|
category_type |
Integer |
|
|
|
|
|
|||||||||||||||
|
External Category |
You may have an external demand category name that does not match any of the categories in your Demand Diagram in InfoWorks. You can use this External Category name to map data onto InfoWorks demand categories during the import process on the Demand Allocation Wizard Special Review Page. |
YES |
YES |
|
30 |
|
NO |
|
external_category |
Text |
|
|
|
|
|
|||||||||||||||
|
Demand Category |
The name of the InfoWorks Demand category |
YES |
YES |
|
30 |
|
NO |
|
category_id |
Text |
|
|
|
|
|
|||||||||||||||
| Number of Equivalent Persons | The number of equivalent person associated with the customer point. See additional table below. | YES | YES | NO | WN_QD | equivalent_persons | Double | |||||||||||||||||||||||
|
Number Of Properties |
The number of properties associated with the customer point. See additional table below. |
YES |
YES |
|
|
|
NO |
|
no_of_properties |
|
|
0 |
|
|
|
|||||||||||||||
|
Specific Consumption |
The daily consumption per property. See additional table below. |
YES |
YES |
|
|
2 |
NO |
WN_QD |
spec_consumption |
|
|
0 |
|
|
|
|||||||||||||||
|
Average Demand |
The average demand per customer point. See additional table below. |
YES |
YES |
|
|
4 |
NO |
WN_DQ |
average_demand |
|
|
0 |
|
|
|
|||||||||||||||
|
Direct Demand Factor |
A factor applied to a demand category created as Direct demand to adjust the demand category values. The factor will normally be 1.0. See additional table below. |
YES |
YES |
|
|
2 |
NO |
|
direct_demand |
|
|
0 |
|
|
|
Customer Point Results
All results fields are displayed on a special results page placed at the front of the property sheet if the sheet is started while viewing a simulation replay.
You can also view these results on graphs or grids for individual customer points. See Graphing Data for a Network Object and Grid Results for a Network Object.
|
Results Field |
Description |
Time Varying |
|---|---|---|
|
Head |
The head at the customer point is calculated from the head at the node, taking into account the elevation of the customer point. There is assumed to be no headloss on the customer connection.
Please Note
If there is no elevation on the customer point, any results are calculated based on the elevation of the attached node. |
YES |
|
Pressure |
Pressure at the customer point |
YES |
|
FFA Residual Pressure |
Residual pressure at the customer point after fire flow is taken into account. Fire Flow Availability simulations only. |
YES |
|
Average Pressure |
Average pressure at the customer point over the length of the simulation |
NO |
|
Maximum Pressure |
Maximum pressure at the customer point over the length of the simulation |
NO |
|
Minimum Pressure |
Minimum pressure at the customer point over the length of the simulation |
NO |
