Systems and methods for scheduling track maintenance

Abstract

To provide a system and a method allowing more accurate reporting of the number of cancelled maintenance time slots, the amount of time maintenance operators spend waiting for maintenance to begin, and hourly cost incurred by a company for those hours.SOLUTION: In one embodiment, a method includes the steps of: generating a first visual representation for a location of a railroad station associated with a railroad track; receiving a request for a first maintenance time slot; and determining that the first maintenance time slot is associated with the railroad station. The method further includes the steps of: determining a first time period; and generating a second visual representation of information associated with the railroad station during the first time period. The information includes an indication of a time that a train is scheduled to cross the railroad station during the time period. The information also includes an indication of a time duration of the second maintenance time slot requested during the time period.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] TECHNICAL FIELD This disclosure relates generally to track maintenance, and more specifically to a system and method for scheduling track maintenance. [Background technology]

[0002] A train dispatcher directs and facilitates train movement in an assigned area (e.g., rail operations). The dispatcher is responsible for scheduling rail maintenance and ensuring that the rail tracks are clear during scheduled maintenance. Although train dispatchers may use existing capacity planning tools to assist in scheduling maintenance windows, these capacity planning tools are often unreliable and inefficient. Summary of the Invention [Means for solving the problem]

[0003] Aspects of the invention are set out in the independent claims and preferred features are set out in the dependent claims. Features of one aspect may be applied to any aspect alone or in combination with other aspects.

[0004] According to one embodiment, the method includes generating a first visual representation for a location of a railroad station relative to the railroad track, receiving a request for a first maintenance window, and determining that the first maintenance window is associated with the railroad station. The method further includes determining a first time period and generating a second visual representation of information associated with the railroad station during the first time period. The information includes an indication of a time when a train is scheduled to pass through the railroad station during the time period. The information also includes an indication of a time duration of a requested second maintenance window during the time period. The request for the first maintenance window may include a name of a maintenance crew, a requested duration for the first maintenance window, and a description of the maintenance.

[0005] In certain embodiments, the method includes scheduling a first maintenance window within the first time period based on the second visual representation. In some embodiments, the method includes determining, based on the second visual representation, that a duration requested for the first maintenance window conflicts with a time scheduled to pass through the rail station during the first time period, and selecting the second time period. In certain embodiments, the method includes determining, based on the second visual representation, that a duration for the first maintenance window conflicts with a duration of a second maintenance window during the first time period, and selecting the second time period.

[0006] In some embodiments, the method includes generating locations of a plurality of rail stations associated with a plurality of rail tracks in a first visual representation, determining whether a request for the first maintenance window is associated with a subset of the plurality of rail stations, and generating information associated with the subset of the plurality of rail stations in a second visual representation. In certain embodiments, the method includes generating a map view displaying the first maintenance window, and generating a calendar displaying dates and durations for the first maintenance window.

[0007] According to another embodiment, a system includes one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including generating a first visual representation for a location of a train station associated with a railroad track, receiving a request for a first maintenance window, and determining that the first maintenance window is associated with the train station. The operations further include determining a first time period and generating a second visual representation of information associated with the train station during the first time period. The information includes an indication of a time when a train is scheduled to pass through the train station during the time period. The information also includes an indication of a duration of a requested second maintenance window during the time period.

[0008] According to yet another embodiment, one or more computer-readable storage media storing instructions that, when executed by a processor, cause the processor to perform operations including generating a first visual representation for a location of a railroad station associated with a railroad track, receiving a request for a first maintenance window, and determining that the first maintenance window is associated with the railroad station. The operations further include determining a first time period and generating a second visual representation of information associated with the railroad station during the first time period. The information includes an indication of a time when a train is scheduled to pass through the railroad station during the time period. The information also includes an indication of a duration of a requested second maintenance window during the time period.

[0009] Technical advantages of certain embodiments of the present disclosure may include one or more of the following: Certain systems and methods described herein include maintenance planning tools that help maximize railroad track capacity through visualization of traffic gaps. The maintenance planning tools help reduce idle time in capacity-limited operating subdivisions. The maintenance planning tools can reduce or prevent train delays. The systems and methods described herein use visual aids to enable more accurate maintenance compliance reporting compared to traditional non-visual systems and methods for scheduling track maintenance. For example, the systems and methods described herein may more accurately report the number of canceled maintenance windows, the amount of time maintenance crews spend waiting for maintenance to begin, the hourly cost incurred by the company for those hours, etc.

[0010] The disclosed maintenance planning tools allow users to maximize visual gaps in train flow. The systems and methods described herein for scheduling track maintenance provide more proactive decision making compared to conventional systems. For example, maintenance crews, maintenance planners, and / or dispatchers can quickly and proactively identify and move maintenance to gaps in train flow. The systems and methods described herein reduce maintenance costs by reducing maintenance crew starts / discontinuances, reducing the time maintenance crews wait to start maintenance, and reducing canceled maintenance windows.

[0011] Other technical advantages will be readily apparent to one skilled in the art from the following figures, descriptions, and claims. Additionally, although certain advantages have been described above, various embodiments may include all, some, or none of the listed advantages.

[0012] For an aid in understanding the present disclosure, reference is made to the following descriptions taken in conjunction with the accompanying drawings. [Brief description of the drawings]

