149 FW_CP_SOW.pdf

Statement of Work

STATEMENT OF WORK (SOW)

for

149th Fighter Wing at Lackland JBSA, TX

05 Aug 2020

Table of Contents

1.0 SCOPE OF WORK

2.0 SPECIFIC TASKS

2.1 PROJECT MANAGEMENT

2.2 FURNISH EQUIPMENT

2.3 REQUIREMENTS

2.4 SHIPMENT

2.5 RESTORATION

2.6 CONSOLE SYSTEM INSTALLATION

2.7 SYSTEM TESTING

2.8 SYSTEM ACCEPTANCE

2.9 TRAINING

2.10 WARRANTY

3.0 DELIVERABLES

3.1. DOCUMENTS

3.2. SYSTEM CONFIGURATION

4.0 GENERAL INFORMATION

4.1. SITE INFORMATION

4.2. SAFETY

4.3 PERSONNEL

4.4 NON-DISCLOSURE

4.5 SECURITY

5.0 APPENDIX

5.1 SOW ABBREVIATIONS

Authority:

AFMAN 10-207:

Paragraph 5.2.6. The Command Post must have consoles configured with all the equipment required by controllers to perform Command Post duties (T-3). The consoles should be side-by-side. The consoles should provide for rapid and assured selection of radios, telephone systems, direct lines, remote controls, and voice recording capability. They should also provide for ground-to-air, radio-to-wire phone patch, and conference calls. The console should provide sufficient controller workspace or desktop area. Each console area must be fitted with a duress capability at each console position, terminating at the Local

Monitoring Facility/Remote Monitoring Facility, or Base Defense Operations Center (T-2).

Paragraph 5.3. Command and Control Systems and Applications. The following is a list of common

Command and Control systems and applications Command Posts use to carry out their Command and

Control functions but is not all inclusive. Command Post consoles will be Joint Interoperability Test

Command certified IAW DoDI 8330.01 and the Joint Interoperability Test Command Interoperability

Process Guide (T-2).

Paragraph 5.3.4. Command Posts will have Telephones or Communications Consoles (T-2). The telephones or communication consoles must meet requirements outlined in DoDI 8100.04., DoD Unified

Capabilities (T-0).

1.0 SCOPE OF WORK

The 149 Fighter Wing Command Post (149 FW/CP) requires the installation of console system as defined in AFMAN 10-207 (see details above). The 149 FW/CP is the nucleus of operations, for the 149th Fighter

Wing, and contains the facilities and communication equipment to conduct emergency actions, operational reporting, mission management and routine command and control functions. The current unsynchronized systems do not meet AFMAN 10-207 requirements, are antiquated, and are not conducive to rapid response of emergency operations. The 149 FW/CP communication equipment is generally a time consuming manual process with separate non-integrated stove-pipe systems without conferencing capabilities. When the main phone line is in use, the Command Post is unreachable via voice. The Command Post must have two (2) Desktop console positions. All consoles must provide immediate access to all communications systems (land-line as well as LMR, UHF/VHF and additional radio networks as needed).

2.0 SPECIFIC TASKS

2.1 PROJECT MANAGEMENT

2.1.1 The contractor shall plan and manage daily operations and activities associated with this requirement to ensure the necessary processes and activities are completed. The contractor shall employ management tools and methods to assure control of schedule and performance. The contractor shall conduct, support and participate in program management and technical reviews, meetings, and conferences to ensure effective and efficient contract execution.

2.1.2 Within two business days of contract award, the contractor shall initiate work by meeting with 149th

Command Post leadership either in person or through telecommunications to review all planned efforts in support of this requirement. The contractor shall support and respond to site personnel discussions and questions on any information regarding this project installation.

2.1.3 The contractor shall provide the name of the point of contact (POC) responsible for overseeing the project to the Contracting Officer’s Representative (COR) within five business days of award. The contractor POC shall contact the COR within five business days of award and shall be the single point of contact from award to site acceptance.

2.1.4 Contractor shall provide a Preliminary Schedule (Contract Data Requirement List [CDRL A001]) to the COR within 21 days of award with a Final Schedule including milestones (CDRL A002) required

21 days prior to any on-site work. The contractor shall meet the milestones that were submitted in the

