Landmark Milestone For ALCAM and RISSB
The Australian Level Crossing Assessment Model (ALCAM) is an assessment tool which supports a national approach to risk management at level crossings. This important tool is a significant weapon in the armoury against level crossing risk; such a critical issue for Australia’s rail networks.
This month, the owner of ALCAM (the National ALCAM Committee) and RISSB executed contracts to transfer support of ALCAM and the level crossing management system (LXM System) from VicTrack, over to RISSB – a transition which has been some months in the planning.
We want to thank VicTrack for showing great industry leadership in assisting the National ALCAM Committee during the development of the LXM System and its support over the past nine years. During this time the ALCAM model and LXM System has helped industry to address level crossing risks and supported us all in our efforts to make improvements. RISSB would also like to thank VicTrack for all their efforts in making the transition to RISSB as seamless as possible.
With ALCAM’s arrival at RISSB it is now supported centrally by a cross-industry body, a logical step in ALCAM’s evolution. At RISSB, ALCAM will join RISSB’s own ARRM (the Australian Rail Risk Model) and the Culture Hub Survey to create a powerful suite of information systems on offer for the benefit of the railway.
From a user’s perspective, very little will change in the immediate future; you will still interact with ALCAM and the LXM System the same way, and you will still access ALCAM information in the same way ie via www.alcam.com.au. ALCAM and the LXM System will still be overseen by its cross-industry committee and its technical subcommittee – the changes will be largely behind the scenes.
Behind the scenes, we will be working hard to leverage RISSB’s extensive expertise and experience collaborating with industry to allow significant growth and improvement of ALCAM and the LXM system. Work is already underway to validate and enhance the road model, but more to come on that at a later date