In order to use HOPS the subscriber railway must appoint a HOPS Administrator. This will be the person who is responsible for HOPS on the railway. The railway's staff and volunteers will deal with the HOPS Administrator for training and issues. We (HOPS) will deal with each railway's HOPS Administrator.
In the initial stages, we will work with the HOPS Administrator to generate an appropriate configuration of HOPS for the railway's requirements and each department's requirements. The HOPS Administrator will be in charge of the users accounts list, allocating access rights to other users on the railway, and making configuration changes as the needs of the railway develop and expand.
We can provide training for HOPS Administrators and for railway staff and volunteers on a group-basis and 'briefing-the-briefer' training, as required by the railway's specific needs. We can also provide implementation support and advice.
There are many functions within HOPS. A subscriber railway can chose to use one, two, many or all of them, whatever is required to suit the railway's needs. There is a comprehensive built-in customisable permissions system (administrated by the Railway HOPS Administrator) to control access to the different components of the system.
The HOPS Administrator at each railway controls the user accounts. Users can be set up as 'offline' or 'live users'. A system user cannot log in and use their own account, whereas a live user can. Either way a person's name and details are in the system and can be used and records generated. This distinction is provided so that a railway can, for example, maintain competence and rostering records, which require individial user records, but only allow their ground-level staff to log in with a generic account to view rosters. Alternatively, if no personnel-specific functions are required, such as if HOPS is to only be used as a document library for example, then only generic accounts will be required.
page for privacy and security information.