5-26TH10RFI Attachment B - Technical Questionnaire Capability Responses - FINAL 03.18.2026.pdf

Jordan School District RFI # 26TH10RFI Attachment B

RFI # 26TH10RFI

Attachment B

Technical Questionnaire & Capability Responses

(This document to be submitted with RFI response.)

Please read all instructions below to ensure all required documentation is submitted with your response.

The capability areas listed below reflect JSD’s current needs and desired outcomes, based on existing network infrastructure and lessons learned from the current network monitoring platform.

Vendors should use this questionnaire to explain how their platform fulfills each capability area, including:

• How the network monitoring solution is implemented.

• Which product(s), module(s), or edition(s) are required.

• Whether the solution is core or requires add-ons.

• Key limitations, tradeoffs, or assumptions.

A. NETWORK ARCHITECTURE

Describe the overall Network Monitoring Solution architecture and agent model.

Describe how solution supports multi-site environments with centralized visibility while operating operational monitoring across distributed locations.

Describe support for centralized infrastructure with optional local caching or distribution nodes.

B. DEPLOYMENT MODEL

Describe your solution and how it can support on-premises deployment models with optional cloud services for mobile access, alert delivery, or remote monitoring.

Solutions that require full cloud-hosted monitoring infrastructure or rely exclusively on SaaS-based management platforms may not meet operational requirements.

Preferred architectures include:

• Fully on-premise monitoring platforms

• Hybrid systems with local collectors and optional cloud services

• Platforms that retain operational monitoring and telemetry data within the local environment

C. OPERATIONAL MONITORING REQUIREMENTS

Describe your comprehensive monitoring solution.

JSD requires comprehensive monitoring across multiple layers of the network infrastructure including:

• Network device health and performance

• Link utilization and error conditions

• Environmental and hardware health metrics

• Traffic analysis and capacity planning

• Wireless performance and client experience monitoring

Monitoring systems must provide clear operational visibility, historical data analysis, and automated alerting for network events and anomalies.

D. ALERTING AND INCIDENT RESPONSE

Describe how your solution supports multiple alerting mechanisms to notify IT staff of operational issues in real time.

Preferred alerting capabilities include:

• Email alerts

• SMS/text message alerts

• Mobile push notifications

• Desktop notifications

• Webhook integrations with collaboration platforms (such as Slack)

Alerts should support threshold-based monitoring, anomaly detection, and customizable escalation workflows.

E. DEVICE TELEMETRY AND HARDWARE MONITORING

Describe your solution’s ability to collect and interpret device telemetry through SNMP or similar protocols.

This includes monitoring for:

• Power supply status

• Fan status and hardware failures

• Device temperature sensors

• Interface status and operational statistics

Solutions should also allow direct access to OID libraries for monitoring vendor-specific telemetry, such as:

• SFP optical light levels

• SFP voltage readings

• SFP temperature readings

F. PERFEORMANCE AND TRAFFIC ANALYSIS

Describe your solution’s visibility into both network utilization and application traffic patterns.

Solutions should support:

• Bandwidth monitoring

• Interface utilization tracking

• NetFlow or sFlow traffic analysis

• Packet-level inspection for identifying latency, jitter, and packet loss conditions

These capabilities are important for troubleshooting performance issues and identifying congestion or abnormal traffic patterns.

G. NETWORK VISUALIZATION AND MAPPING

Describe how your solution provides dynamic network visualization capabilities, including:

• Network topology maps

• Device dependency mapping

• Link state monitoring

• Link speed identification

• Configurable link thresholds

Visualization tools should allow administrators to quickly identify infrastructure failures or degraded network conditions.

H. NETWORK ADDRESS AND DEVICE TRACKING

Describe your solution’s tools to assist in tracking device connectivity and troubleshooting endpoint behavior.

Preferred capabilities include:

• IP address lookup

• MAC address lookup

• Historical IP/MAC address correlation

• Access to ARP and FDB tables

• Historical tracking of endpoint network associations

These tools assist IT staff in troubleshooting connectivity and identifying devices within the network.

I. LOGGING, EVENT CORRELATION, AND HISTORICAL ANALYSIS

Describe how your solution supports centralized log collection and analysis capabilities.

Required capabilities include:

• Log retention for a minimum of 2–6 weeks

• Full-text search across collected logs

• Correlation of logs with network events

• Network event timelines and audit trails

The platform should also support:

• Custom database queries for advanced troubleshooting

• Correlation between network telemetry, logs, and configuration changes

J. CONFIGURATION MANAGEMENT AND CHANGE TRACKING

Describe your solution’s ability to include configuration management capabilities for network devices.

Desired functionality includes:

• Automated configuration backups

• Configuration comparison with change detection

• Historical configuration versioning

• Firmware version tracking for primary and secondary firmware images

These capabilities assist with auditing changes and maintaining configuration consistency across the environment.

K. WIRELESS NETWORK MONITORING

Describe your solution’s wireless infrastructure monitoring abilities. The solution should include visibility into wireless access point performance and SSID-level metrics.

Preferred capabilities include:

• Wireless access point health monitoring

• SSID performance metrics

• Client performance indicators

• Wireless infrastructure alerts

L. AUTOMATION AND SYSTEM INTEGRATION

Describe how your solution supports integration with other systems through modern automation interfaces.

Preferred capabilities include:

• REST-based APIs

• Automation integration with external tools

• Webhooks for alert forwarding

• Ability to integrate with other systems for future expansion

M. CLIENT ACCESS AND MOBILE SUPPORT

Describe how your solution provides remote access capabilities for operational staff.

Desired access methods include:

• Web-based administration interface

• Mobile applications for both iOS and Android

• Secure remote monitoring capabilities for administrators

N. SUPPORT AND OPERATIONS

Describe your solution’s support offerings including:

• Paid support models

• Availability of 24/7 support during support contract periods

• Escalation procedures for critical incidents

• Access to documentation, knowledge bases, and support resources

O. COST STRUCTURE

While pricing should not be included in the RFI response, vendors should describe the general licensing structure of their platform including:

• Licensing models (device-based, interface-based, subscription, etc.)

• Required modules or add-ons for full functionality

• Hardware or infrastructure requirements