Attachment J - Fixed-Route Solution Specifications.xlsx
XLSX spreadsheet 20 KB Posted
- Attached to
- Transit Service Project
- Solicitation number
- 65-RFP050124AMW
- Issued by
- Orange County, Chapel Hill Town, North Carolina
About this file
This document is an attachment titled "Attachment J - Fixed-Route Solution Specifications.xlsx" related to a state and local contract opportunity from the University of North Carolina at Chapel Hill (UNC) for its Department of Transportation and Parking. The opportunity involves the redevelopment of UNC's Point-to-Point (P2P) transportation management system, focusing on three key aspects: an on-demand shuttle reservation, dispatch, and tracking solution; a fixed-route solution with support for General Transit Feed Specification (GTFS) feeds; and a ride aggregator application supporting live bus tracking of the fixed-route service. Interested vendors may submit an offer for any one or more of the aforementioned solutions. The contract will involve the jurisdictions of Orange County and the Town of Chapel Hill, North Carolina.
The attachment provides detailed specifications and requirements for the fixed-route solution, including capabilities related to automatic passenger counting, platform operations, route optimization, data storage and retrieval, network design, testing, support, training, and reporting. It also outlines requirements for the driver and rider applications, as well as feedback and customer service processes.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment K - On-Demand Solution Specifications.xlsx | XLSX spreadsheet | |
| Attachment L - Ride Aggregator Application Specifications.xlsx | XLSX spreadsheet | |
| RFP050124AMW Transit Service Project FINAL.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
Sheet1
| ATTACHMENT J: Fixed-Route Solution Specifications | |
| Platform | Describe the current state of your APC (automatic passenger counter) capabilities and what technology is used. |
| Platform | Describe the platforms operation and elaborate on platform speed and ease of use |
| Platform | Describe how algorithms could be used to improve cost and efficiency |
| Platform | Describe the products efficiency in regards to how some routes may opperate differently or have more or less stops than others. |
| Platform | Describe how you will store data in the cloud. |
| Platform | Will the solution be able to implement on-the-fly route changes made by dispatchers? For example, an emergency repair must be made on campus that affects a route. How will this be handled? |
| Platform | Describe how you will to be able to provide demand forecasting based on recurring trips and certain periods of time |
| Platform | Describe your announcement capabilities. Do you utilize intercom, location based announcements, timed announcements, or visual announcements? |
| Platform | How will the live tracking map be displayed within the app or website? |
| Platform | Can the following information be viewed in the dispatcher map display when clicking on a bus? |
• Vehicle Number;
• Operator;
• Driver;
• Logon state and connection status;
• Upcoming Stop location (or a list of next stops) and last stop location.
• Trip information;
| Platform | How will historical trip data be stored and replayed by the University? |
| Platform | How can logged data be retrieved? |
| Platform | Will logged data be able to be retrieved based on time period? |
| Platform | Describe how the platform is SaaS (software as a service). |
| Platform | Custom fields should be avialable for rider data capture |
| Platform-Reporting | Describe the functions available for staff to be able to customize reporting. |
| Technology | What technology will be used to add an automatic passenger counter (APC) to the fixed-route buses? |
| Technology | How will a network implemented in the solution be able to handle security cameras? Will security cameras use too much network bandwidth? |
| Technology | Will there be network redundancy capabilities? For example, a two-SIM card device running two different network carriers in case one is to go down. This way if a carrier has issues, service can continue. |
| Technology | Describe any wiring and connectors are needed for the project, and how they will be appropriate to on-board where the equipment is to be installed. Describe how technology will be protected and shielded from any interference or damage. |
| Technology | Describe how you would provide a wireless communications system design for client approval. Also describe how this will be installed. |
| Testing | Describe how you will assess the existing network support to determine if performance will be sufficient, and if not, assist in identifying network improvement strategies |
| Testing | Describe how the client database can be migrated by the contractor into the new system prior to launch |
| Testing | Describe the testing process. Describe how testing of software, components, and features will be done using UNC's own data |
| Testing | Describe the testing timeline to ensure it is completed prior to launch date. |
| Testing | Describe the testing of overall components such as billing, reporting, scheduling, the base map, vehicle location/Tablets/wireless fleet communication functions |
| Support | Describe the technology and software support that will be available to UNC and the times at which this support is available |
| Support | If a P2P dispatcher needs assistance further assistance will remote support be offered via a remote desktop access? |
| Support | Describe how Issues and Action items related to UNC support shall be tracked and logged. Will the log shall be accessible 24 hours, 7 days per week? |
| Support | Describe how a project manager may be appointed that will work closely with the university and ensure new features and functionalities are understood and implemented if desired. |
| Support | Describe the project management plan and implementation process that will be provided for UNC. Include detailed steps. |
| Support | Describe the formats of training materials that will be available to UNC to meet the needs of P2P staff |
| Support | How will the vendor ensure that there is adequate training for P2P's own trainers? |
| Support | Describe the extents of marketing and advertising that will be available to UNC for promotion. Also describe how the vendor will work to promote on their own, too. |
| Support | How will the first-time experience for riders be? Describe the tutorial process and introduction for a first-time user. |
| Support | What languages will training materials be available in? |
| Support | Describe how training vizuals and aids will be distributed to the university. What formats are supported? |
| Support | Describe how new users will be guided through the support process. |
| Support | Will a Systems Administration Manual be provided? |
| Driver App | Describe the structure of the GPS system that will be provided. |
| Driver App | Describe the function of notifications that are sent to the user. Can they be both automatically and manually sent? |
| Driver App | Will upgrades be included in the licensing cost of the platform? |
| Rider App | Will you be able to integrate a SSO option using UNC's existing SSO logins? |
| Rider App | Describe the hardware and software required to provide a GTFS feed? How simple will it be to send this GTFS feed to an aggregator app? Also describe this process. |
| Rider App | How will users be notified that their bus is near their stop? |
| Reporting | How will standard reports be provided and how often? Will they include fleet and passenger counts? |
| Reporting | Describe the business intelligent tools that are provided from an open API for use. |
| Reporting | Describe the user-friendly tools for use that enable generation of reports using stored data, including data filtering by time period, fare types, services, vehicles, date |
| Reporting | Describe how day-to-day key performance metrics and statistics will be tracked and visualized for P2P staff. |
| Reporting | Will a heatmap of current and historical stop data be provided to dispatchers and UNC staff? |
| Reporting | Will the following data be provided to UNC through the reporting process? |
Ridership Data:
Boardings: The total number of passengers who boarded.
Average Boardings Per Service Hour: The mean number of Boardings for each hour that service was available.
Alightings: The number of passengers who left the bus Average alighting per service hour: The mean number of passenger alighting for each house that service was available.
Percentage of bus capacity: The current capacity of buses. Number of riders divided by number of total seats.
| Feedback | Describe how customers can provide any kind of feedback |
| Feedback | Describe how complaints based on ADA or Title VI disputes will be handled and stored. |
| Feedback | Describe how it will be possible to follow up on complaints, disputes, or any feedback |
| Feedback | Describe the format for feedback reports to be exported. |
File details come from the government source that posted it. Updated .