RFI-Intelligent-Transport-System-Modernization_26-00295-AXJC.pdf

PDF 433 KB Posted

Attached to
RFI – Intelligent Transport System (ITS) Modernization for Real-Time Passenger Information
Solicitation number
26-00295-AXJC
Issued by
Philadelphia County, Philadelphia City, Pennsylvania

About this file

This is a Request for Information (RFI) issued by the Southeastern Pennsylvania Transportation Authority (SEPTA) for market research regarding Intelligent Transport System (ITS) modernization to provide real-time passenger information for two heavy rail subway lines: the Market-Frankford Line (L) and Broad Street Line (B). The L line spans approximately 12.9 miles with 28 stations and 220 M-4 cars, while the B line covers 12.5 miles with 24 stations and 125 B-IV cars. SEPTA seeks information on technologies, integration approaches, delivery models, and cost/schedule ranges for three solution layers: (1) Vehicle Tracking for continuous train location monitoring including underground segments; (2) Dispatching & Service Management to establish computerized dispatching for headway-based metro service and disruption management; and (3) Passenger Information System to deliver customer-facing real-time predictions, ETAs, service disruptions, and alerts through standardized formats including GTFS-Static and GTFS-Realtime. Responses must address firm profile, technical approach, implementation strategy with rough order-of-magnitude costs and lead times, and procurement/delivery models. No submission deadline is specified in this document.

SEPTA currently lacks real-time vehicle location capabilities and relies on legacy track-circuit occupancy at block-level granularity, which is insufficient for passenger information needs, and operates without any dispatching software. Solutions must support open data architecture with GTFS standards, secure APIs, and ensure data portability within SEPTA's technology ecosystem. The authority prefers a single approach for both lines to avoid duplicated integration and vendor management, though respondents may address one, several, or all three solution layers either directly or through partners. The RFI mentions DBE/SBE status and subcontracting approach as part of the firm profile requirements, and notes that respondents should identify any existing cooperative purchasing agreements or contracts SEPTA could utilize. This RFI is for informational purposes only and does not constitute a commitment to issue a solicitation or award a contract.

View the file

Other files

File Type Posted
SEPTA-RFI-Ltr-ITS-Modernization-10-30-26.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SEPTA | RFI - Intelligent Transport System (ITS) Modernization for Real-Time Passenger Information

SOUTHEASTERN PENNSYLVANIA TRANSPORTATION AUTHORITY (SEPTA)

REQUEST FOR INFORMATION (RFI)

Intelligent Transport System (ITS) Modernization for Real-Time Passenger

Information

Heavy Rail Subway Lines: Market-Frankford Line (L) and Broad Street Line (B)

Notice to Respondents

This Request for Information (RFI) is issued by the Southeastern Pennsylvania Transportation

Authority (“SEPTA” or the “Authority”) for market research and planning purposes only. This RFI is not a Request for Proposal, an Invitation for Bids, or an offer to contract, and it does not commit

SEPTA to issue a solicitation, to award any contract, or to pay any cost incurred in preparing a response.

1. Purpose and Background

1.1 Purpose

SEPTA seeks information from qualified firms regarding technologies, integration approaches, delivery models, and realistic cost and schedule ranges for modernizing Intelligent Transport System

(ITS) capabilities across its heavy rail subway system: the L (formerly Market-Frankford Line) and the B (formerly Broad Street Line), to enable passenger-facing real-time service information.

1.2 System Information

Line Route Length

(approx.)

Stations Fleet size

L (formerly Market-

Frankford Line)

12.9 mi 28 220 M-4 cars

B (formerly Broad Street

Line)

12.5 mi 24 125 B-IV cars

The B runs fully underground, except at the northernmost station, Fern Rock Transit Center.

The L runs underground from 2nd St Station through 40th Street Station. It comes aboveground to the east between 2nd St and Spring Garden Station, and coming above ground to the west between 40th

St Station and 46th St Station, running aboveground to each terminus.

1.3 Problem Statement

SEPTA’s customer-facing real-time information for the L and B lines is limited to in-vehicle and in-station live and recorded announcements, and written service alerts that populate to apps, websites, and digital screens. We are not currently able to provide real-time vehicle locations, ETA predictions, or service disruption information that modern customers expect via digital platforms.

