HC108425R0002.pdf

SEE ADDENDUM

(No Collect Calls)

HC108425R0002 27-Feb-2025

b. TELEPHONE NUMBER

667-890-7534

8. OFFER DUE DATE/LOCAL TIME

11:00 AM 26 Mar 2025

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

HC10849. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

JENNIFER L. KINSER

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

0 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

DISA/DITCO-SCOTT-PS84

2300 EAST DRIVE

SCOTT AFB IL 62225

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

1,250

NAICS:

334210

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF98

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

Voice Switching Systems & Subsystems (VSS3) Replacement

Section SF 1449 - CONTINUATION SHEET

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

FOR

Voice Switching Systems & Subsystems (VSS3) Replacement

Award/Mod Effective Version Date Award

Contract Number: (completed by the KO at time of contract or TO award) Task Order Number: (completed by the KO at time of TO award or N/A) Contractor Name (completed by the KO at time of contract or TO award) Follow-on to Previous Contract and Task Order Number:

Not applicable.

1. Contracting Officer’s Representative (COR).

a. Primary COR. To be completed at time of award.

2. Contract or Task Order Title. Voice Switching Systems & Subsystems (VSS3) Replacement

3. Background: The Air National Guard (ANG) has 67 sites that utilize the Avaya 8800 CM7 that are on the verge of critical failure. The Avaya 8800 CM7 System configuration is manufacturer End of Support (EOS), End of Life (EOL), discontinued or no longer listed on the Department of Defense Approved Products List (DODIN APL).

https://aplits.disa.mil/processAPList.action.

The ANG has 105 sites that require replacement of integrated peripheral systems such as Motorola Vesta (E911) or SPOK E911 systems, Unique Configuration Accounting Information Retrieval System (CAIRS) call accounting systems and Secure Logix Call Recording Systems that are EOL or EOS and some are in critical failure.

4. Objectives: The objective is to provide VSS3 for replacement of the existing Avaya 8800 CM7 VSS, Call Recording, Call Accounting for the ANG at 67 sites listed in Sec 8.1. This requires removing old equipment and installing new materials, software, and equipment. This document also requests Call Recording and Call Accounting capabilities at 38 sites listed in Sec 8.2 for a total of 105 sites that require Telephony Management Systems (TMS), call recording, call accounting and ensuring compliance with Kari’s law and the Ray Baum’s Act Section 506.

5. Scope: The Contractor shall replace the existing Avaya 8800 CM7 at the 67 sites listed in section 8.1. The Contractor shall ensure the solution provides voice recording capabilities, telephony management systems (TMS) which is on Defense Information Systems Agency (DISA) DODIN APL, at the 105 sites in sections 8.1 and 8.2. The proposed on-premises solution shall adhere to the latest DODIN APL approved Voice System configuration and be compliant with current E911 laws (Kari’s Law, Ray Baum’s Act Section 506) and Suicide Prevention Hotline requirements. The Contractor shall provide project management, all associated project management documentation and supply all new equipment, licenses (estimate 1000 per site), tools, materials, training (see para 6.3.15) and quality control necessary to replace the currently failing and non-compliant solutions identified above.

The new proposed VSS replacement will not degrade the capability the current VSS is providing. The proposed system and services shall be compatible with current WAN circuit configurations onsite. All legacy Government Furnished Equipment (GFE) and/or services tied to the existing voice switch shall be replaced without change or limiting the capability previously provided. VSS shall be capable of Session Initiation Protocol (SIP) Trunking to ensure readiness for future connectivity i.e., ECAPS or Services provided by DISA. The vendor may not reuse any existing materials and equipment for this effort at any of the locations. All new hardware and software must be provided. This project will only focus on unclassified voice requirements and the contractor will not support classified voice material requirements. The vendor will ensure all existing classified & unclassified services using the current phone switch is restored prior to departure. Lastly, the contractor shall not perform any task outside the scope of the PWS without approval from the contracting officer.

6. Performance Requirements:

6.1 Network Services and Solutions: The Contractor shall provide services and solutions that enable Network Operations and Network Infrastructure capabilities. Networks as defined in this section are for data, voice and video.

The Contractor shall:

Conduct a physical on-site survey at each site. The contractor must visit each location listed in the PWS in sections 8.1- 8.2.

Provide an integration team to support the installation of the capability.

Provide a test plan with objectives and metrics.

Provide a detailed test report upon completion of integration.

Provided integration services will be compatible with Unified Capabilities (UC) architecture.

Before the hardware and software can be connected to the Air Force Network (AFNET), all system hardware and software shall receive Information Assurance (IA) accreditation compliance instructions and guidance from ANG A2/6 IA Cybersecurity Representatives.

Shall develop and provide to Government any necessary system documentation required for Cybersecurity accreditation from ANG A2/6IA Cybersecurity representatives.

