Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2378aad5fe3a53e

Jump to content

// Workers AI · dad joke modeWhat did Heritage Operations Processing System say? "I'm a legacy.

From Wikipedia, the free encyclopedia

Heritage Operations Processing System
Product typeTransport Administration & Associated Services
OwnerConsortium
CountryUnited Kingdom
Introduced2009
Related brandsHeritage Railway Association
MarketsUnited Kingdom, Australia
Websitehops.org.uk hops.org.au

Heritage Operations Processing System, Heritage Ops, short named HOPS, is a web-based tool for the day-to-day running and management of preserved and heritage railways. The system was developed, from a concept drawn up by Danny Scroggins and Luke Cartey.[1]

Founding and development

[edit]

The HOPS Project began early in August 2009 in the rostering office of the signalling department at the Gloucestershire Warwickshire Railway – who embraced the use of the technology. Beta testing began in January 2010 with a small group of volunteers, the group being enlarged later that year. After this period, the system was made available to other UK heritage railways in January 2011.[2]

The purpose of the system is to provide administration tools associated with operating functions on heritage railways, such as staff rostering, timetabling, competence management and document control, etc. The system is used to assist railways in meeting the requirements of government legislation such as the Railways and Other Guided Transport Systems (Safety) Regulations 2006 (ROGS), which were introduced in Great Britain to put the 2004 European Railway Safety Directive into practice.[3] The system assists with competency management (as a requirement of the Safety Management System).[4][5]

The ethos of the development of the system has been that in the majority of cases, producing large-scale data-handling and storage facilities, with the appropriate level of security, access, backups, etc., would not be economical for an individual railway. A single program, in use by many railway companies, however, would make the investment economical.[citation needed]

The system has grown significantly in the five years it has been in development, mainly in response to feedback from users and demands of the industry.

References

[edit]
  1. "Heritage Operations Processing – System Updates". Heritage Operations Processing website. Heritage Operations Processing. Retrieved 10 February 2014.
  2. "Heritage Operations Processing – History & Growth History". Heritage Operations Processing website. Heritage Operations Processing. Retrieved 10 February 2014.
  3. "The Railways and Other Guided Transport Systems (Safety) Regulations 2006 (as amended) – A Guide to ROGS: May 2013" (PDF). Office of Rail Regulation website. Office of Rail Regulation. Retrieved 10 February 2014.[dead link]
  4. "RSSB – General SMS Guidance". RSSB website. Rail Safety and Standards Board Ltd. Archived from the original on 22 February 2014. Retrieved 10 February 2014.
  5. "RSSB – Competence Management". RSSB website. Rail Safety and Standards Board Ltd. Archived from the original on 22 February 2014. Retrieved 10 February 2014.