Ref A.) SOW.pdf

20 Jan 2021 R06

Statement of Work

For

Kirtland Air Force Base, New Mexico

58th SOW WOC Upgrade

Table of Contents

1 SCOPE

2 Background:

3. TECHNICAL REQUIREMENTS

3.1 Site Specific Requirements:

3.1.1 WOC 1017:

3.1.2 Building 20420:

3.1.3 LaMosca/Sacred Winds:

3.2 System Requirements:

3.2.1 Dispatch Console/Operator Position:

3.2.2 Antennas

3.2.3 Interconnecting Communications/Circuit Requirements:

3.2.4 Demarcation Points:

3.2.5 AES Encryption:

3.3. Applicable Standards

3.3.1 APCO P25 Standards:

3.3.2 Site Preparation Standards:

3.4 Information Assurance (IA)

4 Site Preparation Guidelines

4.1 General Guidelines

4.2 Grounding Guidelines

4.3 Lightning Protection Guidelines

4.4 Uninterruptible Power Supply (UPS) Guidelines

4.5 Cable Trays Guidelines

4.6 Heating, Ventilating and Air Conditioning (HVAC) Guidelines

4.7 Auxiliary Power System Guidelines

4.8 Physical Security Guidelines

4.9 Surge Protection Guidelines

5 Implementation Services

5.1 Schedule

5.2 Program Management

5.3 System Engineering

5.4 Project Status Review (PSR) Meetings

5.5 Transportation of System Equipment

5.6 Site Access Information and Visitor Control Requirements

5.7 Optimization

5.8 Quality Assurance (QA), Testing, and Burn‐In

5.8.1 Quality Assurance

5.8.2 Factory Acceptance Test

5.8.3 System Acceptance Test

5.8.4 RF Coverage Test:

5.8.5 System Burn‐in:

5.9 System Cutover

5.10 As‐Built Documentation

5.11 System Acceptance

6 LOGISTICS REQUIREMENTS

6.1 Spares

6.2 Warranty

6.3 Disposition of removed equipment:

7 DELIVERABLE REQUIREMENTS

ANNEX A (APCO P25 Standards)

ANNEX B (Site Preparation Standards)

ANNEX C (Information Assurance policy and documents)

Hours of Operation/Scheduled Events

Acronyms

Notional System Drawings

1 SCOPE

The 58th SOW requires a "turnkey" Wing Operations Center (WOC) radio and dispatch upgrade including new ground‐to‐air radios and antenna systems, integration with existing radios, and extension of the existing Kirtland Land Mobile Radio (LMR) dispatch system.

The contractor shall provide all personnel, equipment, installation, configuration management, labor, material, documentation, and services in support of the program. Services include: project management and systems engineering services in support of the design, system staging, site preparation/development, equipment installation and optimization, acceptance testing, training, and removal of equipment. The contractor shall perform all necessary efforts in the completion of this project to receive site acceptance.

2 Background:

The following information is provided to assist the contractor in preparing responses to this solicitation and is for reference only. The contractor is responsible for verifying information during the pre‐proposal conference.

Kirtland AFB proper is located in Albuquerque, New Mexico adjacent to the Albuquerque International Sunport Airport (KABQ). The 58th SOW operates out of a facility on the north side of the airport. Flight missions from this location include a mix of aircraft from slow moving TH‐1, UH‐1N (Huey), and HH‐60G (Pavehawk) helicopters, to faster CV‐22B (Osprey) and large frame aircraft such as the MC‐130J (Commando II), HC‐130 (Combat King), and MC‐130H (Combat Talon). The current radio system is inadequate for providing safety of flight or flight following in the low‐level areas.

Sites

Location Building Lat Lon GL[ft]

WOC 1017 35° 2'58.66"N 106°35'37.51"W 5327

20420 20420 35° 2'50.86"N 106°33'7.82"W 5403

LaMosca/Sacred Winds n/a 35°15'9.09"N 107°35'47.74"W 10988

Wing Operations Center (WOC) 1017

Located in Building 1017, this location is where all flight operations are handled out of using an existing and deteriorating radio system. The grounding at this location is not R‐56 compliant. The equipment room lacks a halo ring, tie‐in for equipment, and proper lighting protection for the antenna systems. The facility has an existing AN/GRC‐171v1 that will be replaced under this initiative, and APX‐7500 Consolettes that will be integrated into the Dispatch position. There is a decommissioned RT‐1446 HF radio that is planned for replacement, but not under this effort. Room exists for additional radios and associated electronics. It may be necessary to remove the existing MT‐686 rack and install a standard 19” rack for mounting of equipment. A Brocade switch provides connectivity back to the Kirtland LMR Core and to 20420. This same switch also provides access to commercial internet that can be used to tie the WOC to LaMosca. However, this link must be over a VPN for security.