Coordinate with the designated ANG A2/6 IA Cybersecurity Representatives prior to implementation to determine all Cybersecurity requirements that are to be applied to ensure Cybersecurity compliance.

Perform all recommended Security Technical Implementation Guide (STIG) compliant Cybersecurity settings, programming and configurations of components being provided to ensure compliance with all Cybersecurity requirements.

6.2 Technical Requirements:

6.2.1 VSS Core

o Any system(s) being deactivated shall remain operational until all circuits have been relocated and shall be powered down by the Contractor. (This will allow the Contractor the opportunity to determine the operational status of the switch prior to relocation).

o The Contractor and COR shall coordinate with site personnel to ensure minimal disruption to users.

o Any new hardware, software or firmware product or function developed for or added to the VSS system shall interoperate with both IPv6 and IPv4 systems and products.

o VSS end devices shall be manufactured in accordance with Federal Communication Commission (FCC) hearing aid compatibility technical standards contained in Section 68.316 of the Telecommunication Act of 1996 and Section 508 of the Rehabilitation Act of 1973, as amended.

o The proposed system shall regularly query the LAN switches in the network, discover and keep track of all the phones and their locations in the local database.

o VSS calling solution shall provide the correct Emergency Location Identification Number (ELIN) to the call server at the time of a 9-1-1 call.

o VSS shall provide real time 9-1-1 call notifications to Security Forces, Fire Department, first responders and others as required by base.

o The solution shall support compliance with Kari’s Law and Ray Baum’s Act Sec 506.

o In the event of a server failure, the VSS solution shall have redundancy to ensure correct routing of 9-1-1 calls.

o There will be no remote workers needing to make 9-1-1 calls from outside the bases.

o Contractor shall ensure VSS 9-1-1 transmission information to local Public Safety Answering

Point (PSAP) for the sites referred to in PWS para 8 are operational after the upgrade and compliant with Kari’s Law and Ray Baum’s Act Sec 506. The VSS shall provide an emergency alert notification when 9-1-1 is dialed. If the phone is moved to another location, the VSS shall track the existing or new phone and update its location automatically. Contractors shall test this functionality prior to the upgrade and after the upgrade to demonstrate its operation to Government personnel.

6.2.2 Call Control will have the following characteristics:

o IP based telephony that is compliant with the DoD Multilevel Precedence & Preemption

Capability (MLPP) per the UCR 2013 Change 2.

o Analog telephony (via Call Control) that is compliant with DoD MLPP per the UCR 2013

Change 2.

o VSS based Voicemail Service Capability.

o System shall communicate with gateways via Media Gateway Control Protocol (MGCP) and SIP.

o Shall support Remote Survivability to enable standard availability IP telephony at remote locations.

o Shall support intelligent and automatic failover configuration without manual ANG administrative or telecom intervention.

o Shall support Calling rule restrictions continued in failover mode.

o Automatic synchronization with call control for additions, deletions, and modifications of users and phones.

o Improved user experience in failover mode by maintaining phone displays through an enhanced feature set.

6.2.3 Gateway

o Voice gateways shall provide for multi-protocol trunking for native support and interoperability:

(SIP, MGCP, H.323, TDM).

o Voice gateways shall provide interfaces to integrate into existing systems via TDM, analog, or SIP trunks.

6.2.4 Session Border Controller (SBC)

o SBC shall support SIP Trunking.

o SBC shall support integration with VSS system.

o SBC shall be JITC certified and be on the DODIN APL.

o SBC shall support connection to commercial and DSN SIP circuits.

o SBC shall support flexible security rules that prohibit unauthorized connections.

o SBC shall support behavior evaluation policies that can detect malicious call patterns, including

Telephony Denial-of-Service (TDoS) attacks, and invoke an appropriate response.

o SBC shall support interworking of encrypted and non-encrypted communication streams.

6.2.5 Phones

o Shall be capable of taking multiple (at least 3) calls, and capable of using soft keys which allow multiple call functionality features to reside on a button when the phone status changes.

o The VSS system endpoints, connections, and interfaces shall be SIP compliant with IETF RFC 3261.

o The VSS system telephones shall be configurable for desk top placement and/or wall mounting.

o Chosen IP Phones shall have the ability to operate in SIP.

o Chosen DODIN APL Approved IP Phones shall support Power over Ethernet (PoE).

o Instrument features shall employ only one adjustable ringer, bell, buzzer, chime, or electronic tone to announce calls. The signaling device shall detect an incoming call to the multi-button instrument and provide an audible signal only on designated lines.

o Instrument features shall be equipped with lights to identify the called line and remain illuminated for the duration of the call.

o Instrument features shall have a built-in microphone, speaker, and intercom system capability.

o Instrument features shall be capable of integrating with auxiliary equipment, such as amplified handsets, external chimes, lights, or bells and other similar equipment.

o Shall support “Push to Talk” handsets where required.

