PWS_30Mar13.doc

Solicitation No. FA5215-13-R-0002

Contract No. FA5215-13-C-XXXX

Technical Control Services Solicitation No. FA5215-13-R-0002

Contract No. FA5215-13-C-XXXX

Technical Control Services

Performance Work Statement

Technical Control Services 20 March 2013 Table of Contents

31.1

OVERVIEW

31.2

SCOPE

1.3

OPERATIONS SUPPORT

1.4

TECHNICAL SUPPORT.

Service Summary (Section 2) 222.1 Service Matrix

222.2 Overall Objective Performance Standards

Government Inventory (Section 3) 3.1 Government Inventory General Information (Section 4) 4.1 Hours of Operation 4.2 General Housekeeping 4.3 Base Security Requirements 4.4 Contractor Personnel

APPENDIX 1 TERMS AND DEFINITIONS

APPENDIX 2 ACRONYMS

APPENDIX 3 WORKLOAD ESTIMATES

APPENDIX 4 APPLICABLE DIRECTIVES AND PUBLICATIONS

APPENDIX 5 REQUIRED REPORTS AND FORMS

Technical Control Appendix 6 Support Agreements

APPENDIX 7 CONTINGENCIES, INSPECTIONS, AND EXERCISES

Description Of Services (Section 1) 1.1

OVERVIEW

1.1.1 Mission 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 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.

The 747th Communications Squadron (747 CS), USAF, Pacific Air Force, (PACAF) is charged with ensuring the delivery of communications and informational capabilities to enable Headquarters Pacific Air Forces, 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. The communications squadron workforce includes approximately 200 enlisted, officers, contractors and civil service employees with 18 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 million dollars worth of antennas and satellites provide technical support for over 500 tenant users, and monitoring and managing a base network worth over $16 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 Defense Information System Network (DISN) equipment and personnel. These facilities take into consideration the non-GIG tactical missions of the military departments (MILDEP5) 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.

1.1.2 Purpose of Performance Work Statement

This Performance Work Statement (PWS) establishes the requirements and responsibilities of the Contractor to provide Pacific Air Forces (PACAF) specific requirements for Technical Control Services of materials, facilities, and infrastructures in support of Technical Control Services. 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.

1.2

SCOPE

1.2.1

PROGRAM MANAGEMENT

1.2.1.1 Contract Performance Management

The Contractor shall be responsible for all aspects of contract performance and provide stewardship of Government resources. The Contractor shall provide a responsive and proactive organization that is trained to perform at a proficient skill level.

1.2.1.2 Program Management Plan

The Contractor shall submit a Program Management Plan (PMP) to the Contracting Officer (CO), Functional Director (FD), and Chief of Contracting Officer Representative (COR) 10 working days after receipt of award.

(a) The plan shall be in Contractor format and conform to the following:

i) The plan shall identify with the preparing office or Contractor’s title, the identifying numbers or designators of the contract, the identity of the program, the security classification, and the Government activity issuing the controlling contract.

ii) The plan may include descriptive material such as graphs, worksheets, tables, etc. as required to clarify and or illustrate matters within the text.

iii) The plan shall be legible and reproducible.

(b) The plan shall consist of as a minimum:

i) Contractor’s organizational structure, assignment of functions, duties, and responsibilities.

ii) Contractor’s procedures, policies, and the reporting requirements that are established for the initiation, monitoring, control, completion, and reporting of contractual tasks, projects, and programs;

iii) Contractor’s Phase-out plans;

iv) Contractor’s maintenance plans;

v) Contractor’s security program and procedures;

vi) Contractor’s quality control programs;

1.2.1.3 Program Manager

The Contractor shall provide a Program Manager, located at Hickam side of Joint Base Pearl Harbor – Hickam, responsible for the overall supervision and control of all Technical Control Services required by this PWS.

(a) 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.

b) 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.

1.2.1.4 Meeting with Government

The Contract Manager is required to meet with the Contracting Officer, contract administrator, Contracting Officer Representative (COR), and other Government personnel when requested. The Contractor may request a meeting with the Contracting Officer.

1.2.1.5 Meeting Minutes

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.

1.2.2 Phase Out Plan

