Rail & Transit

Rail scheduling consultant for stations, bridges and track

For rail owners and contractors: P6 schedule management, independent review and delay analysis built around track access, outage windows and host railroad operating requirements. We schedule new stations, rail bridges and trestles, and track production in active corridors, and keep the record straight when a promised window never opens.

Florida intercity rail, Orlando extension. Our scheduler ran owner's-side schedule, change and delay oversight across all four zones: an airport station, 35 miles of new corridor, a 129 mile upgrade in a live right of way, 37 bridges and 156 crossings.

PSP certified Primavera P6 Phase 2 rail program, all 4 zones 37 rail bridges Track access & outage windows Production tracking AACE RP 29R-03 & 52R-06
We know rail

What drives a rail schedule

A rail CPM built like a building schedule misses what drives the work. We build these gates into every rail network.

01Track access and outage windows, modeled with access activities, work calendars and justified constraints. Work inside an outage is planned to the hour.
02Shoofly and phased cutovers. Temporary track and tie-in weekends that cannot slip, each with its own logic and fallback window.
03Active corridor operations. Flagging, roadway worker protection and host railroad coordination gate every shift. On the FEC corridor, that means FECR freight and intercity passenger trains on the track you're working.
04Long-lead special trackwork. Turnouts, movable bridge components and signal equipment, each tracked from submittal to delivery ahead of the window it serves.
05The crossings program. Per-crossing closures sequenced with municipalities and maintenance of traffic, 156 on Zone 4 alone.
06Structures over water. Trestles, pile driving, crane and barge access and marine safety.
07Systems and activation at the end. Signal, communications, crossing activation and testing, where every upstream slip lands.
Stations

Station, platforms and track in one schedule

A station on an existing corridor is a building job, a platform job and a trackwork job stacked next to live trains. We build them as one P6 network so the governing path shows from day one.

01

The station building

Foundations, structure, envelope, MEP, vertical circulation and finishes, plus ticketing, wayfinding, passenger information and fare gates. Long-lead items (elevators, escalators, curtain wall, canopy steel) drive the back end.

02

Platforms and canopies

Platform foundations and edge, canopy steel, finishes, lighting and ADA tactile edge, all tied to final track alignment. Work next to active track is modeled on the railroad's calendar.

03

Rail connections to the existing right of way

Station tracks, turnouts and crossovers tied into the running line. Special trackwork, signal and PTC changes, host railroad cutover windows and testing can govern completion. We link them to the station and platform work and test which path controls revenue service.

04

Host railroad coordination

Right of entry, flagging, outage requests and the railroad's engineering reviews become real activities with real durations, and every window granted, moved or pulled gets documented.

05

Systems, testing and revenue service

Signals, communications, crossing activation, station systems, safety certification and the pre-revenue test period. These gate revenue service and get squeezed when upstream work slips, so they carry their own protected chain.

06

What the owner gets each month

An update and narrative that says where the governing path is, what moved, why, and who owns it. Knowing in March that the opening is at risk, not in October.

Bridges & trestles

On rail bridges, production per bent is the schedule

Across Phase 2 of the program our scheduler oversaw the schedule for 37 bridges, including movable spans over navigable water. On a long trestle, production rate sets the critical path durations. We schedule by production and track bent by bent. When piles per shift drop, we recalculate remaining durations and test the effect on completion that update.

01Pile driving production. Planned piles per shift by rig and bent, tracked weekly, with refusal, splices and obstructions logged as the reason the rate changed.
02Crane and barge access. Work trestles, barge positions and pick plans drive the sequence over water. The schedule shows which bents each crane position serves.
03Caps, beams and deck. Cap pour cycles, beam deliveries and sets, deck, then track on structure, each with its own rate. Beam fabrication tracked as the long-lead feeder it is.
04Movable spans. Machinery, electrical and controls fabrication, marine coordination and Coast Guard windows as separate logic, because that is where these structures slip.
05Safety and environmental windows. Marine safety, over-water fall protection, manatee and turbidity windows and weather stand-downs modeled as calendars, so lost days are visible and attributable.
06Critical path slippage, caught early. Sustained pile production under plan eats total float or moves completion before the field feels it. The update shows the drift and why, and recovery gets priced in time before it becomes an acceleration claim.
Track production

Ballast, rail and ties scheduled by rate and tied to milestones

Track is quantity work. The bid assumes a rate, the field produces one, and an honest schedule shows the second. We load track activities with quantities, track earned quantities weekly, and let remaining durations move with the real rate.

Ballast

Tons unloaded, spread and tamped

Ballast train availability as a constraint, dump and spread rate by segment, surfacing passes to final profile.

Rail

Feet laid, welded and de-stressed

Rail train deliveries and staging, lay rate and weld rate tracked separately, de-stressing before the corridor can go into service.

Ties

Ties placed and fastened

Distribution ahead of placement, placement and fastening rate per shift, turnout ties tied to special trackwork deliveries.

Same approach for drainage, subballast, grade crossings, catenary and signal houses, so the owner, the GC and the trades work from the same planned rate, earned quantity and trend.

Grade crossings, maintenance of traffic and utility relocations run the same way they do on highway work: Roads and highways scheduling →

Systems integration

Systems integration is where time gets lost if it isn't planned

Signals, PTC, communications, crossing activation and station systems come together at the end, after the civil and track work and with the revenue date already set. Carried as a few long bars, they can hide the interfaces, testing sequence and durations that determine whether the remaining float is usable. We break them out early and tie them to the civil, track and vendor work that feeds them.