o The contractor shall maximize flexibility with handset devices and coordinate with the NGB project manager on the amount of handset devices provided by the contractor to allow the government to determine the number of handsets per location regardless of the number of devices requested by the base or found during the site survey. It is the sole discretion of the government to determine the number of handset devices per unit in para 8.

o Softphone is out of scope for this contract and will not be provided by the contractor with this PWS. The government will implement softphone in parallel of this effort and contractor acknowledges awareness the government intends to implement softphone before, during or after this effort which will impact the number of handsets provided by the contractor. The government at its sole discretion will determine all softphone requirements and implement at any time. The contractor will only purchase the number of handsets per the government.

6.2.6 Technical Specifications Call Accounting

o The new Call Accounting solution selected must be a current, latest release and on the DOD-APL and must be an on-premises software-based system.

o The solution must provide call reports which includes information on incoming, outgoing, and internal calls to track call duration, start and end times, calling number, called number and call status.

o The proposed solution should have reports that can be pulled on demand and saved to a file, emailed or sent via Secure File Transfer Protocol (SFTP).

o The proposed solution must integrate with the proposed on-premises VSS solution.

o The solution must have Trunk analysis tools and utilization reporting to optimize telecom capacity and call routing for improved efficiency and cost savings.

o The solution must be able to export the call detail record files to an external SFTP server for long term retention.

o Contractor will ensure locations utilizing CAIRS TMS will be replaced with the proposed new software-based Call Accounting solution. The new solution should provide equal or greater capabilities in the same capacity as it was prior to the new solution installation. The Contractor will configure and ensure integration and interoperability of the new call accounting system into the new VSS, and all technical uses being deployed at the Unit where the systems are present. Call reports must be pulled on demand or generated automatically and sent to a printer, saved to a file or emailed.

6.2.7 Technical Specifications Call Recording

o The VoIP monitoring/recording solution will place a DODIN APL IP compliant appliance at all 105

ANG sites listed in sections 8.1 and 8.2.

o The VoIP recording capability is required to perform recording VoIP sessions. The recorded sessions must be saved in an audio format (such as .MP3, .wav, etc.…) that includes metadata directly related to the call.

o Contractor shall provide a VoIP monitoring/recording capability that can:

Operate from hardware owned and operated by the Air National Guard on a USAF Network (e.g., be interoperable with current VSS systems).

Export/Import recorded calls in “*.wav” format with required metadata.

Capture all inbound/outbound VoIP calls for mission-directed sessions.

Provide unit operators the ability to monitor calls in near real time.

Provide the ability to select voice lines for call recording.

Support installation/deployment of the VoIP call recording solution.

o The VoIP recording solution shall reside on a JITC certified, encrypted SIP appliance.

o The VoIP recording solution shall be JITC certified.

o The VoIP recording solution shall run on TAA-compliant servers.

o The VoIP recording solution shall support no less than 150 concurrent calls.

o The VoIP recording solution shall be able to decrypt up to 150 concurrent call recording.

6.2.8 Voice Trunking

o All Contractor-furnished equipment shall be capable of supporting IP trunking capabilities at the Wings.

The Contractor shall provide all licenses individually to each site location to accommodate IP trunking between the Wings and GSUs.

6.2.9 Hardening & Compliance

o All new hardware and software shall be installed in accordance with (IAW) the OEMs specifications.

New installs may require Military Unique Deployment Guide (MUDG) configuration adjustments (when available) to the OEM provided Commercial off the Shelf (COTS) system for Cybersecurity and compliance with Military Unique feature sets. The Contractor is responsible for ensuring all new hardware is free from unmitigated vulnerabilities prior to cutover and system acceptance and configured to comply with current DISA STIGs. VSS servers/applications, SBCs and Gateways will be scanned by Contractor for vulnerabilities prior to connecting to the Network. Scan results will be provided to the local Cybersecurity personnel. Contractor will be responsible for ensuring vulnerabilities identified by the security scans are mitigated or documented within a Plan of Action and Milestone (POA&M) and accepted by the Government.

6.2.10 Technical Power and Grounding

o The Contractor will not be required to provide or install any electrical panels, circuit breakers, power/ground cables, electrical hardware or connectors to terminate power connectivity from the Government provided Technical Power Panel to the voice switching equipment at the Host or any remote equipment. All VSS equipment shall utilize power provided in the existing rack and grounded per manufactures best practice and grounding shall be in accordance with OEM specs ANSI Joint Standard

607-A (JSTD-607-A).

6.2.11 Configuration Management

o The Contractor shall provide the NGB/A2/6R COR, the NGB/A2/6W PM and the site POC, initial designs and as-built documentation including, but not limited to, drawings and diagrams of the solution identifying specific cards in a chassis/shelf. The as-built documentation shall also include bay face layout drawings, back boards, power drawings/specifications, floor plans, network documentation/drawings and engineering specifications generated in support of the installation of the system. Documentation shall also include equipment listing with serial/model numbers and manufacturer specifications. Documentation shall also include copies of build instructions and automation scripts to enable rebuild of system.

