The vendor is required to provide information statements for an upgraded fuel management system needed in our school district.
- To explore available technologies and system capabilities in the fuel management market.
- System information on modern fuel management solutions to replace its aging system, last updated in 2020 with software from 2014.
- The legacy system poses growing security risks and lacks key capabilities such as reliable credential management, cloud access, license plate recognition, and multi-agency integration.
- Comprehensive product information, security features, integration capabilities, and examples of implementation to inform a future procurement process
- Current system
• Installed hardware at the pump is from 2020.
• Software is based on outdated SQL (2014) and poses ongoing security risks.
• Current key-based access is unreliable; old keys cannot be reprogrammed—only replaced. • Multiple agencies use the system: weld re-4 school district, district, and the local fire protection district. 
• Current software does not support modern features such as auto-alerts, cloud access, or license plate recognition.
- Provide information on current technologies and innovations, including (but not limited to):
• Software features
o Cloud-based management interface.
o Robust user and access control with audit trails.
o Role-based access for multiple agencies.
o Secure remote administration.
o Real-time reporting and vehicle usage data.
o Compatibility with third-party systems (e.g., phoenix software).
• Security and access control
o Two-factor or multifactor authentication.
o License plate recognition and camera integration.
o Integration with district door access control systems.
o Data encryption, secure hosting, and regular security updates.
• Hardware and infrastructure
o Head-end pump system updates.
o One-wire connection and internal switch compatibility.
o Ruggedized components for outdoor conditions.
o Self-service diagnostics and reboot functionality.
• Integration capabilities
o Ability to integrate with other municipal partners.
o Network safety and security protocols.
o Alerts and notifications based on usage, location, or safety thresholds.
• Operational considerations
o Recurring service or software-as-a-service (SaaS) licensing costs.
o Training resources and customer support structure.
o Scalability to support future facility or fleet growth.
- Questions/Inquires Deadline: June 19, 2025