FINAL_Console_PWS_7_May19.pdf

PERFORMANCE WORK STATEMENT

FOR

AIR FORCE RESERVE COMMAND

ENTERPRISE COMMAND AND CONTROL (C2) SYSTEM

7 May 19

Section 1. DESCRIPTION OF SERVICES.

1.1. Scope. This Performance-based Work Statement (PWS) describes the services required to replace and sustain Air Force Reserve Command (AFRC) Command and Control (C2) systems. The scope includes removal of legacy systems, installation of new systems, maintenance and sustainment of the new systems located at Continental United States (CONUS) sites. The legacy consoles are currently employed in AFRC Command Post (CP), Alternate CP, Base Operations (BOPS) and Maintenance Operations Center (MOC), Fire Department (FD), and Security Forces (SF) facilities at the locations listed in Attachment 1. However, the FD and SF only require removal of legacy systems; only CP, BOPS and MOC will have legacy systems removed and new systems installed. Contractor shall provide all personnel, equipment, software, software licenses, supplies, transportation, tools, materials, non-personal services necessary to perform the specified installation and sustainment of the new system.

1.1.1. Removal of Legacy Consoles. The AFRC locations identified in Attachment 1 will have legacy systems and old consoles removed. Representative photos are included in Attachment 2.

AFRC COR will provide a unit POC responsible for legacy equipment disposal.

1.1.2. Site Survey. The Contractor shall be responsible for conducting related site surveys prior to removal or installation of new C2 systems. The Contractor shall identify all required allied support to facilitate new equipment installation. Contractor shall coordinate site survey schedule with the Contracting Officer’s Representative (COR). Site survey results and trip information shall be included in the Contractor’s Monthly Status Report. (CDRL A001, DI-MGMT-80368A/T, Monthly Status Report)

1.2. Installation of New Systems. The Contractor shall provide all the specialized tools and equipment to accomplish installation, training and testing. The Contractor shall meet or exceed industry and Air Force specifications with the appropriate licenses. The Contractor shall be responsible for the provisioning of a completely functional C2 system with required programming, hardware, software, licenses, ancillary equipment, parts and material for all identified requirements. The new system shall be connected to existing ancillary equipment such as radios (UHF, VHF, and HF). The C2 system will provide secure, user connectivity to the console that is not dependent on a user's Common Access Card (CAC). The C2 system shall be scalable to facilitate future system installations. New C2 systems shall be installed at locations indicated in Attachment 1. The C2 system shall be Voice over Internet Protocol (VoIP) capable including a redundant communications server with redundant power supplies and hot-redundant LAN interfaces. The C2 system shall include a VoIP capable dispatch capability, crisis management dispatch, and other associated telecommunications hardware and software. All switches must provide for rapid and assured selection of radios, telephone systems, direct lines, remote controls, and voice recording capability. The new system must also provide for ground-to-air, radio-to-wire phone patch, conference calls, and Secondary Crash Net (SCN) a dedicated relay line for dissemination of emergency situations that are critical to the safety and security of airfield/flight operations. This network environment shall be configured for 24x7 operations and must include built in redundancies to maximize network availability. The C2 system shall be deployed in an Enterprise configuration allowing multiple installations to share resources. There will be two regional servers located at Dobbins ARB, GA and HQ AFRC Robins AFB, GA (see paragraph 2.1). Communications from AFRC Host bases and tenant locations to the regional servers will be accomplished via Session

Initiation Protocol (SIP) lines. Air Force Unified Communications (UC) policy directed all AF installations employ Voice over Internet Protocol (VoIP) systems for telephony requirements which utilize SIP lines.

1.2.1. Voice Recording System. The Contractor shall provide a new voice recording system to support documentation and recall of all voice communications (telephone and radio). The Contractor shall configure the system to record all radio and voice communications to include the ability to retrieve recordings for a minimum of 90 days.

1.2.2. Conference System. The Contractor shall include the installation or integration of a conference capability for this system. The Contractor should provide a solution that will conference a minimum of 30 participants and a minimum of 10 conference lines..

1.2.3. Radio Integration. The Contractor shall provide for the integration of existing radio equipment including Land Mobile Radios (LMRs) into new/upgraded touch screen systems at all console positions. The system shall be capable of integrating with newer Ultra-High Frequency/Very-High Frequency (UHF/VHF) radio technology such as the Army- Navy/Portable Radio Communications (AN/PRC) 117G Multiband radio.

1.2.4. Uninterruptible Power Supplies (UPS). The Contractor shall furnish and install UPS and power components that ensure continuous and full system operability in the event of primary distribution system malfunction. All UPS shall be rated at a runtime of 2 hours.

Individual electrical circuit(s) will be provided by the Government.

1.2.5. Peripherals and Miscellaneous Parts. The Contractor shall include all peripherals and miscellaneous parts not listed as a major component, including but not limited to handsets, headsets, speakers, microphones, IP phones, hardware, media convertors and multiplexers as needed for system operation.

1.2.6. Hotline Configuration. The Contractor shall configure all hotlines identified by the Government representative at each location to support CP operations. After initial programming, the system shall allow local site administrators the ability to program hotlines according to local mission requirements.