[0013] [Figure 1] 1 illustrates an exemplary system for scheduling track maintenance. [Diagram 2] 2 shows a screenshot generated by a maintenance planning tool that may be used by the system of FIG. 1; [Diagram 3] 1 illustrates an exemplary method for scheduling track maintenance. [Figure 4] 1 illustrates an exemplary computer system that may be used by the systems and methods described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Certain embodiments of the present disclosure include systems and methods for scheduling track maintenance using a maintenance visual planning tool. The maintenance visual planning tool allows users (e.g., maintenance planners and corridor superintendent) to visualize traffic gaps in advance. Figures 1-5 illustrate an exemplary system and method for scheduling track maintenance. Figure 1 illustrates an exemplary system for scheduling track maintenance, and Figure 2 illustrates a screenshot generated by a maintenance planning tool that may be used by the system of Figure 1. Figure 3 illustrates an exemplary method for scheduling track maintenance. Figure 4 illustrates an exemplary computer system that may be used by the systems and methods described herein.

[0015] FIG. 1 illustrates an example system 100 for scheduling track maintenance. The system 100 of FIG. 1 includes a network 110, user equipment (UE) 120a, UE 120b, a user 122a, a user 122b, a maintenance request 124, a network operations center 130, a maintenance planning tool 140, and a maintenance reply 144. The system 100, or portions thereof, may be associated with an entity, which may include any entity, such as a business, company (e.g., railroad company, transportation company, etc.), or government agency (e.g., transportation department, public safety department, etc.) that may schedule maintenance. Although the illustrated embodiment of FIG. 1 is associated with a railroad system, the system 100 may be associated with any suitable transportation system (e.g., vehicle / road, ship / water, etc.).

[0016] The elements of system 100 may be implemented using any suitable combination of hardware, firmware, and software. For example, one or more components of system 100 may use one or more components of FIG.

[0017] Network 110 of system 100 may be any type of network that facilitates communication between components of system 100. For example, network 110 may connect UE 120a of system 100 to UE 120b of system 100. Although this disclosure illustrates network 110 being a particular type of network, this disclosure contemplates any suitable network. One or more portions of network 110 may include an ad-hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the public switched telephone network (PSTN), a cellular network, a 3G network, a 4G network, a 5G network, a Long Term Evolution (LTE) cellular network, a combination of two or more of these, or any other suitable type of network. One or more portions of network 110 may include one or more access (e.g., mobile access), core and / or edge networks. The network 110 may be any communication network, such as a private network, a public network, a connection via the Internet, a mobile network, a WI-FI network, a Bluetooth network, etc. The network 110 may include a cloud computing capability. One or more components of the system 100 may communicate over the network 110. For example, the UE 120a may communicate over the network 110, including communicating information (e.g., a maintenance request 124) to the UE 122b and / or receiving information (e.g., a maintenance response 144) from the UE 120b.

[0018] The UE 120a of the system 100 includes any device capable of receiving, generating, processing, storing, and / or communicating information. For example, the UE 120a of the system 100 may communicate information (e.g., maintenance request 124) to the UE 120b and / or receive information (e.g., maintenance response 144) from the UE 120b. In a particular embodiment, the UE 120a is used directly by the user 122a. The UE 120a may be a mobile phone (e.g., a smartphone), a personal digital assistant, a wearable computer, a laptop computer, a desktop computer, etc. In the embodiment shown in FIG. 1, the UE 120a is a mobile device. The UE 120a may include a liquid crystal display (LCD), an organic light emitting diode (OLED) flat screen interface, digital buttons, a digital keyboard, physical buttons, a physical keyboard, one or more touch screen components, a graphic user interface (GUI), etc.

[0019] In certain embodiments, the UE 120a utilizes one or more applications. The applications of the UE 120a may include native applications built for a particular operating system, mobile web applications that render and / or deliver pages in a browser, etc. The browser of the UE 120a is a software application for accessing information on the World Wide Web. The one or more browsers may be optimized to effectively display web content on a small screen.

[0020] A user 122a of the system 100 is any person, organization, or software program that uses a UE 120a. For example, a user 122a may be an engineer (e.g., a project engineer), a supervisor (e.g., a signal supervisor), a director (e.g., a signal director), a technician (e.g., an electronic technician), etc. A user 122a may use a UE 120b. For example, a user 122a may generate a maintenance request 124 using a UE 120b.

[0021] A maintenance request 124 of the system 100 is a request to schedule maintenance in a particular area (e.g., a railroad subdivision). The maintenance request 124 may include the name of the crew assigned to perform the maintenance, a location indicating where the maintenance is to be performed, a description of the work to be performed, the duration the maintenance is requested to be performed, the date the maintenance is requested to be performed, etc. The name of the crew assigned to perform the maintenance may be the name of a maintenance crew, a production gang, etc. The crew name may be expressed as crew initials, crew number, crew letter, symbol, etc.

[0022] In the maintenance request 124, the location indicating where the maintenance is to be performed may refer to any physical location. The location may be represented by an address (e.g., a street address), coordinates (e.g., Global Positioning System (GPS) coordinates), a marker (e.g., a train station, train signal, control point, mile marker, etc.), combinations of the above, etc. In the maintenance request 124, the description of the work to be performed may include a description of the maintenance to a track structure, a signal, or a bridge, etc. For example, the description may be "rail defect repair and welding for slow order," "improvement and repair of slide fence," "replacement of rail," etc. The duration required for the maintenance may be represented in days, hours, minutes, etc.

