Skip Ribbon Commands
Skip to main content
Loading...

R2 FAQs

What is R2 and why do we need a new system? 

R2 is the rail industry’s new database for rolling stock registration, maintenance planning and component tracking. It has replaced both the Rolling Stock Library (RSL) and Rail Vehicle Records System (RAVERS) which were both ‘legacy systems’ originating from the British Rail era. Given their age, current high running costs and lack of industry ownership it was recognised in 2011 that both of these systems were in urgent need of modernisation and upgrading. 

RSSB, the Traction & Rolling Stock Systems Management Group (T&RS SMG) – the industry governing group for the RSL and RAVERS – and Atos Worldline worked together to develop and deliver the new application.

What will the new system contain?

R2 is a replacement of all the existing RSL and Ravers functionality which includes a new rolling stock maintenance planning module. Like the legacy RSL and RAVERS systems R2  integrates with other key Industry Systems including TOPS, Gemini, GENIUS, Integrale, PADS, IMACS and NVR.

New functionality includes:

  • Reconfigured and extended functionality of RSL (Live 28 November, 2015) and RAVERS (Live 31 January 2016)
  • Improved business intelligence capabilities for trending and detailed analysis (Live 28 November 2016)
  • Improved maintenance planning (first organisation implemented 14 September, 2016)
  • Compatibility with European interoperability directives (TAF and TAP TSIs) - (Available on request from 7 November 2016)
  • The ability for the ATOC Component Tracker system to be replaced in due course if the industry wants it
  • Facilitation of sharing important vehicle data (Live 28 November, 2015 via cross organisation enquiries)
  • Hosting open interfaces for use by other systems (Available on request from 7 November 2016):

  • Including an interface to the National Vehicle Register (NVR) – de-scoped, manual interface to be continued
  • Primary source of vehicle and vehicle defect data for the national
    • Defect Recording, Analysis and Corrective Action System (DRACAS)(for CCS)
      • Facilitation of improvements to data quality - ongoing
      • Facilitation of innovation
    • More open information model
    • Business Intelligence Developer Licenses (10 licenses allocated on request to Power users across the industry) 
    • Adhoc Services Contract.
      • R2 is a new modern user friendly application (introduced from August, 2015)
      • It provides a significant reduction to existing costs – the operating costs for R2 will be significantly lower than the current cost for RSL and RAVERS
      • It introduces a simplified structure for the payment for R2 and the RSL managed services through RSSB, replacing the existing payment arrangements for these services between individual companies and Atos Worldline.
      • RSSB, on behalf of the industry, will obtain joint ownership of R2 (Atos Worldline is currently the sole owner of the Intellectual Property Rights for both RSL and RAVERS)
      • It integrates with other key industry systems including TOPS, Gemini, GENIUS, Integrale, PADS, IMACS and NVR. 

    What are the benefits to the industry?

    R2 is a new modern user friendly application.

    It provides a significant reduction to existing costs – the operating costs for R2 will be significantly lower than the current cost for RSL and RAVERS.

    It introduces a simplified structure for the payment for R2 and the RSL managed services through RSSB, replacing the existing payment arrangements for these services between individual companies and Atos Worldline.

    RSSB, on behalf of the industry, has obtained joint ownership of R2 (Atos Worldline was previously the sole owner of the Intellectual Property Rights for both RSL and RAVERS).

    R2 integrates with other key industry systems including TOPS, Gemini, GENIUS, Integrale, PADS, IMACS and NVR.

    Do I need to use R2?

    Input to the RSL is mandatory as required by Railway Group Standard GM/RT2453 ‘Registration, Identification and Data to be displayed on Rail Vehicles’ providing an essential facility for the sharing of rolling stock information and the successful operation of key industry systems such as TOPS and TRUST. 

    The associated Rail Vehicle Record System (RAVERS) provides a common industry system for vehicle and component maintenance information and maintenance planning. While the data recorded in RAVERS is not mandatory, the recording of wheel profile and diameter data, which is mandatory in GM/RT2453, is in many cases, achieved through RAVERS. The same mandatory/non-mandatory requirements will remain for R2. 

    Who was consulted about the need and requirements of a new system? 

    The Traction and Rolling Stock Systems Management Group coordinated the development of the high-level requirement for R2 through a cross-industry consultation. The more detailed requirements were developed via a number of workshops which included representatives from Midland Trains, Angel Trains, DB Schenker, ATOC, South West Trains, Porterbrook, Freightliner, First Great Western, Network Rail, RSSB and the Supplier Atos Worldline.  

    The representatives covered a variety of skills including, but not limited to, Senior Users, Customer Service Rep, Compliance, Contract and Fleet Engineers, Technical Architect, Data Manager, RSL and Ravers Service Managers and Ravers Support. Relevant reference documents and standards were used throughout the process as guidance. While under development, the project will be overseen by the cross-industry R2 Project Board. ​

    I will need to use the new R2 system – how can I get trained?

    RSSB is running training sessions as each module gets closer to going live.   For RSL/RAVERS, the project ran ‘train the trainer’ sessions in September and October 2015 to ensure each organisation was equipped to train their internal staff. For I4 Maintenance planning a number of 1 day training session were held with the Maintenance Planners and Fleet engineers.  Find out who the key R2 contact is within your organisation so you can make sure you’re up to speed. Existing user organisations can raise a help desk ticket directly with Worldline. If your organisation is new to R2 and you need training, get in touch with RSSB.

    Access to the legacy RSL and RAVERS systems

    Will any access be available to the legacy RSL and RAVERS applications following the R2 go-live date?

    Since the implementation of RSL and RAVERS on R2, no user access is available to the legacy RSL and RAVERS applications.

    Was all the data residing in RAVERS and RSL transferred and made available in R2?

    Yes, all the data residing in RAVERS and RSL was transferred and made available in R2.  Data migration reports were circulated for every organisations attention, where specific data could not be migrated.  This refers mainly to RAVERS data. 

    Was the transaction history that had been built up in RAVERS and RSL made available in R2?

    Yes, the transaction history as available in the legacy online Ravers and RSL systems  was made available in R2 and there are no plans to archive any of the data from R2 for the next 6 years. ​

    R2 Process Workflow

    How do I contact another organisation if they are required to complete an action?

    All R2 Key Contacts will be provided with the contact details of all member organisations.  This list will also be made available on the R2 Extranet: http://www.rssb.co.uk/extranet/r2/pages/documents.aspx#

    What happens if a user in another organisation cannot be found to complete an action?

    Some actions can only be carried out by other member organisations but please contact the Rail Service desk (0800 0217744) who may be able to help you if you are stuck.

    How do I ensure system generated messages coming to me are available to a replacement/covering user when I am absent?

    Notifications (known as ‘Alerts’) are issued to groups of users within a specific organisation, rather than to individuals, thus other users within the same organisation having the same role(s) as you will also be able to view/action the alerts.

    Note that although the alerts are targeted towards users that have specific roles within the system. Notifications that a request has been rejected, for example, will only be sent to users within the organisation that have the ability to raise requests of that type), it is not always possible to identify groups of users.  Therefore please ensure that at least one user within each of the roles within your organisation also has the ‘Receive Alerts’ role and that the appropriate people know who this person is.​

    Can I have my notifications sent to an external mailbox?

    All notifications are currently within the R2 application. There is no facility for the notification to be forwarded to an external mailbox.

    Can I change/recall a request after it has been submitted?

    There is no facility to recall a request after it has been submitted. If you want to amend a request after submitting it please contact Managed Service by telephone on Tel: 0121 335 7591 who will be able to reject the request for you.​

    General Support

    Who is my first line of support for R2?

    Your local Administrator is your first internal line of support for role and password queries. 

    For any anything else the first line of support for R2 is the Rail Service Desk. 

    Who are the Rail Service desk and how do I contact them? 

    The Rail Service desk is a general help desk supporting many systems. The Rail Service desk staff have no specific knowledge of R2 but will log your call and send it to the correct referral team for processing.

    You should receive a call back from the correct referral team within 4  working hours.

    The Rail Service desk hours of operation are : 24/7

    You can contact the Rail Service desk by telephone: 0800 0217744.

    Low priority calls can be raised by email to servicedesk.railoperations@atos.net .

    How do I contact the Managed Service if required?

    You can contact the Managed Service by telephone: 0121 335 7591, or by email: rslfvmc@worldline.com

    What are the Managed Service hours of operation?

    The managed Service hours of operation are: 0800 to 1700hrs Monday – Friday.

    Priority 1 requests will be completed within 4 service hours (i.e. urgent requests to register one or more vehicles that are scheduled to run imminently)

    Priority 2 requests will be completed within 9 service hours (i.e. standard requests for vehicle registration that require design or vehicle data changes e.g. amending the status for a vehicle from new build or deregistered to registered)

    Priority 3 requests will be completed within 18 service hours (i.e. ‘cosmetic’ re-registrations which require only the input of a replacement certificate and have no real impact on operations).

    How do I register a defect found within the application?

    You can register a bug by calling the Rail Service Desk. Be prepared to give as much information as possible on when an error has occurred, what functions were being carried out, any error messages.​

    Who manages issues relating to the interfacing of data to other legacy systems?

    Issues relating to the interfacing of data to other legacy systems should initially be reported to the Rail Service Desk. These will then be escalated to the R2 L2 Support Team to manage.

    What browser versions are supported?

    The Windows browser versions currently supported by the R2 application are Internet explorer version 10 and Internet Explorer version 11, as documented in the ‘’Approved Environments’’ section of the User Agreements as well as in the contract between RSSB and Atos Worldline.

    The iPad browser versions currently supported by the R2 application are Safari IOS v7.x and 8.x.

    Although some alternative browsers can be used, Atos Worldline are not obliged to provide Support Services in respect of the R2 Hosting Service when accessed through browser software which does not form part of the Approved Environment. Please contact RSSB if you need additional browsers to be considered to form part of the future R2 application.

    Will the application be kept in line with new browser versions?

    The supported browsers shall be reviewed in line with changing technology and reissued at 6 monthly intervals. 

    Subject to giving RSSB not less than 6 months’ prior notice, Atos Worldine may, with the written agreement (not to be unreasonably withheld or delayed) of RSSB cease to support an ‘’Approved Environment’’. 

    Will there be regular application maintenance windows?

    A regular maintenance window has been agreed to take place on a Sunday morning, for a maximum of 4 hours (See contract schedule 10, section 2.2, sub section 2.2.1 ‘Hosted Software’ for more information on outages).

    How are mass changes to be handled in instances such as a franchise change?

    Major Franchise changes are treated as a project as it would involve changes across a number of Rail Ops products.  To request a change please report this request to the Rail Service desk or RSSB.

    User Licensing

    How many R2 users can my organisation have?

    The number of R2 Users an organisation may have is agreed in each member organisations ‘User Agreement’.  In most User Agreements this is the same number of subscriptions as the member organisation was entitled to create for the RSL/Ravers hosting service.

    The member organisation may, from time to time during the term of this agreement, make use of additional User Subscriptions up to a total in aggregate of 130% of the number of User-id’s agreed in the User Agreement (Clause 4.2). Those member organisations who make use of additional User Subscriptions should notify RSSB in writing and supply any information reasonably requested by RSSB in connection with its increased usage.

    How will additional usage be charged?

    If the member organisation requires more User Subscriptions beyond the increased number of 130% (see Clause 4.3) referred to in the User Agreement, it may request additional User Subscriptions in writing to RSSB.  RSSB, in turn, will evaluate these requests for additional User Subscriptions and may approve or reject the request. (This approval will not be unreasonably withheld but is subject to the grant of any approval required by RSSB from its licensors).  The member organisation will receive notice of the additional fee, if any, payable for the use of the additional User Subscriptions.

    Is the licensing based on active accounts or concurrent users?

    The licensing is based on the number of active users.

    How will we be charged for R2 and when?

    As part of the User Agreement, your organisation will have agreed an annual fee based on your existing usage of RSL/RAVERS.  This fee will be invoiced from August 2015 when RSSB took over the invoicing of RSL/RAVERS from Worldline..   This fee includes the use of the Worldline Rail Support Service as well as any defect fixes.  For the Financial year 16/17 onwards the R2 fee will be invoiced with the RSSB members levy and subjected to the RPI adjustment as set out in clause 6.1.5 of the Constitution Agreement as part of the 5-year fixed funding agreement. Companies that are not members of RSSB will be invoiced accordingly. From year 3 (after go live of R2) the fee will also include a contribution by each organisation towards any enhancements that may be required.  If by the end of the Financial year this contribution has not been used, it will be shared proportionally among all member organisations. Prior to year 3 (after the go live of R2) member organisations may be asked to make a shared contribution towards any enhancements agreed by the R2 Project Board.

    How do we request additional users?

    After R2 go-live, additional users can be added by the local organisation Administrator(s). 

    Security

    What is the password policy?

    For security reasons, you will be required to reset your password on a regular basis. The period of time for which your password will be valid depends on your organisation.

    The R2 system allows the R2 Administrator within each organisation to specify the following parameter values for your organisation:

    • Temporary password expiry (number of days after which a temporary password expires and will need to be reset)
    • Login attempts (number of failed login attempts after which user’s account is suspended)
    • Password expiry period (after changing password, number of days after which password must be changed again)
    • Password expiry warning (number of days before password expiry that a warning message is issued to user)
    • Session timeout (number of consecutive minutes of user inactivity after which user is automatically logged out).

    Your local R2 Administrator will be able to advice you of these values.

    Upon first login (and after a password reset), you will be prompted to change your password. The new value must adhere to the following rules:

    • Must be between 8 and 20 characters in length
    • Must contain at least one number, at least one uppercase character, at least one lowercase character, and at least one non-alphanumeric character
    • Must not be the same value as any of your previous seven passwords.

    On login, you will be warned if your password is due to expire in the near future, and will be given the opportunity to change it. Once your password has actually expired, you will still be able to login however you will not be able to continue to use the system until you have created a new password. 

    Temporary passwords (either generated prior to first login/as a result of a reset) will expire within a certain number of days. Therefore, please login and change your password as soon as you can. 

    Who do I contact to change my password?

    You will be able to change your password yourself at any time using the ‘Administration/User’ option. 

    If you forget your password, you will need to contact your Local Administrator and ask for it to be reset. They will provide you with a new temporary password (which must be changed on next login).

    If you exceed the maximum number of failed login attempts set for your organisation, your account will be suspended. Your Local Administrator will be able to unlock it for you, and reset your password if necessary.

    Who do I contact to change my role(s) / responsibility?

    Your Local Administrator will be able to change your role(s)/responsibility. There are a few roles e.g. ‘Authorised Signatory’ which need to be authorised before they can be allocated. They have to be requested by the Local Administrator via the Rail Service Desk.

    How do I see which of my users are using the application and the operations they are performing?

    This functionality will be made available as part of the R2 Data Warehousing solution. Prior to this part of the Phase 2 implementation, the information can be requested by contacting the Rail Service Desk.

    Are users from other organisations able to see data regarding our vehicles?

    Yes, R2 is a shared system.

    Can users access the application from anywhere that has an internet connection?

    Yes, users can access the application from anywhere that has an internet connection.

    Continuous Improvement

    How are user experiences and concerns to be discussed and managed?

    Every organisation has one (max 3) R2 Key Contacts who are responsible for communicating al the R2 updates within their organisation.  These Key Contacts are also invited to attend a month R2 Working Group meeting where updates, including enhancements and project progress are shared and concerns can be discussed. Whilst R2 (including I4 and Phase 2) is under development, experiences and concerns can also be discussed with the R2 project Board representatives.  In the long term the R2 working Group will be replaced by an R2 User Group who will be responsible for the relationship between the R2 user organisations and Worldline, including the management of any change requests and the associated budget.

    How do users suggest enhancements/improvements to the application?

    While R2 (including I4 and Phase 2) is under development, enhancements / improvements can be suggested to:

    • The R2 key Contacts to discuss at the monthly Working Group meetings
    • The R2 Project managers (RSSB or Worldline) 
    • Any of the R2 Project Board Members (see the R2 Extranet site) 
    • To the Rail Service desk.

    Who decides if suggested enhancements/improvements are to be adopted?

    Who decides if suggested enhancements/improvements are to be adopted?
    While the project is still under development, recommendations as to the content and priorities of enhancements/improvements will be made by the R2 Working Group. As managers of the budget, the adaptation of enhancements/improvements is decided by the R2 Project Board.

    Can I request an organisation specific enhancement?

    Yes, an organisation specific enhancement can be requested.  This cost of this enhancement would need to be covered by that organisation. Note that although no other organisation may wish to make use of this enhancement at the time, there will be no restriction build in to the system to prevent anyone else from using it in the future.

    How are enhancements/improvements to be funded?

    From year two after go-live, a small proportion of the R2 payments to RSSB will be set aside as budget for enhancements/improvements.  Whatever funds are not used by the end of the financial year will be shared proportionally between the member organisations.

    Data Management

    Who is responsible for ensuring the reference data being utilised is being kept up to date?
    Answer: The responsibility for updating reference data lies with each member organisations.  Roles/responsibilities should be allocated to ensure that all reference data is kept up-to-date.

    How do users raise issues regarding incorrect or missing data?

    Issues regarding incorrect or missing data should be reported to the Rail Service desk.

    How is redundant/bad data within the application to be continually monitored & cleansed?

    As part of the R2 application, the data validation rules on input, are stricter than those in RSL/RAVERS with the view to reduce ‘bad’ data. Once the Data Warehouse is in place, the facility will be there for member organisations to run their own regular reports to check for redundant data.

    How is our data protected, is there a disaster recovery mechanism in place?

    The system maintains log files and a backup process for data roll-back purposes. There is a disaster recovery mechanism in place which includes a failover site.  This mechanism was fully tested during the Familiarisation phase prior to the RSL go-live.

    Training

    Are new users to be trained by their employers, or are there courses periodically being scheduled by RSSB/Worldline?

    The agreed approach for the R2 project delivery is for a limited amount of training to be provided as part of each stage within the project.  For RSL and RAVERS this consisted of a variety of Train-The-Trainer courses provided by RSSB / Worldline with the member organisations taking responsibility for internal training.  As new users join, they will also need to be trained by their employers. 

    For I4 Maintenance Planning a number of Short and long term planners as well as Fleet Managers attended a one day training course provided by RRSSB / Worldline.

    RSSB/Worldline can arrange additional training courses for individual organisations, if required, but these will be chargeable.​

    Will user guides be available to all users?

    Yes, The user guides are already available and are stored on the R2 Extranet under ‘Training’.  The Vehicle Management, Core R2 and Wheelset training material is also stored there.

    Will there be a “training environment” available for use after go-live?

    There are only two environments, ‘Production’ and ‘Testing/UAT’.

    All training will need to be given in the Testing/UAT environment: https://uat.r2.rssb.co.uk.

    Please ensure that you let the Rail Service Desk know well in advance if you plan to use the Testing/UAT environment for training as:

    1. They might be using the environment to test some changes/defects which could impact your training.
    2. They might need to take the environment down for short periods of down for maintenance.
    3. The data might need a refresh.

    Document Upload

    Is there a limit on the size of document that can be uploaded into the application?

    Yes, there is a limit of 10mb per document.

    Is there a restriction on the type of document that can be uploaded?

    When you upload a file, it must be one of the following types:

    • PDF
    • doc
    • docx
    • Xls
    • xlsx
    • PPT
    • PPTX
    • msg
    • txt
    • bmp
    • jpeg
    • png
    • tiff

    alternatively a URL can be specified.

    Can their organisations view documents I have uploaded?

    Yes, other organisations can view the documents you have uploaded. When the request is approved, the document/URL becomes associated with the object(s) in the request (i.e. design code, vehicle(s), unit(s) or certificate).

    Can other organisations alter/delete documents I have uploaded?

    No, other organisations cannot alter/delete documents you have uploaded.  They would need to upload a new document.

    Who will be uploading certificates? I’m aware that some issuing bodies have said they won’t be using the system.

    The registering organization - Owner/TOC etc. – (or a certificate issuing body such as a NoBo/DeBo on their behalf) should be loading the certificate record and uploading the pdf for the certificate itself.  If the issuing body is not going to use R2 then this responsibility will fall with the registering organization.

    Document download

    When viewing a downloaded CSV file in Excel, what formatting should you apply to the European Vehicle Number column?

    When viewing a downloaded CSV file in Excel ensure that the EVN column is reformatted to a ‘’number’’ with zero decimal places and no comma separator. 

    Without this setting, the excel exports are rounding the European Vehicle Number up from the 6th digit, 99709594012-5 becomes 997096000000.

    This document is hosted on SPARK

    SPARK

    You are now being redirected to SPARK, RSSB's knowledge sharing hub, to access the requested information.

    Your RSSB user name and password can be used to access SPARK.

    Ok