News

  • 2025-01-17 v4.0.17 Holiday Calendar has been updated for 2025. Work Event submission now requires work plans with valid Start and End dates
  • 2024-04-30 v4.0.16 Map Feature. The mapping functionality is available within the Work Group forms and must be used to create new Work Groups.
  • 2024-02-14 v4.0.15 R842 Flagging validation feature. This feature will validate the number of flagging resources requested for a R842 work block. Work Blocks that exceed the permitted number of flagging resources will be blocked from submission.

Bug or Issues?

If you've encountered any technical issues such as a crash when using the app, please send a description, a screenshot, and any other information that may assist with reproducing the issue to NAPT.training@metrolinx.com

Upcoming Holidays and Deadline Adjustments

* Dates and deadlines may be subject to modification

Loading...

Activity Feed

to

Loading...

Weekly Access Report

to


Download Weekly Access Report (Excel)

Data Filters


to




Work Blocks

Download


Loading...


Data Filters


to


Work Event Report (Non-USRC Work Blocks)

Work Event Table Work Group Details

Loading...

Record Search

Work Events (Booking Requests)

Work Blocks

Download (Excel)
Loading...
Download (Excel)
Loading...

Work Groups

Download (Excel)
Loading...
Download (Excel)
Loading...

Projects

Access Points



Task Numbers



Step 1: New or Existing Project?


Step 2: Enter or Update Project and Contact Information

Project Information

Metrolinx Contact Information

Contractor Contact Information

Project Users

Submit or Update Project Information


Step 3: Enter or Update Task Numbers Associated with the Project



Loading...
Loading...

Step 4: Configure Project Rules

Work Plans and Files



Note: Files that have been referenced in Work Events cannot be deleted. Files that are no longer needed should be archived, and archived files will be hidden by default from most forms in NAPT. Only MX users are permitted to archive files.


Loading...
Loading...

Work Event Selection


Details

Risk Profile



Available Work Plans










Loading...
Loading...





Loading...
Loading...

R842 Resource Conflicts

The below table identifies any Work Blocks requesting R842 protection and determines whether the number of flagging resources requested exceeds the maximum allowable number. Work Blocks without a Approved Increased Sub-Foreman Risk Assessment are limited to 4 flagging resources across all Work Groups. Work Blocks with a Approved Increased Sub-Foreman Risk Assessment are limited to 8 flagging resources across all Work Groups. The Increased Sub-Foreman Risk Assessment field is specified in the Work Block form.

Work Event Structure

Record Validation

Loading...
Loading...


Map View




Loading...
Loading...

Long-Term Planning Calendar

Loading...


Disruptive Periods

to

Loading...
Loading...

Disruptive Possessions

to

Loading...
Loading...


Loading...
Loading...

Calendar Items (LT Planners Only)


to

Activity Report

to

Upload Access Review Data


Upload History

NAPT Guidance on Requesting Rail Corridor Access

How to define a “Work Event”: A Work Event is typically a period of between 1 and 7 days in a specific location/area where a defined set of tasks by one or more sub-contractors are being undertaken. For example, a Work Event could be track work including grading, placing ballast, installing ties and track over the period of Monday-Friday from 06:00 to 17:30 each day at the same location(s).

Work blocks that are adjacent to, overlapping or in close proximity to one another can be grouped as part of a single weekly Work Event.

How to define a “Work Block”: A Work Block is a continuous period of time in a specific location/area when work is occurring during a Work Event. Following the previous example, Monday 06:00 – 17:30 at one location would be one Work Block, whereas Tuesday 06:00 – 17:30 at the same location would be a second Work Block.

A Work Block’s type of protection cannot change. If the Protection Type needs to change, a separate Work Block should be identified. For convenience, it may be useful to separate Work Blocks by shift (i.e. Daytime, Nighttime, etc.) to facilitate modifications or adjustments to only one Work Block.

How to define a “Work Group/Zone”: A Work Group or Work Zone is a group of workers all conducting activities at a single defined site or in a zone. The site or zone is defined by railway mileage. Typically, the Work Group/Zone is protected by a single Flagperson who has visual control of all workers (visibility and ability to communicate) in the Work Group/Zone. See Section 6 of GO TWSI and CROR Rule 855 for where the nature of the work, size of the work crew or length of the work limits prevents a single Flagperson from having visual control of all persons engaged in the work. In such cases, separated Work Groups or Work Zones should be requested.

How to propose the Protection Type: the type of protection will be determined by Metrolinx based on factors existing at the worksite:

  • Nature of the work activity;
  • Machines and distance from rail;
  • Workers and distance from rail;
  • Location (railway mileage, station or crossing) of the work site;
  • Terrain present at the work site (obstructions, curvature, topography, nearby structures);
  • Train activity (volume, speed, number of active tracks);
  • Adjacent work activities or projects;

When proposing a type of protection, please see the Canadian Railway Operating Rules and the GO Track Worker Safety Instructions listed below, or contact Metrolinx Rail Corridor Access & Control for support.

How to propose the correct number of Flagging Resources: A Flagperson must be assigned to each separated Work Group. In certain circumstances as determined by Metrolinx following the CROR and TWSI, an extra Flagperson (a separate Protecting Foreman) may be added to manage the flagging team (one Sub-foreman for each separated Work Group or Work Zone).


Key Rules & Instructions for Rail Corridor Access