20420 The grounding at this location is not fully R‐56 compliant. Two radio sets, one VHF (GRT‐21, GRR‐23), one UHF (GRT‐22, GRR24) will be decommissioned, removed, and replaced by one CM‐350 UDX and one CM‐135 VDX radio. The radios shall be remoted back to 1017 and interfaced at that location. The goal is to allow the WOC access to these radios over both the new MCC‐7500 dispatch and local Radio Control Units (RCU). Existing feed to the OK‐423 remote control head at the WOC will be disconnected. A Department Of Energy (DOE) tower is located here along with the base Land Mobile Radio (LMR) repeaters. The tower has space for additional antennas.

LaMosca/Sacred Winds This is a commercial ISP facility that has facility and tower space for the installation of new radios. The site is fully R‐56 compliant and has available backup power (both USP and Generator) for the additional equipment. Connection to this site will be over commercial internet. This will require the installation of a

Virtual Private Network (VPN) connection back to, and terminating in, the WOC. Solution needs to be compatible with the existing Brocade switch at the WOC. Typical device for this effort is a CISCO WS‐

C3650‐24TS‐E or similar switch with VPN capability.

Google Earth Image Site Picture

3. TECHNICAL REQUIREMENTS

The system shall be capable of providing radio interoperability connections as identified in this SOO.

3.1 Site Specific Requirements:

A notional system sketch is included in Notional System Drawings, an Appendix to this document.

3.1.1 WOC 1017: Effort shall include installation of radios, a new MCC‐7500 Dispatch Position, new radios, rack(s) and associated antenna system (cable, surge protection, antenna mount, and antennas).

This location will bring in multiple radios from two other locations; Building 20420 and LaMosca. The WOC desk shall be provided with General Dynamics Remote Control Unit (RCU) radio controls for the CM‐350 radios installed in 20420, LaMosca, and 1017. These controls will act as backup in the event that the Dispatch console fails or that multiple operators are required.

3.1.1.1 MCC‐7500 Dispatch Positon:

This location is the primary dispatch location and shall consist of a new MCC‐7500 Dispatch Position and associated electronics required to interface into the existing LMR system. The Dispatch Position shall:

Be provided with a Conventional Site Controller (CSC) or similar solution such that loss of connection to the LMR Core does not disrupt communications using locally attached radios

Be provided with eight remote speakers, each designated to a particular radio and reconfigurable by the Operator

Include a 19” flat‐screen monitor

Include two (2) headset jacks using Bantam plugs

Include one (1) gooseneck microphone

Include one (1) footswitch

Provide an Aux I/O that will be connected and configured for door lock control

Provide a VHF APX 6500 or similar radio compatible with the existing FBI system and integrated into the Dispatch System.

The contractor shall interface the Aux I/O into the existing door lock and provide the dispatch operator with an appropriate control.

The Contractor shall install sufficient gateways and associated equipment to tie in the following radio assets:

One Harris AN/PRC‐150 HF Radio

One Harris AN/PRC‐117G SATCOM Radio

Five Motorola APX‐7500 Consolettes

One FBI APX 6500 or similar

Three CM‐350V2 radio assemblies (radios remoted from LaMosca)

Two CM‐350V2 radio assemblies (radios remoted from 20420)

One CM‐350V2 radio assemblies (radios located in 1017)

3.1.1.2 Networking:

The small contractor shall install and configure a switch capable of supporting a Virtual Private Network (VPN) connection between this location and LaMosca. Solution shall be compatible with the existing

Brocade switch at the WOC. Typical device for this effort is a CISCO WS‐C3650‐24TS‐E. This switch shall also be configured to connect back through the Brocade to 20420 over a Government configured VLAN.

3.1.1.3 Radios:

The contractor shall provide and install.

One General Dynamics CM‐350(V2) UDX UHF Radio set with T/R Relay

One VHF LMR radio and antenna for FBI interoperability. This is nominally an APX 6500 with OTAR/OTAP, AES, SmartZone, P25, and APX Mobile Radio Authentication