The Contractor shall provide a transition-out plan of 60 days and shall cooperate with, and assist, the new Contractor’s personnel to assure a thorough, smooth, and effective transfer to minimize loss of efficiency in support of the Government during the transition-out period. Cooperation and assistance shall be limited to guidance and advice, as well as support within the functions covered by the contract. The incumbent Contractor shall establish transition procedures with the new Contractor. Contractor shall ensure all government inventory, information, and processes are accounted for clearly and enabled to be properly transferred to the Successive Contractor. The transfer of all non-proprietary property and processes shall occur between the Incumbent Contractor and Successive Contractor without work stoppage.

1.2.3

FINANCIAL MANAGEMENT

1.2.3.1 Wage Determinations/CBA

Wage determination adjustments through Collective Bargaining Agreement shall be identified to the Government for Government audit approval. The Collective Bargaining Agreement must be signed by the successor contractor and be provided to the CO within 30 days of contract start. The Contractor shall assess potential impacts of future cost increases (if any) and provide the Government options to offset the increases to stay within original contract costs.

1.3

OPERATIONS SUPPORT

1.3.1 Aspects of 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 Technical Control systems.

1.3.2 Operations Support Services

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

Configuration Support

Uninterrupted Power Support

Operations Planning and Scheduling

Training and Certificates

Administrative and Records Keeping

Security Programs, Controlled & Restricted Areas

1.3.2.1

Configuration Support

The Contractor shall maintain accurate hardware and software (HW/SW) listings and configuration documentation for all Technical Control systems as applicable. The Contractor shall provide detailed and accurate documentation and updates to equipment HW/SW changes as a result of Contractor initiated actions or on-going upgrades/modifications to Technical Control systems. To ensure success of Technical Control program, the Contractor shall:

(a) Ensure documentation submissions do not exceed 45 days from any change, to include System Configurations, Physical Configurations, and or Software Configuration changes.

(b) Ensure that a configuration baseline on command supported systems is maintained for all software, firmware, and hardware provided as a part of this contract.

(c) Develop (or leverage existing systems) and maintain an electronic method to categorize, organize, and present configuration information files (AutoCAD drawings, Word, Excel, PDF documents, photos, etc.) such as searchable database or webpage.

(d) Participate in Government-sponsored quarterly configuration control board(s). Contractor shall provide:

Summary review of open action items and their status

Summary review of Contractor’s CM actions for previous quarter

Submit any new action item

Meeting minutes

A technical report, as required

(e) Perform configuration audits as a minimum, annually. Results of audits, to include discrepancies and their corrective actions shall be provided to the Government via technical reports 1.3.2.2 Uninterrupted Power Support The Contractor shall immediately notify the Uninterruptible Power Supply (UPS) coordinator when the UPS in room 120 and/or room 101 alarms. The Contractor shall respond to the alarm by investigating the alarm panel of the UPS system and if alarm is determined to be a true outage, the Contractor will start the repair process by contacting the phone numbers provided. The Contractor shall perform battery inspections on the station UPS in room 120 in accordance with DISAC. Refer to DISAC 350-195-2, see appendix 4.

1.3.3

OPERATIONS PLANNING AND SCHEDULING

1.3.3.1 Planning and Scheduling

The Contractor shall coordinate and participate in meetings with 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

1.3.3.2

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.

(a) 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.

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

(c) Upon successful completion, the Contractor shall provide the 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.

(d) 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.

(a) – Training Chart

Security Training AFI 31-401; 31-501

Anti-Terrorist Force Protection

1.3.4

ADMINISTRATIVE AND RECORDS KEEPING

The Contractor shall be responsible for creating, maintaining, and coordinating records that are specifically cited in Appendix 5, Required Reports and Forms, and per the guidance as stated below.

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

(b) EMAIL ACCOUNTS. The Contractor shall administer and maintain e-mail accounts set up for Circuit Actions and Operations on a daily basis on both the NIPR and SIPR Networks. E-mail accounts are used for service provisioning records i.e. (TSR, TSO, SAM, RFS, In-effect reports, delayed service reports, exception reports, Authorized Outage messages, DISA directives, and etc.) Currently there are a minimum of two email accounts in this category required.

(c) CLASSIFIED MESSAGES. The Contractor shall be qualified to pick up classified messages at the COMSEC Facility or designated location. Messages can also be obtained via SIPRNET.

(d) DISA GENERAL MESSAGES. 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 210-70-2.

(e) USER NOTIFICATION LETTERS. The Contractor shall send GIG user notification letters to each user upon activation of a new circuit, and annually thereafter. An updated letter will be sent any time information contained in the letter 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

