1._Draft_Performance_Work_Statement;_dated_5_Jan_18.pdf

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

Technical Control Facility (TCF) Services

Performance Work Statement

EXECUTIVE SUMMARY

The mission for Technical Control Services is to provide 24/7 on-site support to long-haul activities such as fixed and tactical voice, data, video, and testing communications services to include circuit-based networks and consolidated Defense Information System Network (DISN) transport Internet Protocol (IP) network infrastructure, minor maintenance repair to circuit and communications equipment, provide end-to-end support service, and DISN transport support in the prescribed timeframes required.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

Contents

EXECUTIVE SUMMARY

1. PURPOSE

2. SCOPE

3. REQUIREMENT/DESCRIPTION OF SERVICES

3.1 OPERATIONS SUPPORT

3.1.1 Operations Planning and Scheduling

3.1.2 Administrative

3.1.3 Records Management

3.1.4 Security

3.1.5 Training Requirements

3.2 TECHNICAL SUPPORT

3.2.1 Key Personnel Shifts and Duties

3.2.2 DISA Procedures and Coordination

3.2.3 Maintenance

3.2.4 Technical Documentation

3.2.5 Reporting Procedures and Notices

3.2.6 Technical Tests, Checks, Inspections

3.2.7 Combat Survival Evader Locator (CSEL) Support

3.2.8 Uninterruptible Power Supply (UPS) Support

4. CONTRACTUAL REQUIREMENTS

4.1 OPERATION HOURS AND CONTACTS

4.1.1 Normal Operations

4.1.2 Point of Contact (POC)

4.2 SERVICE SUMMARY (SS)

4.3 PERFORMANCE STANDARD

4.3.1 Quality Assurance (QA)

4.4 GOVERNMENT FURNISHED EQUIPMENT (GFE)

4.4.1 Equipment Inventory

4.4.2 Equipment Accountability

4.4.3 Government Furnished Automatic Data Processing Equipment (ADPE)

4.5 GENERAL HOUSEKEEPING

4.5.1 Site Appearance

4.5.2 Utilities Conservation

4.5.3 Environmental Compliance

4.5.4 Hazardous Materials

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

4.6 BASE SECURITY REQUIREMENTS

4.6.1 Employee Base Access

4.7 CONTRACTOR PERSONNEL

4.7.1 Identification and Appearance

4.7.2 Contractor Employment

4.7.3 Travel / Temporary Duty (TDY)

5. PROGRAM MANAGEMENT

5.1 CONTRACT PERFORMANCE MANAGEMENT

5.2 PROGRAM MANAGEMENT PLAN

5.2.1 Plan Format

5.2.2 Plan Contents

5.3 PHASE OUT PLAN

5.4 FINANCIAL MANAGEMENT

5.4.1 Wage Determination / Collective Bargaining Agreement (CBA)

5.5 PERFORMANCE REPORTING

5.6 MANPOWER REPORTING

APPENDIX 1 REQUIRED REPORTS AND FORMS

APPENDIX 2 CONTINGENCIES, INSPECTIONS, AND EXERCISES

APPENDIX 3 GOVERNMENT FURNISHED EQUIPMENT

APPENDIX 4 SUPPORT AGREEMENTS

APPENDIX 5 APPLICABLE DIRECTIVES & PUBLICATIONS

APPENDIX 6 TERMS AND DEFINITIONS

APPENDIX 7 ACRONYMS

APPENDIX 8 WORKLOAD ESTIMATES

Technical Control Facility (TCF) Services

1. PURPOSE.

This Performance Work Statement (PWS) establishes the requirements and responsibilities of the

Contractor to provide Pacific Air Forces (PACAF) specific requirements for Technical Control

Facility (TCF) Services of materials, facilities, and infrastructures in support of Technical Control

Services. This service is required to install, operate, maintain, and repair circuit and communications equipment systems traversing the Joint Base Pearl Harbor-Hickam site via the DISN transport services. The DISN transport services are essential to the DISN networks and services including Non-Secure Internet Protocol Router Network (NIPRNet), Secure Internet Protocol Router Network

(SIPRNet), Defense Information System Network - Leading Edge Services (DISN-LES), Defense

Switched Network (DSN), Defense Red Switch Network (DRSN), and Defense Message System

(DMS) utilizing Video, Data, Voice, and IP transmissions. Additionally, the TCF services provides base/mission support for critical war fighter organizations under Department of Defense (DoD), National Security Agency (NSA), Hawaii Air National Guard (HIANG), Combat Survival Evader

Locator (CSEL), and more exponentially providing global robust “Net-Centric Warfare” operations.

The Contractor shall also provide specified support to daily operations at the Technical Control

Facilities. The Contractor shall comply with all applicable laws, regulations, technical data, and standards while providing services.

2. SCOPE.

The 747th Communications Squadron (747 CS), USAF, PACAF is charged with ensuring the delivery of communications and informational capabilities to enable Headquarters (HQ) PACAF, 15th Wing, 67 tenant organizations and 13 geographically separated units (GSUs) to project peace and power throughout the Pacific and beyond. The squadron is located on the Hickam side of Joint

Base Pearl Harbor-Hickam (JBPH-H). The communications squadron workforce includes approximately 100 enlisted, officers, contractors and civil service employees with 10 percent deployed at any given time.

The responsibility of the squadron goes beyond Internet and email maintenance and support. It includes providing mission support to critical war fighter organizations, maintaining a half a billion dollars’ worth of antennas and satellites provide technical support for over 25,000 tenant users, and monitoring and managing a base network worth over $25 million.

The Technical Control Facility systems operates using Global Information Grid (GIG) is a composite of DoD-owned and DoD-leased telecommunications subsystems and networks, as prescribed in DoD

