Knowledge of the Route in RailSoft – Requirement, Safety and Full Automation
Knowledge of the route is the foundation of safe railway traffic and a formal requirement of the Railway Transport Office (UTK), which remains under the direct control of the UTK (Office of Rail Transport in Poland).
www.petrosoftinc.com
Without valid knowledge, a train driver should not be allowed to drive a vehicle on a given section at a speed higher than 40 km/h. In practice, this means familiarity with signalling, track layout, danger points, speed restrictions, level crossings, engineering structures and line profile (familiarisation with the regulations of stations included in the RJ (Train Timetable)).
Petrosoft.pl – as a provider of the RailSoft system with dozens of implementations at transport companies – provides tools that record, verify and automatically extend route knowledge, creating a consistent, auditable data chain for the transport company and the supervisory authority.
What is route knowledge – essence and requirements
The rules regarding the number of journeys required to acquire or renew route familiarity are specified in the internal regulations of individual carriers. The RailSoft system is fully flexible – thanks to its configuration, it can be adapted to the individual regulations in force at each company.
Hypothetically, and based on observations of the most common practices in the industry, many carriers adopt rules similar to those in force in previous regulations. This means, for example, that four journeys must be made on a given section (including two at night) in order to acquire route knowledge, that this knowledge is lost after a 6-month break in driving, and that it must be reacquired on the same terms as the first time after two years.
Records of journeys and renewals are then recorded in the Route Familiarity Card, which is the official record of the history of authorisations.
Main basis for knowledge: timetable and written order
The main document necessary to confirm knowledge of the route is the timetable. RailSoft distinguishes between the Purchased Timetable and the Timetable Implementation – i.e. the actual course of the journey, taking into account any changes. These changes are introduced by means of a Written Order, which formally modifies the implementation of the journey.
Importantly, RailSoft calculates connections based on the timetable implementation rather than the plan itself. The system detects discrepancies with the purchased timetable, can stop the process (e.g. when a station is not in the timetable) and directs the service to manual verification by the dispatcher.
Train Composition Report and Work Time Register – operational data that RailSoft works with
R7 – list of carriages and train composition: confirms the composition and staffing, records the participation of the driver (including trainees) in a specific journey; forms the basis for acquiring/extending knowledge.
WCP – working time record: records actual train work (driving, coasting, simulator driving) on specific sections. Referring to the R7 journey and section in the WCP enables automatic extension of knowledge and completion of the card
.
How RailSoft automates the process
. Planning familiarisation journeys – inclusion of the trainee driver in documents, registration in R7/WCP.
. Authorisation of route knowledge – once the travel requirements have been met, an authorisation document is issued and the entry is added to the card
. Automatic extension – each confirmed journey on a ‘known’ section extends the validity; the system updates the card and history.
. Statuses and reminders – no travel → status ‘inactive’; after 12 months, re-purchase is necessary. Available alerts and summaries.
. In the event of corrections (e.g. in WCP), it is possible to refresh and recalculate thedata so that the file reflects the actual status.
Safety and compliance – UTK inspection
Knowledge of the route is a formal requirement of the UTK and the Railway Transport Act and is subject to UTK control. RailSoft ensures full auditability – from the identification of journeys and written orders modifying the RJ, through authorisations, to entries in the Knowledge Card. Reports on ‘unauthorised journeys’ and expiring authorisations are also available for inspection purposes.
Operational scenarios
. Acquisition of knowledge – the trainee driver completes the required journeys (at least 4, including 2 at night); RailSoft counts them on the basis of R7/WCP; once the criteria have been met, authorisation is issued and an entry is made in the card.
. Extension – a confirmed journey on a known route automatically extends the validity and updates the card.
. Loss/reacquisition – after a prolonged absence, status ‘inactive’; after 24 months, reacquisition according to the rules as for the first acquisition.
Why Petrosoft.pl is the best implementation partner
With dozens of successful railway implementations, experience with passenger and freight carriers, and a mature product, Petrosoft.pl effectively combines the formal requirements of the UTK with the realities of dispatchers and train drivers. The implementations reduce operational and regulatory risk (alerts, blockages, reports), simplify preparation for UTK inspections (complete documentation and audit trail from a single location) and are based on Timetable Implementation – i.e. on facts, not just plans.
Four-step implementation plan
. Process diagnosis – review of the circulation of timetables, written orders, R7/WCP, and authorisation rules and requirements.
. Functional design – rules for acquisition/renewals, card definitions, integration with existing tools.
. Implementation and migration – transfer of authorisation and card history, testing of ‘plan vs. execution’ scenarios with written orders.
. Maintenance and continuous auditing – indicator reviews (expiring knowledge, unauthorised journeys), support for UTK inspections.
Summary
Knowledge of the route is a formal requirement of the UTK, controlled by the UTK, and one of the most important pillars of safety. The main basis for confirming knowledge is the timetable and any changes to it introduced by written order, which RailSoft takes into account in Timetable Implementation. The system controls and records the entire process in an automated manner, ensuring compliance, transparency and audit readiness. Petrosoft.pl provides a solution and know-how that translate into real safety and operational efficiency.
wwww.petrosoft.pl