6.2.12 Site Restoral and Damage

o The Contractor shall perform daily area cleanup of all equipment upgrade/installation locations and at completion of each work site. The Contractor shall remove all excess debris (boxes, wrapping, cables, etc.) and return facilities to their previous condition once all upgrade/install actions are complete. All excess legacy hardware shall be returned to the local unit for disposal, excluding batteries. The Contractor shall repair and/or replace all facilities and/or equipment damaged by the Contractor or their subcontractors. The Contractor shall warranty said facilities and/or equipment for the standard warranty period of new equipment of like kind, but for no less than one year. All affected areas shall be restored to their original condition.

6.2.14 Testing and Acceptance

o Testing: Upon successful installation of equipment, Contractor shall test each system IAW Government approved Contractor provided test plan.

o Acceptance: Upon Government COR receipt of verification of successful testing, and ANG base

Communications Flight Commander signed Air Force Technical Order (AFTO) 747, the Government will accept the system as being operational.

6.2.15 Training:

o Within 30 days upon Government acceptance of the system, a maximum of two individuals per site will be provided training vouchers or formal training via virtual classroom to address System Administration, System Maintenance and System Troubleshooting. All responses shall include training for two individuals per ANG site listed in section 8.1 and two individuals at A2/6W. The Contractor is responsible for working with Government assigned personnel for the registration and management of all training.

o System Administrator Training shall cover how to access the VSS, administrative pages to perform adds, moves and changes of the IP phones, while configuring users and associating them with phones, securing the system and performing backups and restoration. Training shall provide a clear understanding of how to configure simple features, such as Do Not Disturb (DND), Music on Hold, “Meet me” conferencing, shared lines, and barge as well as access to system user web pages. Training will cover how to configure voice mail accounts for users, build a VSS Client, and manage licenses using the License Manager provided with the VSS solution. In addition, the training shall cover a basic understanding of route patterns that are used for dialing and Class of Service, which is used to control who can dial where, such as internal, local, or long distance.

o System Administrator Training shall cover how to access and make changes to the proposed Call Recording System o System Administrator Training shall cover how to access and make changes to the proposed (TMS) Call Accounting System o Contractor shall ensure all 105 sites listed in para 8 receive training on associated integrated peripheral systems installed in this effort.

6.2.16 Site Surveys

o Prior to purchasing and installing equipment, Contractor shall prepare and provide to each site a pre-site survey data call and conduct site visits to each of 105 sites to verify all requirements, provide a list of equipment and conduct design review with Government; confirm readiness of site and network (Identified during site survey and pre deployment assessments). The site survey effort should begin 45 days after award. Site Survey reports should be submitted for Government review 10 days after site survey completion. Contractor shall inform ANG staff of any possible deficiencies. Contractor shall at a minimum confirm the following:

Data network readiness, switch Power Over Ethernet (POE) capability, IP addressing.

Rack space and suitable rack types.

Horizontal and backbone cabling.

Demarcation extension cabling.

Number of trunks, SIP and or Primary Rate Interface (PRI) (Commercial & DSN).

Validate number of required VOIP Phones including analog that need to convert to VOIP.

Validate number of analog devices.

Identify analog gateway locations and connectivity.

Confirm number of Voice Mail Boxes.

Validate number of wall mount phones, conference phones and phone types.

Identify number of push-to-talk handsets.

Identify secure phone requirements.

Confirm existing sub systems, OEM, mode, and current connectivity to VSS.

Identify any unique requirements associated with the current VSS.

Identify the use of and verify the make, model, ensure compatibility and count of Telecommunications Security Group (TSG) telephone sets.

6.2.17 Design Documentation

o The Contractor shall, after completing the sites surveys, consult with ANG A2/6W PM, Engineering and COR staff and provide Proposed Designs &Configuration for Government approval, within 30 days after approved site survey report (SSR). The Government will evaluate and approve/disapprove within 21 days after submission. If disapproved, the Contractor shall resubmit corrected system configuration within 10 days of receipt from Government. At a minimum, system design documentation and the system security plan shall include the following:

o Solution Design:

Provides details on the conceptual, logical, and physical design of the voice solution and backup capability.

Facilities Requirements Rack space required for each hardware component & the total solution.

Power draw for each component & the total solution.

Cooling requirements for each component & the total solution.

Conceptual, logical, & physical Architecture.

Physical network design & configuration.

Physical server design & configuration.

Storage, networking, CPU, memory.

Hypervisor design & configuration.

System backup capability.

System Security.

System security settings.

DISA STIG Settings.

Role based access control.

o Numbering plan:

Dial plan.

PRI configuration and migration plan.

PSTN access.

DSN access.

MLPP access per Military Unique Deployment Guide.

Voice mailbox sizing and retention.