Directive 5105.19 (authority document). GIG facilities are configured and engineered to enable technical controllers, as well as other operations and maintenance (O&M) personnel, to maximize the full capabilities of the DISN equipment and personnel. These facilities take into consideration the non-GIG tactical missions of the military departments and are designed to achieve optimum standardization of equipment in terms of layout and procurement specifications, operating procedures, training, manning guidelines, and technical control functions.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3. REQUIREMENT/DESCRIPTION OF SERVICES.

3.1 OPERATIONS SUPPORT

Contractor operations entail all aspects of support to include planning, scheduling, training, hardware support, software support, and feedback to facilitate Technical Control mission. The Contractor shall perform all tasks to maximize technical support while ensuring long-term sustainability and enhancement of TCF systems. Reference: DISAC 310-70-series, 310-v70-series, and AFMAN 33-116.

The Contractor shall provide all operations support services for all site equipment and systems. Several key functional areas/processes which are required to support the Technical Control mission include but are not limited to:

Operations Planning and Scheduling

Administrative

Records Keeping

Security Programs, Controlled & Restricted Areas

Training Requirements

3.1.1 Operations Planning and Scheduling

3.1.1.1 The Contractor shall coordinate and participate in meetings with Defense Information Systems

Agency (DISA) to provide expertise on, and/or status of all Technical Control equipment, Technical

Control systems operations, and to assist with the development of and discern plans and priorities for operation support.

3.1.2 Administrative

The Contractor shall be responsible for creating, maintaining, and coordinating records for Required

Reports and Forms, and per the guidance as stated below.

3.1.2.1 The Contractor shall perform general administration and record keeping functions by utilizing the various forms, logs, and publications required as prescribed in DISAC 310-70-1, Chap. 2 & 9.

3.1.2.2 The Contractor shall administer and maintain e-mail accounts set up for Circuit Actions and

Operations on a daily basis on both NIPRNet and SIPRNet. E-mail accounts are used for service provisioning records i.e. (Telecommunications Service Request (TSR), Telecommunications Service

Order (TSO), Status of Acquisition Message (SAM), Request for Service (RFS), In-Effect Reports (IER), Delayed Service Reports (DSR), exception reports, Authorized Service Interruption (ASI) messages, DISA directives, and etc.) Currently there are a minimum of two email accounts in this category required.

3.1.2.3 The Contractor shall be qualified to pick up classified messages at the Communications Security

(COMSEC) Facility or designated location. Messages can also be obtained via SIPRNet.

3.1.2.4 The Contractor shall maintain, communicate and comply with all operation messages received from DISA Operations Center. Each message shall be recording in the Master Station Log to ensure personnel from all shifts are informed of the latest guidance and follow general DISA messages. Record of each message should remain effective and be retained until superseded or canceled by the originator.

Refer to DISAC 310-55-1.

3.1.2.5 The Contractor shall send GIG user notification memorandums to each user upon activation of a new circuit, and annually thereafter. An updated memorandum will be sent any time information contained in the memorandum affects the user’s ability to contact appropriate personnel (i.e., phone number, point of contact, etc.). Ref: DISAC 310-70-1, Chap. 2. Para, C2.4.20.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3.1.2.6 The Contractor shall maintain a current DISA reference library readily accessible to the technical controllers, to include all technical orders (TO) and technical manuals for all communication and test equipment. A list of basic references is contained in DISAC 310-70-1 Chap. 9, para C9.5.1.

3.1.3 Records Management

The Contractor shall maintain the Files Maintenance and Disposition Plan (Records Management).

Provide and maintain official records (hardcopy or softcopy) with a file plan established. All files shall include unclassified official information and data maintained by properly identifying the subject with current year marking on each folder created. Also, accurate file disposition instructions and year will be clearly marked on each folder for active and inactive files in this plan. File plan shall have disposition instructions for each record on file in accordance with the disposition instructions; follow guidelines for destruction or to move to the installation storage facility. References: AFI 33-360, AFI 33-322, & AFI 33-

364, Ch. 2., para 2.10.

The Contractor shall manage and comply with the Air Force Records Information Management System

(AFRIMS) Record Disposition Schedule, by using the current computer/web-based system available and/or as defined by the Air Force In Accordance With (IAW) AFMAN 33-363. A Records Custodian

(RC) and a Chief of Records shall be appointed in writing and shall receive required training by the

Government, within 30 days of the effective date of the contract. The Contractor shall provide the

Contracting Officer (CO), on request, copies of any records created and/or maintained as result of this contract. These copies shall be provided within five (5) working days of receiving the request. All official records as defined in are the property of the U.S. Government and shall remain so at all times.

3.1.3.1 Circuit Layout Records (CLRs)

The Contractor shall conduct and maintain CLRs in accordance with DISAC 310-70-1, Chapter 2, para.

C2.2.2.8 to C2.2.2.10, and the following summarized guidelines:

3.1.3.1.1 In-facility (CLRs) must be completed for all trunks and circuits that have a physical patch panel appearance in the TCF, and for all trunks and circuits for which the TCF is the servicing entity.

3.1.3.1.2 The CLR must depict "in-facility" equipment and cross-connect information.

3.1.3.1.3 TCFs with numerous circuits of the same configuration may use one CLR that depicts the common configuration as long as the records specify cross-connect, conditioning equipment, and other pertinent information is maintained for each individual circuit.

3.1.3.1.4 CLRs for analog circuits must include audio signal levels, type signaling, and signaling frequency for each transmission level point (TLP).

3.1.3.1.5 CLRs for digital circuits must include timing and sync information (e.g., synchronous, asynchronous or isochronous), data rate, electrical and mechanical interface type, and how clock is passed at the interface, signal type, protocol and source of timing.