1.2.7. Inside and Outside Plant (Cabling). The Government will provide all required labor; interface equipment (major and minor hardware) and cabling to support the connection/extension from the building demark to the primary and alternate CP equipment.

The Contractor shall provide all intra-building wiring/cabling to support connectivity of consoles, radios, recorders, etc. Fiber and/or copper connections between buildings shall be provided by the Government; however, any and all connection devices shall be provided by the Contractor.

1.3. JITC Approved Products. There is NO requirement for any sort of interoperability testing.

The requirement is to use approved products from the Joint Interoperability Test Center’s Approved Products List (APL).

1.4. Required Features/Functions

Multi-line phones Secondary Crash Net (SCN). The telephone must be equipped with a visual feature that activates as each two-way party on the SCN picks up the handset.

Speakers Speed Dialing C2 system will provide secure, user connectivity to the console that is not dependent on a user's Common Access Card (CAC).

Radio-to-Telephone Conferencing Telephone Group Conferencing Radio interoperability Hotlines Telephone directory able to store minimum of 1,000 numbers Capability to monitor phone/radio communication of all workstations Ability to program automatic dial buttons Push-to-Talk handsets with shielded, twisted pair cabling (2 per position) Connectivity to existing radios (Land Mobile Radios, HF, VHF and UHF) Capability to store phone numbers and create address groups Caller ID and call back capability for drop calls Redial last number, call transfer/forwarding and call history Touchscreen functionality Ability to record and save recordings at least 90 days Ability to extract individual recordings Ability to place Conference Calls with “drag and drop”, break-in, add transfer or delete caller functions Multiple programmable phone ring alerts Ability to patch phones No single point of failure Black only architecture

1.5. Moving/Adding/Removing Installed Systems.

1.5.1. Moving. The Government will have the capability to move systems without nullification of the warranty unless there is gross negligence by the Government.

1.5.2. Additional installations. Any additional requests for system installations will be contracted through Option CLINs X004 and X005.

1.5.3. Removal of Installed Systems. If the Government determines that a system will be removed, the Government will remove the system. The Government will notify Contractor 10 days prior to removal of equipment to ensure inventory is updated.

1.6. Shipment of Equipment. No equipment shall be shipped to the units identified in Attachment 1 without Government authorization. Contractor must coordinate all installation and shipment of equipment with the contract COR.

Section 2.

2.1. Risk Management Framework, CERTS, and Cyber Security. The Contractor shall employ use of virtual technology where applicable. Two AFRC host locations have been identified to provide virtual server space for this requirement: Dobbins ARB, Marietta GA and HQ AFRC, Warner Robins GA. Virtual servers will be Government-provided.

2.1.1. These servers will be virtualized in AFRC’s VMware environment.

2.1.2. Servers will support CentOS and Windows Server OS 2012R2 and higher