Proposed solution application requirements.

VMWare vSphere licensing considerations if necessary.

Full bill of materials for VSS and Sub Systems.

All VSS and Sub Systems configuration information.

Systems deployment and implementation plan.

System topology drawings and rack elevations.

o Contractor shall provide Device Templates that are JITC-approved versions. Execution shall at a minimum include the following:

Apply applicable 1 Year licensing.

IP addressing.

Administration accounts.

Unified Messaging & Communications integration.

Call Management Plan.

Default mailbox size quotas and message aging policy.

Any required system features identified by the customer.

Password and lockout policy.

System configuration.

Import user information.

Configure analog gateways.

Download and update IOS to latest approved JITC-certified version (if required).

System Security settings.

o Review and Validate Bill of Material and Tasks The Contractor shall consult with the ANG A2/6 Engineering on Ethernet switching & routing requirements.

Review QoS configuration if implemented and address as necessary.

Voice Virtual Local Area Network (VLAN).

IP addressing scheme.

The Contractor shall obtain license file(s) from OEM or OEM’s.

The Contractor shall provide Administration & Operation Guides for all proposed systems for each site.

The Contractor shall provide System Configurations for each site.

The Contractor shall provide As Built Design Drawings (MS Visio File Format).

6.2.18 Implementation

o Provide access distribution, and core node seatings/configuration commands required to enable all voice solution components to communicate on the network.

o Provide necessary input for Change Request (CRQ) submission to enable 299 NOSS and ANG site to make router configuration changes to extend Voice VLAN from Wing to GSU where applicable.

o Contractor shall perform all physical installation of the equipment following industry and the OEM’s best practices for the racking and cabling of the proposed VSS/UC infrastructure. This includes all servers, media gateways, analog gateways, and cabling required to install all components of the voice solution. Upon completion the install should look clean, organized, with managed and labeled cabling.

o Contractor shall implement complete system configurations of the proposed VSS/UC solution and associated appliances to achieve a fully functional and operational VSS environment. The configuration shall include but is not limited to all servers, Redundant Array of Independent Disks (RAID) preparation, Basic Input Output System (BIOS) preparation, VMware environment, vSphere client, all virtual machines via Open Virtualization Application/Appliance (OVA) template, activating all licensing, and physical network connectivity ready for testing.

o Contractor shall perform installation and configuration of all VSS/UC applications including call routing required for optimal performance of the VSS/UC environment. At a minimum this would include all application configurations, licensing, Network Time Protocol (NTP), Trivial File Transfer Protocol (TFTP), Dynamic Host Configuration Protocol (DHCP) for phones configured on ANG’s existing DHCP server. Region, devise pools, location, enterprise parameters, call routing, time schedules, partitions, calling search spaces, route/ translation patterns, call pickup groups, conferencing whenever and wherever, auto registration and active licensing that leveraged the

USAF UC ELA.

o Contractor shall perform installation, configuration, optimization and apply all STIG compliant configurations with the latest release of the system, which shall include but is not limited to the following:

6.2.19 Phone Installation

o Provision phones & users licenses.

o Contractor shall install one of each model phone while instructing / training / consulting two of the

ANG IT Staff on properly installing the remaining phones.

o Contractor personnel shall allow Government IT Staff to “shadow” the entire installation process to understand the process.

o Contractor shall provide a minimum of eight (8) hours on-site knowledge transfer with Contractor providing a walkthrough of the administration and daily operations of the installed VSS.

6.2.20 Devices

o Voice gateways: Voice gateways must be able to be integrated with the new phone system and include modules to support multiple PRI’s. In addition, the voice gateways must support IPv4, IPv6, static routes, Routing Information Protocol Versions 1 and 2 (RIP and RIPv2), Open Shortest Path First (OSPF), Border Gateway Protocol (BGP), IPv4-to-IPv6 Multicast, MPLS, Layer 2 and Layer 3 VPN, IP sec, Layer 2 Tunneling Protocol Version 3 (L2TPv3), Bidirectional Forwarding Detection (BFD), IEEE802.1ag, and IEEE802.3ah.

o IP Phones: IP phones must support multiple lines, allowing users to answer calls simultaneously.

The phones must also support programmable buttons that can be customized to perform various functions, such as speed dialing, call transfer, and conference calling. The IP phones must include security features like encryption to protect voice traffic and prevent unauthorized access. Vendor will provide different models of IP phones for consideration.

Device profiles will be setup, so the phones use a common set of services and features.

6.2.21 Priority

o Each site will be executed in priority to be determined by ANG. Each site shall be completed within 45 days of the equipment’s arrival at the site. AFTO 747 shall be provided by contractor for signature to each site upon completion of that site as part of closeout.

6.2.22 Virtualization

o Virtualization hardware and software must be compatible with Unified Capabilities applications as part of a Tested Reference Configuration (TRC).

6.2.23 Calling Solution