3.1.2 Building 20420: Effort shall include installation of new rack(s), radios, associated antenna system (cable, surge protection, grounding, antenna mount, and antenna). Government Furnished antennas are available at this location.

3.1.2.1 Radios:

The contractor shall provide and install.

One General Dynamics CM‐350(V2) UDX UHF Radio set with T/R Relay

One General Dynamics CM‐350(V2) VDX VHF Radio set with T/R Relay

3.1.2.2 Networking:

The contractor shall connect the installed radios to the Government Brocade switch at this location. The Government will identify which ports are to be used and where those ports will present at 1017.

3.1.2.3 Tower:

The site has an existing tower with space available. The contractor is responsible for providing all mounting equipment for antennas and cable.

3.1.2.4 Systems Management:

The contractor shall provide System Management software for the General Dynamics radios. The Government provided Systems Management computer is located in Building 20420. This software shall be capable of remote fault detection and maintenance for the CM series radios installed at 20420, LaMosca, and 1017.

3.1.3 LaMosca/Sacred Winds: Effort shall include installation of radios, racks, associated antenna systems, and network backhaul that will be connected to a demarcation provided by Sacred Winds Communications.

3.1.3.1 Networking:

The contractor shall install and configure a switch capable of supporting a Virtual Private Network (VPN) connection between this location and 1017. Solution shall be compatible with the existing Brocade switch at the WOC. Typical device for this effort is a CISCO WS‐C3650‐24TS‐E.

3.1.3.2 Radios:

The contractor shall provide and install.

Two General Dynamics CM‐350(V2) UDX UHF Radio sets with T/R Relay

One General Dynamics CM‐350(V2) VDX VHF Radio set with T/R Relay

3.2 System Requirements:

Functions using the provided frequencies

Complies with the Telecommunications Industry Association/Electronics Industry Association 102 (TIA/EIA 102) suite of standards and specifications where applicable

3.2.1 Dispatch Console/Operator Position:

Operator positions shall allow for End‐to‐End AES encryption. All encryption hardware and software/firmware shall be certified in accordance with the National Institute of Standards and Technology (NIST). All system encryption shall be managed by the same encryption management subsystem. For technology employing link‐encryption; those locations where extension to the operator position is provided by media conversion, either due to space or cost, the encryption requirement may be waived by the Government for that particular link.

All dispatch positions shall be provided with desktop computers.

Operator positions shall be capable of providing the following features:

Activity Log

Aliasing

All‐Points Bulletin

Announcement Group Calls

Auxiliary Input/Output Control

Call Alert

Conventional (mutual‐aid) Interfaces

Dispatcher Interrupt

Emergency Alarm

Intercom

Logging Recorder Interface

Multiple (customized) Operator Screens

Multi‐Select

Private Call Patch

Private Calls

Radio Patch

Tactical Priority

Talkgroup Calls

Talkgroup ID Display

Talkgroup Merge

Talkgroup Patch

Unit ID Display

Instant Replay

3.2.2 Antennas

GFE antennas are available for the CM‐350 radios to be installed at Building 1017 and 20420. In order to standardize antennas on the installation it is desired that for installation of the CM‐350 radios the

Contractor utilize TACO antennas such as:

TACO D2213 (UHF/VHF)

TACO D2214 (UHF/UHF)

TACO D2295 (U/V/U and embedded lightning rod)

TACO D2262 (UHF Single port)

TACO D2216 (VHF Single Port)

3.2.3 Interconnecting Communications/Circuit Requirements:

Contractor shall provide the specifications for all connectivity links to support the proposed system. The default connection media is single mode fiber. Dark fiber will be provided; the contractor is responsible for providing and installing media adapters where their design requires them.

Offerors shall specify the interconnecting communications circuits required for the system and provide the following information:

Number of circuits required (To/From) – From building/ room number to building/ room number. (If there is no building or room number, identify the locations by site common name such as “RF repeater shelter”.)

Type of circuit required ‐ Such as 10/100 Base‐T Local Area Network Extension. LAN extension circuits will be full duplex capable and compliant with IEEE 802.3 standards.

Minimum bandwidth required ‐ specify the minimum required bandwidth (or throughput).

3.2.4 Demarcation Points:

The contractor shall furnish the required cable and equipment to connect to the Government’s designated circuit demarcation point. The contractor shall identify by location all demarcation points and responsibilities for both contractor and base. At a minimum the contractor shall address