(f) DISA REFERENCE LIBRARY. The Contractor shall maintain a current DISA reference library readily accessible to the technical controllers, to include all technical orders 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. Reference DISAC 310-70-1, Chap. 2, para. C2.3.17, C2.4.22; Chap. 9, para. C9.5 1.3.4.1 Record 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-322, HQ PACAF 33-322 Sup 1, AFI 37-138, AFMAN 37-139, AFI 33-332, DOD 5400.7-R/AFSUP.

All official records as defined in are the property of the U.S. Government and shall remain so at all times.

The Contractor shall comply with AFI 33-322, Air Force Records Management Program, by using the current computer based system available and/or as defined by the Air Force (IAW AFMAN 37-123).

A Records Custodian (RC) and a Chief of Records (COR) shall be appointed in writing and shall receive required training by the Government, within 30 days of the effective date of the contract, (see paragraph 1.3.3.2.e).

The Contractor shall provide the 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.

1.3.4.2 Circuit Layout Records The Contractor shall conduct and maintain Circuit Layout Records (CLRs) in accordance with DISA CIRCULAR 310-70-1, Chapter 2, para. C2.2.2.8 to C2.2.2.10, and the following summarized guidelines:

a) 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.

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

c) 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.

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

e) 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.

1.3.4.3 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 CCO/CMO or servicing TCF. Documentation must be kept on record for 1 year and in accordance with DISAC 310-70-1 Chap. 9, para. C9.4.

a) 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.

b) 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 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.

c) 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.

d) 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.

e) Files shall include copies of the quality control waiver requests and approvals, any appropriate documentation (i.e., 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

1.3.4.4 Communications and Information System Records The Contractor shall maintain and file the Communications and Information Systems Records (commonly known as plant-in-place records or as built drawings). Review of each records normally performed annually.

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

b) 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.2.1.

1.3.4.5 Automated Record Keeping

The Contractor may use any 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:

a) 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.

b) 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.

c) 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.

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

e) 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 RFO code and location, and a brief narrative RFO.

1.3.4.6 Master Station Log (MSL)

The MSL, DD form 1753, is the official narrative record maintained to record significant events (e.g., power failures, complete system outages, major equipment outages or impairments such as 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 made in chronological order, see Appendix 5, Required Reports and Forms. Reference DISAC 310-70-1, Chap. C2. para. C2.3.6, Chap. 5, para. C5.4.5, Chap. 9, para C9.1.5.

a) 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.

b) 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 DISAC 310-70-1, (Currently MSL is automated using FACIT Program, however, the Contractor will follow FCO and DISA instructions on the specific program to use).

1.3.5

SECURITY PROGRAMS, CONTROLLED & RESTRICTED AREAS

1.3.5.1 Security Programs The Contractor shall adhere and enforce Department of Defense Security Programs, including Department of the Air Force and Navy Instructions pertinent to protecting the Technical Control Facility’s structure and operational mission.

a) Post and report statuses of Force Protection Condition (FPCON) signage on main entry ways IAW checklists as directed by the JBPHH Installation, HQ Pacific Air Force, and Communications Instructions for real world and exercise scenarios.

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

c) 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.

d) The Contractor shall have access and be trained to perform administrative tasks for the Facility Automated Entry Control System Administrative to resolve restricted area badge issues and information updates for all facility personnel after duty hours.

e) The Contractor shall ensure the AECS information 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 Do.D related instructions and manuals.

1.3.5.2 Escort Duties The Contractor shall provide 24/7 escort services for visitors requiring within Technical Control facility 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.

(a) 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.

(b) 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.

(c) Use and maintain AF Form 1109, Visitor Register Log. Security and escort duties listed above shall be followed IAW: AFI 31-101, PACAF Sup 1 to AFI 31-101, 15AB 31-101, 15AW Installation Security Instruction (ISI), 15AB Installation Security Plan (ISP).

1.3.5.3 DD Forms 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).

1.3.5.4 COMSEC Account

The Contractor shall maintain the Communications Security (COMSEC) Account 632310, Sub-Account E-21, strict adherence shall apply but not limited to the following guides and instructions: COMSEC User Instructions, Responsible Officer Users Guide, STE Users Guide, AFI 33-201 Vols. 1. 2, 4, 5, 7, and 9, and AFKAG-1M, AFI 33-211, AFI 33-215. AFI 33-230 and AFSSIs 3013, 3017, 3031, 3052, 3035, 3041, and 4212. The Contractor shall provide timely safe inspections, maintenance, and shall change the COMSEC safe combination IAW: AFI 33-201 and AFKAG-1M.