[0023] The user 122a may generate a maintenance request 124 using one or more applications executing on the UE 120a. The maintenance request 124 may be a written communication (e.g., email, memo, etc.), an oral communication (e.g., phone call, voicemail, etc.), a video communication (e.g., video clip, FaceTime, etc.), etc. The maintenance request 124 may include one or more words (e.g., a sentence, a paragraph, etc.), a picture (e.g., a picture of a repair site), etc. In a particular embodiment, the user 122a generates the maintenance request 124 and communicates the maintenance request 124 to the network operations center 130 over the network 110.

[0024] The network operations center 130 of the system 100 is a facility with one or more locations housing support staff that manages transportation-related traffic. For example, the network operations center 130 may monitor, manage, and / or control train movements across a state, providence, etc. The network operations center 130 may include transportation planning technology to facilitate collaboration between users 120a (e.g., engineers) and users 120b (e.g., dispatchers). In certain embodiments, the network operations center 130 includes conference rooms, televisions, workstations, etc. Each workstation may include a UE 120b operated by a user 122b. In the embodiment shown in FIG. 1, the network operations center 130 includes the UE 120b, the users 122b, and the maintenance planning tool 140.

[0025] The UE 120b of the system 100 includes any device capable of receiving, generating, processing, storing, and / or communicating information. For example, the UE 120b of the system 100 may communicate information (e.g., maintenance response 144) to the UE 120a and / or receive information (e.g., maintenance request 124) from the UE 120a. In a particular embodiment, the UE 120b is used directly by the user 122b. The UE 120a may be a desktop computer, a laptop computer, a mobile phone (e.g., a smartphone), a tablet, a personal digital assistant, a wearable computer, etc. In the embodiment shown in FIG. 1, the UE 120b is a desktop computer. It may include a liquid crystal display (LCD), an organic light emitting diode (OLED) flat screen interface, digital buttons, a digital keyboard, physical buttons, a physical keyboard, one or more touch screen components, a graphic user interface (GUI), etc.

[0026] In particular embodiments, UE 120b uses one or more applications (e.g., maintenance planning tool 140). The applications of UE 120b may include native applications built for a particular operating system, mobile web applications that render and / or deliver pages in a browser, planning applications, etc. In the embodiment shown in FIG. 1, UE 120b uses maintenance planning tool 140.

[0027] A user 122b of the system 100 is any person, organization, or software program that uses a UE 120b. For example, the user 122b may be a dispatcher (e.g., a train dispatcher), support staff, a crew member, an engineer, a team member (e.g., a machine team member), a maintenance planner, a superintendent (e.g., a passage manager), etc. In certain embodiments, the user 122b manages transportation-related traffic. For example, the user 122b may authorize the movement of trains across one or more regions (e.g., a state, territory, subdivision, division, district, etc.). The user 122b may use the UE 120b. For example, the user 122b may use the UE 120b to schedule one or more maintenance windows using the maintenance planning tool 140.

[0028] The maintenance planning tool 140 of the system 100 is a visual project management tool that allows the user 122b to visualize traffic gaps. The maintenance planning tool 140 can be used to generate one or more images (e.g., screenshot 200 of FIG. 2). In certain embodiments, the image shows a request for a maintenance window. The request can include the name of the worker, the requested duration of the requested maintenance window, and a description of the maintenance.

[0029] In some embodiments, an image generated by the maintenance planning tool 140 shows the location of one or more railroad stations associated with one or more railroad tracks. For example, an image generated by the maintenance planning tool 140 may show the location of 50 railroad stations along a particular subdivision of railroad tracks. In particular embodiments, the image shows the location of requested maintenance windows associated with the railroad stations and the railroad tracks. In some embodiments, an image generated by the maintenance planning tool 140 shows information associated with the railroad stations during a particular time period. The information displayed in the image may include an indication of the times when trains are scheduled to pass through the railroad stations during the particular time period. The information displayed in the image may include an indication of the duration for requested maintenance windows during the particular time period.

[0030] In certain embodiments, the maintenance planning tool 140 allows the user 122b to select a particular time period. For example, the user 122b may select a 24 hour period over the course of a day or two, and the maintenance planning tool 140 may generate a snapshot of information related to the railroad environment during that particular 24 hour period. As another example, the user 122b may select a 5 day period associated with a particular date, and the maintenance planning tool 140 may generate a snapshot of information related to the railroad environment during the particular 5 day period.

[0031] The visual images generated by the maintenance planning tool 140 may assist the user 122b in scheduling the maintenance request 124. For example, the images may show a conflict between a requested maintenance location and a train passing a particular location at a particular time. As another example, the images may show a conflict during a maintenance window of the maintenance request 124 with a previously requested and / or scheduled maintenance window. The user 122b may use one or more images generated by the maintenance planning tool 140 to schedule the maintenance request 124 between a gap in traffic. After scheduling the maintenance request 124, the user 122b may generate a maintenance response 144.

[0032] The maintenance response 144 of the system 100 is a response to the maintenance request 124. The maintenance response 144 may include a maintenance window indicating a particular time when the requested maintenance is scheduled to be performed. The maintenance window may include a duration (e.g., 6 hours), a particular date (e.g., January 1, 2020), an assigned start time for the maintenance (e.g., January 1, 2020 at 6:00 AM), an assigned end time for the maintenance (e.g., January 1, 2020 at 2:00 PM), etc. The maintenance response 144 may include the name of the laborer assigned to perform the maintenance, a location indicating where the maintenance will be performed, a description for the work to be performed, etc. In certain embodiments, the user 122b generates the maintenance response 144 and communicates the maintenance response 144 to the UE 120a via the network 110. The maintenance response 144 may be a written communication (e.g., email, memo, etc.), a verbal communication (e.g., phone call, voicemail, etc.), a video communication (e.g., video clip, FaceTime, etc.), etc. obtain.