1. Civil Engineering Support Requirements Identify the support requirements to be provided by the host civil engineering activity and those provided by the contractor. Such as, but not limited to: generators, UPS, transfer switches, load centers, HVAC (Heating Ventilation and Air Conditioning) work, and any GFE equipment identified for reuse.

Power demarcation

Circuit breaker/Outlet reservation

Required power by rack location

Modifications to or relocation of existing equipment

New equipment installation (space and rack reservation)

2. Communications‐Computer Systems Support Requirements Identify support requirements to be provided by the host communications‐computer systems activity and those provided by the contractor. Such as, but not limited to: fiber and copper demarcation and count, network support, and any GFE equipment identified for reuse.

Fiber demarcation, count, and termination type

Copper demarcation and count

Rack location

Cable ladder and cable management

3.2.5 AES Encryption:

All AES Encryption hardware and software/firmware shall be certified, in accordance with current NIST and NSA requirements.

3.3. Applicable Standards

The system shall comply with the following standards: In the event the standard has been updated, the contractor shall comply with the most current version of the published standards.

3.3.1 APCO P25 Standards:

The system shall comply with the TIA/EIA guidance given in ANNEX A (APCO P25 Standards) The latest version of these documents may be obtained from http://www.tiaonline.org.

3.3.2 Site Preparation Standards:

Site preparation is anticipated to be required in support of this system. All civil work shall be performed in accordance with the following documents and standards given in ANNEX B (Site Preparation Standards). Note: Specific vendor installation criteria is given as reference.

3.4 Information Assurance (IA)

The Dispatch System is an extension to the IA certification of Kirtland LMR. The vendor shall work with appointed representatives to ensure the system is fully documented and compliant with IA controls. The

Contractor shall develop and process necessary Assessment and Authorization packages IAW AFI 17‐101

Air Force Certification and Accreditation Process (AFCAP), DoDI 8500.01 Cybersecurity, 8510.01 Risk

Management Framework (RMF) for DoD Information Technology (IT). The result of this action should result in the issuance of an ATO by the IS appointed Authorizing Official (AO). Firmware shall be current and approved IAW AF EPL. The IS shall meet all required Information Assurance Controls.

4 Site Preparation Guidelines Unless otherwise identified in Demarcation, the contractor shall be responsible for all necessary site preparation/development. Site preparation includes all site work, building modifications, electrical wiring, AC Power, and grounding systems.

4.1 General Guidelines

The contractor shall meet the following minimum Government guidelines:

Connect the new equipment to the existing AC electrical service without disconnecting existing loads. If sufficient spare capacity is not available, the contractor shall install sufficient AC electrical receptacles and circuits from an existing electrical panel to support the equipment.

All equipment installed shall be supported by the building’s emergency generator and UPS or a UPS of sufficient size to maintain operation while the building generator starts shall be provided.

4.2 Grounding Guidelines

If required by the proposed technical solution, the contractor shall meet the following minimum Government guidelines: In the event of a conflict between the following and National/State code, National/State code shall supersede.

The contractor shall ensure that all equipment is electrically bonded, grounded, and protected in accordance with the National Electric Code.

The contractor shall provide all grounding and lightning protection equipment, including surge arrestors, to comply with the requirements of all equipment being installed and connected as part of the system.

Building conductors shall be used to bond the various pieces of equipment, conduit, trays, etc.

together.

All control center and dispatch equipment supplied with a ground connection point, metallic equipment mounting rails or brackets and metallic parts of dispatch furniture shall be suitably bonded to the main ground bar or ground bus conductor.

A single point ground system shall be used, whenever possible, and approved by the site manager, on all equipment installed as part of the system. The single point ground system installed within equipment shelters or buildings shall be connected to the exterior building/tower ground system.

Each waveguide installed on the tower shall be grounded at three points. At the base of the antenna, at the transition from the tower to the ice/cable bridge and at the entrance to the facility.

The grounding system installation shall be in accordance with the following guidelines:

Each single row of equipment shall have a separate ground bus consisting of an American Wire Gauge (AWG) #2 or larger copper conductor.

Each bus shall be connected to the single point ground window.

A single cabinet, rack, or enclosure and any associated transmission line or circuit protection devices shall have a ground conductor bonding all components to a single point ground near the equipment installation.

The antenna support structure/tower must be bonded to the external ground system using an exothermic weld, if permitted by the tower manufacturer.

All grounding conductors that compose the external ground system shall be connected using exothermic welding and where connected to grounding rods shall be a minimum of 1/0.

Transmission lines shall be grounded with proper sized ground kits connected to the tower ground and building entry bus.

