IT Service Monitoring Requirements Matrix short.xlsx
XLSX spreadsheet 27 KB Posted
- Attached to
- IT Operations Center (ITOC) Software
- Solicitation number
- 3003530
- Issued by
-
Defense Finance and Accounting Service
About this file
The file is a Requirements Matrix for IT Service Monitoring, detailing comprehensive monitoring specifications for the Defense Finance and Accounting Service (DFAS) IT Operations Center (ITOC). The matrix outlines 64 specific requirements across priority 1 and 2 indicators, covering monitoring needs for platforms, databases, websites, networks, and integration capabilities. Key monitoring domains include automation, early problem detection, security threat monitoring, root cause analysis, scalability, and comprehensive visibility across IT infrastructure.
The requirements specify detailed metrics and capabilities, such as businessTransaction monitoring, end-user response times, resource utilization tracking, distributed tracing, and integration with tools like ServiceNow, PagerDuty, and various monitoring platforms (New Relic, Splunk, etc.). Critical technical specifications include mandatory Interoperability Level 5 (IL5) security certification, support for cloud and on-premises environments, and the ability to provide real-time status on critical financial systems. The document serves as a pre-solicitation Request for Information to identify commercial off-the-shelf (COTS) monitoring software that can meet DFAS's enterprise-wide monitoring needs, with an estimated performance period starting in October 2026.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DON - ITOC Technical Requirements - V1.0 - 14 Aug 2025.docx | DOCX document |
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
Requirements
| Req. | Requirements - Priority 1 | Indicators | Detailed Requirement Description | |
| # | Effectiveness | Efficiency | ||
| R.1.1 | Automation | Platform must possess the ability to comprehensively self-monitor internal performance and evaluate trends and performance issues. Shall automate intelligent alert generation/routing, incident response, and remediation tasks. | ||
| R.1.2 | Early Detection | Platform must identify critical problems before they impact users or cause significant damage. Must posses prognostics capabilities to identity issues with Priority 1 requirements. | ||
| R.1.3 | Security Threat Detection | Shall monitor for suspicious activity that could indicate a security breach. | ||
| R.1.4 | Fast Root Cause Analysis | Must provide quick and efficient diagnosis of issues. Must correlate data from multiple sources and utilize built-in intelligence to identify specific root causes. | ||
| R.1.5 | Compliance and Auditing | Platform shall log data for compliance with regulatory requirements and auditing purposes. | ||
| R.1.6 | Operational Cost Accountability | Shall posses the ability to trace and account for origination of operational costs. | ||
| R.1.7 | Scalability | Must be able to scale to accommodate future growth and changes in the environment. This includes handling increasing data volumes and the addition of new components. | ||
| R.1.8 | Maintainability | Monitoring platform shall be easy to maintain and update. This includes clear documentation, well-defined processes for adding new monitored items, and a plan for upgrading the monitoring tools. | ||
| R.1.9 | Cost-Effectiveness | Monitoring platform shall provide value that justifies its cost, including both initial implementation costs and ongoing operational costs. | ||
| R.1.10 | Comprehensive Visibility | Shall provide a complete hierarchical and visual status of the health and performance of all artifacts/components (platform, database, website, network) and their interdependencies. |
| # | Priority 2 | Indicators | Detailed Requirement Description | ||
| Effectiveness | Efficiency | ||||
| Platform Monitoring Metrics | |||||
| R.2.1 | Business Transaction Monitoring (Lagging) | Platform shall monitor the performance of DFAS-identified critical business transactions (e.g., placing an order, processing a payment) to ensure they meet business needs. | |||
| R.2.2 | End-user Response Time (Lagging) | Platform must provide the percentage of end-user requests and categorize distinct types of errors (e.g., HTTP 500 errors, platform-specific exceptions). | |||
| R.2.3 | Dependency Performance (Leading) | Platform shall track the performance of calls to external APIs, databases, and other services. | Performance Optimization: Provide built-in analytics to identify performance bottlenecks and areas for improvement to optimize performance and resource utilization. | ||
| R.2.4 | Platform Logs / Crash Reporting / Error Rate (Lagging) | Platform shall measure how it takes for DDA platform to respond to requests, track average, 95th percentile, and maximum response times. Shall provide centralize logging for errors, warnings, and other important events. | |||
| R.2.5 | Throughput (Leading) | Platform must provide the number of requests the platform can handle per unit of time (e.g., requests per second). | |||
| R.2.6 | Resource Utilization / Garbage Collection | Platform shall monitor CPU usage, memory usage, disk I/O, and network I/O. Must monitor platforms and their use of server utilization for platforms that use garbage collection (e.g., Java, .NET) and monitor GC frequency/duration. | |||
| R.2.7 | Custom Metrics | DFAS shall be able to generate platform-specific metrics that are relevant to the business logic (e.g., number of orders processed, number of logins). Generation shall not require specialized skills or generation of code. | |||
| R.2.8 | Code-Level Profiling | Platform shall provide functionality to drill down into code to identify specific lines of code that cause performance problems (e.g., advanced APM tools). | |||
| R.2.9 | Distributed Tracing | Platform shall support user microservices architectures and provide requests as they flow through different services. Distributed tracing helps identify bottlenecks and dependencies across services. | |||
| R.2.10 | Crash Reporting (Lagging Indicator | Platform shall provide detailed and relevant crash reports to help developers diagnose and fix platform crashes. |
| Database Monitoring (SQL, Oracle DB) Metrics | ||
| R.2.11 | Unexpected Downtime / Error Logs / Dead-Locking | Platform shall track how many hours per DFAS-defined time periods the database is not available to dependent platforms/users (documented in the service level agreement) outside approved maintenance windows. |
| R.2.12 | Query Performance / Transaction Throughput / Slow Query Logging | Platform must monitor the execution time of queries, and shall identify slow queries and optimize them or pinpoint table calls for review. |
| R.2.13 | Database Resource Utilization | Shall monitor CPU usage, memory usage, disk I/O, and network I/O. |
| R.2.14 | Backup and Recovery Monitoring | Must monitor the status of database backups and ensure they are performed according to DFAS-defined requirements. |
| R.2.15 | Database-specific Metrics | Shall provide database specific metrics, including, but not limited to: redo log space waits, latch contention, PGA memory usage, buffer cache hit ratio, and page life expectancy. |
| R.2.16 | Connection Pool Usage | Must monitor and report number of active and idle connections in the connection pool. |
| R.2.17 | Database Size | Shall monitor and report sizes of databases and tables. |
| R.2.18 | Index Usage | Shall identify and report unused or missing indexes. |
| R.2.19 | Replication Lag | Shall monitor and report the replication lag between primary and secondary databases. |
| R.2.20 | Transaction Throughput | Shall track and report the number of transactions processed per DFAS-defined unit of time. |
| R.2.21 | Deadlocks | Shall monitor and report deadlocks. |
| R.2.22 | Error Logs | Shall monitor and report database error logs for critical errors. |
| R.2.23 | Query Plan Analysis | Shall provide the functionality to analyze query plans to identify inefficient queries. |
| R.2.24 | Storage Capacity Planning | Shall monitor disk space usage and provide predictive functionality that identifies additional storage needs. |
| R.2.25 | Audit Logging | Shall monitor and report database audit logs for security events. |
| R.2.26 | Slow Query Logging Configuration | Shall monitor slow queries and provide logs for review. |
| Website Monitoring Metrics | ||
| R.2.27 | User Experience | Shall track and report metrics including, but not limited to time on site, bounce rates, and conversion rates. |
| R.2.28 | Response Time | Shall measure and report time taken for website loading, page load time, time to first byte (TTFB), and other DFAS-identified performance metrics. |
| R.2.29 | Synthetic Monitoring | Shall simulate user interactions to proactively identify role-based website problems. Capability shall include testing of critical DFAS-identified workflows such as login, search, and checkout. |
| R.2.30 | Mobile Website Monitoring | Shall monitor and report performance of websites accessed through mobile devices. |
| R.2.31 | Error Rate | Shall measure and report requests that result in errors. |
| R.2.32 | API Monitoring | Shall monitoring the performance and availability of APIs used by the website. |
| R.2.33 | Availability | Platform shall track how many hours per DFAS-defined time periods the website is not available to platforms/users (documented in the service level agreement) outside approved maintenance windows. |
| R.2.34 | Page Size | Shall monitor and report the size of web pages. |
| R.2.35 | Resource Loading Times | Shall track and report the loading times of images, CSS, and JavaScript files. |
| R.2.36 | SSL Certificate Expiry | Shall monitor and report the expiration dates of SSL certificates. |
| R.2.37 | Content Integrity Monitoring | Shall detect and report unauthorized changes to website content (e.g., defacement). |
| R.2.38 | Geographic Performance Monitoring | Shall measure and report website performance from different geographic locations to identify regional issues. |
| Network Monitoring Metrics | |||
| R.2.39 | Latency | Shall measure and report the time it takes for data to travel between DFAS-defined points on the network. | |
| R.2.40 | Packet Loss | Shall track and report percentage of packets that are lost in transit. | |
| R.2.41 | Throughput | Shall measure and report the amount of data that can be transmitted over the network per unit of time. | |
| R.2.42 | Bandwidth Utilization | Shall display and report real-time percentages of available bandwidth and trends. | |
| R.2.43 | Network Device Health | Shall monitor and report health of network devices such as routers, switches, and firewalls. | |
| R.2.44 | Network Interface Status | Shall display, monitor, and report the status of network interfaces (e.g., up/down). | |
| R.2.45 | DNS Resolution Time | Shall display, monitor, and report the time it takes to resolve domain names | |
| R.2.46 | Firewall Logs | Shall monitor and report firewall logs for suspicious activity. | |
| R.2.47 | Wireless Network Monitoring | Shall display, monitor, and report performance and security of wireless networks. | |
| R.2.46 | Cloud Network Monitoring | Shall display, monitor, and report network traffic and pE71:E72 performance within cloud environments (e.g., AWS VPC, Azure VNet, Google Cloud VPC). | ` |
| R.2.47 | Traffic Analysis | Shall utilize network traffic analysis tools to identify unusual traffic patterns that could indicate a security breach or performance problem (e.g. excessive traffic to/from a specific IP address). | |
| R.2.48 | SNMP Traps | Shall configure network devices to send SNMP traps to the monitoring platform when certain events occur (e.g., device failure, interface down). | |
| R.2.49 | QoS Monitoring | Shall display, monitor, and report quality of service (QoS) on the network to ensure that critical platforms are receiving the bandwidth they need. |
| Common Monitoring Tools | ||
| R.2.50 | APM | At a minimum, shall interface with following: New Relic, Dynatrace, AppDynamics, Datadog, Elastic APM, and Logic Monitor. |
| R.2.51 | Log Management | At a minimum, shall interface with following: Splunk, ELK Stack (Elasticsearch, Logstash, Kibana), and Graylog. |
| R.2.52 | Database Monitoring | At a minimum, shall interface with following: SolarWinds DPA, Datadog, Percona Monitoring, and Management (PMM). |
| R.2.53 | Website Monitoring | At a minimum, shall interface with following: Pingdom, UptimeRobot, StatusCake, Google PageSpeed Insights, WebPageTest, and Gtmetrix. |
| R.2.54 | Network Monitoring | At a minimum, shall interface with following: SolarWinds NPM, PRTG Network Monitor, and Zabbix. |
| R.2.55 | Infrastructure Monitoring (Cloud/VMs/Servers) | At a minimum, shall interface with following: Datadog, Prometheus + Grafana, Nagios, Zabbix, CloudWatch (AWS), Azure Monitor, and Google Cloud Monitoring. |
| Integration / Alerting | ||
| R.2.56 | ServiceNow | Solution shall allow for native integration to ServiceNow to open/update tickets for DFAS-identified alerts. |
| R.2.57 | On-Call Scheduling | Shall integrate with, at a minimum, on-call PagerDuty and Opsgenies scheduling tools that allow DFAS-personnel to be notified in accordance with DFAS notification criteria. |
| R.2.58 | Configuration Change Messaging | Shall provide daily/weekly/monthly reports on changes on the hardware, software, and platforms. |
| R.2.59 | Escalation Policies | Shall allow configuration and implementation of DFAS alert escalation policies. |
| R.2.60 | Alert Suppression/Deduplication | Shall provide functionality to configure suppression of duplicate alerts. |
| R.2.61 | Runbook Automation | Shall integrate with runbook automation tools to automatically execute pre-defined remediation steps when certain alerts are triggered. |
| R.2.62 | Incident Management Metrics | Shall generate DFAS-identified incident-related metrics (e.g., mean time to resolution (MTTR) and mean time between failures (MTBF)). |
| R.2.63 | Alert Throttling | Shall prevent alert storms by throttling the number of alerts that are sent. |
| R.2.64 | Integration with ChatOps Platforms (e.g., Slack, Microsoft Teams) | Shall enable teams to collaborate on incident resolution within chat channels. |
| General Requirements | ||
| Agent Management | Shall provide functionality to configure how agents are deployed, updated, and managed across the infrastructure. | |
| Data Retention Policies | Shall provide records management functions to retain data per DFAS-defined records retention policies. | |
| Security of the Monitoring platform | Shall meet the DFAS minimum of Interoperability Level (IL) Level 5 classification, including, but not limited to, access controls, encryption, and regular security audits. If vendor cannot meet IL5 requirement, provide the current IL level product can support. | |
| Training | Shall provide training to users on how to use and configure the monitoring platform. | |
| Governance | Platform must support DFAS governance policies and allow, at a minimum, configuration of adding new monitors, updating configurations, and alerts workflows. | |
| Documentation | Shall provide all documentation for the administration, configuration, and use of monitoring platform. |
File details come from the government source that posted it. Updated .