Current train location visibility for internal operations relies on legacy track-circuit occupancy at block-level granularity, which is not accurate enough to support passenger information needs.

SEPTA currently dispatches L and B trains manually, without any existing dispatching software that could be integrated with a modern passenger information system.

Other notes:

• A single approach for both L and B Metro lines is preferred to avoid duplicated integration, duplicated spares, and duplicated vendor management.

• All approaches must support SEPTA's safety-first culture, and meet existing and emerging standards by regulators, including passenger information standards (ADA, WCAG, etc).

• SEPTA is investigating market capability, integration approaches, and realistic cost and schedule ranges before committing to a procurement structure.

2. Scope of Interest: Three Solution Layers

SEPTA is organizing this inquiry around three solution layers. The layers are independently procurable and may be bundled. A respondent may address a single layer, several layers, or all three, and should state which layers it is responding to and which it would deliver directly versus through partners.

Layer Scope

1. Vehicle Tracking

(Train Location)

The purpose of this layer is to establish continuous, reliable knowledge of where each train is on the L and B Lines, including underground tunnel segments where GPS is currently unavailable. No element of this scope contemplates modification of, or safety-critical dependency on, the existing train control and signaling systems. The system shall be able to identify the track that vehicles are traveling on.

2. Dispatching & Service

Management

SEPTA currently dispatches L and B trains manually, without any dispatching software. This layer would establish a computerized dispatching system, connecting vehicle location data to service operator and vehicle schedules and management. This system should support a high-frequency, headway-based metro service, and provide capabilities to

Layer Scope manage frequent and significant disruptions to regular service

(see below for examples of disruption types). This layer would provide information to the Passenger Information System.

3. Passenger

Information System

This layer would integrate data from both the vehicle location technology and the dispatching system to generate customer-facing real-time predictions and passenger service disruption information in standardized formats, integrating with existing customer-facing platforms. This layer may include a solution to control the signage and audio announcements at the stations, as well as providing data feeds to support on-board signage and announcements.

Customer Information

The customer-facing information needed for these lines includes:

• Real-time vehicle locations

• Real-time vehicle arrival/departure predictions (ETAs) by stations

• Real-time service disruption information, including cancellations, single-tracking/opposite side boarding, headway adjustments, service pattern adjustments (e.g. skipping/expressing past stops or adding stops), short-turns, additional trains, or other disruptions

• Optional: Service alert messaging deriving from service disruptions is also of interest.

Interim Solutions SEPTA is also open to interim or phased solutions that materially improve any aspect of real-time customer-facing information for these lines, even prior to full modernization.

Respondents are encouraged to propose partial deployments, hybrid approaches, or layered upgrades that deliver meaningful near-term benefits.

Open Data Architecture Requirements

SEPTA requires solutions built on open data standards that ensure long-term interoperability of its current and future systems.

Systems must support GTFS-Static and GTFS-Realtime standards for rider-facing information, along with secure, well-documented APIs for integration with SEPTA’s existing and future platforms. All data generated by the solution must remain fully accessible and portable within SEPTA’s broader technology ecosystem.

3. Information Requested from Respondents

3.1 Firm Profile

1. Firm name, address, ownership structure, and primary point of contact.

2. Years delivering the solution layer you are responding to; relevant transit references, preferably for underground high frequency metro service with substantial tunnel mileage.

3. Role sought: prime integrator, subsystem supplier, software provider, or professional services.

4. DBE/SBE status and anticipated subcontracting approach.

3.2 Technical Approach

Note: The following areas are of particular interest to SEPTA and are required as part of your response. Your responses to these points should be clearly stated together as shown below in the Technical Approach section of your response.

1. State which of the three layers in Section 2 you are responding to, and describe your approach for each, identifying what you supply directly and what you would deliver through partners.

2. Explain what features and functionalities your system provides and what problems your system is designed to solve.

3. Describe what communications options your solution supports and behavior under degraded or lost connectivity.

4. Indicate all systems and interfaces your solution supports including signal/train-control, SCADA, CAD/AVL, and passenger information systems, including standards supported (GTFS-Realtime, NTCIP, or other).