The external ground system shall provide a ground resistance of 5 ohms or less. If the soil conditions at a site are such that the contractor cannot reasonably design a ground system that meets this requirement, the contractor shall design a ground system that meets the best possible value as agreed to by the Government.

New grounding systems shall be installed in accordance with the National Electrical Code and applicable best industry practices and standards. All external ground rings, copper ground rods, chemical ground rods, and interconnecting copper conductors must be buried to a minimum depth of 30 inches, or 6 inches below the freeze line for the area, whichever is greater.

4.3 Lightning Protection Guidelines

If required by the proposed technical solution, the contractor shall meet the following minimum Government guidelines:

Lightning protection shall be provided for the shelter, tower and all significant metallic structures IAW the NFPA 780 Standard for Installation of Lightning Protection Devices.

4.4 Uninterruptible Power Supply (UPS) Guidelines

Where applicable, RF site UPS shall be sized for 30 minutes of operation

UPS shall include a maintenance bypass (if required by electrical code)

UPS shall be expandable through the use of expansion battery packs.

Dispatch location (back room equipment) shall be provided with 30‐minute UPS if the facility does not have a UPS. (contractor is responsible for determining existing UPS suitability)

4.5 Cable Trays Guidelines

If required by the proposed technical solution, the contractor shall meet the following minimum Government guidelines: Some equipment rooms are congested and do not allow for these minimums.

The contractor shall notify the government of such locations.

The contractor shall install 24‐inch wide cable trays or ladder over the rows of proposed equipment racks. Cable tray/ladders shall be:

o Installed a minimum of 6‐inches above the equipment racks.

o Bonded together and tied to ground system.

4.6 Heating, Ventilating and Air Conditioning (HVAC) Guidelines The government will provide HVAC to meet the required BTU load of the equipment. Contractor shall provide expected BTU load.

4.7 Auxiliary Power System Guidelines

For each site, expected equipment load shall be provided to government.

4.8 Physical Security Guidelines

Offerors shall utilize existing physical security features.

4.9 Surge Protection Guidelines

If required by the proposed technical solution, the contractor shall provide surge protection from incoming electrical transients on all AC power lines and telephone/data lines.

5 Implementation Services

5.1 Schedule

The offeror shall provide a detailed working schedule for accomplishing the requirements of this SOW in MS Project format which includes all Government activities, e.g. IA activities and network connectivity.

The schedule shall identify all critical milestones and deliverables for the final design, integration, installation, and testing of the system. The milestones and schedule shall be described with reference to days after receipt of notice to proceed. (CDRL A002)

5.2 Program Management

Program Management shall be provided throughout the design and implementation of the system

5.3 System Engineering

Systems engineering services shall be provided from the preliminary system design through the completion of system implementation, security evaluation, and functional testing. As a minimum, system engineering services shall include the following:

System design

System architecture development

Baseline System Configuration

Frequency analysis and planning

Coverage analysis

Traffic (loading) analysis

Fleet map/talk group development and Database Entry

Console programming/migration of previous configurations

Implementation support (design synthesis)

Acceptance testing, to include coverage testing

All IA activities necessary to meet DoD and Air Force requirements and comply with DIACAP as a part of the LMR system implementation

Final (as‐built) system documentation

5.4 Project Status Review (PSR) Meetings

The contractor shall participate in weekly (or as decided by the IPT) PSR meetings. The contractor shall include any existing action items for both the Government and contractor. (CDRL A004)

5.5 Transportation of System Equipment

The Government will provide a “Ship‐to” address and temporary storage/staging area. The contractor shall be responsible for inventory and reconciliation of all shipments, which will be coordinated with and verified by a Government representative. The contractor shall transport all equipment from the temporary storage area to the final destination.

5.6 Site Access Information and Visitor Control Requirements

The contractor shall coordinate all site visits through the LMR Project Leader. The contractor shall provide all necessary site visit information at least 10 days prior to any site visit by any contractor or subcontractor. The contractor shall coordinate all deliveries with the LMR Project Leader at least 10 days prior to delivery and provide any site visit information required for the delivery. This will ensure visit clearances can be obtained from the local Security/Visitor Control Office.

MHAFB will provide escorts as necessary at all installations and locations. Contractor shall provide personal information as requested to facilitate clearance onto military installations.

5.7 Optimization

The contractor shall optimize all new RF equipment after system installation is completed to ensure optimal performance and reliability. The contractor shall time and synchronize the network among the dispatch console(s), the management terminal(s), and the RF site(s) to ensure maximum system reliability.