3.1.3.2 Service Provision Records

The Contractor shall establish and maintain permanent historical records for all links that terminate at their facility, for all trunks and circuits that have physical patching capabilities within the TCF, and for all trunks and circuits for which the TCF is the Communications Control Office (CCO)/ Communications

Management Office (CMO) or servicing TCF. Documentation must be kept on record for one (1) year and in accordance with DISAC 310-70-1 Chap. 9, para. C9.4.

3.1.3.2.1 Circuit history records are not required for through facility trunks and circuits that do not have physical patch appearances, unless the TCF is the CCO/CMO or servicing TCF.

3.1.3.2.2 Temporary circuit history files must be established on all trunks and circuits by each TCF addressed in the DISA TSO, regardless of patching capabilities. The temporary file must be maintained

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

until the link, trunk, or circuit has been in-effected. Once in-effected, the temporary file may be discarded, unless a permanent history file is required by the above criteria.

3.1.3.2.3 Collocated facilities (within the same building) are only required to maintain one history file.

Each history file must contain a copy of the initial test and acceptance data. Copies of the latest TSO that reflects the current end-to-end configuration control office assignment, etc.

3.1.3.2.4 In-effect, exception, and delayed service reports applicable to the latest TSO. When an exception or delayed service report is submitted that pertains to an intermediate facility, the intermediate facility must maintain their history file until the condition causing the report to be rendered is cleared and an in-effect report is submitted.

3.1.3.2.5 Files shall include copies of the quality control waiver requests and approvals, any appropriate documentation (i.e., Quality Check (QC) results, letters, etc.) resulting from action(s) taken to resolve degradations when a trunk or circuit fails management threshold for two consecutive months or more.

3.1.3.3 Communications and Information System Records (CISR)

The Contractor shall maintain and file the CISR (commonly known as plant-in-place records or as built drawings). Review of each record performed annually.

3.1.3.3.1 The Contractor shall use the compatible and current government owned software and hardware available to update, correct, and print these records.

3.1.3.3.2 The Contractor shall collect and file Commercial ‘as built’ drawings from installed equipment/circuits provided by commercial vendors. The Contractor shall work with the 747CS CSIR

Manager for local processing procedures and pertinent tasks written in TO 00-33A-1001, Chap. 7.

3.1.3.4 Automated Record Keeping

The Contractor shall use any authorized Automated Data Processing (ADP) system for record keeping purposes. Ref: DISAC 310-70-1, Chap. 9. Para. C9.2 If the Contractor uses an ADP system, it must conform to the following guidelines:

3.1.3.4.1 The ADP system must provide for adequate backup capability so that computer failure will not prevent the maintenance of required records or the retrieval of information.

3.1.3.4.2 Data must be stored on magnetic media and duplicated on backup media at least once each day to minimize the chance of loss. The backup process should be an automated procedure, or should at least prompt the operator to perform the required actions.

3.1.3.4.3 The ADP system must be redundant with a second computer readily available to replace a failed unit at any time. If this is not possible, a hard copy of all records stored in the ADP system must be manually retained on file for the same length of time as the form it replaces.

3.1.3.4.4 A contingency procedure to provide manual (paper form) record keeping must be developed and implemented and all personnel must be trained on the process.

3.1.3.4.5 The minimum information required for long-term analysis shall include circuit, trunk, link, or facility designator, the date and time out, the date and time in, the Reason for Outage (RFO) code and location, and a brief narrative RFO.

3.1.3.5 Master Station Log (MSL)

The Contractor shall utilize and maintain an MSL (DD form 1753) which is an official narrative record to document significant events (e.g., power failures, complete system outages, major equipment outages or impairments such as Hazardous Conditions (HAZCONs), and any other event that may have an impact on operation of the GIG, time verification, and shift or watch changes, special tests, etc.) Entries must be

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

made in chronological order, see Appendix 1, Required Reports and Forms. Reference DISAC 310-70-1, Chap. C2. Chap. 5, Chap. 6. & Chap. 9.

3.1.3.5.1 The Contractor is required to sign "on" and "off" duty on the MSL. If the MSL is automated, the system should use passwords and require the shift supervisor to log "on" and "off" duty. It is recommended to design the system so that it does not allow alterations.

3.1.3.5.2 The Contractor shall file a hard copy of the MSL at the end of each RADAY. MSLs must be maintained for 11 months after the end of each month. Specific information on the format of the MSL is listed in 31-101 DISAC 310-70-1, (Currently MSL is automated using Facility Circuit Information

Tracking (FACIT) Program; however, the Contractor will follow FCO and DISA instructions on the specific program to use). Funding issues may affect provisioning and decision to use substituted programs as determined equal to current program.

3.1.4 Security

3.1.4.1 Security Programs

The Contractor shall adhere and enforce DoD Security Programs, including Department of the Air Force and Navy Instructions pertinent to protecting the TCF’s structure and operational mission. Reference: AFI

31-101 and PACAF SUP 31-101, & AFIs 31-401, 31-501, and AFI 31-601 and DoD Security instructions where JBPH-H instructions conflict with Air Force Instructions.

3.1.4.1.1 Post and report statuses of Force Protection Condition (FPCON) signage on main entry ways

IAW checklists as directed by the JBPH-H Installation, HQ Pacific Air Force, and Communications

Instructions for real world and exercise scenarios.

3.1.4.1.2 Perform security checklist procedures as required by real world or exercise FPCON postures.

3.1.4.1.3 The Contractor shall be responsible to administer, initialize, update, and ensure accuracy of pertinent Security Programs affecting Building 988 security buffer zone outside the fence line to inside the building during the absence of Military personnel, normally, after duty hours and weekends to ensure

