This page contains a Flash digital edition of a book.
ASSET MANAGEMENT


The application of formal safety management processes to ORBIS delivered Asset Information Systems


Sue Schreiber of Bellwether Enterprises Ltd explains the vital role of safety management to Network Rail’s ORBIS project. M


any of the engineering assets that make up the railway are recognised as safety


related and therefore are the subject of a formal engineering safety case. When engineering assets are safety related, the information that supports their management has the potential to impact upon the safety of the railway. Presenting engineers responsible for making decisions regarding the management of these assets with correct, complete and current asset information should lead to better, and therefore safer, asset management decisions.


However, when information is not fully correct, complete or current then it has the potential to compromise decision-making. To protect against this eventuality, the potential for imperfect information needs to be minimised and the associated decision- making processes need to be resilient to information imperfections.


In recognition of the importance of asset information to a safe railway system, Network Rail Asset Information (AI) operates a formal safety management regime. This regime was originally set up to comply with the good practice set out in the ‘Yellow Book’ and is now aligned with BS EN 61508: Functional safety of electrical/electronic/ programmable electronic safety-related systems, and associated British Standards.


The Network Rail Asset Management Policy includes a commitment “to meet our asset management obligations in a manner that is demonstrably world class”. A key part of fulfilling this commitment has been the creation


122 | rail technology magazine Apr/May 14


of the ‘Offering Railways Better Information Services’ (ORBIS) programme to deliver a step- change improvement in Asset Information Systems. One of the key objectives of ORBIS is to realise improvements in the safety of both the engineering assets and the staff who carry out the associated work.


Each of the projects within the scope of the ORBIS programme must satisfy formal safety management milestones. Safety is included at the planning stage of the project and safety deliverables are produced as appropriate throughout the project lifecycle. The first major safety deliverable is a Safety Implications Statement (SIS) and, if it is deemed appropriate, the second major safety deliverable is a safety case.


A SIS is an assessment undertaken during the requirements definition phase of a project to determine the impact that a proposed change could have on the safety of the operational system. Once the safety implications are understood, the SIS then determines both the safety requirements for the system and the appropriate engineering safety management effort for subsequent project phases.


A safety case is produced to provide the evidence of completion of safety and technical assurance prior to the commissioning of the system into operational use. The need for a safety case is driven by the risk associated with the system and/or the associated novelty and/or the scale of the arising business change.


In order to ensure an appropriate separation


between project execution and the safety assurance, the key safety deliverables must be completed by an appropriately qualified Independent Safety Consultant, and the business acceptance of those deliverables is undertaken by the (project independent) Infrastructure Safety Review Panel (ISRP). At the conclusion of the project, the safety deliverables are transferred to the business system owner, who then becomes responsible for their ongoing management during the operational life of the system.


Mike Mangroo, another principal consultant at Bellwether, is currently the independent safety consultant for the projects delivering the Linear Asset Decision Support (LADS) tool and Asset Data Store (ADS). He has written and gained ISRP approval for both systems.


He explained that Bellwether has been involved with the safety assurance of Network Rail’s information systems for many years now and as a result has developed processes tailored for the task.


Given its past experience, Bellwether has been helping ORBIS to embed suitable safety management processes into its project management framework, hence principal consultant Tim Ballantyne’s role as the acting safety integration manager within the ORBIS Design Authority. He will continue in this role until Network


Rail


has completed the process of recruiting a permanent member of staff.


FOR MORE INFORMATION www.bellwether.co.uk


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  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208