5.8 Quality Assurance (QA), Testing, and Burn‐In

5.8.1 Quality Assurance

The contractor shall provide a Quality Assurance Evaluator (QAE) for the entire life of the project. The QAE shall assist the government representative in performing random spot checks and in performing the system acceptance tests. The QAE shall be responsible for identifying system and outside plant deficiencies and/or discrepancies throughout the life of the project. A Status Report will be submitted, indicating project progress/statuses and listings any deficiencies/discrepancies found and actions to correct them. (CDRL A003)

5.8.2 Factory Acceptance Test

Since this is an addition to an existing system a FAT is not anticipated as there would be no core with which to test the majority of system features. The Contractor may conduct a Factory Acceptance Test at their discretion.

5.8.3 System Acceptance Test

The Contractor shall provide the Acceptance Test Plan for the system. (CDRL A006)

System Acceptance Test shall include:

Operational testing of the features and functions described in the SOW system alarming, monitoring, and fault management as it pertains to the ability to diagnose, monitor, and maintain the LMR system all equipment installed by the prime contractor or its sub‐contractors failover testing of generator and UPS

The contractor shall ensure that the entire system is completely tested 10 days prior to system cutover.

The contractor shall have 15 days after completion of the System Acceptance Testing to research, develop, and document the resolution of all discrepancies. The contractor shall provide in writing a detailed explanation to the Government engineer/LMR Project Leader/QA representative of how the discrepancy will be resolved including any changes to the radio programming or the system data bases.

(CDRL A003) Upon direction of the LMR Project Leader, the contractor shall implement the proposed resolution and perform the portion of the System Acceptance Test that previously failed.

5.8.4 RF Coverage Test:

Coverage testing is intended to verify coverage prediction done under 3.2.1 Coverage section of this document and to ensure installed radios are functioning properly. Due to the complexity of this effort, RF coverage testing is expected to test functionality of UHF/VHF radios installed against Government provided test flights. Basic LMR coverage tests shall consist of proof that radio patching functions as designed. (CDRL A006)

5.8.5 System Burn‐in:

The Government reserves the right to refuse start of 30‐day burn‐in until all discrepancies have been resolved to the satisfaction of the Government. The Government will review all test results and prepare the official list of discrepancies, if any. The contractor shall support this effort by submitting his/her own list of discrepancies based on discrepancies detected/identified during testing and/or inspections conducted by either the contractor or the Government QA representative.

The contractor shall perform a 30‐day Operational Test of the system. The 30‐day equipment burn‐in will not start until the system has successfully passed all of the tests in the system ATP, all QA discrepancies have been resolved, the IA effort is complete, and Government approval has been provided from the Project Leader. If any major failure occurs during the 30‐day burn‐in, the test shall be terminated, corrective action shall be taken and approved, and the entire 30 days shall be restarted. If any minor failure occurs during the 30‐day test period, the testing period may resume after resolution of the problem. The contractor shall document in detail any discrepancies that occur during testing. (CDRL A005)

5.8.5.1 System Burn‐in Tracking Reports Support:

The contractor shall support the site in tracking any problems during the System Burn‐in. As a minimum, the contractor’s responsibilities shall include, answering called‐in trouble calls, creating trouble tickets and logs, providing tracking reports for active and closed tickets, answering questions, and correcting any system deficiencies that are identified. The Project Leader will prioritize the trouble calls.

5.9 System Cutover

The contractor shall develop a cutover plan in coordination with 58 SOW management personnel. The plan shall provide for an orderly, cost effective transition to the new system with minimal disruptions to operations and end users. Soft cutover means that the existing system shall be operational until the new system is completely cutover. (CDRL A006)

5.10 As‐Built Documentation

The Contractor shall provide full documentation on the installed system. All drawings shall be provided in Microsoft Visio and PDF format. (CDRL A001)

Note: As built documentation shall contain an Excel document containing the following information for all end items with a price of $500 or greater.

1. Location/Building

2. Serial Number

3. Manufacturer Name

4. Model Number

5. Model Description

6. Acquisition Cost

5.11 System Acceptance

Formal system acceptance shall be granted after completion of the acceptance test and a successful 30‐ day equipment burn‐in period. Final acceptance shall require at a minimum:

Completion of all facility work, system, component, hardware and software delivery, installation, testing, optimization, phased integration, as built documentation, and training.