o The Calling Solution shall support enterprise unified communications and collaboration for voice calling, messaging, mobility, reliable, secure, scalable, manageable call control, and session management. In addition, voice services shall support all licensed end-users and analog users call functionality features to include 3-way calling, conferencing, multi phone number appearance, caller ID, call forwarding, program ability for local and long-Distance calls, calling on post and off post operational calling to Defense Switched Network (DSN), Public Switched Telephone Network (PSTN) and 911 services.

The Calling Solution shall support Unified Messaging and single storage for different types of messages. Voicemail Users Security Features shall be in place to protect voicemail messages and access, including user authentication and encryption. The system shall also be customizable to handle things such as configuring call handling rules, and voice prompts.

6.2.24 TMS System

o The proposed TMS System must be software based providing ease of reporting and be capable of transmitting reports to a centralized repository. The replacement to the VSS and Call Recording Systems must comply with the latest JITC certified version on the DODIN APL and configured in accordance with Military Unique Deployment Guide, the DoDIN Capabilities Requirement Framework Document v1.0 August 2018, and UCR 2013 change 2.

6.2.25 Licensing

o The Contractor shall provide a 1 Year License for all new equipment and software. The licensing proposed must be transferrable to applicable enterprise license agreements should one become available and shall have the ability to move to an IL5 compliant cloud environment at a future date. The Contractor will not reuse any old equipment or licensing. The premise solutions need to be a single provider, i.e. Cisco or Avaya. The government will be the sole owner of delivered hardware and software delivered under this contract.

6.2.26 Project Manager

o The Contractor shall manage and oversee all activities performed by its personnel (including subcontractors and teaming partners, as applicable) and escalate problems or concerns to the Contracting Officer and COR.

o The Contractor shall provide operational, procedural, and contract management support to assist ANG throughout the sustainment of the VSS3 environments.

o The Contractor shall provide a Program Management Plan within 30 days after contract award.

The plan will document the contractor’s management approach, operating procedures, staffing approach, and overall Work Breakdown Structure.

o 6.2.26.1 Reporting:

The Contractor shall provide a weekly status report via conference call with project stake holders following up with a status report in MS Word or PDF format via email. The project status meetings shall include at a minimum the following information.

Equipment shipping status Equipment backlog status Installation progress at each location & identification of any challenges and resolution to those challenges

7. Performance Standards:

# PWS Paragraph Task Performance

Standard

Acceptable Quality Levels

(AQL)

Surveillance Method / By

Whom 1 6.2 Configuration

Mgt / Cybersecurity

Provide required information during install of requirement.

Provided prior to completion of contract.

Periodic Inspection /

COR

2 6.2.1.5 Testing / Acceptance /

Training

Provide required information during install of requirement.

Provided prior to completion of contract.

100%/

COR

3 6.1 Contractor Travel All travel is approved by the COR prior to travel

Draft travel costs provided & approved before travel

100%/COR

4 6.2 Conduct Site Survey

Survey 100% of in-scope equipment & software

100% of all in-scope hardware & software surveyed with less than 5 discrepancies

100%/Base

POC

5 6.2 Provide a test plan

A detailed plan of objectives and metrics

The plan includes all critical objectives and metrics which proves the new equipment meets the

PWS

100%/

COR/PM

6 6.2 All system hardware and software have Information

Assurance (IA) accreditations

Vendor provides IA documentation to the government for all hardware and software

All equipment and software are IA accredited

100%/COR

7 6.3.21 All hardware and software installed meets the PWS technical requirements

Vendor provides hardware and software which meet

All equipment and software are required

100%/COR/PM

the technical requirements of the PWS to meet the

PWS

8 6.2.1 The vendor shall minimize disruptions to users

The vendor makes every effort to have minimize reports of disruptions

90% of the sites do not report disruptions to normal business to the COR

90%/COR

9 6.2.21 AFTO 747 is signed by all parties

100% of the sites on the

PWS sign the

AFTO 747

The vendor has a signed

AFTO 747

100% prior to closing work at a location

100%/COR

10 6.2.15 Training of two

(2) government reps per site

The vendor provides training for two (2) government reps per site

The vendor meets training requirements

100%

100%/COR/PM

11 5. Contractor shall not perform any task outside the scope of the PWS

The vendor does not perform any task not in scope of this

PWS

The vendor must meet this 100%

100%/COR

Deliverables:

PWS Reference / Deliverable Title

Frequency Number of Copies

Medium/Format Submit To

6.2.16 Site Survey Report for each

site for all systems

1 Electronic Submission – MS

Word or PDF Format

COR/PM

6.2.13 Weekly Status Report 1 Electronic

Submission – MS

Word or PDF Format

COR/PM

6.2.17 Proposed Designs &

Configuration for each site

1 Electronic Submission – MS

Power Point or MS Visio

COR/PM

6.2.11 System As-Builts for each