Final Schedule. Actual or projected failure to meet contract requirement or milestones shall be reported to the COR orally as soon as the information is available to allow for schedule changes to be coordinated to ensure no mission impact to the affected unit. Contractor proposals shall be orally reported to the COR as soon as the information is available. Realistic corrective action shall also be provided for any reported actual or projected failure.

2.1.5 No later than 10 business days prior to arrival on-site, the contractor shall coordinate with the COR and provide the name of a site POC to represent the contractor at each air base.

2.1.6 The contractor shall provide a site kick-off meeting, virtual or in person, to mark the initiation of the work at that particular place of performance. The contractor shall review the overall project, goals, timelines, base support and any other pertinent information related to this contract with the COR and site personnel.

2.1.7 The contractor POC shall direct the project implementation to ensure the installation; testing and in-service dates are coordinated with each unit during site visit or teleconference.

2.1.8 The contractor shall not accomplish work outside the scope of this contract nor deviate from technical orders, manufacturer recommendations, Air Force Instructions or National Consensus Standards at the government facility, nor shall the contractor utilize in other work, any supplies or materials acquired under this contract.

2.1.9 The contractor shall provide a Project Support Agreement (PSA) after site-survey (CDRL A010) to identify all allied support (i.e., items required by host base prior to installation by contractor) required by the government to support the installation, configuration, and operational testing of the new system.

Allied support consists of items such as fiber/copper connections, equipment rack space, power requirements for equipment, hotlines required, and any other support required by the contractor to complete the installation of the system. The PSA will be coordinated and signed by contractor and unit

POC prior to final installation schedule being established. All allied support items shall be completed prior to the beginning of installation. Any open allied support items shall be resolved prior to team travel or installation date.

2.2 FURNISH EQUIPMENT TO SPECIFICATIONS

2.2.1. The contractor shall meet or exceed industry and Air Force specifications with the appropriate pass through licenses. The contractor shall be responsible for the provisioning of a completely functional command post console system with required programming, hardware, software, Right-To-Use (RTU) licenses, ancillary equipment, parts and material for all identified requirements.

2.3 CONSOLE REQUIREMENTS

2.3.1. The contractor shall install a console system and shall provide all necessary hardware, software and services required to meet the latest applicable Joint Interoperability Test Command (JITC) certified release.

2.3.2. The console system configuration shall have the following basic capabilities as well as the other requirements:

2.3.2.1 Provide touch screen panel to facilitate operations and unclassified telephone system with one touch and hands free operation

2.3.2.2 Provide hands free headsets (equipped with belt grip PTT) (1 per console)

2.3.2.3 Provide two Desktop speakers integrated into each console workstation with visual indicators for monitoring select radio and other channels and circuits. These speakers will be able to select UHF, VHF, LMR or other radios. They will also be able to select a phone line to monitor a phone call.

2.3.2.4 Provide instant telephone conferencing with landlines, cell phones, LMR, UHF, VHF radio interfaces.

2.3.2.5 Integrate Primary alert (crash) net capability and Secondary alert (crash) net capability.

2.3.2.6 Provide the ability to press one hotline button and connect at least 16 members into a conference call.

2.3.2.7 Provide programmable macro keys to customize user needs.

2.3.2.8 Provide Voice over IP capability.

2.3.2.9 Ability to transfer to/from admin phones to consoles.

2.3.2.10 Call queuing that allows higher designated calls (via phone number identification in the electronic phone directory) to be routed ahead of others.

2.3.2.11 Electronic Phone Directory (EPD) capable of up to 15,000 listings.

2.3.2.12 Provide voice recording capabilities of all radio and voice communications as identified by the site POC.

2.3.2.13 Prompt incoming calls that they are in a holding cue (if their call has not been answered in a predetermined number of rings) waiting for the next available controller.

2.3.2.14 Connect multiple systems for Virtual Private Networks.

2.3.2.15 Voice mail and unified messaging capable.

2.3.2.16 Ability to integrate with Integrated Nofitication Warning System and Pulic

Annoucement Systems.

2.3.4. The contractor shall configure host equipment with reliability to ensure best possible operation capability. The contractor shall connect the system to the Defense Switched Network (DSN).

2.4 SHIPMENT OF EQUIPMENT