Acceptance of system facilities, individual systems, and equipment by Communications Squadron and management personnel. Correction of any operational, performance, or workmanship defects shall be at the sole expense of the contractor.

Successful completion of System Acceptance Testing. Failure of any tests during the system acceptance test will delay the start of the 30‐day burn‐in period until all tests have passed.

Successful completion of the RF Coverage testing. Failure of the system to provide the required coverage will delay the start of the 30‐day burn‐in period until any RF coverage issues are resolved to the satisfaction of the Government.

Successful completion of the IA certification.

Successful completion of the 30‐day burn‐in period.

Completion of system and maintenance training.

6 LOGISTICS REQUIREMENTS

6.1 Spares

The contractor shall propose all necessary spares for their system.

6.2 Warranty

The contractor shall provide a one‐year manufacturer’s standard commercial warranty in conformance to NetCents contact. The warranty shall commence at the date of final system acceptance.

6.3 Disposition of removed equipment:

All equipment removed under this contract shall be transported back to Building 20420 and. The vendor shall coordinate with 58 SOW to schedule time and location for offloading of removed equipment.

7 DELIVERABLE REQUIREMENTS

All deliverables are subject to Government acceptance and approval. They shall meet professional standards and the requirements set forth in this Task Order. All deliverables shall be produced using recommended software tools/versions as accepted by the Government. The Contractor shall submit the following deliverables:

CDRL Data Item Title A001 Communication-Computer Systems

Installation Records(CSIRs) A002 Work Schedule A003 Status Report A004 Meeting Minutes

A006 Test Plan/Report

ANNEX A (APCO P25 Standards) TIA/EIA TSB 102‐A, APCO Project 25 System and Standards Definition, January 2003

EIA TSB 102.AAAB, Revision A, APCO PROJECT 25 – Security Services Overview, January 26, 2005

TIA/EIA‐102.AAAD, Revision 02, Project 25 Block Encryption Protocol, July 2002

TIA‐102.AABA, Revision A, APCO Project 25 Trunking Overview, June 2004

TIA‐102.AABB, Revision A, APCO Project 25 Trunking Control Channel Formats, July 2005

TIA‐102.AABC, Revision B, Project 25 Trunking Control Channel Messages, January 12, 2005

TIA/EIA TSB 102.AABD, Project 25 Trunking Procedures, October 1997

TIA‐102.AABF, Revision A, APCO Project 25 Link Control Word Formats and Messages, December 16, 2004

TIA/EIA TSB 102.AABG, APCO Project 25 Conventional Control Messages, July 1996

TIA‐102.AACA, Revision 1, Project 25 Over‐The‐Air‐Rekeying (OTAR) Protocol Addendum 2, March 2003

TIA/EIA‐102.AACB, Project 25 Over‐The‐Air‐Rekeying (OTAR) Operational Description, November 2002

TIA/EIA‐102.AACC, Conformance Test for the Project 25 Over‐The‐Air‐Rekeying (OTAR) Protocol, July 2002

TIA‐102.AACD, Revision 5, Project 25 Digital Land Mobile Radio – Key Fill Device (KFD) Interface Protocol, February 2005

TIA‐102.BAAA, Revision A, Project 25 Frequency Division Multiple Access (FDMA) Common Air Interface, September 2003

TIA‐102.BAAB, Revision B, Project 25 Common Air Interface Conformance Test, March 2005

TIA‐102.BAAC, Revision A, Project 25 Common Air Interface Reserved Values, December 2003

TSB‐102.BAAD, Revision 3, APCO Project 25 Common Air Interface Operational Description for Conventional Channels, December 2003

TIA‐102.BABA, Revision 3, Project 25 Vocoder Description, December 18, 2003

TIA/EIA‐102.BABB, Project 25 Vocoder Mean Opinion Score Conformance Test, May 1999

TIA/EIA‐102.BABC, Project 25 Vocoder Reference Test, April 1999

TIA TSB‐102.BABD, APCO Project 25 Vocoder Selection Process, May 1996

TIA TSB 102.BACA, Project 25 – Inter‐RF Subsystem Interface Messages and Procedures for Voice Services, August 2006

TIA TSB‐102.BACC, Revision A, Inter‐RF Subsystem Interface Overview, December 2003

TIA‐102.BAEA, Revision A, Project 25 Data Overview, June 2004

TIA‐102.BAEB, Revision A, Project 25 Packet Data Specification, March 2005

