E Branch: connect station access, transitway and traction-power design
Use a design-stage interface register to connect E Branch station access, track, overhead power and roadway decisions without assuming final scope.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 3 min
- Published
On this page
A useful E Branch design-stage estimate connects the station platform to the track, overhead power and the street around it. For a GC or CM estimator, the immediate decision is which interfaces can be priced from a defined design and which need an explicit allowance, alternative or question. A station-only takeoff can miss the work needed to make the surrounding rail and roadway design fit.
The MBTA's public engineering-services listing describes 15–100% design for accessible Mission Park, Riverway and Heath Street stations, new transitway and track improvements, updated overhead contact system (OCS) poles and contact wire, and traction-power upgrades including a new TPSS E2. This is an engineering-services record, not a station construction award. It should not be confused with the B Branch accessibility package.
The City's project page describes a goal of accessible boarding and operation of new trains by 2030. That goal does not establish a construction completion date for every element. Vehicle procurement, station design and power installation are distinct scopes and schedules.
Make the boundaries visible in the estimate
Use this illustrative register at each design issue. Add the drawing and specification revision, responsible package, quantity basis, assumption and date when each item must be resolved. The questions are estimating recommendations, not established final design requirements.
| Boundary | What must be coordinated | Evidence to request before a firm carry |
|---|---|---|
| Platform to track | Platform edge and boarding geometry against track alignment and construction sequence | Current station plans, sections, track geometry and staged access requirements |
| Track to overhead system | Track arrangement against poles, wire and support locations | OCS layouts and interfaces, support details and railway work windows |
| Power to civil work | TPSS E2 and distribution interfaces against structures, routes and site access | Electrical design, site limits, utility coordination and package responsibility matrix |
| Station to roadway | Platforms and crossings against travel lanes, curbs and pedestrian routes | Agreed cross-sections, traffic staging and current City and MBTA design limits |
| Construction to operations | Sequence of track and station work against continuing service | Owner-issued access, outage and testing requirements when available |
A change to the platform location can affect track alignment, pole placement, crossings and temporary traffic treatment. In a review meeting, follow one proposed station edge through all four drawings rather than assigning a separate plug to each trade. Record whether each cost belongs in the base scope, an alternate or an unresolved gap so that two packages do not both carry the same work.
Treat the street cross-section as a decision still to be made
The City's May 2024 presentation studied Huntington and South Huntington avenues between Brigham Circle and Heath Street, including nearby connected roads. It discussed raised platforms, crossings and other accessibility elements, and showed the constrained street space and potential design elements. The illustrated elements are a menu for tradeoffs, not a final cross-section: adding every listed width does not produce an approved roadway allocation.
For a schematic estimate, compare a station section with the corresponding road section at the same location and revision. Identify where a curb or crossing shifts, where pedestrian access must be maintained and whether the assumed staging consumes the same space as another package. If no coordinated section exists, keep the quantity and its dependence on the layout visible rather than silently fixing a design.
Request the package that controls the carry
Before pricing a procurement, verify the issued project scope, then trace scope changes to the controlling revision. Request the current station, track, OCS, traction-power and City roadway drawings together, along with the interfaces and proposed construction sequence. This source set does not establish actual electrical capacity, clearances, utility commitments or commissioning protocols. Do not turn the earlier presentation's vehicle forecast into a current delivery or construction commitment.
Related reading
Construction addenda management for GC estimators
Addenda are official bid-document revisions. Log them, distribute them, retakeoff the deltas, and require subcontractor acknowledgments so your estimate and every bid reflect the final scope.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.