5. Outline the hosting options you offer: on-premise, agency cloud, or vendor-hosted, and associated cybersecurity measures.

3.3 Implementation strategy, Cost and Schedule

1. Provide rough order-of-magnitude cost ranges by package and by layer, with the assumptions behind them.

2. Indicate the typical lead time from notice to proceed through implementation completion.

3. Outline recurring costs: licensing, hosting, support, and data services.

4. Detail any existing programs, cooperative purchasing agreements or contracts that SEPTA could use to procure your solution.

3.4 Procurement and Delivery Model

1. Define your preferred contracting structure (single integrator across both lines versus separate awards per package) and rationale.

2. Describe warranty and performance guarantees.

3. Describe documentation and scope expected for SEPTA to produce that guarantees a complete, industry-leading solution at original contracted value (without change management).

4. Identify key risks you expect SEPTA to manage, and those you would take on.

5. Response Format and Submission

• Format: PDF, single file, 11-point minimum type.

• Organize the response to mirror Section 3 headings.

• Submit to the point of contact on the cover page by the response due date and time. [TBD:

submission channel and deadline]

• SEPTA may invite selected respondents to one-on-one informational sessions or product demonstrations. Selection is entirely up to the discretion of SEPTA and does not constitute agreement or interest in project delivery approach. Participation by respondent is voluntary.

6. Disclaimers

SEPTA is not liable for any cost incurred by a respondent in preparing or presenting a response.

SEPTA reserves the right to use any information submitted in the development of future specifications and solicitations, subject to marked proprietary designations. This RFI does not restrict

SEPTA's right to pursue any procurement method permitted by law and by Authority policy.

Addendum 1: Glossary of Terms

Intelligent Transport System (ITS) Modernization

Heavy Rail Subway Fleet: Market-Frankford Line (L) and Broad Street Line (B)

Glossary

Term Definition

Application Programming Interface (API)

A documented method to allow software systems to exchange data or request services.

Arrival Prediction A calculated estimate of when a train will arrive at, or depart from, a station.

Automatic Train Supervision (ATS)

Software and related interfaces used to support train monitoring, dispatching, service regulation, schedule adherence, and incident management.

B Line Formerly SEPTA Metro’s Broad Street Line.

B-IV The railcar fleet on SEPTA’s B Line. Manufactured by Kawasaki in 1982.

Block A section of track used by the signal system to detect occupancy and maintain safe train separation.

CAD/AVL Computer-Aided Dispatch / Automatic Vehicle Location. A system for vehicle monitoring and dispatch support.

Computerized Dispatching System

Software that supports dispatchers in monitoring trains, managing service, applying operating strategies, and communicating service changes.

Confidence Score A value or classification that indicates the estimated reliability of a reported train location or prediction.

Consist One or more railcars operated together as a train.

Continuous Telemetry Frequent transmission of train status, identity, location, speed, direction, or other operating data from onboard or wayside systems.

Control Center The SEPTA operating location from which authorized personnel monitor rail service, coordinate responses, and manage incidents and service changes.

Customer Information Information provided to riders about service, including train arrivals and departures, disruptions, cancellations, boarding changes, skipped stops, express operation and other service conditions.

Dead Reckoning Estimate of a train’s current position from a known reference point.

Term Definition

Degraded Mode A defined operating condition in which a system continues to provide reduced or qualified functionality after loss, delay, or reduced quality of data.

Estimated Time of Arrival

(ETA)

The predicted time at which a train is expected to arrive at a station.

Global Positioning System (GPS)

A satellite-based positioning system.

GTFS-Realtime (GTFS-RT) The General Transit Feed Specification format for publishing dynamic transit information, including trip updates, vehicle positions, and service alerts.

GTFS-Static The General Transit Feed Specification format for publishing planned transit schedules, stops, routes, trips, and related reference data.

Headway The time interval between trains traveling in the same direction on a line.

Heavy Rail A high-capacity electric railway operating on an exclusive right-of-way. The L and B Lines are SEPTA’s heavy rail subway lines.

Interlocking An arrangement of signals, switches, tracks, and control logic that permits trains to move safely through intersecting locations.

Intelligent Transport System (ITS)

