2. Robins CP PWS - (15 Jun 25).pdf
PDF 134 KB Posted
- Attached to
- UNIFY CONSOLE ANNUAL MAINTENANCE - 78ABW/CP
- Solicitation number
- F3Q0AC5136AW01
About this file
This Performance Work Statement (PWS) details the requirements for the 78 Air Base Wing Command Post Command and Control (C2) System upgrade at Robins Air Force Base. The document specifies the replacement of the current Unify Telecommunications System with a new OpenScape Voice-based system, adding 12 controller positions for the 78 ABW Command Post and 2 controller positions for BOPS (Base Operations).
The PWS outlines comprehensive technical requirements for the new C2 system, including multi-line phone capabilities, radio interoperability, recording functionalities, secure user connectivity, touchscreen interfaces, and advanced communication features like conference calling and caller ID. Key technical specifications include supporting CentOS and Windows Server OS, providing virtual server space, ensuring system lifecycle management, offering 24/7 customer support with tiered response times for technical issues, and maintaining comprehensive warranty and maintenance provisions. The system must be installed with rigorous safety, security, and quality management protocols, with the incumbent contractor UNIFY/MCS monitoring and supporting maintenance until contract expiration.
View the file
Other files
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
PERFORMANCE WORK STATEMENT
FOR
78 AIR BASE WING COMMAND POST
COMMAND AND CONTROL (C2) SYSTEM
15 Jun 2025
Section 1. OVERVIEW.
1.1 Overview. The 78 Air Base Wing (ABW) Command post, Robins Air Force base currently uses the
Unify Telecommunications System (formerly Siemens) console for telephone and radio communications. In the current configuration, the controller positions are located at the Primary
Command Post (Building 906), the new Alternate Command Post (Building 210), and BOPS (Building
2336) connect to the HiPath 4000 host server located in the switch room of the old Alternate Command
Post in building 2078. In 2019 AFRC headquarters awarded MCS of Tampa a contract to upgrade the
HiPath solution to OpenScape Voice based system. This SOW adds (12) controller positions supporting the 78 ABW/CP and (2) controller positions supporting BOPS. UNIFY/MCS will continue to monitor and support all maintenance for these C2 systems until contract expiration.
Section 2. DESCRIPTION OF SERVICES.
2.1 Required Features/Functions
• Multi-line phones
• Secondary Crash Net (SCN). The telephone must be equipped with a visual feature that activates as each two-way party on the SCN picks up the handset.
• Speakers
• Speed Dialing
• C2 system will provide secure, user connectivity to the console that is not dependent on a user's Common Access Card (CAC).
• Radio-to-Telephone Conferencing
• Telephone Group Conferencing
• Radio interoperability
• Hotlines
• Telephone directory able to store minimum of 1,000 numbers
• Capability to monitor phone/radio communication of all workstations
• Ability to program automatic dial buttons
• Push-to-Talk handsets with shielded, twisted pair cabling (2 per position)
• Connectivity to existing radios (Land Mobile Radios, HF, VHF and UHF)
• Capability to store phone numbers and create address groups
• Caller ID and call back capability for drop calls
• Redial last number, call transfer/forwarding and call history
• Touchscreen functionality
• Ability to record and save recordings at least 90 days
• Ability to extract individual recordings
• Ability to place Conference Calls with “drag and drop”, break-in, add transfer or delete caller functions
• Visual message waiting indicators (phones)
• Multiple programmable phone ring alerts
• Ability to patch phones
• No single point of failure
1619734765C Cross-Out
• Black only architecture
2.2 Moving/Adding/Removing Installed Systems.
2.2.1 Moving. The Government will have the capability to move systems without nullification of the warranty unless there is gross negligence by the Government.
2.2.2 Additional installations. Any additional requests for system installations will be contracted through MCS.
2.2.3 Removal of Installed Systems. Contractor will remove all debris, surplus materials and equipment related to the project as required and as frequently as needed in the best interest of safety, and leave the site in a neat and tidy condition at the completion of the project.
2.3 Shipment of Equipment. Contractor must coordinate all installation and shipment of equipment with the 78 ABW/CP POC.
Section 3. TECHNOLOGY.
3.1. Virtual Technology The Contractor shall employ use of virtual technology where applicable.
Two AFRC host locations have been identified to provide virtual server space for this requirement:
Dobbins ARB, Marietta GA and HQ AFRC, Warner Robins GA. Virtual servers will be
Government-provided.
3.1.1. These servers will be virtualized in AFRC’s VMware environment.
3.1.2. Servers will support CentOS and Windows Server OS 2012R2 and higher
3.2. Lifecycle Management / Warranty.
3.2.1. Software. Contractor shall be responsible for keeping all application software functional through end of contract Period of Performance (PoP). This shall include all updates and required security patches. 95% of scheduled software updates and/or maintenance executed according to schedule, remaining 5% completed within 2 days of scheduled date.
3.2.2. Hardware. Contractor shall be responsible for all C2 system hardware maintenance/repair and tech refreshes to ensure that the hardware will be sustainable throughout the life of the contract to include all option years. No equipment will be removed without prior coordination with contract COR.
3.2.3. New Functionality. If the Government determines that a new functionality is required, it will be billed as a reimbursable expense.
3.2.4. Obsolescence. The Contractor shall be responsible for entire C2 system working at the same or higher level until the end of this contract to include all option years.
3.2.5. Warranty. The Contractor shall provide warranty documentation to the 78
ABW/CP prior to site acceptance and shall begin upon site acceptance and initiated with the signing of the site acceptance form. The site acceptance is achieved with the successful completion of the operational system checklist which has been added as Attachment 1. The
Contractor’s warranty shall cover services for workmanship deficiencies and equipment provided as described and in accordance with the contract. The Contractor shall provide a full/unlimited industry standard commercial warranty for all Contractor provided hardware, software, materials, and workmanship. The warranty shall include emergency technical assistance as required including 24/7 VPN remote access and on‐site responses as appropriate for system failures. Warranty shall cover total system operability to minimize risk of mission failure. The Contractor shall provide written procedures and required information for warranty services prior to completion of the site acceptance form. This information shall include written confirmation of the warranty period, phone numbers and contact information. It shall detail procedures for technical support, troubleshooting assistance, and replacement of faulty equipment.
3.3. Inventory. The Contractor shall provide a complete list of all installed equipment to the 78
ABW/CP POC to include manufacturer, part numbers and serial numbers after completion of all equipment installation.
3.4. Testing. The Contractor shall provide on-site testing to ensure C2 system works properly after installation. The Contractor shall also conduct remote monitoring/testing of the C2 systems after modifications are performed to include software updates and equipment installations/repairs.
NOTE: The initial testing of the system will be in accordance with Attachment 1.
3.5. Training. The Contractor shall conduct in-person user training pertaining to system functionality after installation of the new system at each facility. The Contractor shall also provide end-user training materials either electronically or hard copy for the system operator(s) to properly use and program the system features.
3.6. Software License Management. If developing and/or sustaining a system that requires and/or contains COTS, the Contractor shall provide maintenance and support of that software license to manage its relationship to the overall system life-cycle, which would include applications, license agreements and software upgrades.
3.7. Unscheduled Maintenance. The Contractor shall provide a central point of contact for users with technical, systems/application and program problems, connectivity issues and routine queries.
At a minimum, the central point of contact shall effectively assist customers with telephone support, and logging trouble calls for ticket tracking system. The Contractor shall provide 24/7 customer support for unscheduled outages or system degradation. Primary fix action method is remote access restoration, however, if remote restoration is unsuccessful Contractors will respond on-site within the following timelines:
3.7.1. Routine Support (Tier 1). The Contractor shall respond on-site within 24 hours if unable to restore remotely and reestablish service as soon as possible. Routine outages/technical issues or any other outage(s) not included in the categories below.
3.7.2. Priority Support (Tier 2). The Contractor shall respond on-site within 8 hours if unable to restore remotely, provide fix action in writing within four (4) hours of arrival and reestablish service as soon as possible.
Priority outages include:
(1) Loss of call handling capabilities on one or more of the communication consoles
(2) Loss of radio (UHF/VHF) capabilities on one or more of the communication consoles
(3) Loss of recording capabilities
(4) Loss of any capability of the touch screen monitors or push-to-talk handsets
(5) Any software issue that causes a partial loss of mission capability
3.7.3. Emergency Support (Tier 3). The Contractor shall respond on-site within 2 hours if unable to restore remotely, provide a fix action in writing within two (2) hours of arrival on site and reestablish service within 12 hours of initial trouble ticket.
(1) Total loss of call handling capabilities of all the communication consoles in base primary and alternate CP locations
(2) Loss of any portion of the administrative PC that operates the core system
(3) Any software issue that causes a total loss of mission capability
Section 4. SECURITY
4.1. Physical Security Program.
4.1.1. Installation Perimeter Access Control. The requirements for installation perimeter access are detailed in Air Force Federal Acquisition Regulation Supplement (AFFARS) clause
5352.242-9000 entitled, Contractor Access to Air Force Installations, in Section I, Contract
Clauses, of the basic contract. Contractors merely requiring unescorted access to the installation to perform services, that don’t require access to classified information or network access, will be vetted IAW AFM 31-113, para 4.3 and issued a DBIDS Identification Card.
The Contractor is only allowed to visit the installations specified in the contract.
4.2. Resource Protection and Integrated Defense. The Contractor shall safeguard all government property in accordance with AFI 31-101, Integrated Defense, and any forms provided for Contractor use. The Contractor shall immediately report all thefts, vandalism, or destruction of property and equipment
(Government or Contractor owned) to the Contracting Officer Representative (COR) of this contract.
4.3. USAF Restricted Area and Controlled Area Access. The requirements for USAF
Restricted Area and Controlled Area access are detailed in AFI 31-101, Integrated Defense, and governed at each installation by the Integrated Defense Plan, if required.
4.4. Privacy Act of 1974. The Contractor personnel shall have access to Privacy Act information that requires adherence with the Privacy Act of 1974, Title 5 of the U.S. Code, Section 552a, AFI 33-332, Air Force Privacy Act Program, and other applicable agency rules and regulations. The Contractor personnel shall follow agency procedures to identify and safeguard reports and data accordingly. The
Contractor shall ensure that Contractor personnel assigned to this requirement are briefed annually on properly identifying and handling Privacy Act data and reports. AFI33-332 is the guiding document and can be downloaded from www.e-publishing.af.mil.
4.5 Network Security. Network access is a privilege extended to Contractor personnel. Network access will be granted by the Government after all criteria have been met and may be suspended for cause as defined in AFI 33-115V2, Section 5.6. Network access will be approved by the Government in accordance with AFI 31-501, AFI 16-1406, AFI 33-115V2 and V3, AFI 33-200, DoDI 8510.01, and
DoDM 5220.22-M and its supplement. Pursuant to AFI 33-115V2, every individual who has access to the Air Force (AF) network (af.mil) or af.smil domain, specialized systems, and mission systems is a network user. Before becoming an Air Force network user, the Contractor personnel shall have a favorable background investigation for the designated IT level and system, be trained, and licensed.
This process of training and licensing ensures every AF network user is trained and aware of the basic principles of network security and their role in Information Assurance (IA). The Government will issue a Common Access Card in accordance with Air Force FAR Supplement clause 5352.242-9001 entitled, Common Access Card for Contractor Personnel, to Contractor personnel that meet the criteria
(favorable trustworthiness determination, training and licensing).
Section 5. SAFETY
Health & Safety Program. The contractor shall comply with Public Law 91-596, Occupational
Safety and Health Act (OSHA) and Environmental, Safety, and Occupational Health (ESOH) (DoDD
4715.1E), and these requirements shall be incorporated into the contractor’s safety and health program. The Air Force participates in the OSHA Voluntary Protection Program (VPP). The contractor shall be familiar with VPP tenets. Information on VPP is available at http://www.osha.gov/dcsp/vpp/index.html. The contractor shall be responsible for the safety and health of all subcontractor employees. (CDRL A001, Health & Safety Program)
5.1. Incident or Mishap Procedures. The contractor and its subcontractors (if applicable) shall promptly report pertinent facts regarding mishaps involving Government property damage or injury to Air Force personnel and to cooperate IAW AFI 91-204, Safety Investigations and Reports, in any
Air Force safety investigation. The contractor shall notify (via telephone) the cognizant contracting officer, the contracting officer’s representative, and/or the cognizant program manager within four
(4) hours of all mishaps or incidents to DoD property entrusted by this contract operation. The Government person notified by the contractor will in-turn notify the Safety office. Contractor notifications made after http://www.e-publishing.af.mil/ http://www.osha.gov/dcsp/vpp/index.html duty hours shall be reported to the 78 ABW Command Post (Note: the Robins AFB Command Post commercial phone number is (478) 327-2612). If requested by the cognizant contracting officer, the contracting officer’s representative, and/or the cognizant program manager, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records until released by the investigating safety office. If the Government investigates the mishap, the contractor and the subcontractors shall cooperate fully and assist the Government personnel until the investigation is completed. (CDRL A002, Accident/Incident Report)
5.2.1 Damage, Loss, theft. Contractor agrees to protect any Government-owned equipment from damage, loss, theft and infection with computer viruses and must follow
Report of Survey (ROS) procedures for damaged, lost, or stolen Government equipment.
5.2. Fire Emergencies. The Contractor personnel shall dial 911 to report fire related emergencies.
5.3. Department of Labor (DoL) Inspection of Contractor Operations. The
Contractor is subject to DoL inspections and enforcement by OSHA health and safety officials while performing work on a Government installation. The OSHA health and safety officials may access workplaces on Government installations at any time, scheduled or unscheduled, during regular business hours. The OSHA health and safety officials must meet security requirements to enter restricted or classified areas.
5.4. Fire Protection and Prevention Program - Robins AFB GA. All Contractor personnel performing work on properties under jurisdiction of 78 Air Base Wing shall be responsible for fire safety and compliance with all applicable OSHA, State, Air Force, AFMC, and base regulations and directives. Contractor shall ensure that all Contractor personnel and sub-Contractors under their control are briefed on fire prevention practices in accordance with host base instructions.
5.5. Quality Management System (QMS). The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a Quality Control Plan
(QCP) 30 days after contract award, addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur.
The plan shall include the schedule of quality assurance/control inspections planned by the
Contractor.
File details come from the government source that posted it. Updated .