2.4.1. The contractor may use base storage for the execution of this contract if available; however, the contractor is responsible for the staging and deployment of the material and equipment. No equipment shall be shipped to the base without government authorization. The contractor must obtain authorization and a shipment address from the COR. Contractor must coordinate all installation and shipment of equipment with the unit POC.

2.5 RESTORATION

2.5.1. The contractor shall ensure that all facilities where work is performed are restored and returned to their original condition. Any damage or changes to existing facilities shall be repaired and shall include documentation of any alterations to the premises [Property Restoration Documentation (CDRL A004)].

The Property Restoration Documentation shall be submitted to the COR if required for review three business days prior to the restoration. The contractor shall restore any roads, grounds, and buildings disturbed during this project to a state equivalent to the conditions existing prior to installation of project.

The contractor shall follow base grounds restoration policy and all applicable regulations for detailed grounds restoration requirements.

2.6 CONSOLE SYSTEM INSTALLATION

2.6.1. The contractor shall install console equipment on existing furniture and mounted (touch screens desk top or swivel mounted) based on user requirements.

2.6.2. The contractor shall provide all the required hardware and software to implement the installation of voice and radio components required for full voice and radio integration into the console system.

2.7 SYSTEM TESTING

2.7.1. The Contractor shall identify and provide approved industry and OEM procedures that outline, sequence, and indicate qualifications for system acceptance, i.e. 24-hour burn-in, etc. The test procedures shall be provided to unit POC, Plan and Implementation work center, and COR for review and approval prior to the beginning of any testing. These test procedures will be used in the final testing and results provided as the final test results (CDRL A005). Final test are completed prior to final acceptance of system. The testing shall ensure the system is fully functional and meets the intended use per this SOW.

2.7.2. The contractor shall notify the COR as to the dates and times of the entire testing process in advance of the testing. Equipment testing shall be per industry and OEM installation testing standards.

2.7.3. The contractor shall furnish Final Test Results on a contractor-provided test completion form to the

COR for review seven business days prior to site acceptance. The contractor shall ensure that the final test results indicate that the system passed and the system is fully operational. Any test failure will result in contractor fixing issue and retesting. All tests must be acceptable and signed as complete by unit POC, the

Communications Quality Assurance Representative, COR, and contractor.

2.7.4. The contractor shall perform all testing as specified in the contractor provided and Government approved (which approval shall not be unreasonably withheld or delayed) test plan to verify that the system meets the minimum feature requirements specified therein. The contractor has the responsibility to test the installation prior to cutover. The Government may witness all testing. The contractor shall document these test results. The contractor shall provide copies of the test results to the Government upon the Government’s request. All hardware and software procured under this SOW shall be tested as set forth in the test plan described above.

2.8. SYSTEM ACCEPTANCE

2.8.1. Upon the contractor’s successful completion of testing in accordance with Section 2.7, above, the contractor shall cutover the installation. Upon successful cutover and acceptance of all testing, the

Government will provide acceptance. At that time, the Government will finalize all applicable acceptance documentation required to close out the project.

2.8.2. Site acceptance shall be considered after the test acceptance of the system and the system is in operation for a period of seven days without a major failure (25% of system capability). The contractor shall submit to the site POC, COR, and Plan and Imlementation work center a DD250 form Material

Inspection and Receiving Report as the Site Acceptance Form. The DD250 will only be signed by a government representative after the 7 day period for site acceptance. Only the COR will authorize site acceptance of the installation.

2.8.3. The Site Acceptance Form (CDRL A009) shall be submitted as an attachment to the final invoice via WAWF with a shipment number ending with a “Z.” If the site acceptance form is not attached, the invoice shall be rejected.

2.9. TRAINING

2.9.1. The contractor shall provide training that is tailored to the specific systems integrated and installed for this SOW. The contractor shall train government personnel on site to demonstrate the ability to operate and maintain the system without contractor assistance. The contractor shall submit training syllabus and lesson plans after award. Training shall be conducted based on unit personnel availability once the system is operational and prior to system acceptance. The contractor shall provide hands-on training for up to 15 personnel. Training classes shall be provided as listed below.

2.9.2. The contractor shall conduct Initial Training for new users to provide hands-on familiarization with basic system functions to meet their operational requirements.

