The vendor is required to provide to enhance its ability to monitor, alert, and report on its network infrastructure and related services' health, performance, and availability.
• Offer complete visibility across all networking devices, systems, and services.
• Provide real-time monitoring and proactive alerting to reduce downtime.
• Integrate easily with existing tools (SIEM solutions, ticketing systems, etc.).
• Support scalability, security, and performance analytics.
• Comply with data residency and privacy standards.
- Core functional requirements
• Real-time monitoring of device health, network performance, bandwidth usage, latency, certificates and uptime across physical, virtual, and cloud infrastructure.
• Alerting and notifications based on customizable thresholds, anomalies, and event correlation.
• Dashboards and reports with a centralized and customizable “single pane of glass” view.
• Automatic device discovery across local and remote subnets with classification capabilities.
• Protocol support: SNMP (v2c, v3), NETFLOW/SFLOW, WMI, syslog, and API-based monitoring.
• Cloud service monitoring, including microsoft 365, google workspace, and optional integration with AWS or azure.
• Historical data retention with support for trend analysis and performance forecasting.
• Role-based access control (RBAC) to assign different permission levels to administrators based on primary responsibilities or roles.
• Multi-tenant support, if applicable to the vendor's design and licensing model.
- Deployment and integration
• Deployment options: must support on-premises, cloud-hosted, or hybrid configurations.
• Integration capabilities: seamless integration with SIEM, log collectors, ITSM Platforms, and authentication services.
• API access: full API support for custom integrations or automation.
• Mobile access: secure mobile or web-based interface for remote monitoring and alerts.
• Support for high availability (ha) or clustering to prevent monitoring downtime.
• Migration support: migration assistance and compatibility with existing configurations are desirable if replacing an existing tool.
- Security and compliance
• Data residency: all identifying data must be stored in a data center or repository.
• Data encryption: all stored or transmitted data must be encrypted at rest and in transit.
• Audit logging: tracking and reporting of all administrative or configuration changes for compliance.
- Usability and support
• User interface: intuitive, responsive, and easy to learn for IT administrators.
• Training resources: access to a public knowledge base, user documentation, and training materials should be provided.
• Support and maintenance SLAs: please outline available support tiers and response times.
• Trial or proof of concept availability: indicate if a trial license or PoC environment is available.
- Questions/Inquires Deadline: June 19, 2025
Set up free email alerts and get notified when new government bids, tenders and procurement opportunities match your industry and location. Choose daily or weekly delivery.