TIA/EIA‐102.BAEC, Project 25 Circuit Data Specification, June 2000

TIA‐102.BAEE, Revision A, Project 25 Radio Control Protocol, September 2004

TSB‐102.BAFA, Revision A, Project 25 Network Management Interface Overview, July 1999

TIA‐102.CAAA, Revision B, Digital Continuous 4 Frequency Modulation, Constant Amplitude (C4FM) / Compatible Quadrature Phase Shift Keying (6.25 KHz bandwidth (CQPSK) Transceiver Measurement Methods, December 2004

TIA‐102.CAAB, Revision B, Digital C4FM/CQPSK Transceiver Performance Recommendations, July 2004

TIA/EIA TSB 102.CAAC, Project 25 Mobile Push‐to‐Talk and Audio Interface – Definitions and Methods of Measurements, September 2002

TIA/EIA TSB 102.CABA, Project 25 Interoperability Test Procedures Conventional Voice Equipment, February 2002

TIA‐102.CABB, Interoperability Test Procedures OTAR, August 2003

TIA‐102.CABC, Interoperability Testing for Voice Operation in Trunked Systems, September 2006

ANNEX B (Site Preparation Standards) American National Standards Institute (ANSI/EIA/TIA‐222, Structural Standards for Steel

Antenna Towers & Antenna Supporting Structures, June 1996

National Fire Protection Association (NFPA) 780, Standard for Installation of Lightning Protection Devices, 5 August 2004

NFPA 70 National Electrical Code (NEC) 2005

FAA Advisory Circular 70/7460‐2k, Proposed Construction or Alteration of Objects that May Affect the Navigable Airspace, 1 March 2000

FAA Advisory Circular 70/7460‐1K, Obstruction Marking and Lighting, 1 August 2000

FAA Advisory Circular150/5345‐43F, Specification for Obstruction Lighting Equipment, 12 September 2006

Motorola R56 Standard rev2005, “Standards and Guidelines for Communications Sites”

ANNEX C (Information Assurance policy and documents) DoD Directive 5000.1, The Defense Acquisition System (ref (a), (j), and (k)).

Department of Defense Directive (DoDD) 8500.1, Information Assurance (IA).

Department of Defense Instruction (DoDI) 8500.2, Information Assurance (IA) Implementation.

DOD 8510.01‐M Department of Defense Information Assurance Certification and Accreditation

Process (DIACAP)

DOD 8570 IA workforce

10 U.S.C. Section 2224, Defense Information Assurance Program.

Office of Management and Budget Circular A‐130, Appendix III, Management of Federal

Information Resources.

AFI 33‐202V1, Network and Computer Security, 03 February 2006.

AFI 33‐210, Air Force Certification and Accreditation Process (AFCAP), 23 December 2008

Database STIG, Version 7, Release 2, 30 November 2005.

Network Infrastructure STIG, Version 6, Release 4, 16 December 2005.

UNIX Security STIG, Version 4, Release 4, 15 September 2003.

WEB Server STIG, Version 5, Release 1, 29 October 2004.

Hours of Operation/Scheduled Events Normal hours of operation 07:30 – 16:30 M‐F

Acronyms

AES Advanced Encryption Standard AFB Air Force Base AO Authorizing Official APCO Association of Public-Safety Communications Officials ARO After Receipt of Order ATO Authority To Operate ATS Automatic Transfer Switch CCGW Conventional Channel Gateway CE Civil Engineering CIO Chief Information Officer DISN Defense Information Systems Network DoDD Department of Defense Directive DoDI Department of Defense Instruction EFI&T Engineer, Furnish, Install, and Test FCC Federal Communications Corporation GFE Government Furnished Equipment GoS Grade of Service IA Information Assurance IAVA Information Assurance Vulnerability Alert IP Internet Protocol ISM Installation Spectrum Manager IT Information Technology LMR Land Mobile Radio NIST National Institute of Standards and Technology NTIA National Telecommunications and Information Administration OEM Original Equipment Manufacturer P25 Project 25 PSR Program Status Review RCU Radio Control Unit RF Radio Frequency RMF Risk Management Framework RX Receive SMT System Manager Terminal TIA Telecommunications Industry Association TX Transmit UHF Ultra High Frequency UPS Uninterruptable Power Supply VHF Very High Frequency VLAN Virtual Local Area Network VPN Virtual Private Network

Notional System Drawings These drawings are provided for general reference only. They are not to be used for ordering or connecting equipment, and are provided to assist in understanding system layout.