Canadian Railway Operating Rules (Canadian National CROR used on Metrolinx Territory)

  • CROR Rule 103(g) – Public Crossings at Grade
  • CROR Rule 105 – Operation on Non-Main Track
  • CROR Rule 803 – Track Unit and Track Work Authorization
  • CROR Rule 841 – Protection of Track Work on Non-Main Track
  • CROR Rule 842 – Planned Protection – Rule 42
  • CROR Rule 849 to 864 – Track Occupancy Permits

GO Transit Track Worker Safety Instructions

  • TWSI Section 5.0 – Safety Watch
  • TWSI Section 6.0 – Separated Work Groups
  • TWSI Section 10.0 – Off Track Machinery (incl. 10.4 Temporary Concrete Barriers)

Key Terms

Calendar of Opportunities: The dates when disruptive possessions can be booked, including low ridership weekends (discounted) and high ridership weekends (blackout). Example: Aug 27-28 2021 – Blackout;Nov 19-20 2021 – 50% Discount;

Contingency Plan: A description of what measures are in place should a Work Block within the Work Event have a risk of overrunning its scheduled time. Example: A document describing mitigation measures.

Disruptive Possession: A Work Block that cancels all trains or reduces train services that operate on that part of the subdivision. Example: Major Track Closures & Minor Track Closures

Employee in Charge (EIC): See definition of a Sub-foreman.

Flagperson: Refers to the Protecting Foreman (including separate Protecting Foreman) and Sub-foreman protecting work activities on the rail corridor. The titles refer to their assignments for a specific Work Block, as all Flagging Resources are qualified as a Protecting Foreman as per CROR. Example: See Canadian Railway Operating Rules.

Major Track Closure: A Work Block where all tracks are closed, forcing the cancellation or re-routing of all train services. Example: A 2-Day Bus Bridge Replacement

Minor Track Closure: A Work Block where tracks are closed, but a select or reduced number of scheduled train services using that subdivision can still operate. Example: 1-week closure of 1 of the 2 tracks, forcing reduction from 4 trains per hour to 2.

Non-Disruptive Access: A Work Block where no tracks are closed and there is no impact to train services (GO or 3rd Party). This includes off-corridor access. Example: Vegetation Control protected by a Safety Watch

Non-Positive Protection: Forms of protection that do not involve CROR Rule 841, CROR Rule 842 and Track Occupancy Permits (see TWSI for examples, such as Sections 5.0 and 10.3). Example: See Track Worker Safety Instructions.

Off Track Monitoring (OTM): Other methods of Non-Positive Protection other than Safety Watch.

Positive Protection: The use of CROR Rule 841, CROR Rule 42/842 and Track Occupancy Permits to protect work. Example: See Canadian Railway Operating Rules.

Project: The project (GO Rail, LRT, etc.) or contract (maintenance, surveying, etc.) the Work Event is for. Example: Davenport Diamond Grade Separation

Protecting Foreman: Responsible for communicating with Train Crew and having visual control (direct sight and communication) of all workers engaged in the work. Where Metrolinx has determined that, due to the nature of the work, the Protecting Foreman named in the authority does not have visual control of workers and therefore will be dedicated to communicating with the Train Crew and the Sub-Foremen rather than also visually control workers, this is described as a separate Protecting Foreman. Example: See Track Worker Safety Instructions section 6.0 and CROR Rule 855

Rules of the Route: A document produced by Metrolinx identifying opportunities for working when trains are not running on some or all tracks in a location. Example: White Period Possessions

Safety Watch: A type of Non-Positive Protection defined in Section 5.0 of the Track Worker Safety Instructions.

Sub-foreman: Responsible for protecting a separated work group as per TWSI Section 6.0.

Train Crew: The operators of a train (the Qualified Commuter Train Operator and Commuter Train Operator on GO Trains; the Locomotive Engineers on Freight/VIA Rail trains)

White Period Possession: A Work Block typically after GO revenue service or during off-peak hours where existing train services are maintained with minimal impacts (Special Routing). Example: See “Rules of the Route” for specific times for each location on the network. Typically protected by a Rule 842 or Track Occupancy Permit.

Work Block: A continuous block of time when a rail corridor access is occurring at a site, lasting no more than 24hrs (except for Major Track Closures). A Work Block may have multiple Work Groups. Work Blocks should be entirely within a single Controlled Location and should have one continuous form of protection. Example: Mon Jan 3 from 06:00 – 17:30; MP 3.3 – MP 5.0; Track Occupancy Permit

Work Event: The rail corridor access work taking place, which typically lasts no longer than 1 week/7 days. A Work Event may have multiple Work Blocks within it. Example: Mon Jan 3 – Fri Jan 7; 06:00 – 17:30 each day; MP 3.3 – MP 5.0 Newmarket

Work Group / Work Zone: A group of people undertaking specific tasks in a defined area during a Work Block. Example: Work Group 1 – Track Work; Proposed Flagging Resources = 1

Work Plan: A document conforming to the Metrolinx standards describing the activities and work methods used by a Work Group/Zone during a Work Event or Work Block. Example: Track Work Plan on Newmarket Sub

Application Details

Application: MX Rail Cooridor Access Tool v4.0.15
Date Accessed: 03 April, 2025 12:11:30

Support

For questions, comments or other feedback, please email  NAPT.training@metrolinx.com

User Info

Assigned Projects

Administered Projects

Admin Dashboard





Note: If a user has been created and deleted multiple times, the Date_Added field will refer to the most recent creation. Also, users that were created through a batch upload may not have a Date_Added value.

Loading...
Loading...
Download User Info
Download User Project Assignments
Download Project Information

User Session Information


Loading...

Create User

Edit User



Delete User