[0033] In operation, a user 122a (e.g., a train engineer) determines that maintenance needs to be performed at a particular railroad station along the railroad track of a particular railroad subdivision. The user 122a uses the UE 120a to generate a maintenance request 124. The maintenance request 124 includes the particular railroad station where the maintenance is to be performed, the name of the worker who will perform the maintenance, the requested duration for the maintenance (e.g., 6 hours), and a description of the maintenance. The maintenance request 124 is communicated from the UE 120a to a network operations center 130 via the network 110.

[0034] A user 122b of the network operations center 130 receives the maintenance request 124 via the UE 120b. The user 122b forecasts a time period for scheduling a maintenance window. Using the maintenance planning tool 140, the user 122b selects a time period (e.g., a 48 hour period starting on January 1, 2020 at 6:00 AM and ending on January 3, 2020 at 6:00 AM). The maintenance planning tool 140 generates a first visual representation of the railroad environment in the particular subdivision where the maintenance will be performed. The first visual representation includes the location of the railroad stations relative to the railroad tracks. The user 122b selects the railroad station from the first visual representation where the maintenance will be performed. In response to the selection of the railroad station, the maintenance planning tool 140 generates a second visual representation of information related to the selected railroad station during the first time period. This information includes an indication of the time when a train is scheduled to pass through the railroad station during the selected time period. This information also includes an indication of the duration for previously requested and / or scheduled maintenance windows during the selected time period. The first visual representation and the second visual representation are displayed as a single image (eg, screenshot 200 of FIG. 2) on UE 120b.

[0035] The user 122b determines to schedule a maintenance window for the maintenance request 124 during a selected time period using the imagery. For example, the user 122b may determine from the imagery that there are no train crossings or previously requested / scheduled maintenance windows within a six hour period beginning on January 1, 2020 at 6:00 AM and ending on January 1, 2020 at 2:00 PM. As a result of this determination, the user 122b may schedule a maintenance window from January 1, 2020 at 6:00 AM to January 1, 2020 at 2:00 PM. The user 122b generates a maintenance response 144 using the UE 120b that includes information related to the scheduled maintenance window. The UE 120b communicates the maintenance response 144 to the UE 120a via the network 110. In this manner, the system 100 of FIG. 1 allows the user 122b to maximize visual gaps in the train flow, which may reduce idle time in capacity limited operational subdivisions.

[0036] 1 illustrates a particular arrangement of the network 110, the UE 120a, the user 122a, the maintenance request 124, the network operations center 130, the maintenance planning tool 140, the UE 120b, the user 122b, and the maintenance response 144, this disclosure contemplates any suitable arrangement of the network 110, the UE 120a, the user 122a, the maintenance request 124, the network operations center 130, the maintenance planning tool 140, the UE 120b, the user 122b, and the maintenance response 144. For example, the maintenance planning tool 140 may operate on the UE 120a instead of the UE 120b. As another example, the user 122a may schedule a maintenance window using the maintenance planning tool 140 of the UE 120 instead of generating the maintenance request 124.

[0037] 1 illustrates a particular number of networks 110, UEs 120a, users 122a, maintenance requests 124, network operations centers 130, maintenance planning tools 140, UEs 120b, users 122b, and maintenance responses 144, this disclosure contemplates any suitable number of networks 110, UEs 120a, users 122a, maintenance requests 124, network operations centers 130, maintenance planning tools 140, UEs 120b, users 122b, and maintenance responses 144. For example, FIG. 1 may include multiple maintenance requests 124 and / or multiple maintenance responses 144.

[0038] Figure 2 illustrates an example screenshot 200 that may be generated by the visual planning tool 140 of the system 100 of Figure 1. The screenshot 200 is an image that is displayed on a computer (e.g., the UE 120b of Figure 1) at a particular point in time. The screenshot 200 shows an overview of a subdivision 202. The screenshot 200 includes tabs 210, maintenance requests 220, maintenance request information 230, tracks 240, rows 242, stations 250, maintenance locations 252, rows 254, trains 260, maintenance windows 270, and durations 280.

[0039] The tabs 210 of the screenshot 200 are navigational elements used to allow a user (e.g., user 122b of FIG. 1) to access other areas of the maintenance planning tool 140. Selecting (e.g., clicking or tapping) a tab 210 directs the user to the tab-related content. In the embodiment shown in FIG. 2, the tabs 210 include a planner tab 212, a calendar tab 214, an assignments tab 216, and a map tab 218. The planner tab 210 of the screenshot 200 may be used to schedule a maintenance request. In the screenshot 200 of FIG. 2, the planner tab 210 is selected. The calendar tab 214 of the screenshot 200 may be used to display a calendar that includes one or more maintenance requests. For example, the calendar may show specific dates and / or times for requests and / or scheduled maintenance windows.

[0040] The assignments tab 216 of the screenshot 200 may be used to display one or more maintenance-related assignments. The assignments may be provided in list format. Each maintenance-related assignment may include the name of the maintenance worker, the subdivision where the maintenance is to be performed, the date of the scheduled / requested maintenance, the number of maintenance windows requested per maintenance request, the location of the scheduled maintenance (e.g., start / end mile posts, start / end control points, etc.), the number of tracks affected by the maintenance, the start time of the maintenance, the duration of the maintenance, a description of the maintenance to be performed, etc.

