The two ‘excel’-files of this check
(check_names_[n]ok.TXT) have got the structure:
|
column
|
remark
|
|
Unite
Centrale
|
asset on the old
database
|
|
ITEQUIP
Name
|
contact name in the
old database
|
|
Sevice Desk
Name
|
contact name in the
old database
|
|
state
|
result of the
check
|
|
del
|
‘del’
status in the new databse
|
Depending on the value of ‘state’ the
asset is listed in either the ‘_ok’ or the
‘_nok’ file.
-
state of the ‘_ok’ file and actions
to be done
In this file the
state-column has got two values:
-
ok
-
ignored,
inactive in Service Desk
state ‘ok’
The name in the new database is correct, no action
to be taken.
state ‘ignored, inactive in Service
Desk’
The name in the new database is incorrect or
missing, but the entry is marked with ‘inactive (del=1) in
the new database. No action has to be taken.
-
state of the ‘_nok’ file and
actions to be done
In this file the
state-column has got four values:
-
-
names are
different
-
new name
missing
-
reference
missing, update possible
-
unit not
found in new database
state ‘names are
different’
The name in the new database is different from the
old database name. Every item has to be checked, if only the
writing of the name is different, if the old database was an
organisational name (like consultant), if there is an
addition to the name (like (FEI) ) or if the name is different.
Based on these checks the entry can be left ‘as it is’
or has to be changed in the old or new
database.
state ‘new name
missing’
The name in the new database is missing. A
corresponding name was not found in the new database. Every item
has to be checked in the old database, if that entry is correct.
Based on this information the new database has to be
altered.
state ‘reference missing, update
possible’
The name in the new database is missing. A
corresponding name was found in the new database. Every item
has to be updated manually with the new name by using the name of
the old database. The file ‘check_names_upd.ca’
contains appropriate Unicenter commands, but by doing it manually
there is an additional visual check.
state ‘unit not found in new
database’
This asset is missing in the new database. It has
to be checked if it still is an active asset and then be entered
into the new database.
1. Hardware Requirements