24/7 operational functions continue.

3.1.4.1.4 The Contractor shall have access and be trained to perform administrative tasks for the Facility

Automated Entry Control System (AECS) Administrative to resolve restricted area badge issues and information updates for all facility personnel after duty hours.

3.1.4.1.5 The Contractor shall ensure the information input into the AECS is accurate and current to ensure proper authentication of all personnel authorized into the building. Performance shall be in accordance with pertinent Unit Operating Instructions, 31-Series AFI, and DoD related instructions and manuals.

3.1.4.2 Escort Duties

The Contractor shall provide 24/7 escort services for visitors requiring within TCF boundary access, building 988. Organizations required access to the areas in and around building 988 affecting the technical control mission will plan and coordinate (unless otherwise on schedule) with the Technical

Control with a no later than 72-hour lead time to ensure a qualified escort is available during periods of work in and around building 988. Exceptions shall apply on a case-by-case basis and for emergency actions. Any person with access to building 988’s controlled/restricted area without a line badge will be kept under close escort throughout the duration of their visit.

3.1.4.2.1 The Contractor shall maintain their company and visitors’ current and accurate facility Entry

Authorization Letter (EAL) at the entry control point. Coordinate with other organization's security managers to obtain appropriate EALs.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3.1.4.2.2 The Contractor shall contact the Officer-In-Charge or Senior Non-Commissioned Officer at the site to coordinate additional escort requirements outside of the Contractor’s assigned areas of responsibilities. If no military escorts are available, the Contractor shall provide escort to cover visitors on a mission priority and manpower availability basis.

3.1.4.2.3 Use and maintain AF Form 1109, Visitor Register Log. Security and escort duties listed above shall be followed IAW: AFI 31-101 and PACAF Sup Chapter 7, Installation Security Plan (ISP).

3.1.4.3 Contract Security Classification Specification (DD Form 254)

The Contractor is responsible for ensuring information and signature of personnel is provided to the

Government for the completion of DD 254. The overarching security requirements and Contractor access to classified information shall be as specified in the basic DD Form 254, which will be further identified in the DD Form 254 for each TO, as required. All contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable National Agency Check

(NAC).

3.1.4.4 COMSEC Account

The Contractor shall be assigned as COMSEC Responsible Officer (CRO) and maintain the COMSEC

Account 632310, Sub-Account E-21, strict adherence shall apply but not limited to the following guides and instructions: COMSEC User Instructions, and Responsible Officer Users Guide IAW AFMAN 33-

283. The Contractor shall provide timely safe inspections, maintenance, and shall change the COMSEC safe combination IAW: AFMAN 33-283.

3.1.4.5 Controlled & Restricted Areas

The Contractor shall maintain Controlled and Restricted Area by providing 24/7 monitoring services and ensuring all Site Perimeter Fence Pedestrian and Vehicle Entry Control Points (ECP) are kept secured, to include building entry ways and work center access points.

3.1.4.5.1 The Contractor shall validate visit(s), determine level of escort, and sign visitor into facility using AF Form 1109 unescorted/escorted access. The Contractor shall escort to and around Building 988 a Controlled Area (inside fence line) and Restricted Area (inside the building) for visiting personnel with a verified requirement, EAL, and/or appropriate security documents/clearances.

3.1.4.5.2 The Contractor shall allow authorized access to areas they are operationally responsible for to include the following areas: Common areas for site appearance, house-keeping, safety, security, survey teams, emergency fire/ambulance/police crews, and VIP visits. Reference AFI 31-101 and DoD 5200

Security Publications. Cost of re-keying or the replacement of the lock or locks shall be at the expense of the Contractor.

3.1.4.6 Employee Security Responsibility

The Contractor shall adhere to physical, personal, structural, and operational security guidelines. Access for personnel in the facility without a badge shall be escorted at all times. If the Contractor has an employee awaiting a SECRET clearance, that person will have to be escorted at all times, and must leave the area during COMSEC tasks and cryptographic loads.

3.1.4.6.1 The Contractor shall ensure all individuals having access to classified material and classified equipment possess a minimum security clearance of SECRET. Classified material shall be protected to the applicable level of standards in AFI 31-401.

3.1.4.6.2 The Contractor shall attend meetings to discuss problems and improvements to the facility or security structure surrounding the building. Reference: AFI 31-501 and AF31-601, Installation Security

Instruction (ISI), Installation Security Plan (ISP).

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3.1.5 Training Requirements

3.1.5.1 Training and Certificates

The Contractor shall ensure all personnel, as specified in Training Chart 1.3.3.2. (e) Have successfully completed and are current with all training requirements during the contract period.

3.1.5.1.1 The Contractor shall require all position identified employees, as indicated below, to attend

Government provided training within 30 days of contract start and during the contract period. Requests for initial training must be submitted to the CO no later than 10 workdays after contract start date, unless mandatory completion dates dictate otherwise.

3.1.5.1.2 The Contractor and or Government may request additional government training/certification through the CO's designated representative.

3.1.5.1.3 Upon successful completion, the Contractor shall provide the Contracting Officer Representative

(COR) and CO a status report that includes each individual’s name, certificate completion date, and expiration date. The status report must be submitted no less than quarterly.

3.1.5.1.4 The Contractor must ensure frequent review of revisions, changes and supplements for any cost impact to training (increase or decrease in the cost of meeting PWS requirement) incurred or expected, and must advise the contracting officer or CO’s designated representative within 30 calendar days.

3.1.5.1.5 The contractor will be required to participate in the government’s in-house and web-based security training program under the terms of the contract. The government will provide the contractor with access to the online system.