[0041] The map tab 218 of screenshot 200 displays a map of requested / scheduled maintenance locations. The map is a graphical representation of the area affected by the maintenance. The map may show the geographic location of train stations where maintenance is scheduled in a particular area (e.g., subdivision 202). Each location where maintenance is scheduled can be marked. The marking may include information about the scheduled maintenance (e.g., name of the maintenance worker, date / time / duration of the scheduled maintenance, etc.).

[0042] The maintenance requests 220 of the screenshot 200 indicate the number of maintenance requests received by the maintenance planning tool 140. Each maintenance request 220 is represented by a shape. The first maintenance request 220 is represented by a circle and the second maintenance request 220 is represented by a square. In a particular embodiment, the maintenance requests 220 are classified as either uncommitted or committed. An uncommitted maintenance request 220 is a maintenance request that is not scheduled. For example, an uncommitted maintenance request 220 may include a maintenance request that is not authorized by a dispatcher. A committed maintenance request 220 is a scheduled request. For example, a committed maintenance request 220 may include a maintenance request that is approved by a dispatcher. The illustrated embodiment of FIG. 1 shows five uncommitted maintenance requests 220 and no committed maintenance requests 220.

[0043] The maintenance request information 230 in screenshot 200 is information contained in the received maintenance request 220. The maintenance request information 230 includes the name of the worker (e.g., CDW), the requested maintenance time slot (e.g., 6 hours), the maintenance location (e.g., Station 40 to Station 42), and any comments related to the maintenance (e.g., rail defect repair and welding with speed limit order). The maintenance request information 230 is specific to the particular maintenance request 220. In the embodiment shown in FIG. 1, a circular maintenance request 220 was selected. If the user selects a square maintenance request 220, the maintenance request information 230 changes to reflect the information contained in the square maintenance request 220.

[0044] Track 240 in screenshot 200 is a graphical representation of the railroad tracks of subdivision 202. Track 240 is represented as one or more lines in rows 242. The lines representing track 240 are divided between rows 242 to allow a user of the maintenance planning tool to visualize the entire track 240 in one image. A single line represents a single track 240 and a double line represents a double track 240.

[0045] The stations 250 in screenshot 200 are markers indicating particular locations along the track 240. The stations 250 may represent one or more railroad stations, control points, railroad signals, distance markers, combinations thereof, or any other suitable markers that may be used to indicate particular locations along the track 240. In screenshot 200 of FIG. 2, each station 250 is represented by a point along the track 240. In certain embodiments, the stations 250 may be labeled with a station name and / or number, a control point name and / or number, a distance marker number, etc. In the embodiment shown in FIG. 2, the stations 250 are labeled as station numbers 1 through 42.

[0046] Maintenance locations 252 include stations 250 affected by maintenance calls 220. Maintenance locations 252 include stations 250 numbered 40 through 42. In screenshot 200, maintenance locations 252 correspond to the locations provided in maintenance call information 230 for circular maintenance calls 220. If a square maintenance call 220 is selected, maintenance locations 252 changes to include stations 250 affected by the selected square maintenance call 220.

[0047] Rows 254 of screenshot 200 indicate stations 250 included in maintenance location 252. A first row 254 indicates station 40, a second row 254 indicates station 41, and a third row 254 indicates station 42. Each row includes markings indicating activity occurring within a particular time period 280. Time period 280 may extend over any suitable time frame (e.g., hours, days, or weeks). In the embodiment shown in FIG. 2, time period 280 begins at 4:00 a.m. on Wednesday, November 27th and ends at midnight on Friday, November 29th. Time period 280 may be selected and / or changed by a user (e.g., a dispatcher). For example, a train dispatcher may use a mouse to scroll in to a shorter time period 280 (e.g., 24 hours) and / or scroll out to a longer time period (e.g., 7 days).

[0048] The trains 260 in screenshot 200 are represented by vertical lines in rows 254. Each vertical line indicates a time that the train 260 passes through a particular station 250 according to time period 280. For example, in the first row 254, the train 260 represented by the first vertical line indicates that the train 260 passes through station 40 at 4:00 a.m. The illustrated embodiment of FIG. 2 uses vertical line notation to indicate the train 260, but any suitable notation (e.g., character, letter, number, color, and / or shape) may be used to represent the train 260. In certain embodiments, the train notation may be different to indicate various types of trains 260. For example, a thin vertical line may indicate a shuttle train, while a thick vertical line may indicate a destination efficient train. As another example, an asterisk may indicate a unit train of coal, and a hashtag may indicate a unit train of grain.

[0049] The maintenance windows 270 in screenshot 200 are represented as shaded blocks in rows 254. The beginning of each shaded block indicates a scheduled start time for each maintenance window 270, and the end of each shaded block indicates a scheduled end time for each maintenance window 270. For example, in the first row 254, the maintenance window 270 represented by the first block indicates that the maintenance window 270 is scheduled from 7:30 PM on Wednesday, November 27th to 3:00 AM on Thursday, November 28th. Although the illustrated embodiment of FIG. 2 uses shaded block notation to indicate the maintenance window 270, any suitable notation (e.g., letters, characters, numbers, colors, and / or shapes) may be used to indicate the maintenance window 270.