site and proposed system

1 Electronic Submission – MS

Power Point or MS Visio

COR/PM

6.2.17 Administration & Operation

Guides for all proposed systems

1 Electronic Submission

COR/PM

6.2.14 Testing & Acceptance Signed

AFTO 747 for each site

1 Electronic Submission -

PDF

COR/PM

6.2.26.1 Project Management

Documentation

1 Electronic Submission

COR/PM

8. Places of Performance: The work will be performed at the following Air Force Bases including geographically separated units attached to the Air Force Base located within the United States of America and its Territories in the recommended order, but ANG reserves the right to reprioritize during the project:

8.1 VSS/Call Accounting & Call Recording Replacement Bases:(Atch 1 tab 2) 102 Intelligence Wing (IW), Otis ANGB MA 103 Airlift Wing (AW), Bradley ANGB CT

103 AW - 103ACS CT

104 Fighter Wing (FW), Barnes ANGB MA 106 Rescue Wing (RW), Francis S. Gabreski ANGB NY 110 AW, Battle Creek ANGB MI 115 FW, Truax Field ANGB WI 117 Air Refueling Wing (ARW), Birmingham ANGB AL 119 Wing, Fargo ANGB ND 120 FW, Great Falls ANGB MT 121 ARW, Rickenbacker ANGB OH

121 ARW - 220EIS OH

123 AW, Louisville ANGB/ Standiford Field KY 124 FW, Gowen Field ANGB ID 127 Wing, Selfridge ANGB MI 128 ARW, General Mitchell ANGB WI 129 RW, Moffett Federal Airfield CA 131 Bomb Wing, Jefferson Barracks - Whiteman AFB MO

136 AW, NAS JRB Fort Worth TX 136 AW – 254 CBCS Hensley Fld TX 137 Special Operations Wing (SOW), Will Rogers ANGB OK 138 FW, Tulsa ANGB OK 139 AW, Rosecrans ANGB MO 142 FW, Portland ANGB (ROSC 6) OR

142 FW - 116 ACS OR

143 AW, Quonset Point ANGS RI

143 AW - 282 CBCS RI

145 AW, Charlotte ANGB NC 145 AW - New London NC 146 AW, NAS Point Mugu/ Channel Islands ANGS

146 AW - 261CBCS CA

148 FW, Duluth ANGB MN 151 ARW, Salt Lake City ANGB UT 152 AW, Reno ANGB NV 153 AW, Cheyenne ANGB (ROSC 5) WY 155 ARW, Lincoln ANGB (ROSC 4) NE

156 WG Muniz PR

156 WG - 141ACS PR

156 WG - 285CBCS USVI

156 WG CBCS Punta Salinas PR 158 FW, Burlington ANGB VT 161 ARW, Phoenix Sky Harbor International Airport (Sky Harbor ANGB) AZ 164 AW, Memphis ANGB TN 165 AW, Savannah ANGB GA

165 AW - 117ACS GA

165 AW - 224JCSS GA

166 AW, New Castle ANGB DE 167 AW, Shepherd Field ANGB WV 169 FW, McEntire ANGB SC 171 ARW, Pittsburgh IAP ARS PA

171 ARW - 258ATCS PA

173 FW, Kingsley Field ANGB OR

175 Wing, Martin State Airport/Warfield ANGB MD 177 FW, Atlantic City ANGB NJ 178 Wing, Springfield ANGB OH 178 Wing - 123ACS OH 185 ARW, Sioux City ANGB IA 186 ARW, Key Field ANGB MS 187 FW, Montgomery ANGB/Dannelly Field AL

187 FW - 226 CCG AL

187 FW - 280 CBCS AL

190 ARW, Forbes Field ANGB KS 193 SOW, Harrisburg ANGB PA

193 SOW - 112AOS PA

193 SOW - 211EIS PA

193 SOW- LFA PA

194 Regional Support Wing, Joint Base Lewis- McChord (aka McChord AFB) WA

8.2 Call Accounting & Call Recording Replacement Bases: (Atch 1 tab 1)

140 WG-233 SPG CO

125 FW FL

125 FW - 202 RHS FL

109 AW NY

174 ATKW NY

114 FW SD

132 FW IA

122 FW IN

180 FW OH

181 IW IN

181 IW, Jefferson Proving Grounds IN

118 WG TN

134 ARW TN

134 ARW - 241st EIS TN

172 FW MS

147 RW TX

183 FW IL

105 AW NY

159 FW LA

159 FW - 122 ASOS LA

159 FW - 236 CBCS LA

159 FW - 259 ATCS LA

130 AW WV

157 ARW NH

101 ARW ME

101 ARW - 243 EIS ME

111 ATKW PA

162 FW AZ

163 RW-147 CBCS CA

182 AW IL

188 FW AR

CETSC Minot ND CRTC- Volk Field, WI CRTC-Alpena MI CRTC-Gulfport MS