The project umbrella term used in this RFI for coordinated train location, dispatching and service-management, prediction, and customer-information capabilities for the L and B Lines.

L Line Formerly SEPTA Metro’s Market-Frankford Line.

Location Engine Software that receives and combines available location inputs, associates them with the rail network, and produces a usable train position.

M-4 The railcar fleet used for revenue service on SEPTA’s L Line. Manufactured by Adtranz in 1997.

M-5 The railcar fleet planned for revenue service on SEPTA’s L Line.

Manufacturing by Hitachi STS ongoing.

Map Matching Aligning a measured or estimated train position to the correct track, route, direction, and location on the rail network.

Notice to Proceed (NTP) Formal written authorization from SEPTA directing a contractor to begin work under a contract.

NTCIP National Transportation Communications for ITS Protocol, standards used primarily for transportation-system communications and device interoperability.

Odometry Measurement or estimation of distance traveled using onboard inputs such as wheel rotation, tachometer data, or inertial sensors.

On-Premise Computing infrastructure is installed within facilities controlled by SEPTA.

Open Data Architecture An architecture that uses documented, non-proprietary data standards and accessible interfaces.

Term Definition

Passenger Information System (PIS)

Systems that create, manage, or distribute customer-facing transit information.

Portal The transition point between an open-air rail segment and a tunnel.

Real-Time Customer Information

Current or predicted information delivered to riders about train location, arrivals, departures, service status, disruptions, and operating changes.

Real-Time Vehicle Location

A continuously or frequently updated estimate of a transit vehicle’s location.

SCADA Supervisory Control and Data Acquisition, a system used to monitor and control infrastructure and equipment.

Short Turn When a train reverses direction before reaching the normal end of its route, to restore service balance or respond to an incident.

Single Tracking Temporary operation of trains in both directions over one track while the other track is unavailable or restricted.

Train Control and Signaling System

The safety-critical systems, equipment, and operating rules used to detect trains, establish routes, display or enforce movement authority, and maintain safe separation.

Train Identity Correlation The process of associating a train position with the correct train.

Track Circuit A signal-system device or circuit used to detect whether a defined track block is occupied.

Wayside Equipment, infrastructure, or reference points installed along the railroad right-of-way rather than onboard a train.

Wayside Reference A fixed, known location used to verify or correct an onboard or system-generated train-position estimate.

Appendix A: current state of passenger information for L and B lines:

SEPTA.org, the SEPTA app, and third-party apps can only provide scheduled departure times for the L and B -- no real-time ETAs or vehicle locations on the map.

L and B customers rely on service alerts like those above to understand any delays, cancellations, or operational changes that result in deviations from the planned schedule.

Appendix C: Line and System Maps

Please find maps of the L, B, and Metro network here:

Metro & Frequent Bus Network Map: https://wwww.septa.org/wp-content/uploads/page/communication/SEPTA_System-Map_v3-0.pdf

L Map: https://wwww.septa.org/wp-content/uploads/page/communication/SEPTA_L_WEB_v2-0.pdf

B Map: https://wwww.septa.org/wp-content/uploads/page/communication/SEPTA_B_WEB_v2-0.pdf https://wwww.septa.org/wp-content/uploads/page/communication/SEPTA_System-Map_v3-0.pdf https://wwww.septa.org/wp-content/uploads/page/communication/SEPTA_System-Map_v3-0.pdf https://wwww.septa.org/wp-content/uploads/page/communication/SEPTA_L_WEB_v2-0.pdf https://wwww.septa.org/wp-content/uploads/page/communication/SEPTA_B_WEB_v2-0.pdf

Notice to Respondents
1. Purpose and Background
1.1 Purpose
1.3 Problem Statement
SEPTA’s customer-facing real-time information for the L and B lines is limited to in-vehicle and in-station live and recorded announcements, and written service alerts that populate to apps, websites, and digital screens. We are not currently able to ...
2. Scope of Interest: Three Solution Layers
3. Information Requested from Respondents
3.1 Firm Profile
3.2 Technical Approach
3.3 Implementation strategy, Cost and Schedule
3.4 Procurement and Delivery Model
5. Response Format and Submission
6. Disclaimers
Addendum 1: Glossary of Terms
Glossary

File details come from the government source that posted it. Updated .