43
accept able format . If t he new
syst em requires
addit iona l dat a it ems,
dat a conversion
mi ght
not
be able to be automat ed ( Shel ly,
2010).
A
p
roject needs
t
o
run a series
of mock
runs
t
o
ensure t hat
everyt hing works
as exp ect ed. M ock runs
help highli ght w here
chan ges m ay add efficiencies.
(United
Communic at ons
ions
Group ,
1999)
2.8. 2. Data Conversi on S ecuri ty a nd Control s
When
dat a is
ext remely vulnerable, conversion
process
must
be
est ablished
w t h st rict
it h st rict
input
cont rols.
All
syst em control
measures must
be in place and op erat ional t o protect dat a
from
unauthoriz ed
access
and t o
help prevent erroneous inp ut .
Careful
dat a
conversion and
inp ut
cont rols
don’t guarant ee
error-free
process;e.g.
dup licat e cust omer
records or
inconsist ent
part
numbers
might
have been t olerated
by
the
old sy st em,
but will
cause
t
he
new sy stem
t
o crash. It is
said t hat most
organizat ions
require
that users
verify
all dat a,
correct
all errors,
and
sup ply
every missing
dat a
it em
during
conversion.
Alt hough t he
process
can
be
t m e-consumin g and e xp ensive, it
im e-consumin g and e xp ensive, it
is
essent ial t hat
t
he new
syst em be loaded w t h accurat e, error-fr ee dat a ( Shel ly, 2010).
it h accurat e, error-fr ee dat a ( Shel ly, 2010).
2.8. 3. What Data
to Co nvert
Broek
(2010)
st at es t hat imp ort ant
dat a conversions
include :New cost
center
st ruct ure,
coding sy st em for st atist cal
ical
dat a,
booking codes
for p roject bookin gs, market
codes, product
codes,
G/L account
numbers, cust omer dat a, unsett ed cust omer
led cust omer
 |