[0050] In this manner, screenshot 200 of FIG. 2 provides a visual aid that enables a user of maintenance planning tool 140 of FIG. 1 to maximize train flow and visual gaps during maintenance windows, which may provide more efficient maintenance scheduling by reducing idle time in capacity-limited operational subdivisions.

[0051] 2 illustrates a particular arrangement of tabs 210, maintenance requests 220, maintenance request information 230, tracks 240, rows 242, stations 250, maintenance locations 252, rows 254, trains 260, maintenance windows 270, and time periods 280, this disclosure contemplates any suitable arrangement of tabs 210, maintenance requests 220, maintenance request information 230, tracks 240, rows 242, stations 250, maintenance locations 252, rows 254, trains 260, maintenance windows 270, and time periods 280. For example, tabs 210 and / or maintenance request information 230 may be displayed in a different order. As another example, time period 280 may span more than three days or less than three days.

[0052] 2 depicts a particular number of tabs 210, maintenance requests 220, maintenance request information 230, tracks 240, rows 242, stations 250, maintenance locations 252, rows 254, trains 260, maintenance windows 270, and periods 280, this disclosure contemplates any suitable number of tabs 210, maintenance requests 220, maintenance request information 230, tracks 240, rows 242, stations 250, maintenance locations 252, rows 254, trains 260, maintenance windows 270, and periods 280. For example, FIG. 2 may include more or less than 42 stations. Although screenshot 200 in FIG. 2 is associated with a railroad system, screenshot 200 may be associated with any suitable transportation system (e.g., vehicle / road, ship / water, etc.).

[0053] Figure 3 illustrates an example method 300 for scheduling track maintenance. Method 300 begins at step 310. At step 320, a maintenance planning tool (e.g., maintenance planning tool 140 of Figure 1) generates a first visual representation of locations of rail stations relative to the railroad track. For example, with reference to Figure 2, the maintenance planning tool may generate stations 1 through 42 on track 240 of subdivision 202. Method 300 then moves from step 320 to step 330.

[0054] In step 330, the maintenance planning tool receives a maintenance request. For example, a train engineer (e.g., user 122a in FIG. 1 ) may determine that maintenance needs to be performed at a particular train station in a particular subdivision. The train engineer uses a mobile phone (e.g., UE 120a in FIG. 1 ) to generate a maintenance request (e.g., maintenance request 124 in FIG. 1 ). The maintenance request may include the particular train station where the maintenance will be performed, the name of the worker performing the maintenance, the duration of the maintenance request (e.g., 6 hours), and a description of the maintenance. The train engineer transmits the maintenance request to a dispatcher (e.g., user 122b in FIG. 1 ) at a network operations center (e.g., network operations center 130 in FIG. 1 ). The dispatcher processes the maintenance request using the maintenance planning tool. Method 300 then moves from step 330 to step 340.

[0055] In step 340, the maintenance planning tool determines that the maintenance request is associated with a particular subset of rail stations. For example, the maintenance planning tool may determine from information provided in the maintenance request that the requested maintenance will affect stations 40 through 42 of subdivision 202. The maintenance planning tool may emphasize (e.g., highlight, shade, etc.) stations 40 through 42 in a first visual representation that allows a user of the maintenance planning tool to visually identify the affected stations. Method 300 then moves from step 340 to step 350.

[0056] In step 350, a user of the maintenance planning tool predicts a time period for scheduling the requested maintenance. For example, a dispatcher may predict that the maintenance can be scheduled from 4:00 a.m. on November 27th to midnight on November 29th based on a requested 6 hour maintenance window included in the maintenance request. The dispatcher may then use the maintenance planning tool to select that particular time period. The method then moves from step 350 to step 360.

[0057] At step 360, the maintenance planning tool generates a second visual representation of information related to the selected rail station during the selected time period. In certain embodiments, this information includes an indication of times when trains are scheduled to pass through the rail station during the selected time period. For example, the second visual representation may show lines indicating trains passing at particular times during the selected time period. In some embodiments, this information includes an indication of durations of previously requested and / or scheduled maintenance windows during the selected time period. For example, the second visual representation may show cross-hatched blocks indicating start times and end times of previously requested and / or scheduled maintenance windows. The first visual representation and the second visual representation may be displayed as a single image (e.g., screenshot 200 of FIG. 2) on the dispatcher's device. Method 300 then moves from step 360 to step 370.

[0058] In step 370, the dispatcher determines whether the information in the second visual representation indicates that a previously requested / scheduled maintenance window or train crossing will interfere with the requested maintenance window. If the dispatcher determines that the information in the second visual representation does not interfere with the requested maintenance window (e.g., if the information does not indicate a previously requested / scheduled maintenance window or train crossing within the requested maintenance window) or if the interference is permissible, method 300 moves from step 370 to step 380.

[0059] In step 380, the dispatcher schedules a maintenance window during the predicted time period. For example, the requested maintenance window may be six hours and the second visual representation may indicate that station 40 to station 42 has a six hour gap (e.g., from noon to 6pm on November 27) within the selected time period that does not show a previously requested / scheduled maintenance window and / or train crossing. The dispatcher then schedules the maintenance window for the six hours. As another example, the requested maintenance window may be six hours and the second visual representation may indicate that station 40 to station 42 has a six hour time slot (e.g., from noon to 6pm on November 27) within the selected time period with only one conflict (e.g., train crossing or scheduled maintenance window). The dispatcher then resolves the conflict (e.g., delaying a train or rescheduling the scheduled maintenance window) and schedules the requested maintenance window for that six hour time slot.

