PWS - Voicemail Services.pdf

USAF –LRAFB– Voicemail Services Project ID #: F2S3375217AC01

Little Rock Air Force Base Voicemail Messaging System

PERFORMANCE WORK STATEMENT

AIR MOBILITY COMMAND

12 August 2025

A. INTRODUCTION

A.1 Objective

A.2 Background

A.3 Constraints

A.4 Project Meetings

A.5 Integrated Master Schedule (IMS)

A.6 Schedule Delays

A.7 Work Schedules

A.8 Federal Holidays

A.9 Joint Interoperability Test Center (JITC) Approved Product List (APL)

A.10 Certification and Accreditation (C&A)

A.11 System Installation Plan

A.12 Project Support Agreement (PSA)

A.13 Site Survey

A.14 Configuration Management

A.15 Technical Requirements

A.16 Packaging, Handling, Tracking, Storage and Transportation

A.17 Training

A.18 Equipment Removal

A.19 Maintenance Support

B. INSPECTION AND ACCEPTANCE

B.1 Place of Inspection and Acceptance

B.2 Scope of Inspection

B.3 Basis of Acceptance

B.4 Testing

B.5 Post User Migration Support

B.6 Site Acceptance

Table 1 Services Summary

B.7 Written Acceptance/Rejection by the Government

B.8 Non-Conforming Products or Services

Table 2 Milestones

C. SPECIAL CONTRACT REQUIREMENTS

C.1 Key Personnel

C.2 Key Personnel Substitution

D. CONTRACT ADMINISTRATION

D.1 Contracting Officer

APPENDIX 1 Acronym List

APPENDIX 2 References

A. INTRODUCTION

A.1 Objective The objective of this Performance Work Statement (PWS) is to define the requirements for the Contractor to Engineer, Furnish, Install, and Test (EFI&T) a turn-key voicemail system solution that replaces the existing voicemail system at Little Rock AFB. The proposed system shall be an Avaya IX Messaging System and must be the latest version and configuration on the Joint Interoperability Test Center (JITC) Approved Products List (APL) at the time of award. The Contractor shall configure the system to fully integrate with the existing Avaya Telephony system already in use at LRAFB including all licensing requirements and use all, if any, Government Furnished Equipment (GFE) licenses. The Contractor shall integrate, facilitate, and engineer a solution satisfying all system requirements, line side requirements, carrier side requirements, and ancillary equipment integration requirements outlined in this PWS and/or currently implemented in the existing architecture. The Contractor shall provide and install all necessary equipment to provide a turn-key solution compliant with the latest version of the Department of Defense (DoD) Unified Communications Requirements (UCR), Risk Management Framework (RMF), and all other references set forth in this PWS. The Contractor shall provide a technical solution that meets the requirements of the PWS utilizing existing equipment and provided GFE to the maximum extent practical to support the proposed technical solution. Work shall be accomplished within 30 days in accordance with

PWS.

A.2 Background The scope of this project includes the installation of a new Avaya IX Messaging System with the migration of all users, lines, ancillary systems, trunks, and services currently interfaced with the Little Rock AFB Avaya CM10 The Contractor shall be required to transition using Session Initiation Protocol (SIP). If any users, lines, ancillary systems, trunks, and services are identified that were not called for in this PWS, the Contractor must present them to the Government for engineering review. The Government reserves the right to exercise allied support, optional CLINs and contract modifications.

A.3 Constraints All contracted personnel shall comply with established security procedures for entering an installation and its facilities, including special security procedures for gaining entry into restricted or controlled areas. All personnel entering restricted or controlled areas including data centers, communications closets, environmental control rooms, etc. must possess a valid Secret Security Clearance. The Contractor shall submit proof of a valid Facilities Clearance by completing the DD-254 at the time of award. The Contract shall submit a visit request IAW the procedures contained in DoD 52220.22-M, National Industrial Security Program Operating Manual, and DoD 5220.22-M-Sup 1 prior to each on site visit. The Contractor shall coordinate with the site Point of Contact (POC) to obtain and return temporary badges and vehicle registrations. The Contractor shall request a Government escort 2 business days prior to requiring access to restricted or controlled areas.