2.9.3. The contractor shall conduct System Administrators (SAs) training with familiarization on the

Dispatch/System Manager Application giving SAs the ability to perform basic Moves/Adds/Changes

(MACs). Number of students will be provided by the unit POC.

2.9.4. The contractor shall provide Level 1 (system administrator training) system customer training to ensure that telephone/network/system technicians have the necessary skills to perform Level 1 maintenance and system MACs. Specific number of students will be provided by the unit POC. This training can be offered to host base communications squadron personnel if needed.

2.9.5. The contractor shall provide training related to use of the conference system, voice recorder and radio interface equipment. Specific number of students will be provided by the unit POC.

2.9.6. The contractor shall ensure that training materials and references (CRDL A006) are made available for up to 15 personnel for in-class training. As part of the onsite training the contractor shall also deliver a

CD containing all training materials to the unit POC in order to allow for continued training after system acceptance.

2.10. WARRANTY

2.10.1. The contractor shall provide warranty documentation (CDRL A008) to the COR prior to site acceptance and shall begin upon site acceptance (not test acceptance) and initiated with the signing of the

Site Acceptance Form (CDRL A009).

2.10.2. The contractor’s warranty shall cover services for workmanship deficiencies and equipment provided as described and in accordance with the contract. The contractor shall provide a full/unlimited commercial one‐year warranty for all contractor provided hardware, software, materials, and workmanship. The warranty shall include emergency technical assistance as required including 24/7 remote dial‐in and on‐site responses as appropriate for system failures. Warranty shall cover at a minimum the HiPath Server and Dispatch Manager to minimize risk. On-site spares will be provided to minimize the risk of replaceable items.

2.10.3. The contractor shall provide as an option an additional 1-year warranty (2-year total).

2.10.4. The contractor shall provide written procedures and required information (CDRL A008) for warranty services prior to completion of the Site Acceptance Form (CDRL A009). This information shall include written confirmation of the warranty period, phone numbers and contact information. It shall detail procedures for technical support, troubleshooting assistance, and replacement of faulty equipment.

2.10.5. The contractor shall provide the OEM's recommended critical spare parts for equipment and systems provided under this effort.

2.11. MAINTENANCE AND SUPPORT

2.11.1. A catastrophic failure means loss of the ability to initiate or answer calls on 25 percent or more of the circuits. If a catastrophic failure occurs, the Contractor shall perform a service call, if contractor deems necessary or if the CO requires that the contractor perform a service call. The contractor’s personnel shall use all commercially reasonable efforts to begin diagnosis and repair efforts within two

(2) hours of the contractor’s receipt of the notification of the failure and immediately commence efforts to diagnose and repair the problem. The contractor shall continue to work on the problem until full system capabilities are restored.

2.11.2. A major failure means the loss of supervision, conference ability, or ability to initiate or answer calls on 10 percent or more of the circuits. If a major failure occurs, the contractor shall perform a service call, if contractor deems necessary or if the CO requires that the contractor perform a service call. The contractor’s personnel shall use all commercially reasonable efforts to begin diagnosis and repair efforts within three (3) hours of the contractor’s receipt of the notification during the contractor’s normal business hours. In the event of a notification during contractor’s non-business hours, the contractor’s personnel shall use all commercially reasonable efforts to begin to repair the problem at the beginning of the contractor’s next business day during the contractor’s normal business hours. The contractor shall use commercially reasonable efforts to restore the service within forty-eight (48) business hours of the contractor’s initial notification.

2.11.3. A minor failure means any abnormal hardware or software error that degrades service to less than the desired performance, but which does not constitute a major or catastrophic failure. If a minor failure occurs and the customer notifies the contractor of such minor failure, the contractor shall begin repair efforts as soon as commercially reasonable. The contractor shall use commercially reasonable efforts to repair minor failures within three (3) business days after the contractor’s receipt of notification of the minor failure.

3.0 DELIVERABLES

3.1 DOCUMENTS

3.1.1. The contractor shall provide deliverables via electronic as well as printed means to the COR. The contractor shall deliver all products and reports in the current version of MS Word, MS Project, Power

Point, MS Excel, or MS ACCESS. All deliverables shall be identified by 1) CDRL number, 2) SOW task number, and 3) deliverable title.

