2-RFP 25-014 School Flashing Beacons Questionnaire.xlsx
XLSX spreadsheet 35 KB Posted
- Attached to
- RFP Traffic School Flashing Beacons Replacement
- Solicitation number
- 25-014
- Issued by
- Douglas County, Colorado
About this file
This file is a technical requirements questionnaire for RFP 25-014 issued by the Town of Parker, Colorado, seeking replacement school flashing beacon systems for their existing Eltec School Flasher Assemblies. The document outlines comprehensive software and hardware functional requirements that vendors must evaluate for compliance, including general software functions, communication capabilities, alarm systems, power logging, and physical controller specifications. The software requirements emphasize web-based or installed application capabilities, radio or cellular communication with 10-year data plan options, automatic firmware upgrade notifications, user access controls, and daylight savings time management. Hardware specifications require controllers capable of 12-24 VDC operation with 120 VAC option, environmental operation ranges from -34.6°F to +165.2°F, mounting capability on 4-inch poles, Federal Green #10456 paint finish, Ethernet connectivity, USB ports, and integrated keypads with optional touchscreens.
The questionnaire uses a scoring matrix where vendors must indicate compliance levels (Compliant, Partially Compliant, or Not Compliant) for each requirement, with weighted scoring of 10 points for required compliant functions, 5 points for optional compliant functions, and 0 points for non-compliant items. The document contains some formatting errors in the scoring calculations but establishes clear evaluation criteria for solar-powered beacon systems with secure enclosures, communication modules, status indicators, and knock-down alarm sensors. Vendors must provide system information including primary contact details, software/firmware versions, and hardware specifications as part of their response to demonstrate their ability to replace the existing Eltec systems with modern, feature-compliant alternatives.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 1-RFP 25-014 Traffic School Flashing Beacons Replacement.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
Software Requirements Traffic School Flashing Beacons RFP 25-014
| Traffic School Flashing Beacons Functional Requirements | System Vendor: |
| Primary Contact: | |
| Unit Software & Version: | |
| Unit Hardware & Version: |
For each Function noted, please identify if your proposed system/product is Compliant, Partially Compliant or Not Compliant. Please use Comments box to explain the reason for any Functions that are noted Partially Compliant.
| Traffic School Flashing Beacons Software Functional Requirements | ||||||||||||
| A | B | C | E | F | G | H | I | J | K | L | M | N |
| # | Category | Function | Function Compliance | Comments | Score | |||||||
| Required | Optional | Compliant | Partially Compliant | Not Compliant | Category Score | Compliance Score | Weighted Score | |||||
| 10 | 5 | 10 | 5 | 0 | ||||||||
| 1. General Software Functions | ||||||||||||
| Function | Description | |||||||||||
| 1.1.1 | X | Interaction Standards | Software must be capable of interacting with radio setup or must have a 10-year data plan for cellular | 10 | 0 | 0 | ||||||
| 1.2.1 | X | General Setup | Software must be capable of web-based or installed application on central system. | 10 | 0 | 0 | ||||||
| 1.2.2 | X | Each user shall be able to access all data fields in the controller through a database editor embedded in software program. | 10 | 0 | 0 | |||||||
| 1.3.1 | X | Standard Location Labeling | Street Location | 10 | 0 | 0 | ||||||
| 1.3.2 | X | Traveling Direction | 10 | 0 | 0 | |||||||
| 1.3.3 | X | School Name | 10 | 0 | 0 | |||||||
| 1.4.1 | X | Software Version Control | The software shall have a data field readable in application showing the version that is currently being utilized | 10 | 0 | 0 | ||||||
| 1.4.2 | X | Automated notice of available Manufacturer firmware upgrades, with user initiated firmware installation. | 5 | 0 | 0 | |||||||
| 1.5.1 | X | Software Upgrades | Each user shall be automatically notified by the vendor when firmware upgrades are available. The notification must also include a description of changes to the firmware. | 10 | 0 | 0 | ||||||
| 1.5.2 | X | The firmware shall allow each user to manually download upgrades to the local controller firmware from a remote location. | 5 | 0 | 0 | |||||||
| 1.5.3 | X | A controller restart shall be required to replace the existing firmware. | 5 | 0 | 0 | |||||||
| 1.5.4 | X | A firmware upgrade shall be aborted in the event of any power interruption, and unit should revert to last good operating version. | 5 | 0 | 0 | |||||||
| 1.5.5 | X | The firmware shall verify that the upgraded firmware was successfully downloaded to the controller without any errors. | 10 | 0 | 0 | |||||||
| 1.6.1 | X | User Tools | The firmware shall provide a copy and paste capability for user-entered parameters. The functionality shall be available for individual cells, rows, columns, and full tables. | 5 | 0 | 0 | ||||||
| 1.6.2 | X | The firmware shall require each user to confirm any changes to the controller database prior to accepting the change or downloading a change into the controller from a laptop or other device. | 10 | 0 | 0 | |||||||
| 1.6.3 | X | Changes shall take effect upon confirmation by each user. | 10 | 0 | 0 | |||||||
| 1.6.4 | X | Typical activities the firmware shall allow remotley include but not be limited to the ability to: manage field assets including an entity tree view of the system, monitoring manual commands, unit status display, upload compare, download controller timing and troubleshooting by maintenance personnel through either vendor-provided software installed on maintenance laptops or other devices. | 10 | 0 | 0 | |||||||
| 1.6.5 | x | All of the User Tools including database editor with upload and download capabilities shall be available in the field through either vendor provided software or through a standard web browser or applicaion if a connection to central system is not available | 10 | 0 | 0 | |||||||
| 1.7.1 | X | Daylight Savings | The firmware shall provide the capability to automatically adjust the controller clock to reflect daylight savings time. Dates and time for the start and end of daylight savings time shall be programmable by each user. | 10 | ERROR:#REF! | ERROR:#REF! | ||||||
| 1.7.2 | X | Daylight savings time shall be disabled by default. | 10 | ERROR:#REF! | ERROR:#REF! | |||||||
| 1750 | ERROR:#REF! | |||||||||||
| 2. Other Requirements | ||||||||||||
| Function | Description | |||||||||||
| 2.1.1 | X | Communication | Firmware and controller hardware shall support Ethernet radio or cellular communication. | 10 | 0 | 0 | ||||||
| 2.1.2 | X | Alarms | Ability to send alarm notifications for loss of power and communication. May have the abilty to report de-syncronization or knock down of structure. | 10 | 0 | 0 | ||||||
| 2.1.3 | X | Power Logs | Software shall provide a log of power failure and what time the power failure ended. | 10 | 0 | 0 | ||||||
| 2.1.4 | X | Report Log Date/Time Stamps | Software shall create reporting logs that include date/time stamp occurrence for activations. | 5 | 0 | 0 | ||||||
| 2.1.5 | X | Remote Report Extraction | Software shall allow for all data, logs and reports to be extracted remotely locally. | 10 | 0 | 0 | ||||||
| 2.1.6 | X | Operation Logs | Ability to recall the last five days to review operation. | 5 | 0 | 0 | ||||||
| 0 | 0 | 0 | 500 | 0 | ERROR:#REF! | |||||||
| 0 | ||||||||||||
| Total Available Score | ERROR:#REF! | |||||||||||
| Firmware Score | ERROR:#REF! | |||||||||||
| Percentage of Total for Firmware | ERROR:#REF! |
Hardware Requirements Traffic Signal Controller RFP 2024
| Traffic School Flashing Beacons Physical Requirements | System Vendor: |
| Primary Contact: | |
| Controller Firmware & Version: | |
| Controller Hardware & Version: |
For each Function noted, please identify if your proposed system/product is Compliant, Partially Compliant or Not Compliant. Please use Comments box to explain the reason for any Functions that are noted Partially Compliant.
| Traffic School Flashing Beacons Hardware Requirements | ||||||||||||
| A | B | C | E | F | G | H | I | J | K | L | M | N |
| # | Category | Function | Function Compliance | Comments | Score | |||||||
| Required | Optional | Compliant | Partially Compliant | Not Compliant | Category Score | Compliance Score | Weighted Score | |||||
| 10 | 5 | 10 | 5 | 0 | ||||||||
| 1. General Controller Features | ||||||||||||
| Function | Description | |||||||||||
| 1.1.1 | X | Hardware Standards | The controller shall be capable of receiving and broadcasting real-time information for vehicle and pedestrian counts. | 5 | 0 | 0 | ||||||
| 1.1.2 | X | Electrical Operating Range shall allow applied line voltage: 12 to 24 VDC with an option for 120 VAC | 10 | 0 | 0 | |||||||
| 1.1.3 | X | Inline fuse running between solar power, battery power, and controller | ||||||||||
| 1.1.4 | X | Environmental Operating Ranges shall permit normal operation in humidity of 5% to 95%, and ambient Temperature: -34.6 0 F to +165.2 0 F | ||||||||||
| 1.2.1 | X | Design | The controller and/or batteries shall be installed in a secured enclosurethat has the ability to mount to a 4" pole. | 10 | 0 | 0 | ||||||
| 1.2.2 | X | Enclosure shall be painted Federal Green #10456 | ||||||||||
| 1.2.3 | X | Solar panel assembly shall be capable of mounting to a 4" pole | ||||||||||
| 1.2.4 | X | Corbin 2 style lock for cabinet enclosure | ||||||||||
| 1.2.5 | X | Controller shall include a status light or interface to indicate normal operation or malfunction. | ||||||||||
| 1.3.1 | X | Communications | The controller shall have a 10/100 Mbit Ethernet port including WAN connection | 5 | 0 | 0 | ||||||
| 1.3.2 | X | Connected Vehicle information shall be supported with appropriate co-processor or other vendor recommended boards. | 5 | 0 | 0 | |||||||
| 1.3.3 | X | Shall have communications to controller over radio or cellular | ||||||||||
| 1.3.4 | X | Controller shall include 1 USB 2.0 port for firmware upgrades or database maintenance/transfer. | ||||||||||
| 1.4.1 | X | Human Interface | Controller shall include keypad capable of entering or changing data for all fields of associated firmware. | 10 | 0 | 0 | ||||||
| 1.4.2 | X | Controller shall include graphics card and touchscreen if availabe in product line. | 5 | 0 | 0 | |||||||
| 1.4.3 | X | Controller may provide audible feedback of keystrokes or errors. | 5 | |||||||||
| 1.4.4 | X | Audible feedback if included in controller shall have provisitons to enable/disable by user. | ||||||||||
| 1.4.5 | X | Controller shall include a dedicated ON/OFF test switch for LEDs | 10 | 0 | 0 | |||||||
| 650 | 0 | |||||||||||
| 2. Other | ||||||||||||
| Function | Description | |||||||||||
| 2.1.1 | X | Alarm | Knock down alarm sensor | 5 | 0 | 0 |
image1.png
File details come from the government source that posted it. Updated .