TRAINING TYPE REQUIRED

ATTENDEE

COURSE LENGTH FREQUENCY

COMSEC Responsible

Officer (CRO)

Primary and Alternate

CRO

½ Day Annually

Controlled and

Restricted Area Training

All Contractors 1 Hour Initial/Annual

Operations Security

(OPSEC) Training

All Contractors 30 min Online CBT Annual

Information Security

Program Management

FOUO: Physical Security

Standards

AFI 31-401, AFI 31-501,

AFI 31-601

All Contractors 3 Hour Online CBT Annual

Electrostatic Discharge

(ESD) Training

All Contractors 30 min PowerPoint

Slideshow

One Time

TRAINING TYPE REQUIRED

ATTENDEE

COURSE LENGTH FREQUENCY

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

Hazard Communication

Training to standards in

AFI 91-202

All Contractors ½ Day One Time

Privacy Act Training All Contractors 30 min Online CBT One Time

Records Management

Level 1

All Contractors 1 Hour Online CBT Annual

Records Management and Chief of Records

Records Manager and

Chief of Records

1 Day Online CBT One Time

Information Protection All Contractors 1 Hour Online CBT Annual

DoD Cyber Awareness

Training

All Contractors 1 Hour Online CBT Annual

Site Alarm Custodian

Account 1007

Primary and Alternate

Custodians

1 Hour Security Forces

Briefing

Initial and after procedure changes

Site Alarm

Operation/Authentication

Procedures

All Contractors 15 Minute Site

Custodian Training

Initial and after procedure changes

Test, Measurement, and

Diagnostic Equipment

(TMDE) Training

Primary and Alternate

TMDE Monitors

1 Day Initial and refresher

Automated Entry Control

System Administration

Training

Primary and Alternate

Monitors

1 Hour Initial and refresher

Supply Management

Training – Equipment

Management System

Primary and Alternate 1 Week – Supply Class

Block III / Online CBT

Initial and refresher

3.2 TECHNICAL SUPPORT

The goal of Technical Support is to provide and maintain fully functional equipment and systems for maximum mission effectiveness. The Contractor shall manage and perform technical support tasks and processes in a manner such that it achieves these goals. The Contractor shall work collaboratively with all other contractors and the Government toward the common goal of a fully operational technical systems and its equipment to also include support for maintaining a current DoD Information Assurance

Certification and Accreditation Process (DIACAP) Interim Authority to Operate (IATO) or ATO.

The Contractor shall provide technical support services for all equipment and systems. Several key areas, processes, and/or systems which require support include but are not limited to:

Key Personnel Duties

DISA Procedures

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

Maintenance

Technical Documentation

Reporting Procedures and Notices

Technical Tests, Checks, and Inspections

CSEL

Uninterruptible Power Supply (UPS) Support

3.2.1 Key Personnel Shifts and Duties

The contractor shall provide 24 hours a day 7 days a week performance to include Federal holidays at the

Hickam side – JBPH-H, Hawaii. The following establishes minimum performance acceptability, per shift, but shall not limit the Contractor from exceeding the following shift performance acceptability or changing the length of time per shift. A shift schedule shall be provided, in writing, to the COR upon contract award and any changes thereafter must be made in writing within a reasonable time.

3.2.1.1. WATCH STANDING SHIFT REQUIREMENT A minimum of two (2) bodies are needed to properly man each watch standing shift.

3.2.1.2 WATCH STANDING SHIFT ONE (AM/PM) Plans network installations by studying customer orders, plans, manuals, and technical specifications; ordering and gathering equipment, supplies, materials, and tools, assessing installation site; preparing an installation diagram.

3.2.1.2.1 Establishes voice and data networks by running, pulling, terminating, and splicing cables;

installing telecommunications equipment, routers, switches, multiplexors, cable trays, and alarm and fire-suppression systems; building ironwork and ladder racks; establishing connections; programming features; establishing connections and integrations; following industry standards; activating remote access tools; coordinating with contractors.

3.2.1.3 WATCH STANDING SHIFT TWO (AM) Verifies classified and unclassified service by testing circuits, equipment, and alarms; identifying, correcting, or escalating problems. Documents network by labeling and routing equipment and cables; recording configuration diagrams and specifications.

3.2.1.3.1 Maintains network by troubleshooting and repairing outages; testing network back-up procedures; updating documentation. Maintains customer rapport by listening to and resolving concerns;

answering questions. Maintains safe work environment by following codes, standards, and legal regulations.

3.2.1.3.2 Updates job knowledge by reading technical publications stationed onsite.

3.2.1.4 WATCH STANDING SHIFT THREE (PM) Verifies classified and unclassified service by testing circuits, equipment, and alarms; identifying, correcting, or escalating problems. Documents network by labeling and routing equipment and cables; recording configuration diagrams and specifications.

3.2.1.4.1 Maintains network by troubleshooting and repairing outages; testing network back-up procedures; updating documentation. Maintains customer rapport by listening to and resolving concerns;

answering questions. Maintains safe work environment by following codes, standards, and legal regulations.

3.2.1.4.2 Updates job knowledge by reading technical publications stationed onsite.

3.2.1.5 Program Manager

The Contractor shall provide an onsite Program Manager, located at Hickam side of JBPH-H, responsible for the overall supervision and control of all Technical Control Facility Services required by this PWS.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3.2.1.5.1 The name of the Program Manager and alternates shall be designated in writing to the CO, FD, and Chief COR within 30 days prior to start of contract. Updated letters shall be provided within two (2) business days of appointment.