CDRL/TITLE

A001: Preliminary Schedule

A002: Final Schedule

A004: Property Restoration Document If Required

A005: Final Test Results

A006: Training Materials and References

A007: As-Built Documentation

A008: Warranty and Procedures

A009: Site Acceptance Form

A010: Project Support Agreement

3.2 SYSTEM CONFIGURATION

3.2.1. After completion of work, the contractor shall provide As-Built documentation (CDRL A007), which shall also include Configuration Management Information. The As-Built documentation shall be provided to COR after completion of work. The As-Built documentation must be in Microsoft Standard format. As-Built documentation includes drawings and diagrams of the console identifying specific cards in a chassis/shelf. It shall also include power drawings and specifications, as well as floor plans and engineering specifications generated in support of the installation of the system. Equipment listings with serial/model numbers and manufacturer specifications shall also be included in the As-Built documentation.

4.0 GENERAL INFORMATION

4.1 SITE INFORMATION

4.1.1. The contractor shall abide by the local host base rules and first request a gate pass, then acquire it prior to arrival for official work. The contractor shall ensure that the proper equipment needed to perform has been cleared through the host base authorities to be allowed on the installation. The contractor shall contact the Security Forces Squadron to receive assistance to acquire base access.

4.2 SAFETY

4.2.1. The contractor shall take appropriate measures to protect personnel, property, and materials from mishaps. The contractor shall ensure that 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 contract. Compliance with AFI 91-202, Air Force Mishap

Prevention Program, and all applicable safety-related requirements identified is mandatory.

4.3 PERSONNEL

4.3.1 All personnel performing work under this contract shall be fully trained (can be local company representatives) to accomplish all tasks associated with this SOW.

4.3.2 The contractor shall ensure that personnel performing the installations are U.S. citizens and have no criminal record. If access is denied, the contractor shall provide appropriately cleared personnel for access. If the Contracting Officer (CO) finds it to be in the best interest of the government he/she may at any time during the performance of this contract, order the contractors to remove any contractor personnel from further performance under this contract for unethical conduct, security reasons, and/or for violation of installation regulations.

4.3.2.1 In the event that it becomes necessary to replace any contractor personnel for any of the above reasons the contractor shall bear all costs associated with such removal, including costs for the replacement of any personnel so removed. These costs will not be chargeable to the government.

4.4 NON-DISCLOSURE - RELEASE OF INFORMATION

4.4.1. In performance of this contract, the contractor may obtain access to sensitive, nonpublic information. The contractor agrees (a) to use and protect such information from unauthorized disclosure in accordance with the FAR; (b) to use and disclose such information only for the purpose of performing this contract and to not use or disclose such information for any personal or commercial purpose; (c) to obtain permission of the government COR before disclosing/discussing such information with a third party; (d) to return, upon government request, any non-public, sensitive information no longer required for contractor performance; and (e) to advise the government COR of any unauthorized release of such information. Upon request, the contractor shall have its employees assigned to this contract execute a non-disclosure agreement for delivery to the government.

4.5 SECURITY REQUIREMENTS

4.5.1 At this time, this SOW does not require access to classified information. As such, a security clearance is not required for this effort; the base shall provide escorts as required.

4.5.2 The contractor shall ensure that those employees requiring access to the Air Bases have the proper identification credentials prior to entering the Air Bases. The contractor shall ensure company identification badges are worn at all times that identify the individual, company name, and clearly indicate the wearer is a contractor.

5.0 APPENDIX

5.1 SOW Abbreviations

CDRL -- Contract Data Requirements List

COR -- Contracting Officers Representative

CP -- Command Post

FW – Fighter Wing

DOD -- Department of Defense

DSN -- Data Source Name

EPD -- Electronic Phone Directory

GFE -- Government Furnished Equipment

IAW -- In accordance with

JITC -- Joint Interoperability Test Command

LMR -- Land Mobile Radio

MAC -- Moves Adds Changes

MOC -- Maintenance Operations Center

OEM -- Original Equipment Manufacturer

PC -- Personal Computer

POC -- Point of Contact

PSA- Project Support Agreement

PTT -- Push-To-Talk

RTU -- Right-To-Use

UHF -- Ultra-High Frequency

VHF -- Very High Frequency