No personnel presenting potential threats to the health, safety, security, general wellbeing, or operational mission of the installation and its population shall be employed by the Contractor during the execution of this task order. Compliance with Air Force Instruction (AFI) 91-202 (https://static.epublishing.af.mil/production/1/af_se/publication/afi91-202/afi91-202.pdf) The US Air Force Mishap Prevention Program is mandatory.

The Contractor is responsible to ensure all equipment purchased and installed underneath this PWS is free of any manufacturer defect or recall. The Contractor is fully responsible for all labor and equipment associated to any defect or recall to include any damage or loss of service to GFE due to the defect.

The Contractor must ensure all installed equipment is in compliance with the Trade Agreements Act

(TAA).

The Contractor shall comply with the Privacy Act of 1974 and shall comply with all applicable safeguarding and handling requirements associated with Privacy Act information.

The Contractor shall comply with all references listed in Appendix 2 during the performance of all tasks associated with this PWS. Should a more current version of these references become available the Contractor must use the most current version.

A.4 Project Meetings If deemed necessary by the Contracting Officer Representative (COR) for any of the following project meetings, the Contractor shall be responsible for providing an agenda and meeting minutes for ALL types of meetings to the Contracting Officer Representative (COR) within one day prior to and one day following the meeting. At a minimum, these minutes shall include attendance, issues discussed, decisions made, and action items assigned.

A.4.1 Project Kickoff Meeting The Contractor shall conduct a virtual project kickoff meeting with 19th CS within 5 business days after award. It will provide an introduction between Contractor personnel and Government personnel to allow the review of requirements, timetable expectations, transition plan as well as discuss technical, management, and contractual procedures. At a minimum, the attendees shall include Key Contractor personnel, the Contracting Officer (CO), the COR, and any other relevant Government personnel.

A.4.2 Site Kickoff Meeting The Contractor shall conduct a site kickoff meeting with the COR and selected members of the project team upon arrival at the site for any activity including follow on visits. The Contractor shall review the overall project, goals, timelines, required base support, and any other pertinent information related to the site visit. The Contractor shall support and respond to questions regarding any relative issues pertaining to this PWS by providing a written response to the CO and COR.

A.4.3 Technical Status Meetings The Contractor shall convene a technical status meeting with the COR and other Government stakeholders during preliminary project planning if such a meeting is deemed necessary. The meeting shall be in the form of teleconferences and be attended by Key Contractor Personnel, the COR, and any other relevant Government personnel.

A.4.4 Ad-hoc Meetings The Contractor shall host requisite ad-hoc project meetings onsite or via teleconference to discuss current issues, preliminary schedule, or the proposed and final solution as needed to satisfy the requirements set forth in this PWS.

A.5 Integrated Master Schedule (IMS) The Contractor shall provide a preliminary IMS with the Contractor’s proposal. The IMS shall clearly identify all tasks required for successful implementation and completion, to include the identification of all task interdependencies. The Contractor shall only make changes to the final IMS if the CO authorizes a change.

A.6 Schedule Delays In the event of a delay caused by either the Government or Contractor in which the Contractor incurs schedule delays, the Contractor must document and notify the CO and COR the reasons for any change in the schedule within 1 business day.

The COR is not authorized to change any of the terms and conditions, scope, schedule, or price of the Contract or the PWS. Changes in the scope of work will be made only by the CO by a properly executed modification to the Contract or PWS.

A.7 Work Schedules All work shall be performed during normal duty hours except Authorized Service Interruptions (ASI), which must occur outside normal installation operating hours. ASIs and any other service affecting actions must be pre-approved by the COR and scheduled during maintenance windows. The Contractor shall request such approvals with the COR and must receive written approval prior to any related activities taking place.

Work Hours Normal work hours: Monday – Friday (except federal holidays) (7:00 am – 4:00 pm CST Time) unless otherwise approved in writing and in advance by the CO/COR.

A.8 Federal Holidays Holidays occurring on weekends will be observed as directed by the published Air Force calendar.

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

A.9 Joint Interoperability Test Center (JITC) Approved Product List (APL) All proposed solution(s) shall be on the JITC-certified APL at the time of proposal submission and deployed in the current JITC configuration unless specified in writing by the Government. All equipment or system(s) proposed shall be at the latest JITC-certified software version at the time of award. The systems shall meet all JITC interoperability requirements to ensure seamless integration and functional interfaces with commercial and military interface standards. All Operating Systems (OS) and applications shall be configured in accordance with (IAW) Security Technical Implementation Guidelines (STIGs). The Contractor shall provide a copy of all Interoperability (IO) and Information Assurance (IA) certifications and approval letters as an attachment to the proposal. The proposed solution shall be installed IAW the JITC and Military Unique Deployment Guidelines (MUDG) from the Original Equipment Manufacturer (OEM) and be compliant with appropriate STIGs upon implementation. The Contractor shall identify any non-compliance with any STIGs prior to Government acceptance.

It is the Contractor’s responsibility to ensure there are not any known interoperability issues between GFE hardware or software and the Contractor proposed hardware or software. Any patches, fixes, or workarounds to known issues must be included in the Contractor’s proposal. Should at any time a more up-to-date version of software or hardware become available on the JITC APL and meet the requirements of this PWS, the Contractor must propose a solution in writing to the CO.

A.10 Certification and Accreditation (C&A) The systems installed or manipulated underneath this PWS are to be considered Unified Communications (UC) and will be added to the existing enclave’s accreditation package.

A.11 System Installation Plan The Contractor must obtain Government approval prior to start of any installation work. The Contractor shall clearly identify a detailed step by step process on how the installation and migration of users will be executed.

A.12 Project Support Agreement (PSA) The Contractor must obtain Government approval prior to start of any installation work. The Contractor shall clearly identify expected Government labor, GFE equipment, and allied support required to implement a fully functional solution. Allied support is defined as any tasks required to be performed by the Government to prepare the facilities and environment for installation. Allied support requirements shall be identified in the PSA and approved by the Government in conjunction with the SIP.

A.13 Site Survey

There is no site survey

A.14 Configuration Management Configuration Management information shall be provided to the Government COR and MAJCOM A64I office in common format; email is the preferred method of delivery. All drawings or topologies shall be provided in both Microsoft Visio and PDF format. All other documents shall be in Microsoft Excel or Word format. Documentation shall include but is not limited to:

Bay face layout drawings and diagrams of the chassis/shelf/cabinets identifying installed servers, gateways, circuit packs, modules, line equipment, etc.

Network topologies that depict the overall architecture to include the solution’s connection to the production AFNET, services rendered from the AFNET, line side gateways and VoIP users, carrier side trunks, ancillary side systems, etc.

IP/Fully Qualified Domain Name (FQDN)/Certificate accountability mechanism [inputs in the GFE Telephone Management System (TMS)] that identifies all equipment’s network address, domain name and certificate expirations throughout the UC enclave.

Cable and power drawings/specifications, floor plans, and engineering specifications generated in support of the installation.

A complete list of equipment type, equipment location and equipment serial numbers as well as any OEM documentation or specifications.

Permanently identify all new, upgraded, relocated or reconfigured equipment and material (i.e., cabinets, racks, termination blocks, patching, cables, etc.) through stenciling or tags. The Contractor shall ensure the stenciling and tagging follow the format used by the specific site. Hand written tags and red-lined drawings are unacceptable. All network topologies in the USAF are considered both sensitive and proprietary.

A.15 Technical Requirements The Contractor shall provide and facilitate all configurations and equipment required to satisfy the requirements of the system, line, carrier, and ancillary equipment portion of this PWS. The Contractor shall provide and install all necessary equipment and software to transition the scoped user base from the existing voicemail system to the Avaya IX Messaging System. The Contractor must provide a complete solution that provides the same or better level of service currently provided by the LRAFB telephony architecture.

A.15.1 System Requirements The Contractor must ensure all equipment installed or interfacing with the Avaya IX Messaging System is using DoD PKI certificates. Under no circumstances should the Contractor use OEM certificates shipped with the equipment. The Contractor shall leverage the GFE TMS to provide a consolidated list of certificates and their expiration dates to the CS upon completion of on-site installation activities.

The Contractor shall install the Avaya IX Messaging System by providing a geographically located node in Building 988 that is recognized by the OEM as one system..

The Contractor shall be responsible for all required network configurations needed to satisfy the requirements of this PWS. The Contractor shall leverage GFE available network services to the fullest extent possible. In the event that a required network service cannot be leveraged from the GFE network, the Contractor shall work with the Government to provide a solution to fulfill the shortfall.

The Contractor shall engineer all system control devices (gateways, servers, etc.) with Government provided public IP addresses and if applicable, FQDNs.

The Contractor shall leverage existing racks in Building 988. The Contractor shall ensure the rack (including GFE) facilitate a complete AS-LAN environment for all equipment physically installed within the rack to include network and power requirements. The Contractor shall provide appropriate server rack accessories needed for a professional grade data center installation (i.e., cable management hardware, patch panels, patch cords, etc.).

A.15.2 Carrier Side Requirements The Contractor shall inform the Government of all required carrier side signaling services that become necessary. This includes the transferring of all external connections, [Local, Long Distance, and Defense Switch Network (DSN)] that facilitate outbound services as well as lateral connections that facilitate services for tenant organizations.

A.15.3 SIP Mesh The Contractor shall establish AS-SIP trunks from both Session Managers to SIP enabled system interfacing with the Avaya IX Messaging System in an effort to create a SIP mesh. The Contractor shall ensure the GFE AS-SIP trunks with current DSN capability currently interfaced with the Avaya CM10 and GFE SBCs are transitioned and fully operationally capable according to DISA as needed with the Avaya IX Messaging System.

A.15.4 Ancillary Equipment Requirements The Contractor shall provide and install all necessary equipment to configure the proposed solution to facilitate all ancillary equipment requirements outlined in this PWS and/or currently implemented in the existing architecture.

A.16 Packaging, Handling, Tracking, Storage and Transportation The Contractor shall be responsible for the packaging, handling, tracking, storage, transportation, staging, and deployment of any equipment and materials provided as part of this solicitation. All equipment shall be stored by the Contractor in an appropriate climate-controlled location prior to installation. The Contractor may check with the Government for on-site storage availability throughout the duration of this solicitation; but if there is no space available, the Contractor must secure off-site climate controlled storage.

The Contractor will thoroughly and accurately inventory all equipment being installed or manipulated underneath this solicitation in the presence of the Government.

A.17 Training The Government aims to provide ample and thorough training to all personnel responsible for supporting the Avaya IX Messaging System at LRAFB. The Contractor shall provide a draft training syllabus, lesson plan and training plan. The training curriculum must support 6 students. These areas should include, but are not limited to, end-point additions, voicemail creation and management, A.18 Equipment Removal The Contractor shall remove and decommission the existing Callware Voicemail System. The Contractor shall ensure upon removal of equipment; all ladder racks and cable pathways are connected to the true ceiling in order to support the infrastructure in the absence of the racks and cabinets being removed.

Decommissioned equipment will be the responsibility of the government to turn in to the Defense Logistics Agency (DLA) Disposition Services.

A.19 Maintenance Support and Responsibilities The Contractor shall perform corrective maintenance to restore any and all outages associated to any and all equipment manipulated underneath this solicitation prior to formal project acceptance. The Contractor shall work in coordination with the local CS to restore these outages. If there is an outage reported, the Contractor shall immediately contact the COR to investigate who will be responsible to start a work order or advise as to other course of action. The Contractor shall provide written notification via email to the COR or designated representative at each site, within two hours after service is restored. Included in this notification shall be a description of the corrective action(s) taken to restore the system to proper operation and the cause of the outage. If an outage is identified to not be the responsibility of the Contractor, the Contractor shall ensure proper hand off of the incident to appropriate local CS personnel. The Contractor shall provide a monthly trouble ticket report detailing any trouble tickets escalated to the Contractor for action and the fix actions associated to the outage.

Major Failures Per AMC AS-LAN guidelines derived from DoD UCR 2013, a major failure is described as a loss of 96 or more ports/users as a result of any hardware or software failure. The Contractor shall respond remotely within four (4) hours upon notification of the problem and restore service.

Minor Failures Per AMC AS-LAN guidelines derived from DoD UCR 2013, a minor failure is described as any normal or abnormal hardware or software fault that degrades services to less than designed performance; but which does not constitute a Major Failure. The Contractor shall respond remotely to all minor failures within 24 hours Monday through Friday during regular duty hours, excluding Federal holidays.

OEM Sustainment The Government executes a contract known as the Enterprise Cyber Transport Systems (CTS) contract each calendar year and the AMC CTS contract each fiscal year in support of UC deployments. The Contractor is required to provide OEM sustainment coverage throughout the duration of this PWS and additionally from site acceptance until the start of the next Enterprise CTS or AMC CTS contract respectively. The Contractor will not terminate coverage until the Government has confirmed the system is either covered by the Enterprise or AMC CTS contract. During the entire duration of this solicitation leading up to the termination with the Enterprise or the AMC CTS Contract, the Government requires the Contractor to provide upgrade protection that allows the Government to exercise major version upgrades at no cost from the OEM. The Contractor shall provide written procedures and required information to access these OEM support functions prior to Government acceptance.

Professional Services Warranty The Contractor shall provide a workmanship warranty for services and equipment provided or installed underneath this solicitation for one year after project acceptance. This warranty should include any Contractor configurations or solutions. The Contractor shall provide expertise via remote support or on-site support as needed should an issue arrive related to the professional services rendered by the Contractor.

The Contractor shall provide written procedures and required information to solicit warranty support prior to Government acceptance.

B. INSPECTION AND ACCEPTANCE

B.1 Place of Inspection and Acceptance Inspection of all work performance, reports, and other deliverables shall be performed by the COR throughout installation process. Final acceptance of all work performance, reports, and other deliverables shall be performed by the COR with coordination from the CO.

B.2 Scope of Inspection All deliverables will be inspected for content, completeness, accuracy and conformance to PWS requirements by the COR. Inspection may include validation of information or software through the use of automated tools, testing, or inspections of the deliverables, as specified in this PWS. The scope and nature of this inspection will be sufficiently comprehensive to ensure the completeness, quality, and adequacy of all deliverables.

B.3 Basis of Acceptance The basis for acceptance shall be in compliance with the requirements set forth in the base contract and relevant terms and conditions of this PWS. Deliverable items rejected shall be corrected in accordance with the applicable clauses.

The final acceptance will occur when all discrepancies, errors, or other deficiencies identified in writing by the Government have been resolved, through documentation updates, program correction, or other mutually agreeable methods.

Reports, documents, and narrative-type deliverables will be accepted when all discrepancies, errors, or other deficiencies identified in writing by the Government have been corrected.

If the draft deliverable is adequate, the Government may accept the draft and provide comments for incorporation into the final version.

All of the Governments’ comments on deliverables must either be incorporated in the succeeding version of the deliverable, or the Contractor must demonstrate to the Government's satisfaction why such comments should not be incorporated.

If the Government finds that a draft or final deliverable contains spelling errors, grammatical errors, improper format, or otherwise does not conform to the requirements stated within this PWS, the document may be immediately rejected without further review and returned to the Contractor for correction and resubmission. If the Contractor requires additional Government guidance to produce an acceptable draft, the Contractor shall arrange a meeting with the COR.

B.4 Testing Equipment testing shall be per industry and OEM testing standards The COR shall participate and witness all tests conducted. The Contractor shall coordinate the testing dates with the COR. Test results will be reviewed and approved by the COR by signing the system test completion document indicating the system has passed all testing standards upon successful completion of any testing The Contractor shall document and retest any failed test portions within 24 hours, unless equipment has failed and requires replacement.

Upon receipt of the replacement equipment, the test will be restarted. The Contractor shall document all test activities on a Contractor provided test completion form.

B.5 Post User Migration Support The Contractor shall provide on-site post user migration support and services during business hours two business days after any migration of more than 100 users to completely validate operations during high volume service. Remote access, if required, must be coordinated with the Government and comply with all applicable security guidelines and regulations.

B.6 Site Acceptance The system will be considered accepted or completed once all of the requirements of this PWS are met and the Government accepts the requirements stated herein as completed. The DD-250 document shall be used for acceptance of hardware only and AFTO Form 747 will be used to document completion of the project.

The Government is responsible for initiating the 747 process once applicable. The Contractor shall not consider the system accepted without the COR signing off on the DD-250 and AFTO 747. The COR will be the final signatory on the DD-250 and AFTO 747 documents with the CO having final authority for all delivery order activities. The Contractor shall notify the Government upon completion of all delivery order tasks.

The COR will coordinate and approve site acceptance. Site acceptance shall conclude upon successful installation, commissioning, connecting and testing of the system, and receipt of all deliverables. Before site acceptance, the system shall operate without any major or minor failure for a minimum of seven consecutive days prior to Government acceptance. The minimum seven consecutive days without any major or minor failure will start over until the Government receives seven consecutive days without any major or minor failure. The Government reserves the right to refuse final acceptance until all discrepancies are resolved to the satisfaction of the Government. The Contractor shall prepare a project discrepancy list and share this list during the technical status meetings; report detected issues during meetings and track all discrepancies until resolved. The Government will review and monitor all discrepancies and deliverables.

The discrepancy list shall include any problem(s) detected and identified. The Contractor shall retain a history of discrepancies. Problems identified during the period of performance shall be documented, provided to the Government, and corrected prior to final acceptance.

B.7 Written Acceptance/Rejection by the Government The CO may provide written notification of acceptance or rejection of all final deliverables within five business days (unless specified otherwise). All notifications of rejection will be accompanied with an explanation of the specific deficiencies causing the rejection.

B.8 Non-Conforming Products or Services The Contractor shall have ultimate responsibility for the successful completion of this PWS. Any work deemed non-compliant by the COR and communicated in writing to the Contractor via the CO shall immediately be re-worked by the Contractor. Non-conforming products or services will be rejected.

Deficiencies will be corrected by the Contractor within 10 days of the rejection notice. If the deficiencies cannot be corrected within 10 days, the Contractor shall immediately notify the COR of the reason for the delay and provide a proposed corrective action plan within three days. The Government will not provide acceptance for any products or services that do not conform to the requirements of this task order.

C. SPECIAL CONTRACT REQUIREMENTS

C.1 Key Personnel The following are the minimum personnel who shall be designated as “key.” The Government does not intend to dictate the composition of the ideal team to perform this PWS (i.e., if the Contractor intends to propose additional labor categories as “key”); but the Contractor shall submit a Key Personnel Qualifications Matrix for each proposed person assigned a key personnel role. The Key Personnel

Qualifications Matrix shall be clear and verify the proposed person for each key personnel labor category meets all requirements as detailed below. The Government will evaluate additional key personnel as proposed by the Contractor.

a. PM

b. OSE

The Government desires that key personnel be assigned for the duration of the task order. Substitutions will only be made in accordance with the instructions in Section C.2.

C.1.1 Project Manager The Contractor shall identify by name in the Contractor’s proposal the PM responsible as the single POC for the duration of this PWS. The PM must be a prime Contractor employee, have authority to make decisions, signatory authority, and ability to commit the company. The PM is responsible for scheduling, organizing, and leading weekly meetings to track planning and progress of the project from planning stages through completion and Government acceptance. The PM shall be responsible for providing the deliverables to the Government. The PM shall be responsible for supervision of all contract personnel and performance of all Contractor-related functions.

C.1.2 On-Site Engineer The Contractor shall identify by name in the proposal an OSE who is responsible for the technical implementation of this solicitation. The OSE should provide a high level of expertise pertaining to integrating the different components of the LRAFB telephony environment and shall become the liaison for all technical implications and action items associated to this solicitation. This individual must follow all personnel requirements and constraints outlined in Section A.3 of this solicitation to include the IAT Level 2 and security clearance qualifications.

The OSE shall support regular OJT of Government personnel in an attempt to transition control of the new LRAFB Avaya IX Messaging System back to knowledgeable and confident Government technicians. The OSE shall maintain the databases associated to the systems by ensuring entries and configurations are labeled and organized, ensuring STIG and IA compliance, ensuring policies associated to moves, adds, changes, and removes are in place and followed, and conducting quality assurance processes on the databases. The OSE should be working with the Government to establish sustainment and maintenance processes and policies such as scheduled server backups, patch management, database management, topology and documentation management, training plan development, etc. The OSE shall be responsible to support ongoing operations and assist the Government in restoring any outages associated to equipment within the scope of this PWS.

C.2 Key Personnel Substitution Individuals proposed for key personnel positions under this PWS are expected to remain dedicated to the tasks required within this entire PWS. Substitutions will not be accepted unless specifically agreed upon and shall be made in accordance with this clause. All proposed substitutions of key personnel must be submitted in writing at least 10 days in advance of the proposed substitution and must be sent to the CO and the COR. All requests for substitutions must provide a detailed explanation of the circumstances necessitating the proposed substitution(s) and any other information requested by the CO or COR to make a determination as to the appropriateness of the proposed substitution(s). Substitution requests shall clearly identify how the proposed replacement meets or exceeds applicable standards established in the solicitation (i.e., evaluation criteria minimum qualifications), and any betterment made thereto by the Contractor via its offer. All proposed substitutes must have qualifications at least equal to the person being replaced. The Government will evaluate requests for substitutions and the CO or COR will notify the Contractor of approval or disapproval.

APPENDIX 1 Acronym List AFB Air Force Base AFBAN Air Force Base Area Network AFI Air Force Instruction AFMAN Air Force Manual AFNET Air Force Network AFTO Air Force Technical Order AMC Air Mobility Command AMC/A64I Air Mobility Command A6 Ground Communications APL Approved Products List AFFARS Air Force Federal Acquisition Regulation Supplement AS-LAN Assured Services Local Area Network ASI Authorized Service Interruption C&A Certification and Accreditation CFR Code for Federal Regulation CLIN Contract Line Item Number CM Communication Manager CNSSI Committee on National Security Systems Instruction CO Contracting Officer COR Contracting Officer’s Representative CPARS Contractor Performance Assessment Reporting System CS Communications Squadron CUI Controlled Unclassified Information DISA Defense Information Systems Agency DoD Department of Defense DoDI Department of Defense Instruction DODIN Department of Defense Information Network DSN Defense Switched Network EFI&T Engineer, Furnish, Install and Test ESC Enterprise Session Controller FAR Federal Acquisition Regulation GFE Government Furnished Equipment GWT Government Witness Testing HA High Availability HVAC Heating, Ventilation and Air Conditioning IA Information Assurance IAW In Accordance With IDF Intermediate Distribution Frame IO Interoperability IMS Integrated Master Schedule IP Internet Protocol IPT Integrated Project Team IT Information Technology ITSS Information Technology Support Service JITC Joint Interoperability Test Center LAN Local Area Network LRAFB Little Rock Air Force Base LSC Local Session Controller MSR Monthly Status Report MUDG Military Unique Deployment Guidelines NAICS North American Industry Classification System

NDA Non-Disclosure Agreement NLT No Later Than NOC Network Operations Center O&M Operations and Maintenance OEM Original Equipment Manufacturer OJT On-the-job training OS Operating System OSE On-site-Engineer PM Project Manager PNR Problem Notification Report POC Point of Contact PoE Power over Ethernet PSA Project Support Agreement PWS Performance Work Statement QASP Quality Assurance Surveillance Plan SIP Session Initiation Protocol SIP System Installation Plan SM Session Manager SMGR System Manager SMTP Simple Mail Transfer Protocol STIG Security Technical Implementation Guide TAA Trade Agreements Act TBD To-be-determined TDM Time-Division Multiplexing TO Task Order TSG Telecommunications Security Group TMS Telephone Management System UC Unified Communications UCD Unified Call Distribution UCR Unified Communications Requirements UPS Uninterruptable Power Supply USAF United States Air Force VoIP Voice over Internet Protocol VPS Voice Protection System

APPENDIX 2 References

• UCR 2013 Change 2 - (https://storefront.disa.mil/kinetic/disa/service-catalog#/forms/dod-information-network-dodin-apl-process-guide)\

• OSHA CFR 29 Part 1910-268 - Telecommunications - (https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.268)

• NEMA TC 2-2013 - Electrical Polyvinyl Chloride (PVC) Conduit -

(https://www.nema.org/Standards/ComplimentaryDocuments/Contents%20and%20Scope%20NEM A%20TC%202-2013.pdf)

• TIA-607-C - Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises (https://global.ihs.com/doc_detail.cfm?&csf=TIA&item_s_key=00576657&item_key_date=821131 &input_doc_number=607C&input_doc_title=&org_code=TIA)

• EIA/ECA-310-E - Cabinets, Racks, Panels, and Associated Equipment - (https://global.ihs.com/doc_detail.cfm?&rid=IHS&item_s_key=00032880&item_key_date=940031 &input_doc_number=CABINETS%2C%20RACKS%2C%20PANELS%2C%20AND%20ASSOCI ATED%20EQUIPMENT&input_doc_title=)

• NFPA 70 - (2017) National Electric Code - (https://www.nfpa.org/codes-and-standards/all-codes-and-standards/list-of-codes-and-standards/detail?code=70)

• NFPA 780 – Standard for the Installation of Lightning Protection Systems - (https://www.nfpa.org/codes-and-standards/all-codes-and-standards/list-of-codes-and-standards/detail?code=780)

• MIL-HDBK-419A – Grounding, Bonding, and Shielding for Electronic Equipment and Facilities - (https://www.dtic.mil/dtic/tr/fulltext/u2/a239565.pdf)

• DoD Manual 4160.21, Volume 1, Change 2 – Defense Material Disposition: Disposal Guidance and Procedures - (https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/416021_vol1.pdf)

• DoD Instruction 8510.01, Change 2 - RMF for DoD Information Technology (https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001_2014.pdf)

• UFC 4-010-06 CyberSecurity of Facility-Related Control Systems (https://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc/ufc-4-010-06)

• Telecommunications Security Group (TSG)- TSG Standards 1 through 5 - (https://www.cnss.gov/CNSS/issuances/TSG_Standards.cfm)

• DISA STIGs - (https://iase.disa.mil/stigs/)

• APL - (https://aplits.disa.mil/processAPList.action)

• AFI 13-204v3 - Airfield Operations Procedures and Programs - (http://static.e-publishing.af.mil/production/1/af_a3/publication/afi13-204v3/afi13-204v3.pdf)

• AFMAN 13-215V3 - Airfield Operations Equipment Systems -

(https://static.epublishing.af.mil/production/1/af_a3/publication/afman13-215v3/afman13- 215v3.pdf)

• DoDI 8560.01 - Communications Security (COMSEC) Monitoring - (https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/856001p.pdf)

• MIL-STD-1130C - DoD Standard Practice Connections, Electrical, Solderless Wrapped - (https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwiemI6c x7_bAhUF74MKHVdACIIQFggpMAA&url=http%3A%2F%2Feveryspec.com%2FMIL- STD%2FMIL-STD-1100-1299%2Fdownload.php%3Fspec%3DMIL-STD- 1130C.040655.pdf&usg=AOvVaw08dvjiAvkd7DVfmgtDIS8n)

• DISA ACAS - (https://www.disa.mil/cybersecurity/network-defense/acas)

• UFC 3-580-01 Change 1 Telecommunications Interior Infrastructure Planning and Design -

(https://www.wbdg.org/FFC/DOD/UFC/ufc_3_580_01_2016_c1.pdf)

• CNSSI 5001 - Type-Acceptance Program for Voice over Internet Protocol (VoIP) Telephones – https://storefront.disa.mil/kinetic/disa/service-catalog#/forms/dod-information-network-dodin-apl-process-guide)%5C https://storefront.disa.mil/kinetic/disa/service-catalog#/forms/dod-information-network-dodin-apl-process-guide)%5C https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.268 https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.268 https://www.nema.org/Standards/ComplimentaryDocuments/Contents%20and%20Scope%20NEMA%20TC%202-2013.pdf https://www.nema.org/Standards/ComplimentaryDocuments/Contents%20and%20Scope%20NEMA%20TC%202-2013.pdf https://global.ihs.com/doc_detail.cfm?&csf=TIA&item_s_key=00576657&item_key_date=821131&input_doc_number=607C&input_doc_title=&org_code=TIA https://global.ihs.com/doc_detail.cfm?&csf=TIA&item_s_key=00576657&item_key_date=821131&input_doc_number=607C&input_doc_title=&org_code=TIA https://global.ihs.com/doc_detail.cfm?&rid=IHS&item_s_key=00032880&item_key_date=940031&input_doc_number=CABINETS%2C%20RACKS%2C%20PANELS%2C%20AND%20ASSOCIATED%20EQUIPMENT&input_doc_title= https://global.ihs.com/doc_detail.cfm?&rid=IHS&item_s_key=00032880&item_key_date=940031&input_doc_number=CABINETS%2C%20RACKS%2C%20PANELS%2C%20AND%20ASSOCIATED%20EQUIPMENT&input_doc_title= https://global.ihs.com/doc_detail.cfm?&rid=IHS&item_s_key=00032880&item_key_date=940031&input_doc_number=CABINETS%2C%20RACKS%2C%20PANELS%2C%20AND%20ASSOCIATED%20EQUIPMENT&input_doc_title= https://www.nfpa.org/codes-and-standards/all-codes-and-standards/list-of-codes-and-standards/detail?code=70 https://www.nfpa.org/codes-and-standards/all-codes-and-standards/list-of-codes-and-standards/detail?code=70 https://www.nfpa.org/codes-and-standards/all-codes-and-standards/list-of-codes-and-standards/detail?code=780 https://www.nfpa.org/codes-and-standards/all-codes-and-standards/list-of-codes-and-standards/detail?code=780 https://www.dtic.mil/dtic/tr/fulltext/u2/a239565.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/416021_vol1.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001_2014.pdf https://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc/ufc-4-010-06 https://www.cnss.gov/CNSS/issuances/TSG_Standards.cfm https://iase.disa.mil/stigs/ https://aplits.disa.mil/processAPList.action http://static.e-publishing.af.mil/production/1/af_a3/publication/afi13-204v3/afi13-204v3.pdf http://static.e-publishing.af.mil/production/1/af_a3/publication/afi13-204v3/afi13-204v3.pdf https://static.epublishing.af.mil/production/1/af_a3/publication/afman13-215v3/afman13-215v3.pdf https://static.epublishing.af.mil/production/1/af_a3/publication/afman13-215v3/afman13-215v3.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/856001p.pdf https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwiemI6cx7_bAhUF74MKHVdACIIQFggpMAA&url=http%3A%2F%2Feveryspec.com%2FMIL-STD%2FMIL-STD-1100-1299%2Fdownload.php%3Fspec%3DMIL-STD-1130C.040655.pdf&usg=AOvVaw08dvjiAvkd7DVfmgtDIS8n https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwiemI6cx7_bAhUF74MKHVdACIIQFggpMAA&url=http%3A%2F%2Feveryspec.com%2FMIL-STD%2FMIL-STD-1100-1299%2Fdownload.php%3Fspec%3DMIL-STD-1130C.040655.pdf&usg=AOvVaw08dvjiAvkd7DVfmgtDIS8n https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwiemI6cx7_bAhUF74MKHVdACIIQFggpMAA&url=http%3A%2F%2Feveryspec.com%2FMIL-STD%2FMIL-STD-1100-1299%2Fdownload.php%3Fspec%3DMIL-STD-1130C.040655.pdf&usg=AOvVaw08dvjiAvkd7DVfmgtDIS8n https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwiemI6cx7_bAhUF74MKHVdACIIQFggpMAA&url=http%3A%2F%2Feveryspec.com%2FMIL-STD%2FMIL-STD-1100-1299%2Fdownload.php%3Fspec%3DMIL-STD-1130C.040655.pdf&usg=AOvVaw08dvjiAvkd7DVfmgtDIS8n https://www.disa.mil/cybersecurity/network-defense/acas https://www.wbdg.org/FFC/DOD/UFC/ufc_3_580_01_2016_c1.pdf

(https://www.cnss.gov/CNSS/issuances/Instructions.cfm)

• CNSSI 5002 - National Information Assurance (IA) Instruction for Computerized Telephone

Systems – (https://www.cnss.gov/CNSS/issuances/Instructions.cfm)

• ISO 33.040.35 - Telephone Networks - (https://www.iso.org/ics/33.040.35/x/)

• BICSI Telecommunications Distribution Methods Manual (TDMM) ©, 13th Edition -

(https://www.bicsi.org/education-certification/education-@-bicsi-learning-academy/technical-publications/telecommunications-distribution-methods-manual)

• DoDD 8570 IAT Level II Certification – (https://iase.disa.mil/iawip/Pages/iabaseline.aspx) https://www.cnss.gov/CNSS/issuances/Instructions.cfm https://www.cnss.gov/CNSS/issuances/Instructions.cfm https://www.iso.org/ics/33.040.35/x/ https://www.bicsi.org/education-certification/education-@-bicsi-learning-academy/technical-publications/telecommunications-distribution-methods-manual https://www.bicsi.org/education-certification/education-@-bicsi-learning-academy/technical-publications/telecommunications-distribution-methods-manual https://iase.disa.mil/iawip/Pages/iabaseline.aspx

C.2 Key Personnel Substitution