EDAMS Network Assets Management
Frequently Asked Questions
July 2010
To transfer NAM data using the Merge Utility follow the steps below:
1)
Restore the supplied
[WUC_Blank_MSSQL_Database_4304.35.rar]
MS SQL database using DB Manager. (Target Database).
This is a blank EDAMS database into which the Oracle databases’ data will be
transferred.
2)
Backup the currently used Oracle Database from live environment. (Source
Database) and restore it to another instance of Oracle, test
environment. (NB!! This is important as during the merge process certain
data in this database will be deleted).
3)
Merge Utility.
Run DB Manager. (Use supplied DB Manager
[DBManager_2009_08_18.rar] or later version)
a)
Select Other tasks

b)
Select option Merge Assets database and select
Begin
4)
Connecting to the databases.
a)
Fill in the details of the Source Database. This is the Oracle
database from which the data will be migrated. Connect to the Test
Environment Instance created in Step 2 above. Select
Test. The version of
the Source Database should now be shown.

b)
Fill in the details of the Target Database. This is the MS SQL database
into which the data will be migrated. Choose the supplied restored database (See
1 above) as the target database. Select Test.
The version of the Target Database should now be shown.

c)
NB!
It is important that the source and Target versions are the same. In this case
4304.35
5)
In preparation for the merge,
we first cleanup any unwanted data from source and destination database.
a)
Select the option. Verify Extra Data Tables (Src
& Dst) (see below)

b)
You will be asked to delete some data from either source or
destination databases (see below). Select Yes to delete. This
message will be given for all necessary deletes on tables in source and
destination database.

c)
Once the validation is complete you will see the Completed message

d)
These actions are logged in merge.log in the db Manager
Installation folder. Check it for any problems.
6)
Performing the merge.
a)
Select actions to be
performed as per screen shot below
(see below). Since the database does not have Sewer Network data. Select the
Water Network Only option. De-select the Verify Extra
Data Tables option (as that has been performed in step 5 above). Also
select Zoning if this is used by the client.

b)
Start the Merge routing.
Select Process and wait for
process to complete. This will take a while to run. You should see the progress
bar appearing as each table’s data is saved.
c)
Once the merge is completed the Completed message will be shown.

d)
Now the merge is completed. Check the merge.log file for any
problems.
e)
Exit DB Manager.
7)
Post Merge Checks.
a)
Connect to the
Target Database with
NAM and validate that all data is correct.
b)
Perform any post
merge settings required.
8)
If the process needs to be repeated, run ALL steps again,
including steps 1 and 2.
Back to Top
This action can be performed using EDAMS Network Assets Managenent by following the steps below:
- Setup GIS File first
- Add a Custom Line or point or polygon element

Press + to add new element
Remember that the name here should not be the same as below


You may add any custom fields
Create 2 more custom int fields.
1 for the street_id (the id to merge many sections of a street)
1 to keep their ID of section for future synchronisation (in case new update file is received)
3. Load data now from shape files to Database under the specific element just created



Load any attributes in Shape file as custom fields. Replace Ref
(Custom fields must be defined first)




Back to Top
We have a problem with element Pressure gauges with tab Conditional assessment. In that tab you cannot choose predefined conditions.
When you open Pressure gauges and then tab operational condition you cannot see predefined conditions (see picture below)

In case the above problem appears go to system administration - reference files - operational condition types, and click the OK button without changing anything.
The code there will ensure that all default condition types exist for all element types and predefined condition types should appear as shown below.

Back to Top
A quick solution to rollback in such a case is to find a database backup in a desirable state and restore it to the current database that has duplicate elements. In order to do that you need to be certain that no other changes to the database were made from the time of the backup that is going to be restored. Otherwise all new changes to the database after the date of the backup will be lost!
Back to Top
To set up house connections from your commercial database for use in EDAMS Network Asset Management please read the last chapter of the latest System Administration manual that fully describes the process.
Back to Top
Water Connections and Geo Water Connections are different entities. entities as explained below:
The Water Connections element type is a representation of Billing Water Connections. It represents legal connections, and is fully controlled by Billing. These elements can not be created, deleted, modified, imported/exported in Assets, they are included for sake of Demand Management - Assets and are used for calculating the AADC of Node Area. The relation between Water Connections and Node Areas is graphical (contained by). Water Connections are represented in GIS by Points.
Geo Water Connections are Assets elements, and represent consumer connections pipes from the mains to the houses. They are represented by lines and they have connectivity and linked to chains. Those connections are controlled by Assets and are not visible in Billing.
Back to Top
It is completely up to you how to call network layers, but there are limitations on name prefix and suffix for SDE.
Back to Top
Key column is required because of the way the system accesses shapefiles, therefore it is important to select a column with unique values in the appropriate combo. If a key column is selected that contains not unique values all data from repeated key values will be lost.
Back to Top


