ADVERTORIAL FEATURE
Asset Register: the essential base for ISO 55000 in the rail industry
Marcel van Velthoven, managing director of ZNAPZ, describes asset management challenges and opportunities across the rail industry.
T
he total investment in the rail industry across Europe in the coming decade will
be in the hundreds of billions of euros. The rail industry is making a rapid move from ‘old- fashioned’ to ‘modern’, and becoming a more effi cient and environmentally friendly form of transport. Today, more than ever before, these investments must be well-managed.
ISO 55000 is a new standard, launched in January
2014, describing high-level best
practice for asset management. The key criteria for this ISO standard focus on:
• Alignment of strategic business plan with asset plan
• Lifetime cost management • Lifetime risk management • Lifetime revenue management • Continuous improvement
This article describes the challenge that most rail companies have today in getting started with this well thought-through standard.
Going around the European rail industry, from north to south and from east to west, the challenges for the rail companies are very much the same. How do we get started? One should think that it is quite easy to manage the rail infrastructure – but real life is diff erent. A major challenge that many rail companies have is to know all their assets – and not only this, but also to know all the relevant information about these assets. This is at the heart of good asset management.
There are many questions that can be asked, starting with: what assets have been installed? When were the assets installed? What is the maintenance history of these assets? Which
22 | rail technology magazine Aug/Sep 14 asset components have been renewed?
Many of these questions can be answered, because it is documented, either electronically (often in many separate systems) or on paper. Sometimes, the people who work in the organisation have the answers as part of their day-to-day knowledge.
However, today, that isn’t good enough. Today we need direct access to this information, at any location and at any time of the day. This requires, for many organisations, the creation and development of a completely new asset management system. This will integrate what is already available and complete, and clean up that which is incomplete or incorrect. This creates the core of the asset management practice.
We need to have asset data for many diff erent topics under this ISO standard. Of course we need a full physical asset register, but now we need to enhance this with:
• Cost information over the lifetime of the asset (taking into account new techniques in maintenance, logistics and monitoring) • Risk information over the lifetime of the asset; for example, what can fail? How can this fail? What are the consequences? What is the likelihood of this failure? • Revenue information over the lifetime of the asset; for example, what is the intensity of the usage of that piece of rail infrastructure? What is the load?
All of these questions demand an up-to-date and well-equipped information system to deal with these requirements. Many of the legacy systems rail companies have are either not completely
set-up to deal with these requirements, or lack the fl exibility to be easily enhanced to include the latest required information.
IBM’s MAXIMO, an enterprise asset management system, is one of the applications capable of dealing with those specifi c requirements. It has most of the functionality to build and maintain a full suitable asset register, fully integrated with the leading GIS or geospatial systems (such as ESRI) and it is fl exible enough to be enhanced where the rail company would like to add data. Several European rail organisations have chosen MAXIMO as their system to build a data register.
This process still involves several challenges – one of them being the specifi c nature of the rail industry. We are talking about assets that are miles and miles long, or assets positioned at locations that are seemingly in the middle of nowhere but which have a specifi c critical task, like the signposts. How can we locate these assets and identify them uniquely?
The solution is in defi ning linear asset management to be able to defi ne a track and each specifi c location / position along the track, with its specifi c conditions and requirements. However, just the location isn’t good enough.
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164