1.3.5.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.

a) 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, Entry Authorization Letter (EAL), and/or appropriate security documents/clearances.

b) 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-Series.

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

1.3.5.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.

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

b) The Contractor shall attend meetings to discuss problems and improvements to the facility or security structure surrounding the building. Reference: AFI 31-101, PACAF Sup 1 to AFI 31-101, 15AW 31-101, Installation Security Instruction (ISI), Installation Security Plan (ISP).

1.4

TECHNICAL SUPPORT.

1.4.1 Sustainment Goal

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 DIACAP Interim Authority to Operate (IATO) or ATO.

1.4.1.1 Technical Support Services

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:

Maintenance

Preventive Maintenance

Maintenance Management

Combat Survival Evader Locator

Technical Order Library

Reporting Procedures and Notices

Technical Inspections, Checks, and Acceptance Key Personnel Duties DISA Procedures

1.4.2 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.

(a) 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.

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

(c) 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 and DISAC 310-65-1, DISAC 310-130-2, DISAC 310-130-4, and DISAC 310-D70-30.

1.4.2.1 Preventative 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 plan that allows corrections to be made before part, subsystem, or equipment failure.

(a) All PMIs shall be performed on a non-interference basis with scheduled training operations. PMIs may be performed on scheduled systems between missions if the PMI can be performed without interruption to scheduled operations.

(b) The Contractor shall report the cause, Estimated Completion Date (ECD), and action taken to prevent reoccurrence when PMIs with a frequency of 14 days or more are deferred more than once. The Contractor shall place such equipment in RED status when this occurs and the equipment will not be operated until the PMI(s) are completed.

(c) The Contractor shall include summaries of missed PMIs, the status of applicable system(s), and projected get-well dates in its Monthly Status Report.

1.4.2.2 Maintenance Management The Contractor shall establish a maintenance management function using AFI 21-101, AFI 21-103, AFI 33-150 & Methods and Procedures Technical Order (MPTO) 00-33A-1001, AFI 21-303, and PACAF Supplements as guidance.

1.4.3 Combat Survival Evador Locator (CSEL) The Contractor shall perform 24/7 monitoring operations on the CSEL remote alarm. If the alarm is activated or Contractor is otherwise notified of anomalous condition, the on-duty personnel shall respond to UBS failure in accordance with the checklist derived from Air Force Technical Manual 31R2-2GRC242-1.

(a) When notified or alarmed of an anomalous condition, the Contractor shall complete the actions required by the checklist within 30 minutes of alarm or notification.

(b) The Contractor shall immediately notify the Tier-Two Maintenance (TTM) support personnel that a fault has been detected and report the identified actions accomplished to restore function or continued failure.

(c) The Contractor shall participate in CSEL-provided on-site training - 1 day with 3 to 5 students (more days available as needed by the TCF). Reference: 747 CS and CSEL Program Office Memorandum of Understanding.

1.4.4 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 as specifically cited in Appendix 4 and Appendix 5.

(a) 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.

(b) 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.

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

(d) 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.

(e) 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.

1.4.4.1 System Diagrams

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

(a) The Contractor shall maintain specific systems diagrams. These diagrams must include interface, multiplex, timing, and transmission equipment configurations that indicate the required frequencies, transmission level point (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: DISA CIRCULAR 310-70-1, Chapter 2, para. C2.2.2.7.

1.4.4.2 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 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.

1.4.5 Reporting Procedures and Notices 1.4.5.1 Auxiliary Electric Power System Report(s)

The Contractor shall administer Auxilliary 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.

1.4.5.2 Technical Controller Notices The Contractor shall immediately publish and post in the MSL to Hickam Technical Control personnel on all shifts.

a) 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.

1.4.5.3 Facility Status Report(s) 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.

a) Submit DISA Status reports IAW DISAC 310-55-1 and DISA area supplements. See DISAC 310-55-1 Table T1.1 Summary of Reportable Conditions 1.4.5.4 Organization Mission Status Report(s) The Contractor shall report Mission Status via current medium (database, slideshow, etc.) determined best by the Communications Leadership.