01Design and vendor deliverables. Signal and PTC design, vendor submittals, factory acceptance testing and shipping carried as logic from NTP, not one procurement bar.
02Installation by segment. Signal houses, cable, crossing equipment and communications installed segment by segment, each gated by the track and civil work it sits on.
03Interface milestones. Hand-offs between the civil, track and systems contractors and the host railroad carried as dated milestones, so a late hand-off shows who it hit.
04Testing in order. Point-to-point, local and integrated testing, field qualification and PTC testing sequenced with retest loops, because first-pass failures happen.
05Certification and pre-revenue operations. Safety certification, regulator reviews, training and the pre-revenue test period as their own protected chain to revenue service.
06Durations from history, not leftovers. We set systems and testing durations from historical data on comparable work and, when the program needs it, run a quantitative schedule risk analysis to show the range of likely revenue service dates.
Rail services

What we do on rail programs

01

Owner-side schedule review

Independent review of the contractor's baseline and updates, production trend reports, and a straight monthly answer on whether the opening date is still real. How we help owners →

02

Change management

Every change and directive priced for time as well as cost, with fragnets inserted into the current update so cumulative impact is measured, not guessed.

03

Claims and delay oversight

A contemporaneous record built to survive a dispute, and the delay analysis run on it when one comes: retrospective under AACE RP 29R-03, prospective TIAs under RP 52R-06.

04

Scheduling and schedule management

Baselines and monthly P6 management built around access windows, outage calendars, phased cutovers and production rates, with plain-language narratives.

05

Coordination in active rail environments

Sequencing around live operations, access requests, flagging and third-party approvals, and documenting it when the railroad, a municipality or a utility takes your window.

06

Interim or embedded scheduler

Need a rail scheduler for 18 months, not a hire? We embed with your team, run the schedule, and hand off a clean network at the end.

Where rail schedules fail

On a rail job, operations always win

When operations pulls a window, a flagger doesn't show, or a permit sits with a municipality, the work slips and the next window may be weeks away. Who carries that depends on the contract and the record, so the schedule has to plan for it and the record has to show it.

+A missed cutover weekend that costs a month
+Access windows promised in the contract and pulled in execution, with the delay landing on the contractor's record
+Pile or track production under the bid rate for months while the schedule still shows it
+Third parties controlling a calendar nobody on the project owns
+Systems, testing and activation compressed at the end to hold a revenue date set years earlier

More on compression and stacked work: When schedules get compressed →

Representative program

Phase 2, zone by zone

Schedule, change and delay oversight across the Orlando extension of a Florida intercity rail program. Contractor names withheld, references available on request.

Zones 1 & 2, Urban & Airport

Orlando International Airport station and maintenance facility

An intermodal station at MCO, a 138,000 SF vehicle maintenance facility, and double track under active airport taxiways, where airport operations set the work windows.

Zone 3, Greenfield Corridor

35 mile new rail corridor

Three million CY of excavation, 865,000 SF of MSE walls, 18 new bridges and arch tunnels beneath active roadways, with shoofly phasing and I-95 roadway work woven through the rail sequence.

Zone 4, Active Corridor

129 mile Class VI high speed upgrade in the FEC right of way

Phased upgrade in a live corridor shared with FECR freight: 156 crossing upgrades and 19 bridges including movable spans, sequenced around track access, outages and cutovers.

Program-wide

Change and delay oversight across every zone

Fragnets and time impact analyses on changes, production trending on structures and track, and one record across contractors and zones that answered "where are we and why" with the schedule.

Rail FAQ

Questions we get on rail work

How do you schedule around track shutdowns and work windows?
As access activities, work calendars and justified constraints in the P6 network. Cutover weekends carry their own logic, and the schedule shows what cascades when a window is pulled.
How do you schedule a new station on an existing corridor?
As three linked schedules in one network: building, platforms, and the trackwork tie-in to the existing right of way. The tie-in usually governs because it depends on the host railroad's windows, so we build that logic first.
How do you track production on bridges and trestles?
Bent by bent. Piles per shift, caps poured, beams set, deck and track on structure, each against its planned rate and fed back into P6 as remaining duration. Production under plan triggers a check of total float and the driving path.
Do you track ballast, rail and tie production?
Yes, weekly against plan: tons of ballast, feet of rail laid and welded, and ties installed. Remaining durations move with the real rate.
A cutover weekend slipped. What does that do to the program?
Rarely just a weekend, because the next window may be weeks out. We model the slip as a fragnet and run a time impact analysis per AACE RP 52R-06 to measure the completion-date impact.
Can you coordinate with the host railroad's access and flagging process?
Yes. Access requests, flagging and operating windows become logic tied to the activities they gate. When access is denied or flagging doesn't show, that month's update records the restriction, its schedule effect and who carries it.
Do you handle claims and delay oversight on rail programs?
Yes. Retrospective analysis under AACE RP 29R-03 ties each delay to its driver, prospective TIAs follow RP 52R-06, and both run on the monthly record we keep.
Why do systems and testing slip at the end of rail programs?
They inherit every upstream slip and are usually carried as a few long bars with float that is not real. We break out design, vendor, installation, interface and testing logic early, set durations from historical data on comparable work, and run a schedule risk analysis on the back end when the program needs a confidence range on revenue service.

Building a station, a bridge or a corridor? Let's look at the schedule

Send the baseline or latest update. In 20 minutes we'll look at your access constraints, production records and decision deadlines, and scope the review.

Back to top ↑