3.2.1.5.2 The Program Manager or alternate shall be available within 1 hour during normal Government duty hours (0730 – 1630, Monday – Friday) to discuss contract matters with Government personnel. After normal duty hours, the manager or designated alternate shall be available within one (1) hour. The

Program manager or alternate shall attend quarterly or as needed Multi-Functional Team meetings.

3.2.1.5.3 The Program Manager is required to meet with the CO, contract administrator, COR, and other

Government personnel when requested. The Contractor may request a meeting with the CO.

3.2.1.5.4 The Contractor shall record the minutes for meetings with the Government relating to this contract. The Contractor shall coordinate the minutes with the Chief COR prior to finalizing, publishing, and distributing meetings minutes to all attendees within 5 business days.

3.2.1.6 Communications Circuit Control Office (CCO) Duties

The Contractor shall perform the duties of a Communications Control Office. The CCO shall exercise technical supervision over assigned GIG trunks and circuits. In order to ensure that transmission facilities provide maximum quality service to users of the GIG, it is necessary the CCO be notified of all fault isolation, alternate routing, realignment, and changes to in-station configurations of any GIG trunk or circuit in CCO responsibility. The CCO will be notified by the GIG station initiating action or identified problem. Responsibilities of the CCO/CMO shall follow tasking detail in Chapter 3 of DISACPAC 310-

70-1 Sup 1. Performance monitoring, testing and monitoring of parameters, threshold violations, alarm status, error rates, and other such indicators of transmission media performance. CMO and CCO duties are similar control offices within this Technical Control Facility. Processes in responsibility are similar to

CCO in that it is assigned to the Technical Control Facility when the trunk or circuit physically traverses in or near the site. Usually the Node Site Coordinator is assigned as CMO, and since CCO duties are similar, both CCO and CMO shall maintain a focal point on site. Reference: DISAC 310-70-1 and supplements.

3.2.1.6.1 The Contractor is responsible for initially activating the trunk or circuit, accepting leased service on behalf of the U.S. Government, and submitting appropriate completion reports required by the TSO issuing authority.

3.2.1.6.2 Immediately upon receipt of a TSO, or no later than five working days prior to the service date prescribed in the TSO, ensure that each facility, user terminal, and commercial vendor involved must be ready to provide the required service.

3.2.1.6.3 The Contractor shall ensure the completion of all initial quality control tests, direct necessary adjustments, and ascertain that the trunk or circuit meets the specified technical schedule before acceptance.

3.2.1.6.4 Prepare and submit completion reports for which control responsibility has been assigned.

Immediately advise the TSO issuing authority and all other addressees on the original TSO of any conditions, which might affect service activation.

3.2.1.6.5 Ensure service reports (i.e., delay, exception, or in-effect) are submitted in accordance with

DISAC 310-130-1.

3.2.1.6.6 The working duties of the CCO/CMO shall not be cross utilized to perform Watch Stand duties.

3.2.1.7 DISA Node Site Coordinator (NSC)

The Contractor shall perform the duties as NSC for DISA. DISAC 310-55-9 outlines specific node site administrative requirements and procedures and describes node site features. The NSC will have a designated alternate NSC and may delegate some tasks to the alternate; however, the NSC is responsible

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

for all network node site matters. NSC functions may be augmented by Service Level Agreements (SLA), Memorandum of Agreement (MOA), Memorandum of Understanding (MOU), and/or other support agreements. A complete listing of NSC responsibilities is outlined in DISAC 310-55-9. Also, refer to

DISAC 310-70-1 and supplements.

3.2.1.7.1 The working duties of the NSC shall not be cross utilized to perform Watch Stand duties.

3.2.1.8 Circuit Actions Officer

The Contractor shall ensure all transmission media and interface equipment meet, and be maintained in accordance with GIG performance standards. Any portion of a system or circuit that fails to meet GIG performance standards must be corrected prior to acceptance. If the system or circuit is accepted with exceptions, the cause must be annotated and appropriate action taken to correct the exceptions or obtain a waiver from the appropriate DISA Allocation and Engineering (A&E) activity. Each circuit installed in the GIG shall be tested in accordance with the criteria specified in the GIG Technical Schedule for the type of circuit (circuit parameter code) in the TSO, SAM. Reference: DISAC 310-70-1 Chapter 2 and

Chapter 8 & LINK DISN Implementation Standards.

3.2.1.8.1 Troubleshooting Communications Trucks, Links, Systems, and Equipment.

The Contractor shall troubleshoot circuit, trunks, links, equipment, and systems. Take immediate action on any deterioration or failure of GIG systems, equipment, trunks, or circuits causing degradation to or loss of service to users of the GIG.

3.2.1.8.1.1 The Contractor shall coordinate with the DISA, adjacent facilities, using agencies, maintenance agencies, and commercial vendors to effect restoration of service and isolation and repair of the fault. Telecommunication Service Priority (TSP), the TSP system ensures priority treatment of our nation's critical telecommunications services. Individual circuits are restored in accordance with their assigned National Communications System (NCS) TSP level. Refer to DISAC 310-70-1 and supplement.

3.2.1.8.1.2 The Contractor shall not allow outages or troubleshooting deferment to another shift due to insufficient manning. Ref: DISAC 310-70-1.

3.2.1.8.2 Tactical Circuits

The Contractor shall provide assistance and direction to personnel of tactical units when interfacing with the GIG. Follow the guidelines, procedures, and responsibilities to support the interface of tactical and

GIG technical controls and patch and test facilities. Refer to DISAC 310-70-1, Chapter 5, para C5.5.

3.2.1.8.3 Commercially Leased Circuits

The Contractor shall coordinate circuit actions for those circuits provided by commercial carriers.