144 FW CA

179 AW OH

179 AW – 200th RH OH

HC108425R0002

8.3 Contractor Travel:

The Contractor may be required to travel while performing tasks in support of this requirement. Travel shall be authorized by the Contracting Officer Representative (COR) in writing prior to performance. Travel is subject to the availability of funding and COR approval. The Government will not reimburse expenses for travel within 50 miles of the contractor’s place of performance. All other travel will be paid as a reimbursable expense in accordance with FAR Part 31. The Government will review for approval all travel orders under this contract prior to the travel taking place and after travel has been taken. The contractor shall provide with each monthly invoice, a legible, detailed actual travel cost breakout by task/subtask, trip and travel location to include all sub-contractor travel, for all travel associated with this contract. No profit or fee will be authorized for travel. Applicable burdens, e.g., G&A, may apply to travel IAW the contractor’s accounting practices.

9. Telework: The Government does not permit the Contractor to telework in support of this requirement.

10. Period of Performance: Project completion for all 105 sites shall be within 1095 days from award of contract.

11. Security Requirements: None.

12. Government Furnished Information:

The local Government Communications Flight staff will provide the following information in a station review document upon request from the Contractor.

o Usernames o Extension(s) or directory number(s) per user o Set type (Soft phone or what type of IP phone) per user o Direct Inward Dial (DID) telephone number(s) per user o All other customer E.164 telephone numbers and their uses o Required phone features to be compliant with Military Unique Deployment Guide o IP addressing scheme and VLAN plan for IP telephones, gateways, servers, and network management

Communications Flight staff includes Voice system administrators, network operations and inside plant.

13. Other Information & Special Considerations:

Base operating hours are 0730 – 1630. Contractor shall provide a work plan showing the ability to finish the work within the period of performance within 14 calendar days of contract award.

Recognized Holidays: The following are recognized United States (US) holidays. The Contractor shall not perform services on these days:

New Year’s Day Martin Luther King, Jr.’s Birthday President’s Day Memorial Day Juneteenth National Independence Day Independence Day Labor Day Columbus Day Veteran’s Day Thanksgiving Day Christmas Day

14. Section 508 Accessibility Standards E201.1 Scope ICT that is procured, developed, maintained, or used by agencies shall conform to the Revised 508 Standards.

E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E207.1 General Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5 Exception from E207.1 General: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5.

E207.2 WCAG Conformance User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

Exceptions from E207.2 WCAG Conformance:

● Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.

● Non-web software shall not be required to conform to the following four Success Criteria in WCAG 2.0:

2.4.1 Bypass Blocks; 2.4.5 Multiple Ways; 3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.

● Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in

WCAG 2.0.

E208.1 General Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E302 Functional Performance Criteria

302.1 Without Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

302.3 Without Perception of Color. Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

302.6 Without Speech. Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

302.8 With Limited Reach and Strength. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

302.9 With Limited Language, Cognitive, and Learning Abilities. ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

501.1 Scope - The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

Exception from E501.1 Scope: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

602.1 General. Documentation that supports the use of ICT shall conform to 602.

603.1 General. ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

PWS Attachments:

PWS Attachment 1: VSS and Subsystems Site Locations

QUALITY ASSURANCE

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

1. Contract or Task Order Title: VSS 3 & Sub Systems Replacement

2. Purpose:

The purpose of the QASP is to describe the systematic methods used to monitor performance and to identify the required documentation and the resources to be employed. The QASP provides a means for evaluating whether the contractor is meeting the performance standards/quality levels identified in the PWS and the contractor’s quality control plan (QCP), and to ensure that the government pays only for the level of services received.

This QASP defines the roles and responsibilities of all members of the integrated project team (IPT), identifies the performance objectives, defines the methodologies used to monitor and evaluate the contractor’s performance, describes quality assurance documentation requirements, and describes the analysis of quality assurance monitoring results.

3. Roles and Responsibilities:

The following personnel shall oversee and coordinate surveillance activities.

Program/Project Manager (PM) – The PM provides program oversight and supports the COR’s performance assessment activities.

Contracting Officer (KO) – The KO shall ensure performance of all necessary actions for effective contracting, ensure compliance with the contract terms, and shall safeguard the interests of the United States in the contractual relationship. The KO shall also ensure that the contractor receives impartial, fair, and equitable treatment under this contract. Determine the final assessment of the contractor’s performance.

Contracting Officer’s Representative (COR) – The COR is responsible for providing continuous technical oversight of the contractor’s performance. The COR uses the QASP to conduct the oversight/surveillance process.

The COR shall keep a Quality Assurance file that accurately documents the contractor’s actual performance. The purpose is to ensure that the contractor meets the performance standards contained in the contract. The COR is responsible for reporting early identification of performance problems to the KO. The COR is required to provide an annual performance assessment to the KO which will be used in documenting past performance. The QASP is the primary tool for documenting contractor performance.