This configuration is modeled as one pump station with 3 pumps in parallel.
The system allows a configuration within the pump station with a bulk meter after each pump.
The Pump station must have a meter position (and bulk meter) installed in configuration.
Notice that you have to specify the correct MDQ (readings combining rule) in the properties of the configuration.
Back to Top
Yes there is an option in EDAMS GIS for converting display units between X,Y and Lat Long (display coordinates in X, Y or Lat and Long)
Back to Top
There is a function in EDAMS NAM to insert either a node or point custom element by typing in its coordinates. When you click that button, you have to indicate the point position in GIS, and immediately after pops up the window where you can refine coordinates by typing. Note that for this to work, the corresponding point layer in GIS must have a defined geographic coordinate system which utilizes lats and longs and not meters. The form which pops up after insertion detects if it should display coordinates in degrees (from system settings).After that the system checks if the relevant point layer in the GIS has a Geographic coordinate system and if yes - it displays coordinates in degrees. The layer coordinate system will be used to convert x and y to lat and long, and vise versa.
Back to Top
When I zoom to a specific layer the map zooms really out showing all data as a small dot on the map. There must be a problem with the extends of the specific layer. Can I modify the extends of this layer to overcome the problem.
Yes you can do that by using the command line utility.
How to use it:
You must know the server name, password, username and service name or port number
First, you should write a command to describe the layer:
c:\>sdelayer -o describe_long -u sde -p sde -i 5153 -s panagiotis -l water_nodes,shape
where
-u sde - SDE user name, neeeded for connectiong to the server
-p sde - password (in my case these username and password both set to "sde")
-i 5153 - service name or port number, in their case it most likely should be ESRI_SDE or 5151 (default)
-s panagiotis - SDE server name
-l water_nodes - name of layer to describe
in response, command output must look similar to this:
ArcSDE 9.2 for SQL Server Build 1081 Sun Sep 17 16:01:22 2006
Layer Administration Utility
-----------------------------------------------------
Layer Description ....: <None>
Database : SDE
Table Owner ..........: SDE
Table Name ...........: WATER_NODES
Spatial Column .......: SHAPE
Layer Id .............: 35
SRID .................: 2
Minimum Shape Id .....: 1
Offset ...............:
falsex: 14576.323038
falsey: -3772098.860287
System Units .........: 31097.202055
Z Offset..............: 0.000000
Z Units ..............: 1.000000
Measure Offset .......: <None>
Measure Units ........: <None>
XY Cluster Tolerance .: 0.000000
Spatial Index ........:
parameter: SPIDX_GRID,GRID0=1079.01771656251,FULL
exist: Yes
array form: 1079.01771656251,0,0
Layer Envelope .......:
minx: 21403.93977, miny: -3769203.76108
maxx: 76752.32770, maxy: -3717705.67790
Entities .............: pc
Layer Type ...........: SDE
Creation Date ........: 03/05/09 17:46:48
I/O Mode .............: NORMAL
Autolocking ..........: Enabled
Precision.............: High
User Privileges ......: SELECT, UPDATE, INSERT, DELETE
Coordinate System ....: PROJCS["NMMM",GEOGCS["GCS_Hartebeesthoek_1994",DATUM["D_
Hartebeesthoek_1994",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Green
wich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],
PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Centra
l_Meridian",25.0],PARAMETER["Scale_Factor",1.0],PARAMETER["Latitude_Of_Origin",0
.0],UNIT["Meter",1.0]]
Layer Configuration ..: DEFAULTS
The Important information to check in the above is the :
connection to server is ok
layer name and spatial column is ok
layer envelope: minx, maxx, miny, maxy
after that you must run the command:
c:\>sdelayer -o alter -u sde -p sde -i 5153 -s panagiotis -l water_nodes,shape -E 21403.93977,-3769203.76108,76752.32770,-3717800
which will alter layer envelope, coordinates listed as minx,miny,maxx,maxy
You must put required coordinates to enlarge layer extents. In this example, I modified max y coordinate.
Notice that there are no spaces after commands between layername, shape column and between coordinate specifications.
Back to Top
You should clear registry brunch:
HKCU\Software\Edams\Assets\4.3\Placements
this will reset all form placement positions
Back to Top
When creating an annotation query to label pipes in EDAMS GIS the labels appear with too many decimal places which is not desirable. How can I remove these unnecessary decimal places?

To overcome this problem you must re-write the query which is used for the annotation.
Apparently the data for the labeling field in the database are stored using floating point number.
You must cast it to integer data, so the query should contain string CAST(ND) as INT instead of just having ND
Back to Top
Which attribute field should I use for calculating total length of pipes I_LENGTH or GIS_LENGTH
I_LENGTH is user defined length
GISLENGTH is actual length calculated from points.
Normally GISLENGTH = I_LENGTH but user is able to override the calculated by the geometry length in case he has more accurate information about the length and thus you should use I_LENGTH for calculation of total length of pipes.
Back to Top