Defense Commercial Communications Acquisition Procedures, is the prescribing directive for leasing commercial circuits IAW DISAC 310-70-1 Chapters 6 and 10.

3.2.1.8.3.1 The Contractor shall submit DD Form 1368 (Modified Use of Leased Communication

Facilities) on leased circuit outages. Submit DD Form 1368 to Defense Information Technology

Contracting Organization Pacific Air Force (DITCO-PACAF). Refer to DISAC 310-70-1.

3.2.1.8.4 The working duties of the Circuit Actions Officer shall not be cross utilized to perform Watch

Stand duties.

3.2.1.9 Equipment Custodian

The Contractor shall assign a primary and alternate equipment custodian, and ensure equipment issued and listed is properly controlled and accounted for IAW Air Force Supply Management Publications.

Reference: AFI 23-101 Air Force Materiel Management Procedures & AFMAN 23-122 Materiel

Management Procedures & AFH 23-123 all volumes.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3.2.2 DISA Procedures and Coordination

3.2.2.1 Contingency Operations Restoral Plans

The Contractor shall implement DISA restoral plans, local restoral plans (LRPs), and Minimal Essential

Circuit Listings (MECLs) as directed by the DISA element or Facility Control Office (FCO)/Network

Control Operations (NCO). Assist in the development of DISA R-Plans and MECLs when requested by

DISA. Develop LRPs. Perform periodic review of all restoral plans and ensure corrections are provided to the DISA element and to the appropriate DCC/DNC. Maintain current copies of these plans. Each TCF must have documented plans available that provide precise actions. Ref: DISAC 310-70-1, and supplements.

3.2.2.2 Subordinate Patch and Test Security

The Contractor shall exercise technical control coordination and supervision over subordinate GIG facilities, transmission systems, trunks, and circuits. Submit outage reports in accordance with DISAC

310-55-1. Coordinate troubleshooting with the Patch and Test Facility (PTF). Coordinate with PTF personnel when an after duty PTF related outage occurs. The PTF is manned normal duty hours, Monday

– Friday 0730 – 1630 (Hawaii Standard Time), a standby person is on call at all other times. Reference:

DISAC 310-70-1, and supplements, in addition Organizational Standby and Local Help Desk/Central

Focal Point procedures apply.

3.2.2.3 Bulk Encryption

The Contractor shall ensure bulk encryption is included as part of each Military Departments O&M

OPSEC, COMSEC, and inspection programs. Compliance with these requirements and procedures will be reviewed during DISA Performance Evaluations and included in COMSEC review/inspections. Refer to

DISAC 310-70-1, supplements, and AFI 33-283.

3.2.2.4 Authorized Service Interruptions (ASI)

The Contractor shall request a scheduled outage to perform necessary repairs, cutovers, power improvements, quality control testing, etc. In the event a scheduled outage is necessary, the Contractor shall do the following:

3.2.2.4.1 Submit a request to the appropriate DISA element IAW DISAC 310-70-1 and supplement and

310-55-9 and 310-55-1.

3.2.2.4.2 Plan interruptions as far in advanced as possible to minimize inconvenience to users or disruption in mission.

3.2.2.4.3 Ensure appropriate approval is received prior to scheduled outage.

3.2.2.5 Technical Control Meetings and Site Visits

The Contractor shall meet with DISA engineers to coordinate installations, upgrades, power requirements, TSO actions and any other DISA requirements. The Contractor shall assist in submitting work order requirements through Project Management 747CS/SCX office, or Facility Manager to posture the facility for any project changes or upgrades. (E.g. submit TF-1 Form for equipment power and environment requirements). Refer to NAVFAC Facility Handbook/Webpage. Reference DISAC 310-70-58 DISN

Commissioning Program Pacific.

3.2.3 Maintenance

The Contractor shall determine the priority of maintenance on all equipment supporting GIG and DII operations; ensure corrective maintenance is performed in the order dictated by the National

Communications System/Telecommunications Service Priority (NCS/TSP) system of the trunks or circuits that are degraded.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3.2.3.1 Maintenance Management

The Contractor shall establish a maintenance management function following guidance in AFI 21-103, AFI 21-109, AFI 33-150 & Methods and Procedures Technical Order 00-33A-1001 Para. 1.5 as it applies to only AF equipment, otherwise DISA guidance applies.

3.2.3.2 GIG and DII Maintenance

3.2.3.2.1 Ensure maintenance schedules are coordinated with affected facilities, personnel, and GIG operations. Perform appropriate quality control tests when equipment is returned from maintenance, before putting it back into operation.

3.2.3.2.2 Ensure maintenance technicians obtain approval from the TCF shift supervisor before any equipment in support of the GIG is taken off-line for maintenance, or before any on-line maintenance is performed.

3.2.3.2.3 When the Contractor is replacing cards, the Contractor must ensure the cards are properly configured. This information is especially critical for TDM and data transmission equipment that have specific protocols and interfaces. Refer to DISAC 310-70-1, Chap. 2, 5, &8, and DISAC 310-65-1.

3.2.3.3 Preventive Maintenance

The Contractor shall adhere to an organized and systematic approach that ensures marginal components, parts, and assemblies are discovered or their failure predicted to allow corrective actions to begin and prevent failures that could be anticipated as well as prevent degradation in the equipment and subsystems covered in this contract. This concept follows a Preventive Maintenance Inspection (PMI) plan that allows corrections to be made before part, subsystem, or equipment failure.

3.2.4 Technical Documentation

3.2.4.1 Technical Order Library

Technical Order library is an essential program to maintain critical information needed for guidance in operations of a Communications Site such as the Technical Control Facility. The Contractor shall be responsible for creating and or maintaining the Technical Order Library used to maintain and repair systems and equipment, to include test equipment, methods and procedures for maintenance, and other pertinent programs such government and commercial equipment protection, historical records, and drawings. Reference TO 00-33A-1001.