[0060] If, in step 370, the dispatcher determines that the information in the second visual representation indicates a previously requested / scheduled maintenance window and / or a train crossing within a requested maintenance window that cannot be rescheduled, method 370 moves again to step 350 where the dispatcher selects another time period for scheduling a maintenance window. For example, the dispatcher may select the time period from midnight on November 29th to midnight on December 3rd. Steps 360 through 380 are then repeated until the dispatcher determines that the information in the second visual representation does not indicate a previously requested / scheduled unresolvable maintenance window and / or a train crossing within a requested maintenance window. Method 300 then moves from step 380 to step 390, where method 300 ends.

[0061] Modifications, additions, or omissions may be made to the method 300 shown in Figure 3. Method 300 may include more, fewer, or other steps. For example, method 300 may include generating a maintenance response (e.g., maintenance response 144 of Figure 1) and communicating the maintenance response to a train engineer. Method 300 may relate to any suitable transportation system (e.g., vehicle / road, ship / water, etc.).

[0062] The steps may be performed in parallel or in any suitable order. For example, generating a first visual representation 320 may occur after receiving a maintenance request 330. Although discussed as specific components completing steps of method 300, any suitable component may perform any step of method 300. For example, one or more steps of method 300 may be automated using one or more components of the computer system of FIG.

[0063] 4 illustrates an example computer system that may be used by the systems and methods described herein. For example, network 110, UE 120a, and / or UE 120b of FIG. 1 may include one or more interfaces 410, processing circuitry 420, memory 430, and / or other suitable elements. Interface 410 (e.g., interface 122 of FIG. 1) receives input, sends output, processes the input and / or output, and / or performs other suitable operations. Interface 410 may include hardware and / or software.

[0064] The processing circuitry 420 (e.g., processor 126 of FIG. 1) executes or manages the operation of the components. The processing circuitry 420 may include hardware and / or software. Examples of processing circuitry include one or more computers, one or more microprocessors, one or more applications, etc. In certain embodiments, the processing circuitry 420 executes logic (e.g., instructions) to perform actions (e.g., operations), such as generating an output from an input. The logic executed by the processing circuitry 420 may be encoded in one or more tangible, non-transitory computer-readable media (e.g., memory 430). For example, the logic may include a computer program, software, computer-executable instructions, and / or instructions that are executable by a computer. In certain embodiments, the operations of the embodiments may be performed by one or more computer-readable media storing, embodied, and / or encoding a computer program, and / or having a computer program stored and / or encoded therein.

[0065] The memory 430 (or memory unit) stores information. The memory 430 (e.g., memory 124 of FIG. 1) may include one or more non-transitory, tangible, computer-readable, and / or computer-executable storage media. Examples of the memory 430 include computer memory (e.g., RAM or ROM), mass storage media (e.g., hard disks), removable storage media (e.g., compact discs (CDs) or digital video discs (DVDs)), databases and / or network storage (e.g., servers), and / or other computer-readable media.

[0066] An embodiment of the present disclosure relates to a system and method for generating a first visual representation for a location of a railway station associated with a railway track, receiving a request for a first maintenance window, and determining that the first maintenance window is associated with the railway station. The method further includes determining a first time period and generating a second visual representation of information associated with the railway station during the first time period. The information includes an indication of the time when a train is scheduled to pass through the railway station during the time period. The information also includes an indication of the duration of a requested second maintenance window during the time period. The request for the first maintenance window may include the name of a maintenance worker, the requested duration for the first maintenance window, and a description of the maintenance.

[0067] As used herein, a computer-readable non-transitory storage medium or media may include one or more semiconductor-based or other integrated circuits (ICs) (e.g., field programmable gate arrays (FPGAs) or application specific integrated circuits (ASICs)), hard disk drives (HDDs), hybrid hard drives (HHDs), optical disks, optical disk drives (ODDs), magneto-optical disks, magneto-optical drives, floppy disks, floppy disk drives (FDDs), magnetic tapes, solid state drives (SSDs), RAM drives, secure digital (SD) cards or drives, other suitable computer-readable non-transitory storage media, or any suitable combination of two or more thereof, as appropriate. A computer-readable non-transitory storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, as appropriate.

[0068] In this specification, "or" is inclusive and not exclusive, unless expressly indicated otherwise or the context indicates otherwise. Thus, in this specification, "A or B" means "A, B, or both" unless expressly indicated otherwise or the context indicates otherwise. Also, "and" means jointly and plurally, unless expressly indicated otherwise or the context indicates otherwise. Thus, in this specification, "A and B" means "A and B, jointly or severally," unless expressly indicated otherwise or the context indicates otherwise.

[0069] The scope of the present disclosure includes all changes, substitutions, variations, modifications, and alterations to the exemplary embodiments described or illustrated herein that can be understood by a person skilled in the art. The scope of the present disclosure is not limited to the exemplary embodiments described or illustrated herein. Furthermore, although the present disclosure describes and illustrates each embodiment herein as including certain components, elements, features, functions, operations, or steps, any of these embodiments may include any combination or permutation of the components, elements, features, functions, operations, or steps described or illustrated anywhere herein that can be understood by a person skilled in the art. Furthermore, in the appended claims, a reference to an apparatus or system component that is adapted, arranged, capable, configured, enabled, operable, or operative to perform a particular function includes the apparatus, system, component, or particular function activated, turned on, or unlocked, so long as the apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operative, or operative. Moreover, although this disclosure describes or illustrates particular embodiments as providing certain advantages, the particular embodiment may provide none, some, or all of these advantages.

