tag:blogger.com,1999:blog-19562859.post574390672420374075..comments2008-06-12T08:30:11.617ZDale Vilehttp://www.blogger.com/profile/04136788355130256923noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-19562859.post-42627019919903994022008-06-12T08:30:00.000Z2008-06-12T08:30:00.000ZIn a simplistic view, these two disciplines could be combined, however, one of the critical functions of both asset and IT management relates to long term asset replacement planning. <BR/><BR/>In the case of IT assets, they typically have short lives (3-7 years) and will typically be replaced by newer technology. Planning can therefore be more simplistic based upon strategic decisions (e.g. implement ERP) or headcount (e.g. desktop/laptop replacement).<BR/><BR/>In the case of fixed assets, particularly in a transport or utilities environment, assets will have lives ranging from 20 years to 100years+ (for civil assets e.g. bridges and tunnels). Capital maintenance on these assets will be a combination of maintenance/repair, overhaul/re-engineering or replacement. With large stocks of assets which have relatively slow deterioration rates, inadequate capital maintenance planning will not be obvious in the short term (which can keep politicians happy in government controlled enterprises) however, there is a large risk of a 'bow wave' forming where the number of critical asset replacements overwhelms an organisations abilities and funding to resolve.<BR/><BR/>These two approaches are very different, both requiring significant levels of functionality which will be suitable for the other area.julian.schwarzenbachhttp://www.blogger.com/profile/11634323140060862644noreply@blogger.com