a) 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 ii. below.

b) 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.

1.4.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.

a) 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.

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

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

1.4.6

TECHNICAL INSPECTIONS, CHECKS, AND ACCEPTANCE

1.4.6.1 Test and Accept (T&A) The Contractor shall supervise installation and T&A team responsible for accepting GIG communications systems and subsystems. The Contractor shall perform T&A on all GIG circuits, and trunks assigned parameter codes. The CCO assigned in the TSO is responsible for ensuring T&A testing is completed. Refer to DISAC 310-70-1 Chap. 6 & 10 for T&A of government-owned circuits and commercially leased circuits.

1.4.6.2 Quality Control (QC) Test(s) The Contractor shall perform quality control (QC) tests and measurements on all trunks, channels, circuits, and equipment for which the TCF is responsible. To include: In-service QC’s, out-of-service QC’s, and equipment QC’s.

1.4.6.3 Alarm Checks The Contractor shall, at the beginning of every shift change, conduct a station walk through inspection to check for alarms and annotate the results of this check on the Master Station Log (MSL):

a) Racks and Equipment containing cryptographic devices, power supplies, and the Clock Distribution System (Global Positioning System (GPS), CDS-10, 56000, etc).

b) The Contractor shall respond walk up to equipment and investigate the CSEL alarms and contact the CSEL Technician within 30 minutes (refer to CSEL Tier One and Two Maintenance Memorandum of Understanding), and the UPS outages reported to the UPS QAE or UPS Contract Help Desk immediately. Reference: References: 310-70-1.

1.4.6.4 Test, Measurement, and Diagnostic Equipment (TDME) The Contractor shall maintain a Test, Measurement, and Diagnostic Equipment (TMDE) account IAW T.O.s 00-20-14,00-33A-1001, and local Precision, Measurement, and Equipment Laboratory policies.

a) If PMEL cannot calibrate a certain piece of equipment, Test Sets, etc., the Contractor shall send the test equipment to the manufacture or vendor for calibration at the Contractor’s expense.

b) The Contractor must maintain an up-to-date status of available test equipment with calibration status, and actively pursue replacement of non-available test equipment.

1.4.7

PERSONNEL DUTIES.

1.4.7.1 Shifts

The contractor shall provide 24 hours a day 7 days a week performance to include Federal holidays at the Hickam side – Joint Base Pearl Harbor Hickam, Hawaii. The following establishes a 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 Contracting Officer Representative upon contract award and any changes thereafter must be made in writing within a reasonable time.

a) 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.

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.

b) 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.

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.

Updates job knowledge by reading technical publications stationed onsite.

c) 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.

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.

Updates job knowledge by reading technical publications stationed onsite.

1.4.7.2 Communications Control Office (CCO) Duties The Contractor shall perform the duties of a CCO. The CCO shall ensure that transmission facilities provide maximum quality service to users of the GIG, testing and monitoring of parameters, threshold violations, alarm status, error rates, and other such indicators of transmission media performance.

a) 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.

b) 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.

c) 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.

d) 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.

e) Ensure service reports (i.e., delay, exception, or in-effect) are submitted in accordance with DISAC 310-130-1.

1.4.7.3 NODE Site Coordinators (NSC) (DISA).

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 for all network node site matters. NSC functions may be augmented by 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.

1.4.7.4 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 AFMAN 23-110, AFI 23-111, and Air Force Supply Management Publications.

1.4.8

DISA PROCEDURES AND COORDINATION

1.4.8.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 Local Control Center (LCC)/Network Control Operations (NCO). Assist in the development of DISA R-Plans and MECLs when requested by DISA. Develop local restoral plans (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, Chap. 2 and 4.

1.4.8.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, Chap 1, para C1.5, and Chapter 2, Organizational Standby and Local Help Desk/Central Focal Point procedures apply.

1.4.8.3 Bulk Encryption The Contractor shall ensure bulk encryption is included as part of each Military Departments (MILDEP) O&M operations security (OPSEC), communications security (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, Chap. 4, para. C4.2 and AFI 33-201 and AFSSIs.

1.4.8.4 Authorized Outages

The Contractor or DISA may occasionally be required to 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:

(a) Submit a request to the appropriate DISA element or comply with the DISA request

(b) Plan interruptions as far in advanced as possible to minimize inconvenience to users or disruption in mission.

(c) Ensure appropriate approval is…