Claims

1. 1. A method comprising: generating a first visual representation of a location of a railway station relative to the railway line; receiving a request for a first maintenance window; determining that the first maintenance window is associated with the rail station; determining a first time period; generating a second visual representation of information related to the railway station during the first time period; Including, The information is an indication of the times that trains are scheduled to pass through said railway station during said period; an indication of the duration of a second maintenance window requested during said period; and Including, method.

2. The request for the first maintenance window comprises: The name of the maintenance worker, a requested duration for the first maintenance window; and Maintenance instructions and Including, The method of claim 1.

3. The method of claim 1 , further comprising scheduling the first maintenance window within the first time period based on the second visual representation.

4. determining, based on the second visual representation, that a requested duration for the first maintenance window conflicts with the time scheduled to pass through the rail station during the first time period; selecting a second time period; Further comprising: The method of claim 1.

5. determining, based on the second visual representation, that a duration for the first maintenance window conflicts with the duration of the second maintenance window during the first time period; selecting a second time period; Including, The method of claim 1.

6. generating in the first visual representation locations of a plurality of railroad stations associated with a plurality of railroad tracks; determining whether the request for the first maintenance window is associated with a subset of the plurality of rail stations; generating information relating to the subset of the plurality of railway stations in the second visual representation; Further comprising: The method of claim 1.

7. generating a map view displaying the first maintenance window; generating a calendar displaying dates and durations for the first maintenance window; Further comprising: The method of claim 1.

8. 1. A system comprising: one or more processors; A memory for storing instructions; Including, The instruction: When executed by one or more processors, causes the one or more processors to perform operations; The operation includes: generating a first visual representation of a location of a railway station relative to the railway line; receiving a request for a first maintenance time period; determining that the first maintenance window is associated with the rail station; determining a first time period; generating a second visual representation of information related to the railway station during the first time period; and Including, The information is an indication of the times that trains are scheduled to pass through said railway station during said period; an indication of the duration of a second maintenance window requested during said period; and Including, system.

9. The request for the first maintenance window comprises: The name of the maintenance worker, a requested duration for the first maintenance window; and Maintenance instructions and Including, The system of claim 8.

10. The system of claim 8 , further comprising an act of scheduling the first maintenance window within the first time period based on the second visual representation.

11. determining, based on the second visual representation, that a requested duration for the first maintenance window conflicts with the time scheduled to pass through the rail station during the first time period; An operation of selecting a second time period; Further comprising: The system of claim 8.

12. determining, based on the second visual representation, that a requested duration for the first maintenance window conflicts with the duration of the second maintenance window during the first time period; An operation of selecting a second time period; Further comprising: The system of claim 8.

13. generating in the first visual representation locations of a plurality of railroad stations associated with a plurality of railroad tracks; determining whether the request for the first maintenance window relates to a subset of the plurality of rail stations; generating information relating to the subset of the plurality of railway stations in the second visual representation; Further comprising: The system of claim 8.

14. generating a map view displaying the first maintenance time period; generating a calendar displaying dates and durations for the first maintenance window; Further comprising: The system of claim 8.

15. One or more computer-readable storage media, storing instructions which, when executed by a processor, cause the processor to perform operations; The operation includes: generating a first visual representation of a location of a railway station relative to the railway line; receiving a request for a first maintenance time period; determining that the first maintenance window is associated with the rail station; determining a first time period; generating a second visual representation of information related to the railway station during the first time period; and Including, The information is an indication of the times that trains are scheduled to pass through said railway station during said period; an indication of the duration of a second maintenance window requested during said period; and Including, One or more computer-readable storage media.

16. The request for the first maintenance window comprises: The name of the maintenance worker, a requested duration for the first maintenance window; and Maintenance instructions and Including, 16. One or more computer-readable storage media as recited in claim 15.

17. 16. The one or more computer-readable storage media of claim 15, further comprising an act of scheduling the first maintenance window within the first time period based on the second visual representation.

18. determining, based on the second visual representation, that a requested duration for the first maintenance window conflicts with the time scheduled to pass through the rail station during the first time period; An operation of selecting a second time period; Further comprising:

16. One or more computer-readable storage media as recited in claim 15.

19. determining, based on the second visual representation, that a requested duration for the first maintenance window conflicts with the duration of the second maintenance window during the first time period; An operation of selecting a second time period; Further comprising:

16. One or more computer-readable storage media as recited in claim 15.

20. generating in the first visual representation locations of a plurality of railroad stations associated with a plurality of railroad tracks; determining whether the request for the first maintenance window relates to a subset of the plurality of rail stations; generating information relating to the subset of the plurality of railway stations in the second visual representation; Further comprising:

16. One or more computer-readable storage media as recited in claim 15.

21. In the apparatus, means for generating a first visual representation of a location of a railway station relative to a railway line; means for receiving a request for a first maintenance window; means for determining that the first maintenance window is associated with the rail station; means for determining a first period of time; means for generating a second visual representation of information associated with the railway station during the first time period; Including, The information is an indication of the times that trains are scheduled to pass through said railway station during said period; and, an indication of the duration of a second maintenance window requested during said period; and Including, Device.

22. Apparatus according to claim 21, further comprising means for carrying out the method according to any one of claims 2 to 7.

23. A computer program, computer program product or computer readable medium comprising instructions which, when executed by a computer, cause the computer to perform the steps of the method of any one of claims 1 to 7.

Images