The file's text, extracted by GovTribe without its formatting.
Appendix B1: System Requirements - Detailed Responses
| Requirement Number |
| Requirement |
| Verification |
| Does proposed system satisfy requirement? |
| Bidder’s Detailed Response |
| DET-01-1 |
| The detection system shall utilize thermal imaging, video, LIDAR, and/or radar for detection methodology. |
| Demonstration |
| ☐ Yes |
☐ No
☐ N/A
List the type of detection methodology.
Bidder Response:
| DET-01-2 |
| The detection system shall be capable of detecting and distinguishing, at a minimum, the following modes of traffic: |
· Motorized vehicles
· Pedestrians
· Bicycles/Bike(+)
The detection system shall support NTCIP 1209 for communication of applicable detection system configuration, status, and data.
The detection system shall detect various modes of traffic following NTCIP 1209 3.5.3.2.8:
- Motorized Vehicles
- Pedestrians
- Bicycles/Bike(+)
☐ No
What modes are detected?
Bidder Response:
What elements of NTCIP 1209 are incorporated and explain any alternative methods or approaches that are used to meet the requirement?
Bidder Response:
| DET-01-3 |
| The detection system shall identify various modes of traffic: |
- Motorized Vehicles
- Pedestrians
- Bicycles/Bike(+)
☐ No
What modes are identified?
Bidder Response:
What format is the data transmitted in?
Bidder Response:
| DET-01-4 |
| The detection system shall track (object trajectory) various modes of traffic: |
- Motorized Vehicles
- Pedestrians
- Bicycles/Bike(+)
☐ No
What modes are tracked?
Bidder Response:
What format is the data transmitted in?
Bidder Response:
| DET-01-4.1 |
| The detection system should assign georeferenced information for various modes of traffic: |
- Motorized Vehicles
- Pedestrians
- Bicycles/Bike(+)
☐ No
Elaborate on how the system assigns georeferenced information.
Bidder Response:
What format is the data transmitted in?
Bidder Response:
| DET-01-5 |
| The detection system shall classify various modes of traffic: |
- Passenger Car
- Bus
- Single Unit Truck
- Tractor Trailer
- Motorcycles
☐ No
Which of the 13 FHWA vehicle categories are classified?
Bidder Response:
How are the multi-modal items not part of the 13 FHWA vehicle categories classified/binned?
What format is the data transmitted in?
Bidder Response:
| DET-01-7.1 |
| The detection system shall be capable to issue alerts through IP connected devices and/or systems. |
| Test |
| ☐ Yes |
☐ No
What types of alerts are issued? Explain below how the system issues these alerts including frequency, format, content.
Bidder’s Response:
| DET-01-12 |
| The detection system should be approved by PennDOT Bulletin 15 or receive approval from another state. |
| Test |
| ☐ Yes |
☐ No
List what State(s) your system is approved for?
Bidder Response:
| DET-01-13 |
| The detection system shall support ATSPMs and setup. |
| Demonstration |
| ☐ Yes |
☐ No
Describe how your system provides both advance detection and stop-bar detection to support ATSPMs. Also, identify the typical maximum distance upstream of an intersection where detection can be established to collect advance/approach ATSPM data?
Bidder Response:
| DET-01-13.2 |
| The detection system shall support detection across a minimum of eight lanes for each leg of the intersection (combined approach and receiving lanes). |
| Demonstration |
| ☐ Yes |
☐ No
What is the maximum number of lanes that can be included based on the recommended mounting height?
Bidder Response:
| DET-01-16 |
| The complete detection system shall support a minimum of 64 simultaneously configurable and operational detection zones. |
The 64-zone minimum applies to the aggregate detection system installed at each intersection and does not apply separately to each sensor, processor, controller, or NTCIP 1209 agent.
The 64-zone requirement does not require 64 traffic signal controller detector channels.
Each detection zone shall be uniquely identifiable within the proposed system.The detection system shall utilize NTCIP 1209 3.5.3.2.1 to allow up to a minimum of 64 detection zones.
☐ No
How many detection zones can be provided? How are they configured?
Bidder Response:
| DET-01-19 |
| The detection system should allow the user to create a detection zone that is irregular shape with the use of at least 10 nodes. |
| Demonstration |
| ☐ Yes |
☐ No
What is the maximum number of nodes?
Bidder Response:
Requirement Number
| Requirement |
| Verification |
| Does proposed system satisfy requirement? |
| Detailed Response |
| DET-01-26 |
| The detection system, if applicable, should provide varying levels of video quality to limit the bandwidth demands to the Traffic Management System and Remote Connection. |
| Demonstration |
| ☐ Yes |
☐ No
List the levels of video quality available.
Bidder Response:
| DET-01-29 |
| The detection system shall have a local processor with sufficient storage to operate system based on the requirements specified in this document. |
| Demonstration |
| ☐ Yes |
☐ No
What are the specifications of the processor?
Bidder Response:
How much storage is provided?
Bidder Response:
| Requirement |
| Verification |
| Does proposed system satisfy requirement? |
| Detailed Response |
DET-01-30.1
| The detection system shall allow for the user to increase the system's storage if needed. |
| Demonstration |
| ☐ Yes |
☐ No
What is the maximum amount of storage able to be added and what format is allowable? If the additional storage is local or cloud-based, please include the price under the optional costs.
Bidder Response:
| DET-01-30.5 |
| The detection system processors should have at a minimum one USB port to retrieve data or to provide software updates. |
| Demonstration |
| ☐ Yes |
☐ No
How many and what type of USB ports are available?
Bidder Response:
| Requirement |
| Verification |
| Does proposed system satisfy requirement? |
| Detailed Response |
| DET-02-1.1 |
| The detection system shall provide open outbound API access to enable third-party systems to retrieve data and interact with system services. |
| Test |
| ☐ Yes |
☐ No
How does the system provide outbound API access for third-party systems? How do third-party systems connect to and consume the endpoints? What open standards does the system conform too?
Bidder Response:
What authentication methods are supported for third-party access? How are credentials issued, refreshed, and revoked?
Bidder Response:
What data formats are available and/or required for outbound data exchange?
Bidder Response:
What are the response structures and how can third parties test and validate API Access? What level of API documentation is available?
Bidder Response:
How is API versioning handled?
Bidder Response:
| Requirement |
| Verification |
| Does proposed system satisfy requirement? |
| Detailed Response |
| DET-02-1.2 |
| The system should support inbound API integration to enable ingestion of data and services from third-party systems. |
| Test |
| ☐ Yes |
☐ No
How does the system support inbound API integration from third-party systems? What open standards are supported for inbound APIs? How are third-party systems expected to integrate and submit data?
Bidder Response:
What authentication methods are supported for inbound integrations? What access control mechanisms exist for restricting inbound data or system interaction?
Bidder Response:
What data formats are accepted and/or required for inbound data?
Bidder Response:
How does the system handle response and validation including confirmation of successful ingestion and error handling and validation feedback?
Bidder Response:
What tools or methods are available for testing inbound integrations. What level of API documentation is provided for inbound integration?
Bidder Response:
How is API versioning handled?
Bidder Response:
| Requirement |
| Verification |
| Does proposed system satisfy requirement? |
| Detailed Response |
| DET-03-1.1 |
| The detection system shall organize the counts in a searchable database. |
| Test |
| ☐ Yes |
☐ No
What formats are the databases compatible with?
Bidder Response:
What format is the data transmitted in?
Bidder Response:
DET-03-7
| The detection system shall report traffic counts at a minimum of 1-minute intervals. |
| Demonstration |
| ☐ Yes |
☐ No
What are the possible intervals to report data?
Bidder Response:
What format is the data transmitted in?
Bidder Response:
NOTE** - The Detail Response should clearly state if the feature requires an additional cost and if an additional cost, please include in the applicable price/cost tables (Appendix C) and note them as “Optional” in the bidder pricing forms. Optional Costs will not be included in the price evaluation.
B1.1
Appendix B2: System Requirements – Simple Responses
| Requirement Number |
| Requirement |
| Verification |
| Requirement Satisfied? |
| DET-01-6 |
| The detection system shall support NTCIP 1209 communications and shall interface with the traffic signal controller and management system as required to provide the specified functionality. |
NTCIP 1209 is not required to be the exclusive interface for real-time controller actuation, central-system integration, or delivery of all system data.The detection system shall utilize NTCIP 1209 3.5.3.1.1.6 to connect to the controller and management system.
Test
| DET-01-6.1 |
| The detection system shall integrate with Type 2070 advanced traffic controllers and MAXTIME IC Local Controller. |
| Test |
| DET-01-6.2 |
| The detection system shall integrate with Q-Free Kinetic ATMS. |
| Test |
| DET-01-7 |
| The detection system shall be capable to be connected to the internet through an ethernet port. |
| Test |
| DET-01-8 |
| The detection system shall input and log the real-time traffic signal phase state and timing data. |
| Test |
| DET-01-9 |
| The detection system shall support the mandatory and conditional NTCIP 1209 requirements applicable to the NTCIP 1209 functions specifically required by this procurement. |
NTCIP 1209 functions not specifically required by this procurement are not required solely by reference to NTCIP 1209 or its associated Profile Requirements List (PRL).The detection system shall follow all mandatory requirements Profile Requirement Lists (PRLs) from NTCIP 1209 v02A-SE.06 (Aug2017) Demonstration
| DET-01-10 |
| The detection system shall satisfy the requirements of PennDOT Publication 408 Section 950.3 |
| Demonstration |
| DET-01-11 |
| The detection system shall satisfy the material requirements of PennDOT Publication 408 Section 956.2 |
| Demonstration |
| DET-01-11.1 |
| The detection system may utilize H.265 compression streams |
| Demonstration |
| DET-01-11.2 |
| The detection system, if applicable, should have internal heater capable of heating the camera lensdevice to allow for continued detection operations during ice, snow, and frost. |
| Test |
| DET-01-12.1 |
| If not approved by PennDOT Bulletin 15, the detection should be approved by time of installation (estimated Q3 2027). |
| Demonstration |
| DET-01-13.1 |
| The detection system shall support detection zones on the approach and departing lanes. |
| Demonstration |
| DET-01-14 |
| The detection system shall be configured, monitored, and operated through a web-based central platform. |
| Demonstration |
| DET-01-14.1 |
| The detection system shall allow the user to create and modify detection zones through the central platform. |
| Demonstration |
| DET-01-15 |
| The detection system shall time stamp each detector actuation. |
| Demonstration |
| DET-01-15.1 |
| The detection system shall produce actuation logs consisting of detection type including zone identifier, mode, phase or channel actuation, detector call initiation, and detector call termination, and time stamp. |
| Demonstration |
| DET-01-15.2 |
| The actuation logs shall organize the data in a searchable database compatible with Microsoft Excel. |
| Test |
| DET-01-17 |
| The detection system shall allow the user to create detection zones for a single mode of traffic. |
| Demonstration |
| DET-01-18 |
| The detection system shall allow the user to create detection zones for multiple modes of traffic. |
| Demonstration |
| DET-01-20 |
| The detection system should allow the user to create a detection zone that is irregular size that can be extended to cover the full line of sight of the detector. |
| Demonstration |
| DET-01-21 |
| The detection system should allow the user to assign the same space or detection zone to multiple phases. |
| Demonstration |
| DET-01-21.1 |
| The detection system should allow for the user to assign detection zones that are able to overlap. |
| Demonstration |
| DET-01-22 |
| The detection system shall allow the user to designate failure protocol for each detection zone. |
| Test |
| DET-01-22.1 |
| The detection zone or system failure shall be capable to place a call for the failed detection zone(s). |
| Test |
| DET-01-22.2 |
| The detection zone or system failure shall be capable to hold a call for the failed detection zone(s). |
| Test |
| DET-01-23 |
| The detection system shall provide an IP-based indication of a detector or detection-zone failure that can be received or retrieved by the applicable central system. |
The requirement is not to prescribe a specific alarm transport mechanism. The requirement may be satisfied through Simple Network Management Protocol (SNMP), API notification or status, central-system polling, or another documented IP-based method, provided the applicable failure condition is detected, communicated, timestamped, and made available to the City.The detection system shall issue an IP alarm when the detector or detection zone has failed .
Test
| DET-01-24 |
| The detection system shall be capable to omit a mode call if an object has not cleared the detection zone after a designated period. |
| Test |
| DET-01-24.1 |
| The detection system shall allow the user to determine the length of duration required before object is omitted as a detection actuation. |
| Test |
| DET-01-24.2 |
| The detection system should issue an IP alarm when an object has not cleared the detection zone after a specified period. |
| Test |
| DET-01-25 |
| The detection system, if applicable, shall allow the user to convert the 360-degree video feed from a spherical view to a flat view (de-warp). |
| Demonstration |
| DET-01-27 |
| The detection system, if applicable, should allow for the user to record video with a time stamp. |
| Demonstration |
| DET-01-28 |
| The detection system shall allow system user to view the video camera(s) feed or detection inputs real-time. |
| Demonstration |
| DET-01-30 |
| The detection system shall have a local processor with sufficient memory to store system data and applicable video/detection inputs locally for 24 hours. |
| Demonstration |
| DET-01-30.2 |
| The detection system shall process the data at the edge. |
| Demonstration |
| DET-01-30.3 |
| The detection system shall allow the user to access the data through the central platform. |
| Demonstration |
| DET-01-30.31 |
| The user interface shall have assignable security levels. |
| Demonstration |
| DET-01-30.4 |
| The detection system shall allow the user to record and transmit data through IP. |
| Demonstration |
| DET-01-31 |
| The detection system should allow an updateable library to detect, track, and identify objects. |
| Demonstration |
| DET-01-32 |
| The detection system equipment should sustain wind speeds up to 125 mph. |
| Test |
| DET-01-33 |
| The detection system shall simultaneously operate with pedestrian push buttons/accessible pedestrian signals as a fail-safe and a means to detect/communicate detection to the visual impaired. |
| Test |
| DET-01-34 |
| The City of Pittsburgh shall own the data collected by the detection system. |
| Demonstration |
| DET-01-35 |
| The detection system shall provide software updates, patches, and upgrades for 5 years. |
| Demonstration |
| DET-01-36 |
| The detection system shall have a local processor that is field hardened and capable of working in temperatures between -29F to 165F. |
| Demonstration |
| DET-02-1.13 |
| The detection system shall allow access to all system outputs including video if applicable. |
| Demonstration |
| DET-02-2 |
| The detection system shall allow the user to set detection zones with delay(s) for: |
- Motorized Vehicles
- Pedestrians
- Bicycles Demonstration
| DET-03-1 |
| The detection system shall be able to collect traffic data. |
| Demonstration |
| DET-03-2 |
| The detection system shall report data outputs with low latency (equal or less than a second) near real-time. |
| Demonstration |
| DET-03-3 |
| The detection system shall transmit data through the IP. |
| Demonstration |
| DET-03-3.1 |
| The detection system shall utilize the system communication network to allow for near real-time download and upload of data to the integrated systems. |
| Demonstration |
| DET-03-3.2 |
| The detection system shall store data on the local processor for a minimum of 72 hours. |
| Demonstration |
| DET-03-4 |
| The detection system output shall be available through an API. NTCIP 1209 is not required to transport every system data product. |
| Test |
| DET-03-5 |
| The detection system shall count traffic by approach (link), turning movement count, and lane by lane. |
| Analyze |
| DET-03-5.1 |
| The detection system shall count traffic exiting the intersection by lane and approach. |
| Analyze |
| DET-03-6 |
| The detection system shall classify the counts by vehicle modes/classification as identified object. |
| Analyze |
| DET-03-8 |
| The detection system should report the detected object's speed. |
| Analyze |
| DET-03-9 |
| The detection system should report the detected object's trajectory. |
| Analyze |
| DET-03-10 |
| The detection system should report the detected object's location. |
| Analyze |
| DET-04-1 |
| The detection system should prepare and maintain interface documentation sufficient to support system configuration, integration, testing, commissioning, operation, and maintenance. At a minimum, the documentation shall identify, as applicable: |
1. Interfaces used by the proposed system;
2. Data exchanged through each interface;
3. Detection-zone identifiers;
4. Controller detector-channel and/or phase mappings;
5. Applicable NTCIP 1209 functions;
6. API endpoints and applicable data structures;
7. Authentication and access-control requirements;
8. Third-party system dependencies; and
9. Interface test and validation procedures.
Demonstration
| DET-05-1 |
| The detection system shall utilize a hardwired connection between the field sensors and applicable cabinet equipment |
| Demonstration |
Appendix B3: Open Question and Answer
| Question 1A |
| Is the detection system capable of detecting and notifying the controller that pedestrians remain within the cross walk near the end of the “flashing don’t walk time” or steady “don’t walk”? |
Response
Response
| Question 1C |
| If this has this been implemented elsewhere, please provide contact info. |
Response
| Question 2A |
| Is the detection system capable of detecting and tracking individual object wait-time, i.e., tracks the time the object enters a designated boundary (or detection zone) and leaves the designated boundary (or detection zone)? |
Response
Response
| Question 2C |
| If this has this been implemented elsewhere, please provide contact info. |
Response
| Question 3 |
| Are there any features not discussed in this procurement that would aid the City of Pittsburgh in reaching their goals highlighted in the Concept of Operations? |
Response
| Question 4A |
| Has your product been independently reviewed for accuracy? |
Response
| Question 4B |
| If so by whom? |
Response
| Question 4C |
| What were the results by mode? |
Response
| Question 4D |
| Please provide the verification document and contact. |
Response
| Question 5A |
| Is the detection system capable detecting and tracking individual objects in the field of view rather than utilizing boundaries (detection zones)? With object tracking, is the system able to place a call into the controller by identifying the trajectory of the object (approaching a specific route) and dropping the object (leaving the specific route)? |
Response
| Question 5B |
| If this has this been implemented elsewhere, please provide contact info. |
Response
| Question 6A |
| Is the detection system capable of capturing and reporting ATSPMs (Automated Traffic Signal Performance Metrics)? If so, what ATSPMS are available? |
Response
| Question 6B |
| How and what format are the ATSPMs provided? |
Response
| Question 6B |
| If ATSPMS have been collected and reported elsewhere, please provide contact info. |
| Question 7A |
| Is the detection system capable of capturing and reporting custom performance metrics? If so, what custom performance metrics are available? |
Response
| Question 7B |
| How and what format are the custom performance metrics provided? |
Response
| Question 7C |
| If custom performance metrics have been collected and reported elsewhere, please provide contact info. |
Response
B3.1 NOTE** - The Open Answer should clearly state if the feature requires an additional cost and if an additional cost, please include in the applicable price/cost tables (Appendix C) and note them as “Optional” in the bidder pricing forms. Optional Costs will not be included in the price evaluation.
B1.10
Appendix B4: References and Past Implementation
| Location |
| Point of Contact |
| Number of Devices Installed |
| Deployment Date (Month |
/Year) Was the system used to detect motorized and non-motorized travel, if so which modes?
1.
Name:
Organization:
Address:
E-mail:
Phone:
1. Motorized Vehicles:
2. Pedestrians:
3. Bicycle/Bike(+):
2.
Name:
Address:
1. Motorized Vehicles:
3.
Name:
Address:
1. Motorized Vehicles:
4.
Name:
Address:
1. Motorized Vehicles:
5.
Name:
Address:
1. Motorized Vehicles:
B4.1
Appendix C1: List of SmartPGH Phase 1 Potential Multimodal Detection System Installations - 2027
Permit Plan Number (SmartPGH Intersection Number)
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-514
(95) Second Ave and Ross St
TS-596*
(96) Second Ave and Manor Dr/Garage
TS-640
(97) Second Ave and Municipal Courts Dr
TS-48*
(98)
Second Ave and 10th St Bridge/ Armstrong Tunnel
(SmartPGH Intersection Number)
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-631
(99) Second Ave and Pittsburgh Parking Authority Parking Lot
TS-612
(101) Second Ave and Technology Dr West
TS-671
(102) Second Ave and Middle Access Dr
TS-572
(108) Second Ave and Mobile St
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-394*
(109) Second Ave and Hazelwood Ave
TS-323
(110) Second Ave Flowers Ave
TS-573
(111) Second Ave and Tecumseh St
TS-284
(112) Second Ave and Elizabeth St
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-560
(113) Second Ave and Mansion St
TS-382
(114) Second Ave and Glenwood Ave
TS-681
(36) Fifth Ave and University Pl
TS-243
(72) Forbes Ave and Craft Ave
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
| TS-325 *(73) |
| Forbes Ave and Halket St |
TS-329
(74) Forbes Ave and McKee Pl
TS-330
(75) Forbes Ave and Meyran Ave
TS-054
(76) Forbes Ave and Atwood St
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
| TS-551 *(77) |
| Forbes Ave and Oakland Ave |
TS-131
(78) Forbes Ave and Bouquet St
TS-717
(79) Forbes Ave and David Lawrence Hall
TS-120
(80) Forbes Ave and Bigelow Blvd / Schenley Dr
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-336
(81) Forbes Ave and Schenley Dr Ext
Installation and Maintenance Training for Phase 1
5-Year Subscription (yearly fee) Lump Sum
| Total |
| Equipment and Services Total Quantity |
| Total Component Price |
| Total Phase 1 Price |
*Intersections marked for Accuracy Evaluation
C1.2
Appendix C2: List of SmartPGH Phase 1 Potential Multimodal Detection System Installations – 2032
Permit Plan Number (SmartPGH Intersection Number)
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-514
(95) Second Ave and Ross St
TS-596*
(96) Second Ave and Manor Dr/Garage
TS-640
(97) Second Ave and Municipal Courts Dr
TS-48*
(98)
Second Ave and 10th St Bridge/ Armstrong Tunnel
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-631
(99) Second Ave and Pittsburgh Parking Authority Parking Lot
TS-612
(101) Second Ave and Technology Dr West
TS-671
(102) Second Ave and Middle Access Dr
TS-572
(108) Second Ave and Mobile St
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-394*
(109) Second Ave and Hazelwood Ave
TS-323
(110) Second Ave Flowers Ave
TS-573
(111) Second Ave and Tecumseh St
TS-284
(112) Second Ave and Elizabeth St
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-560
(113) Second Ave and Mansion St
TS-382
(114) Second Ave and Glenwood Ave
TS-681
(36) Fifth Ave and University Pl
TS-243
(72) Forbes Ave and Craft Ave
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
| TS-325 *(73) |
| Forbes Ave and Halket St |
TS-329
(74) Forbes Ave and McKee Pl
TS-330
(75) Forbes Ave and Meyran Ave
TS-054
(76) Forbes Ave and Atwood St
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
| TS-551 *(77) |
| Forbes Ave and Oakland Ave |
TS-131
(78) Forbes Ave and Bouquet St
TS-717
(79) Forbes Ave and David Lawrence Hall
TS-120
(80) Forbes Ave and Bigelow Blvd / Schenley Dr
| Example Ave Location |
| Do you recommend deploying your system at this intersection? |
If not, why not?
| Servies and Equipment Needed (Include Item and Quantity) |
| Price / |
Component Total Intersection Price
TS-336
(81) Forbes Ave and Schenley Dr Ext
Installation and Maintenance Training for Phase 1
5-Year Subscription (yearly fee) Lump Sum
| Total |
| Equipment and Services Total Quantity |
| Total Component Price |
| Total Phase 1 Price |
*Intersections marked for Accuracy Evaluation
C2.2
Appendix C3: Yearly (Subscription) Price Subscription
Subscription
Optional Subscription Only
C3.2
Component:
3-Day Training
| Year |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
Appendix C4 - Pricing
Component:
| Year |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
Optional Components Only:
| Year |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
| Cost |
C4.1