2.2. AFNet Requirements: The Contractor shall include as a minimum an Interim Authority to Test (IATT) with Authority to Operate (ATO) completed within 12 months of contract award date prior to connection to the Air Force Network (AFNet). Contractor shall oversee the development of required Risk Management Framework (RMF) documentation (and provide all system artifacts required to submit the Security Authorization Package to the USAF Authorizing Official (AO) for review and ATO approval. (CDRL A002, DI-MGMT-82000/T, Risk Management Framework)

2.3. TAA Compliance or Certification: TAA refers to the Trade Agreements Act (19 U.S.C. § 2501–2581), which is intended to foster fair and open international trade. TAA requires that products must be produced or undergo “substantial transformation” within the United States or a designated country. The new system must be TAA compliant.

2.4. National Information Assurance Partnership (NIAP) certified: If system software is Information Assurance enabled (IA-enabled) (product or technology whose primary role is not security, but which provides security services as an associated feature of its intended operating capabilities), it must be NIAP certified.

2.5. Certification: Contractor personnel performing remote monitoring and System Administration shall complete mandated training required for performance of this contract, as stated below and/or as required by the AFRC/A6 COR. Security Plus Certification is required for System Administration privileges and must have at time of award through the end of the contract. All other required training shall be completed not later than 30 days after award with evidence of course completion submitted to the COR. Performance cannot begin until all mandated training has been completed. (CDRL A003 Training Certificates)

2.5.1. DoD Information Assurance Awareness (ZZ133098)

2.5.2. Security Administration (ZZ133078)

2.5.3. As a minimum, only Contractor personnel performing remote monitoring and System Administration must have a SECRET clearance. The following items also apply:

2.5.3.1. A National Agency Check with Local Agency Check and Credit Check (NACLS) Clearance is required

2.5.3.2. NACI for unclassified network access and CAC issuance

2.5.3.3. If a person is declined an appropriate clearance then they must be removed from the contract

2.5.3.4. Every AF network user must possess a current and favorable National Agency Check with Written Inquires (NACLC) Investigation

2.6. Integrated Master Plan and Schedule: The Contractor shall manage the execution of the Enterprise C2 project using an Integrated Master Plan (IMP) and associated Execution Integrated Master Schedule (IMS) as day-to-day execution tools and to periodically assess progress in meeting program requirements. The IMP and IMS shall be maintained and updated to reflect Government approved changes in the IMP, or changes in the Contractor’s detailed execution activities or schedule changes to the ongoing program. The Contractor shall report on program or project progress in accordance with the IMP on a monthly basis or upon request by the Government. This IMP will include a schedule for removal of legacy consoles and delivery and installation of new C2 systems.

(CDRL A004, DI-MGMT-81797/T, Integrated Master Plan). The Execution IMS shall include the activities of the prime Contractor and their major sub-Contractors. All Contractor schedule information delivered to the Government shall originate from the Execution IMS. The Contractor shall perform appropriate analyses of the Execution IMS tasks and report potential or existing problem areas to the COR and recommend corrective actions to eliminate or reduce schedule impact.

Final IMS is due 10 business days after post award orientation meeting. The Government will reject a deliverable if accuracy errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection. Minor errors (e.g., grammatical, typographical, etc.) will not be counted.

2.7. Lifecycle Management / Warranty.

2.7.1. Software. Contractor shall be responsible for keeping all application software functional through end of contract Period of Performance (PoP). This shall include all updates and required security patches. 95% of scheduled software updates and/or maintenance executed according to schedule, remaining 5% completed within 2 days of scheduled date.

2.7.2. Hardware. Contractor shall be responsible for all C2 system hardware maintenance/repair and tech refreshes to ensure that the hardware will be sustainable throughout the life of the contract to include all option years. No equipment will be removed without prior coordination with contract COR that will affect the ATO certification.

2.7.3. New Functionality. If the Government determines that a new functionality is required, it will be billed as a reimbursable expense.

2.7.4. Obsolescence. The Contractor shall be responsible for entire C2 system working at the same or higher level until the end of this contract to include all option years.

2.7.5. Lifecycle Management Plan. The Contractor shall submit a Lifecycle Management Plan to the Government detailing their proposed system asset management to sustain the Enterprise C2 system and deliver a product support package that maintains affordable system operational effectiveness over the system life cycle. The Lifecycle Management Plan will be updated annually to reflect the increased maturity of the product support strategy, any changes in the corresponding product support package and current risks. (CDRL A005, DI- ILSS-81225/T, Lifecycle Management Plan)

2.7.6. Warranty. The Contractor shall provide warranty documentation 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. The site acceptance is achieved with the successful completion of the operational system checklist which has been added as Attachment 3. The Contractor’s warranty shall cover services for workmanship deficiencies and equipment provided as described and in accordance with the contract. The Contractor shall provide a full/unlimited industry standard commercial warranty for all Contractor provided hardware, software, materials, and workmanship. The warranty shall include emergency technical assistance as required including 24/7 VPN remote access and on‐site responses as appropriate for system failures. Warranty shall cover total system operability to minimize risk of mission failure. The Contractor shall provide written procedures and required information for warranty services prior to completion of the site acceptance form. This information shall include written confirmation of the warranty period, phone numbers and contact information. It shall detail procedures for technical support, troubleshooting assistance, and replacement of faulty equipment.

2.8. Inventory. The Contractor shall provide a complete list of all installed equipment to the Government to include manufacturer, part numbers and serial numbers at each location 30 days after completion of all equipment installations. No APL approved equipment will be removed without prior coordination with contract COR that will affect the ATO certification. Contractor shall send updated equipment inventory to COR after any change in equipment inventory. (CDRL A006, DI- SESS-80858C/T, Inventory)

2.9. Testing. The Contractor shall provide on-site testing to ensure C2 system works properly after installation. The Contractor shall also conduct remote monitoring/testing of the C2 systems after modifications are performed to include software updates and equipment installations/repairs.

NOTE: The initial testing of the system will be in accordance with Attachment 3.

2.10. Training. The Contractor shall conduct in-person user training pertaining to system functionality after installation of the new system at each facility. The Contractor shall also provide end-user training materials either electronically or hard copy for the system operator(s) to properly use and program the system features. (CDRL A007, DI-ILSS-80872/T, Training Materials)

2.11. Remote System Monitoring and Diagnostic Testing. The Contractor shall monitor operational status of the network services and systems using monitoring software applications and take corrective action to resolve performance degradation or system/service failures. The Contractor shall evaluate/install Operating System application patches, maintain system Information Assurance Vulnerability Management (IAVM) compliance and manage system security configurations on all information systems, including systems distributed to remote sites. The system will maintain an average of ≤ 2.5 vulnerabilities per device. Information Assurance Vulnerability Alert (IAVA) will be accomplished within 30 days of notification as reported by Assured Compliance Assessment Solution (ACAS) via AFRC MAJOM Communication Coordination Center (MCCC). The contractor will test in their environment and then push through protocol.

2.11.1. Government Access to Tracking System. The Contractor shall provide the Government access to the Contractor’s tracking system for scheduled and unscheduled maintenance actions. Actions shall be associated with a timestamp. The Contractor shall provide the COR a unique identifier to be used to examine all maintenance actions for a particular site. Advanced search capabilities shall be available for the aggregating of elements to be used in trend analysis and performance monitoring.

2.12. Software License Management. If developing and/or sustaining a system that requires and/or contains COTS, the Contractor shall provide maintenance and support of that software license to manage its relationship to the overall system life-cycle, which would include applications, license agreements and software upgrades.

2.13. Monthly Status Report. The Contractor shall submit monthly status reports. Each report shall include, at a minimum, task area summaries including a narrative of work accomplished and significant events, problem areas, maintenance calls/responses/non-repairs to include start and completion times, trip reports, training and anticipated activity for the next reporting period. There shall be no more than two total rejection(s) of deliverables per contract year. The Government will reject a deliverable if accuracy errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection.

(CDRL A001, DI-MGMT-80368A/T, Monthly Status Report)

2.14. Unscheduled Maintenance. The Contractor shall provide a central point of contact for users with technical, systems/application and program problems, connectivity issues and routine queries.

At a minimum, the central point of contact shall effectively assist customers with telephone support, and logging trouble calls for ticket tracking system. The Contractor shall provide 24/7 customer support for unscheduled outages or system degradation using the following defined timeline and Tiered Maintenance approach (CDRL A001, DI-MGMT-80368A/T, Monthly Status Report).

Primary fix action method is remote access restoration, however, if remote restoration is unsuccessful Contractors will respond on-site within the following timelines:

2.14.1. Routine Support (Tier 1). The Contractor shall respond on-site within 48 hours if unable to restore remotely and reestablish service as soon as possible, but not to exceed five (5) days of initial trouble ticket. Routine outages/technical issues or any other outage(s) not included in the categories below. 95% of routine unscheduled outages responded to and resolved within 48 hours of notification, remaining 5% completed within 2 days of scheduled date. There shall be no more than 2 discrepancies within a 30 day reporting period.

2.14.2. Priority Support (Tier 2). The Contractor shall respond on-site within 24 hours if unable to restore remotely, provide fix action in writing within three (3) hours of arrival and reestablish service as soon as possible, but shall not exceed two (2) days of initial trouble ticket.

95% of unscheduled priority outages responded to and resolved within 24 hours of notification, remaining 5% completed within 2 days of scheduled date. There shall be no more than 2 discrepancies within a 30 day reporting period.

Priority outages include:

(1) Loss of call handling capabilities on one or more of the communication consoles

(2) Loss of radio (UHF/VHF) capabilities on one or more of the communication consoles

(3) Loss of recording capabilities

(4) Loss of any capability of the touch screen monitors or push-to-talk handsets

(5) Any software issue that causes a partial loss of mission capability

2.14.3. Emergency Support (Tier 3). The Contractor shall respond on-site within 12 hours if unable to restore remotely, provide a fix action in writing within two (2) hours of arrival on site and reestablish service within 24 hours of initial trouble ticket. Contractor will notify COR of all emergency trouble tickets. 95% of unscheduled emergency outages responded to within 12 hours and resolved within 24 hours of initial notification, remaining 5% completed within 2 days of scheduled date. There shall be no more than 2 discrepancies within a 30 day reporting period. Emergency outages/technical issue include:

(1) Total loss of call handling capabilities of all the communication consoles in base primary and alternate CP locations

(2) Total loss of radio (UHF/VHF) capabilities of all the communication consoles primary locations

(3) Loss of any portion of the administrative PC that operates the core system

(4) Any software issue that causes a total loss of mission capability

Section 3

3.1. Organization. The AFRC organization with primary responsibility for this requirement is HQ AFRC/A6XP with input from HQ AFRC/A3.

3.2. Place of Performance. These services may be performed from the Contractor’s facility with travel required. (See PWS Paragraph 5.4-- NOTE: The travel cost will be included in the Firm Fixed Price (FFP) for legacy console removal, new system installation and site surveys.

Periodic travel to include repairs or training, will be on a cost reimbursable basis on CLIN X006 in accordance with the Joint Travel Regulation (JTR). All travel requirements (including plans, agenda, itinerary, or days) shall be pre- approved by the Contracting Officer/COR. Cost for travel shall be billed in accordance with regulatory implementation of Public Law 99-234 and FAR 31.205-46, Travel costs. The Contractor shall make necessary travel arrangements for their personnel.

4.1. SERVICES SUMMARY (SS).

Performance Objective PWS Reference Performance Threshold

Update software in systems/databases

PWS Paragraph 2.7.1

95% of scheduled software updates and/or maintenance executed according to schedule, remaining 5% completed within 2 days of scheduled date.

Maintain inventory of installed equipment

PWS Paragraph 2.8

100% compliance. The Contractor shall provide a complete list of all installed equipment to the Government to include manufacturer, part numbers and serial numbers at each location 30 days after completion of all equipment installations. Contractor shall send updated equipment inventory to COR after any change in equipment inventory.

Provide timely routine unscheduled maintenance support

PWS Paragraph 2.14.1

95% of routine unscheduled outages responded to and resolved within 48 hours of notification, remaining 5% completed within 2 days of scheduled date. No more than 2 discrepancies within a 30 day reporting period.

Provide timely priority

PWS Paragraph 2.14.2

95% of unscheduled priority outages responded to and resolved within 24 hours of notification, remaining 5% completed within 2 days of scheduled date. No more

Provide timely emergency

PWS Paragraph 2.14.3

95% of unscheduled emergency outages responded to within 12 hours of notification and resolved within 24 hours of initial notification, remaining 5% completed within 2 days of scheduled date. No more

Section 5. GENERAL REQUIREMENTS.

5.1. Post Award Meeting. The Contractor shall attend a one (1) day post award meeting convened and hosted by the AFRC/A6XP COR. The post award conference will be held within two (2) weeks of contract award. The location will be a mutually agreed upon site to be determined after award.

The Functional Commander, AFRC/PKA CO and AFRC/A6XP COR will participate with Contractor Representatives. The meeting will provide an orientation and overview of the contract scope, terms and conditions. The meeting will detail the roles and responsibilities of AFRC team members, QASP, performance evaluations, and contract closeout.

5.2. Training Requirements. All authorized users of Department of Defense (DoD) information systems (IS)/Platform Information Technology (PIT) systems must receive initial cybersecurity user awareness training as a condition of access to an IS in accordance with DoD 8570.01-M, thereafter all users will complete annual cybersecurity awareness refresher training. This training can be found on the Defense Information Systems Agency (DISA) Information Assurance Support Environment (IASE) portal: http://iase.disa.mil/eta/Pages/index.aspx

5.3. Contractor Identification. Contractor personnel shall wear Contractor-provided identification at all times while in Government facilities so as to distinguish themselves from Government personnel. Contractor personnel may attend meetings, answer phones, and work in other situations where their status is not obvious to third parties; therefore, Contractor personnel shall always identify themselves as Contractor support to avoid potential misrepresentation as Government personnel or to avoid situations arising where sensitive topics might be better discussed solely amongst Government personnel. Electronic mail signature blocks shall identify their company affiliation. Where practicable, Contractor personnel occupying collocated space with their Government program customer shall identify their work space with their name and company affiliation.

5.4. Travel. The Contractor shall coordinate specific travel arrangements with COR thirty days in advance, unless emergency travel (will be coordinated immediately), and obtain advance, written approval from HQ AFRC/PKA CO for any travel. The Contractor’s request for travel shall be in writing and contain the purpose of the trip, number of participants, dates, locations and estimated costs of the travel. The Contractor travel payment is limited to reasonable and allowable costs to the extent that they do not exceed on a daily basis the maximum per diem rates in effect at the time of travel as set forth in the Government’s Joint Travel Regulation, Volume 2 and allowable per FAR 31.205-46, Travel Costs. No profit or fee will be paid.

5.5. Contractor Manpower Reporting. Per 10 U.S.C. 2330a, the Contractor shall provide an annual count of Contractor/sub-Contractor personnel performing work for each fiscal year if the DoD is the requiring activity, if the acquisition is using U.S. Government appropriated funds, and if the acquisition is greater than or equal to the simplified acquisition threshold (SAT). The Contractor shall report all Contractor labor hours, including sub-Contractor labor hours, required for performance of the services provided under the contract in the Enterprise-wide Contractor Manpower Reporting Application (eCMRA). Reporting shall be conducted for each fiscal year, which extends October 1 through September 30. While inputs may be made any time during the fiscal year, all data shall be reported no later than October 31 of the following fiscal year. The Contractor shall establish a record for the contract/order in eCMRA no later than 30 calendar days after contract/order award.

The Contractor shall enter Order Data, Contact Data and Location Data. Data for Air Force service requirements must be input at the Air Force CMRA link at http://www.emra.mil. The Contractor may direct questions to the help desk at the eCMRA site: http://www.ecmra.mil

5.6. Continuation of Mission-Essential Services during a Crisis.

5.6.1. Designation of Services as Mission-Essential. The Functional Commander (FC) or civilian equivalent has determined, by placing the decision in writing, that all or a portion of the Contractor services performed under this contract in PWS Paragraphs 1.1 thru 1.6; 2.7;

2.9; 2.11; 2.12; and 2.14 are mission essential (M-E) and will continue in the event of a crisis.

If a crisis is declared by the Secretary of Defense, the PCO or COR will verbally advise the Contractor of the revised requirements, followed by written direction. The Contractor shall continue providing on-call service to the requesting organization 24-hours a day until the crisis is over. The Contractor shall ensure enough skilled personnel are available during a crisis for any operational emergency. The M-E contract services required in the event of a crisis are the minimum essential to ensuring all C2 systems remain operational. Contractor personnel for on-call or remote access to C2 Systems include the Contractor’s technicians and others as determined by the PKA PCO, AFRC/A6XP COR and Contractor’s program manager based on the declared crisis. The government reserves the right to make additional paragraphs mission essential if mission dictates.

5.6.2. Mission-Essential Contractor Services Plan. The Contractor shall submit a plan describing procedures for continuing performance of mission-essential services during a crisis with the proposal. This plan will be evaluated as acceptable/non-acceptable. The Contractor shall identify provisions for ensuring required personnel and resources are available to support continuity of operations for up to 30 calendar days or until normal operations can be resumed. The Contractor shall submit any revision to the plan for approval prior to implementation. The Contractor shall activate the plan only if authorized by the PCO acting under the direction of the FC or civilian equivalent.

5.7. Non-personal Services. The Government will neither supervise Contractor personnel nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor personnel. It shall be the responsibility of the Contractor to manage its personnel and to guard against any actions that are of the nature of personal services, or give the perception of personal services. The Contractor shall notify the AFRC/PKA CO immediately if any task requires action by the Contractor personnel that constitutes, or are perceived to constitute personal services. These services shall not be used to perform work of a policy/decision making or management nature, i.e.

inherently governmental functions. All decisions relative to the Enterprise C2 Systems program supported by the Contractor shall be the sole responsibility of the Government.

5.8. Security. The Contractor shall comply with all security regulations and directives identified herein and other security requirements as shown elsewhere in this contract.

5.8.1 Information Security Program. The Contractor shall be integrated into the sponsoring Government activity’s Information Protection Program (IPP) which participates in the host Servicing Security Activity’s IPP.

5.8.2 Controlled Unclassified Information. The Contractor shall mark, handle and safeguard Controlled Unclassified Information in accordance with the DoD Manual 5200.1-M, Volume 4, DoD Information Security Program: Controlled Unclassified Information (CUI), and the DD254, DoD Contract Security Classification, if applicable.

5.9. Personnel Security Program

5.9.1. Background Investigation Requirements. The Contractor shall be responsible for processing background investigations for all employees that require access to classified information. The Servicing Security Activity at the installation will be responsible for processing background investigations for Contractor personnel that do NOT require a National Security determination.

5.9.2. Contractor Notification. The Contractor is notified by Servicing Security Activity at the installation Personnel Security section of the results of the Contractor personnel background investigation for Trustworthiness Determinations.

5.9.3. COR Notification. The Servicing Security Activity at the installation will document the HSPD-12 credentialing determination when the case file is returned to the submitting office number (SON) for a local decision. The Contractor personnel shall not have access to sensitive information, automated information systems, or restricted areas until a final determination is made. The Servicing Security Activity at the installation provides final credentialing determinations to the COR and sponsoring unit security manager.

5.9.4. Terminations. If Contractor personnel are terminated before the Government completes the Trustworthiness Determination, the Contractor’s PM shall immediately forward written notice to the Servicing Security Activity at the installation with a copy of the notice to the COR.

Section 6.

6.1. Physical Security Program.

6.1.1. Installation Perimeter Access Control. The requirements for installation perimeter access are detailed in Air Force Federal Acquisition Regulation Supplement (AFFARS) clause 5352.242-9000 entitled, Contractor Access to Air Force Installations, in Section I, Contract Clauses, of the basic contract. Contractors merely requiring unescorted access to the installation to perform services, that don’t require access to classified information or network access, will be vetted IAW AFM 31-113, para 4.3 and issued a DBIDS Identification Card.

The Contractor is only allowed to visit the installations specified in the contract.

6.2. Resource Protection and Integrated Defense. The Contractor shall safeguard all government property in accordance with AFI 31-101, Integrated Defense, and any forms provided for Contractor use. The Contractor shall immediately report all thefts, vandalism, or destruction of property and equipment (Government or Contractor owned) to the Contracting Officer Representative (COR) of this contract.

6.3. USAF Restricted Area and Controlled Area Access. The requirements for USAF Restricted Area and Controlled Area access are detailed in AFI 31-101, Integrated Defense, and governed at each installation by the Integrated Defense Plan, if required.

6.4. Privacy Act of 1974. The Contractor personnel shall have access to Privacy Act information that requires adherence with the Privacy Act of 1974, Title 5 of the U.S. Code, Section 552a, AFI 33-332, Air Force Privacy Act Program, and other applicable agency rules and regulations. The Contractor personnel shall follow agency procedures to identify and safeguard reports and data accordingly. The Contractor shall ensure that Contractor personnel assigned to this requirement are briefed annually on properly identifying and handling Privacy Act data and reports. AFI33-332 is the guiding document and can be downloaded from www.e-publishing.af.mil.

Section 7.

7.1. Network Security. Network access is a privilege extended to Contractor personnel. Network access will be granted by the Government after all criteria have been met and may be suspended for cause as defined in AFI 33-115V2, Section 5.6. Network access will be approved by the Government in accordance with AFI 31-501, AFI 16-1406, AFI 33-115V2 and V3, AFI 33-200, DoDI 8510.01, and DoDM 5220.22-M and its supplement. Pursuant to AFI 33-115V2, every individual who has access to the Air Force (AF) network (af.mil) or af.smil domain, specialized systems, and mission systems is a network user. Before becoming an Air Force network user, the Contractor personnel shall have a favorable background investigation for the designated IT level and system, be trained, and licensed.

This process of training and licensing ensures every AF network user is trained and aware of the basic principles of network security and their role in Information Assurance (IA). The Government will issue a Common Access Card in accordance with Air Force FAR Supplement clause 5352.242-9001 entitled, Common Access Card for Contractor Personnel, to Contractor personnel that meet the criteria (favorable trustworthiness determination, training and licensing).

7.2. Information Technology (IT) Level and Investigation Required. Contractor personnel shall possess a Tier 3 background investigation for IT Level II as mandated by DoD Regulation 5200.2-R entitled, Personnel Security Program, paragraph C3.6.15 and DoD Instruction 8500.1 entitled, Cybersecurity, para 3i. These background investigations will be submitted by the Govt. and they do not result in security clearance eligibility. Contractor personnel shall possess a current and favorable background investigation for designated level IT Level II access prior to contract performance.

Contractor personnel without a current investigation shall follow the procedures in paragraph 5.9.1, above.

IT LEVEL 2 (Limited Privileged): An individual that has elevated administrative access over one or more programs but not network configuration.

7.3. Foreign National Network Access. All Contractor personnel that are Foreign Nationals shall meet the requirements of AFI 31-501 prior to network access. The Contractor shall ensure the request for network access for Foreign Nationals in their employ are processed and approved by the Foreign Disclosure Office (FDO) in accordance with Air Force Security Systems Instruction (AFSSI) 8522 entitled, Access to Information Systems, paragraphs 3.2.1 and 3.2.3. All requests for must be staffed through the AFRC Foreign Disclosure Office at least 30 days in advance of the intended visit.

7.4. Health & Safety Program. The contractor shall comply with Public Law 91-596, Occupational Safety and Health Act (OSHA) and Environmental, Safety, and Occupational Health (ESOH) (DoDD 4715.1E), and these requirements shall be incorporated into the contractor’s safety and health program. The Air Force participates in the OSHA Voluntary Protection Program (VPP).

The contractor shall be familiar with VPP tenets. Information on VPP is available at http://www.osha.gov/dcsp/vpp/index.html. The contractor shall be responsible for the safety and health of all subcontractor employees.

7.5. Incident or Mishap Procedures. The contractor and its subcontractors (if applicable) shall promptly report pertinent facts regarding mishaps involving Government property damage or injury to Air Force personnel and to cooperate IAW AFI 91-204, Safety Investigations and Reports, in any Air Force safety investigation. The contractor shall notify (via telephone) the cognizant contracting officer, the contracting officer’s representative, and/or the cognizant program manager within four

(4) hours of all mishaps or incidents to DoD property entrusted by this contract operation. The Government person notified by the contractor will in-turn notify the Safety office. Contractor notifications made after duty hours shall be reported to the appropriate installation Command Post (Note: the Robins AFB Command Post commercial phone number is (478) 327-2612, and they can connect with any DoD Command Post worldwide). If requested by the cognizant contracting officer, the contracting officer’s representative, and/or the cognizant program manager, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records until released by the investigating safety office. If the Government investigates the mishap, the contractor and the subcontractors shall cooperate fully and assist the Government personnel until the investigation is completed.

7.6. Fire Emergencies. The Contractor personnel shall dial 911 to report fire related emergencies.

7.7. Department of Labor (DoL) Inspection of Contractor Operations. The Contractor is subject to DoL inspections and enforcement by OSHA health and safety officials while performing work on a Government installation. The OSHA health and safety officials may access workplaces on Government installations at any time, scheduled or unscheduled, during regular business hours. The OSHA health and safety officials must meet security requirements to enter restricted or classified areas. The Contractor shall notify the AFRC/PKA CO and AFRC/A6XP COR upon notification of a visit.

7.8. Fire Protection and Prevention Program - Robins AFB GA. All Contractor personnel performing work on properties under jurisdiction of AFRC shall be responsible for fire safety and compliance with all applicable OSHA, State, Air Force, AFMC, and base regulations and directives.

The Contractor personnel shall attend a Contractor's briefing on fire safety prior to any work. The Contractor shall ensure that all Contractor personnel and sub-Contractors under their control are briefed on fire prevention practices in accordance with host base instructions.

7.9. Quality Management System (QMS). The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a Quality Control Plan (QCP) 30 days after contract award, addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur.

The plan shall include the schedule of quality assurance/control inspections planned by the Contractor. (CDRL A008 Contractor’s Quality Control Plan, DI-QCIC-81722/T)

7.10. Management of Records. All records, files, documents and work papers provided by the Government or generated in support of this requirement are Government property and shall be marked, maintained, and disposed of per AFMAN 33-363, Management of Records.

7.11. Performance Reporting. The Contractor performance will be monitored by the government and reported in annual Contractor Performance Assessment Report (CPARs) in accordance with DoD Guide in Collection and Use Past Performance Information. The performance objectives and thresholds are set forth in PWS Section 4.1.

Section 8.

8.1. GOVERNMENT PROPERTY AND SERVICES. Government-Furnished Property (GFP) is defined as property in the possession of or acquired by the Government and subsequently furnished to the Contractor for performance of a contract. If the equipment is located on a Government facility or military installation, used within the location, or remains accountable to the Government, it is not considered GFP.

8.1.1. The Contractor will be provided a laptop to enable the Contractor to utilize the AFNet’s Virtual Private Network (VPN) capability to remotely manage the servers and overall system to resolve systems.

8.1.2. Contractors will maintain connectivity as much as practical with their assigned laptops via VPN to continue to receive General Policy Objects (GPOs), Host Base Security System (HBSS) updates, and System Center Configuration Manager (SCCM) updates.

8.1.3. Contractors will not be provided the WIFI, printers, peripheral devices for use at the remote location.

8.2. HQ AFRC/A6 retains ownership of the hardware, software, and data associated with, or generated by, Government-owned systems. The assigned Equipment Custodian (EC) must account for the equipment on a hand receipt and inventory annually. Any equipment not returned to the Government shall be paid for by the Contractor.

8.3. Government equipment is FOR OFFICIAL USE ONLY (FOUO). Commanders may authorize installation, repair, and/or maintenance of equipment at their discretion and direction. The equipment is for authorized use by the Contractor only.

8.4. The Contractor agrees to protect any Government-owned equipment from damage, loss, theft and infection with computer viruses.

8.5. Contractors are not authorized to install hardware or software on a Government system without Government approval.

8.6. Contractors must follow Report of Survey (ROS) procedures for damaged, lost, or stolen Government equipment.

8.7. Government information must be protected from modification, destruction, or inappropriate release.

8.8. Contractors using Government owned equipment must sign an agreement outlining the required equipment, software, hardware, data, and telecommunication services.

8.9. Contractors must ensure that software use conforms to all copyright law and any contractual agreements.

8.10. If a network connection is required at their remote location, it shall be at the Contractor’s expense.

8.11. Upon contract completion/termination, the Contractor must immediately return Government owned hardware, software, data, and cancel all telecommunication services that the Government provided.

Section 9

9.1. STANDARDS: The Contractor shall adhere to all applicable installation and standards below.

Where conflicts exist between any standards listed, the most stringent standard shall apply. The list below provides a quick reference. The Government will provide copies upon request.

FEDERAL GOVERNMENT / DEPARTMENT OF DEFENSE

o OSHA Occupational Safety and Health Administration (OSHA) CFR 29 Part 1910-268 – Telecommunications o EPA Rules, Regulations, and Legislation o DODD 5220.22-M – Industrial Security Program o DODI 8100.3 – Department of Defense (DoD) Voice Networks o DODI 8510.01 – Risk Management Framework (RMF) for DoD Information

Technology (IT) o DODM 4160.21 – Defense Material Disposition: Disposal Guidance and

Procedures.

STANDARD INSTALLATION PRACTICES & TECHNICAL ORDERS

o EIA/ECA-310-E - Telecommunications Cabinets, Racks, Panels, and Associated Equipment o ANSI/TIA/EIA-568-D-1 – Telecommunications Cabling Standard o ANSI/TIA/EIA-607-C – Telecommunications Bonding and Grounding

Standards o TO 31‐10‐6 – Cable Racks, Troughs and Their Supports o TO 31‐10‐7 – Terminating and soldering Electrical Connections o TO 31‐10‐9 – Marking Site Layouts o TO 31‐10‐10 – Anchoring Devices for Ground Comm‐Electronic Equipment o TO 31‐10‐11 – Cross‐connections and Strapping of Fixed Ground C‐E

Components o TO 31‐10‐12 – Metal Ducts and Conduits o TO 31‐10‐13 – Cabling for Fixed Ground C‐E Equipment o TO 31‐10‐24 – Comm Systems Grounding, Bonding, and Shielding o TO 31‐10‐34 – Fiber Optic Communication Cables And Connectors o TO 31‐1‐141 Series – Basic Electronics Technology

MILITARY STANDARDS

o AFMAN 10‐207 – Command Posts o AFI 32‐1065 – Grounding Bonding and Shielding for Electronic Equipment and Facilities o MIL‐STD‐188‐124B – Grounding Bonding and Shielding o MIL‐HDBK‐1857 – Grounding, Bonding and Shielding Design Practices o MIL‐HDBK‐454A – General Guidelines for Electronics Equipment o Building Industry Consulting Service International, Inc. (BICSI)

COMMERCIAL STANDARDS AND MANUALS

o NEMA TC 2 – Electrical Polyvinyl Chloride (PVC) Tubing and Conduit

Appendix A, CDRLs

Document Identifier

DID Title

PWS

Reference(s

A001 DI-MGMT-80368A/T Monthly Status Report

1.1.2; 2.13;

2.14 A002

DI-MGMT-82000/T Risk Management Framework 2.2

A003 DI-ILSS-80872/T Training Certificates

2.5

A004

DI-MGMT-81650/T Integrated Master Plan

2.6

A005 DI-ILSS-81225/T Lifecycle Management Plan

2.7.5

A006

DI-SESS-80858C/T Inventory

2.8

A007

DI-ILSS-80872/T Training Materials

2.10

A008

DI-QCIC-81722/T Contractor’s Quality Control Plan

7.9

Attachment 1

Siemen's 3-in-1 Count List 2_26_2019

Attachment 2 console images.docx

Attachment 3

Operational Checklist 4 Apr 2019

Attachment 4

Consoles Install Schedule.docx