Attachment 1 - Statement of Work.pdf
PDF 157 KB Posted
- Attached to
- SolarWinds
- Solicitation number
- FA480326Q0069
About this file
This is a Statement of Work (SOW) prepared by the 20th Communications Squadron at Shaw Air Force Base, South Carolina, dated March 23, 2026, for the procurement and implementation of a SolarWinds network monitoring and management solution on the NIPRNet.
The contractor must procure, furnish, install, configure, and provide training (PFIC&T) for two SolarWinds software products: SolarWinds Observability Self-Hosted Advanced (A500 license tier, quantity 1) and SolarWinds Network Topology Mapper (Standard tier, quantity 1). All software licenses must be new and perpetual with one year of included maintenance and support beginning upon final system acceptance. The contractor is responsible for installing and configuring the platform on government-furnished servers in compliance with DoD Security Technical Implementation Guides (STIGs), executing network discovery scans to identify critical devices, creating a minimum of two custom monitoring dashboards, configuring at least five critical proactive alerts, and generating an accurate logical map of the Shaw AFB NIPRNet core infrastructure using the Network Topology Mapper. The contractor must provide five consecutive business days of hands-on, on-site training for up to ten government technicians covering platform administration, advanced node management, dashboard customization, monitoring and troubleshooting, topology mapping, and mission-critical application monitoring.
The project period of performance is 90 days from contract award, with performance taking place at Shaw AFB, South Carolina, during normal duty hours (0730-1630, Monday-Friday). All contractor work must comply with federal, state, and local safety and security laws, including DoD cybersecurity directives. The contractor must provide a Project Manager and on-site Site Point of Contact, both fluent in English, with the lead installer/trainer holding current SolarWinds Certified Professional (SCP) certification or equivalent and the contractor company demonstrating a minimum of three years' experience deploying SolarWinds solutions within DoD environments. Additional deliverables include a one-year workmanship warranty, manufacturer manuals and documentation, an "As-Built" configuration document, and a Test and Acceptance Plan with specific verification procedures for functional modules, monitoring of at least 20 critical network devices, alert triggering, topology mapping accuracy, and technician proficiency demonstration. Final project acceptance is granted by the government Project Manager upon successful completion of all Test and Acceptance Plan items, delivery of all software licenses, and receipt of required documentation.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment 2 - Salient Characteristics.pdf | ||
| Solicitation - FA480326Q0069.pdf | ||
| Brand Name Justification_Redacted.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
STATEMENT OF WORK (SOW)
for SolarWinds Network Monitoring and Management Solution for NIPRNet at Shaw Air Force Base, South Carolina
23 Mar 2026
Prepared By 20th Communications Squadron (20th CS) Shaw AFB, SC
1.0 SCOPE
This Statement of Work (SOW) defines the requirement for the Contractor to Procure, Furnish, Install, Configure, and provide Training (PFIC&T) for a SolarWinds network monitoring solution on the NIPRNet at Shaw Air Force Base (AFB), South Carolina. The Contractor will provide all specified software licenses, support, maintenance, training, supervision, management, and other incidentals necessary to meet the requirements as stated in this SOW. The Contractor will comply with all applicable Department of Defense (DoD) and Air Force (AF) cybersecurity directives, regulations, and base installation standards.
All software licenses, maintenance, and support provided will be new and not refurbished or previously activated.
2.0 REQUIREMENTS
2.1 GENERAL REQUIREMENTS
2.1.1 Safety Requirements. The contractor will remain in compliance with all Federal, State, county, and base security and safety laws, regulations, policies, and requirements.
2.1.2 Site Coordination. The Contractor will meet with the government Project Manager (PM) and base safety officer, if required, immediately upon arrival on site for a review of specific safety and security requirements prior to commencing work.
• 2.1.2.1 Accident/Incident Reporting and Investigation. The Contractor will record and report all available facts relating to each instance of injury to either Contractor or Government personnel.
Notification will be provided to the 20th CS Project Manager and the Base Safety Office. The Contractor will secure the scene of any accident until released by the accident investigative authority through the Base POC. If the Government elects to conduct an investigation of the incident, the Contractor will cooperate fully.
2.1.3 Security Requirements. The Contractor will process and provide a Site Visit Request Letter to the 20th CS POC within 5 calendar days after contract award. This letter will identify the names, driver’s license numbers, state of issue, and birth dates of all personnel who will be performing work under this
SOW.
• 2.1.3.1 Security Clearances. Stated work and associated products will be performed at the UNCLASSIFIED level on NIPRNet. However, some work may take place in controlled or secure areas where Contractor employees must be escorted. The Contractor must coordinate access to secure areas at least five (5) calendar days in advance. The Government is responsible for providing escorts.
• 2.1.3.2 Operational Security (OPSEC). Network infrastructure details, configurations, and vulnerabilities are considered sensitive information and must be protected. The Contractor will take appropriate measures to protect detailed information pertaining to this effort, to include appropriate marking of documents as “Controlled Unclassified Information (CUI),” and ensuring limited distribution of documents to only those individuals with a valid need-to-know. The contractor will follow the OPSEC guidance of AFI 10-701 to ensure the protection of CUI.
2.1.4 Environmental Compliance. The Contractor will comply with the most stringent environmental federal, state, and local laws and regulations. The work outlined in this SOW is software-based and is not expected to generate environmental waste.
2.1.5 System Access and Change Control. The Contractor shall be responsible for coordinating all system access and change requests required to complete the installation. All system modifications must be coordinated with the 20th CS PM and approved through the local change management process prior to implementation.
2.1.6 Integrated Process Team (IPT). The Contractor will chair a weekly (or as-needed) IPT meeting that includes Contractor representatives, the Government Contracting Officer (CO), the Government Project Manager, and other base personnel as required. The Contractor will provide an agenda NLT 1 working day prior to the scheduled meetings. The purpose of the IPT meeting is to discuss project progress, problems being encountered, and other information necessary to ensure timely completion of contract requirements. The Contractor will record and distribute meeting minutes NLT 1 working day after each meeting.
2.1.7 Quality Assurance. The Contractor will provide Quality Assurance for the entire life of the project. A weekly status report (soft copy) will be submitted to the government PM by Close of Business (COB) each Friday, indicating progress, status, and listing any deficiencies and corrective actions.
2.1.8 Contractor Personnel.
• 2.1.8.1 Project Management. The Contractor will provide a Project Manager (PM) and alternate(s) responsible for contract performance. The PM will be the primary point of contact for all contractual matters.
• 2.1.8.2 Site Point of Contact (POC). The Contractor will designate an on-site team leader as the Site POC. The Site POC will be on site during duty hours for the duration of the installation and training and will be the interface for all work site communications with the Government.
• 2.1.8.3 Personnel Requirements. The Project Manager, Site POC, and respective alternate(s) will be able to read, write, speak, and understand English.
• 2.1.8.4 Minimum Contractor Qualifications. All work will be performed by an experienced and certified SolarWinds technical professional. The lead installer/trainer must possess a current SolarWinds Certified Professional (SCP) certification or equivalent, and the Contractor company must have a minimum of 3 years of experience in deploying SolarWinds solutions within DoD environments.
2.1.9 Warranty. The Contractor will provide a one-year warranty on workmanship for the installation and configuration services provided. This is separate from the software maintenance/support provided by the manufacturer. The warranty period will start from the date of final system acceptance by the government.
2.1.10 Manuals and Documentation. The Contractor will provide the latest version of operation, installation, and maintenance manuals and user guides for each software product as provided by the original manufacturer.
2.2 SPECIFIC REQUIREMENTS
The Contractor shall Procure, Furnish, Install, Configure, and provide Training (PFIC&T) for the SolarWinds solution on government-provided servers.
2.2.1 Software Procurement. The Contractor shall procure and deliver the following new, perpetual software licenses and associated one (1) year of maintenance/support.
Product Name License Tier/Model Quantity
SolarWinds Observability Self-Hosted Advanced A500 1
SolarWinds Network Topology Mapper Standard 1
• All license keys and download links shall be delivered electronically to the 20th CS PM.
• The one-year maintenance and support term shall begin upon final system acceptance.
2.2.2 Installation and Configuration. The Contractor will install and configure the SolarWinds software on government-furnished servers operating on NIPRNet.
• 2.2.2.1 Platform Installation. Install the SolarWinds platform in coordination with 20th CS personnel, ensuring compliance with all DoD Security Technical Implementation Guides (STIGs) applicable to the underlying operating system and the SolarWinds application.
• 2.2.2.2 Network Discovery. Configure and execute network discovery scans to identify and import critical network devices and mission-critical applications into the monitoring platform, as identified by the 20th CS PM.
• 2.2.2.3 Dashboard and Alert Configuration. In coordination with government technicians, create at least two (2) custom monitoring dashboards focused on network health and mission-critical application performance. Configure a minimum of five (5) critical, proactive alerts to notify technicians of potential issues (e.g., high latency, packet loss, device down).
• 2.2.2.4 Topology Mapping. Configure the Network Topology Mapper to generate and display an accurate, logical map of the Shaw AFB NIPRNet core infrastructure.
2.2.3 Training. The Contractor shall provide five (5) consecutive business days of on-site, comprehensive training for up to ten (10) government technicians. The training must be hands-on and utilize the newly installed Shaw AFB SolarWinds instance. The curriculum shall cover, at a minimum:
• SolarWinds Platform Administration and Maintenance
• Advanced Node Management and Network Discovery
• Customizing Dashboards, Reports, and Alerts
• Proactive Monitoring and Troubleshooting with PerfStack™
• Using the Network Topology Mapper for Visualization and Documentation
• Monitoring mission-critical applications and services
2.2.4 As-Built Documentation. The Contractor shall provide a final "As-Built" document detailing the complete configuration of the installed system. This will include, but not be limited to, server details, administrator account information (to be changed by government personnel post-handover), custom alert configurations, dashboard layouts, and network discovery settings.
2.2.5 Test and Acceptance Plan. The Contractor will provide a Test and Acceptance Plan detailing the procedures to validate that the system is fully operational and meets all requirements of this SOW. This plan will be the basis for final system acceptance. The tests shall include, at a minimum:
• 2.2.5.1 Functional Verification. Demonstrate that all licensed modules are installed and functioning correctly.
• 2.2.5.2 Monitoring Verification. Demonstrate successful polling of at least 20 critical network devices and the accurate display of their status on a dashboard.
• 2.2.5.3 Alerting Verification. Successfully trigger a test alert for a monitored device and demonstrate that the notification is received by a designated test group.
• 2.2.5.4 Mapping Verification. Demonstrate that the Network Topology Mapper accurately displays a segment of the network as defined by the 20th CS PM.
• 2.2.5.5 Technician Proficiency Verification. At the conclusion of training, at least two (2) government technicians must successfully demonstrate the ability to add a new network device to monitoring and create a custom alert for that device.
2.2.6 Final Acceptance. Final project acceptance will be granted by the government PM upon successful completion of all items in the Test and Acceptance Plan, delivery of all software licenses, and receipt of all required documentation.
3.0 GENERAL INFORMATION
3.1 Period of Performance. The period of performance for the project will be 90 days from the contract award date.
3.2 Place of Performance. The place of performance is Shaw AFB, South Carolina.
3.3 Hours of Operation. The Contractor will routinely work during normal duty hours (0730-1630, Mon- Fri). Work outside these hours must be approved in advance by the Contracting Officer.
3.4 Holidays. The Contractor will not perform work on federal holidays unless expressly authorized by the CO.
3.5 Government Furnished Equipment/Information. The Government will provide the necessary server infrastructure (virtual or physical) meeting the software manufacturer's minimum specifications, as well as network connectivity and administrative credentials required for installation.
End of Statement of Work
File details come from the government source that posted it. Updated .