3.2.4.1.1 Coordinate for/establish/obtain working/field copies for all publications required to perform tasks detailed in this PWS. Temporary removal of master documents may occur as needed to ensure mission accomplishment.

3.2.4.1.2 Ensure working/field copies of publications, technical orders, commercial manuals, and any other non-AF publications required for specified tasks are maintained for currency and are in usable order. The unavailability or noted inaccuracy of any publication does not constitute a reason for noncompliance within the requirements of this PWS.

3.2.4.1.3 Ensure that copies of documentation received directly through acquisition/procurement processes are incorporated into the Technical Library.

3.2.4.1.4 Submit T.O. Change Requests via USAF Form Air Force Technical Order (AFTO) Form 22, Technical Order Publication Improvement Report, NOT LATER THAN 30 days after the discovery of a

T.O. discrepancy to update and/or correct publications.

3.2.4.1.5 Document noted discrepancies in working/field copies of commercial or non-commercial documents by Contractor format change pages at the front of the affected document. Provide a copy of change page(s) to the librarian in order to update Technical Library copy.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3.2.4.2 System Diagrams

Diagrams shall depict signal flow through the facility readily available in the operations area of the TCF to aid circuit restoration and troubleshooting efforts.

3.2.4.2.1 The Contractor shall maintain specific systems diagrams. These diagrams must include interface, multiplex, timing, and transmission equipment configurations that indicate the required frequencies, TLP, signal levels, and noise levels for analog transmission media. Digital transmission media must include bit rates, bit error rate specification, and timing and sync information. Reference:

DISAC 310-70-1, Chapter 2, para. C2.2.2.7.

3.2.4.3 Restoration Priority List

The Contractor shall establish and maintain a list of equipment, systems, software and circuits stipulating their priority for the Contractor’s attention should failure or problems occur. The Restoration Priority List is established by the Circuit Actions Officer in coordination with the base customers.

3.2.4.4 Labeling

The Contractor shall label all patch bays, test boards, or other circuit access points used by technical control personnel. Labeling must include the last four characters of the circuit Command

Communications Service Designator (CCSD) and the NCS TSP circuit restoration priority. If a NCS TSP is not assigned, then the letters "NA" (none assigned) must be entered with the CCSD to indicate that the circuit has no assigned restoration priority. Ref: DISAC 310-70-1, Chap. 2, para. C2.4.21.

3.2.5 Reporting Procedures and Notices

3.2.5.1 Auxiliary Electric Power System Reports

The Contractor shall administer Auxiliary Electric Power System Exercise reports. The report(s) shall, at minimum, include start and stop times, problems occurred, corrective action taken will be recorded in the

Master Station Log and in any other files as Agency, Service, and etc. directives prescribe. The

Contractor shall report auxiliary power system exercise failures to the DISA-PAC DNC. Follow procedures outlined in DISAC 350-195-2.

3.2.5.2 Technical Controller Notices

The Contractor shall immediately publish and post in the MSL to Hickam Technical Control personnel on all shifts. DISAC 310-70-1, para. 2.4.23.

3.2.5.2.1 Notices, at minimum, shall include additions, deletions, or changes in circuitry and equipment, special missions being supported, special tests on circuits or equipment, changes in operational procedures, and any upcoming authorized outages.

3.2.5.3 Facility Status Reports

The Contractor shall complete status reporting for the TCF. Status reports shall include status of facilities, transmission links, trunks, and circuits in accordance with DISA reporting directives.

3.2.5.3.1 Submit DISA Status reports IAW DISAC 310-55-1 and DISA area supplements. See DISAC

310-55-1.

3.2.5.4 Organization Mission Status Reports

The Contractor shall report Mission Status via current medium (database, slideshow, etc.) determined best by the Communications Leadership.

3.2.5.4.1 Contractor shall use a professional format (e.g. Microsoft Power Point) and provide a brief to military leadership. This can be in a form of a Weekly Activity Report, where the information shall contain at minimum listed in Appendix 1.

DRAFT PERFOMANCE WORK STATEMENT 5 JAN 2018

3.2.5.4.2 The Contractor shall attend the unit mission status briefing 1 time per week unless otherwise required, to advise the commander/leadership on the status of major circuit, trunk, link, and facility outages/HAZCONs and concerns. Also, attend flight briefing once a week as required.

3.2.5.5 GIG Facility and Link Reports

The Contractor shall maintain a copy of the latest facility reports printout. Review semi-annual printout to ensure accuracy and immediately report any inaccuracies to DISA-PAC.

3.2.5.5.1 Submit facility report, within 5 working days, of any major changes (site, facility, or link is activated/deactivated, or organizational changes are made), or within 15 working days when equipment status, building/room numbers, or link capacity changes.

3.2.5.5.2 Submit negative report if no change occurred in the last 180 days.

3.2.5.5.3 Submit reports to FCO Hawaii reference DISAC 310-55-9; 310-70-1, Chap. 2, para. C2.3.4, DISA area supplements, and FCO instructions.

3.2.5.6 Monthly Status Report (MSR)

The contractor shall document the efforts performed in the completion of the above tasks in a detailed

MSR, which shall be submitted to the COR for review and acceptance. All reports, documents, papers, and briefings, must be coordinated/approved by the COR. The Monthly Status Reports will be submitted as soft copy deliverable via the Wide Area Work Flow (WAWF) as an attachment to the monthly invoice.

The MSR must include:

LEAVE OR ABSENCES THIS PERIOD: Document any leave or absences taken during this…