Current_PWS.docx

PERFORMANCE WORK STATEMENT

STATEMENT OF WORK

FOR THE

PERIMETER ACQUISITION RADAR ATTACK CHARACTERIZATION SYSTEMS (PARCS)

LOCATED AT

CAVALIER AFS

NORTH DAKOTA

Contract Number FA2517-09-C-8000

PARCS FA2517-09-C-8000

Attachment 3

DRAFT

11/03/2014 iv

PARCS FA2517-09-C-8000

PARCS FA2517-09-C-8000

PERIMETER ACQUISITION RADAR ATTACK CHARACTERIZATION SYSTEM

SERVICE REQUIREMENTS

CHAPTER 1

GENERAL REQUIREMENTS

1.1. SCOPE. Provide non-personal services to operate, maintain, and support (OM&S) the Perimeter Acquisition Radar Attack Characterization System (PARCS) site at Cavalier Air Force Station (CAFS), North Dakota. Services encompass base support including management of radar and mission computer maintenance, civil engineering, environmental functions, security, transportation, supply, fuels, sensitive and non-sensitive communications. Cavalier AFS receives limited support from Grand Forks AFB, located approximately 90 miles south of Cavalier. Contractor shall provide all necessary personnel, administrative, and managerial resources necessary on a continuous, 24-hours-a-day, 7-days-a-week (24/7) basis to meet Air Force Station operations and maintenance requirements as specified in this PWS. Support Radar Operational Time as specified in chapter 2 of the PWS. The Contractor shall also interface with other Contractors, and/or Government agencies in support of all programs and efforts dealing with evolution and/or operation of systems and equipment, as well as in providing day-to-day site support services.

1.1.1. SERVICE AREA. The service area as defined herein is for all areas within Cavalier AFS, ND, also referred to as “the site”, with the exception of areas identified within installation boundaries under the control of the privatized Military Family Housing contractor controlled areas. Points of Demarcation are identified in exhibit A, Points of Demarcation.

1.2. MISSION. The PARCS provides tactical warning and attack assessment of sea-launched and intercontinental ballistic missiles launched against the continental United States and southern Canada; continuously provides critical missile warning and space surveillance data to North American Aerospace Defense Command, United States Strategic Command and regional combatant commanders; and monitors and tracks earth-orbiting objects to enable space situational awareness and space control.

1.3. CONTINUANCE OF PERFORMANCE. In the event of a crisis declared by the President of the United States and/or the Secretary of Defense, the Contractor shall perform all the PWS requirements except the tasks in PWS Chapters 13, 14 and 15. The Contractor shall continue services through all Force Protection and Defense Conditions without interruption. In a time of crisis, other services to increase the security and well-being of the site may be required on a 24/7 basis as determined by the Site Commander (10SWS/CC) and directed by the Contracting Officer (CO) and will be funded via the applicable cost reimbursable contract line item number (CLIN).

1.3.1. Contingency Planning. The Contractor shall develop a contingency plan and provide to the CO prior to contract start; provide updates within 30 calendar days to the CO. The plan shall provide for continued operations and timely return of systems to operational status in the event of a declared crisis, catastrophic and non-catastrophic events and work stoppages for the site. Include all the PWS requirements identified in PWS para 1.1.above. The plan shall contain the following information at a minimum: contingency actions, emergency work requests, natural disasters, labor strike/personnel walk-off, contingency mobilization and mobilization recall commitments.

1.4. PROGRAM MANAGEMENT. The Contractor shall provide:

1.4.1. Records, Documentation, Deliverables and Compliance. The Contractor shall:

1.4.1.1. Records. Maintain all Government records in the format provided. Maintain all records generated in performance of PWS requirements in electronic format (Copyrighted materials are exempt) and make available for Government review upon request (see Chapter 13).

1.4.1.2. Documentation. Use the Contractor’s format for documentation (reports, logs, etc.) created in performance of PWS requirements.

1.4.1.3. Reports. Provide reports to the Government as specified in Appendix 6, Reports Cross Reference.

1.4.1.4. Compliance. Apply industrial and commercial best practices and comply with local, state and federal statutes in the performance of PWS requirements. The contractor shall comply with all referenced publications preceded by “in accordance with”, or “IAW”; the publications are incorporated by reference into the PWS and are cross-referenced in Section 4, Appendix 5 of this PWS.

1.4.1.5. Advise the Contracting Officer, Site Commander and Government PM, in writing, of any required support not reflected in support agreement FB4659-081010-428 with Grand Forks AFB.

1.4.1.6. Maintain all equipment IAW user manuals or technical orders (TOs).

1.4.2. Quality Control Program. The Contractor shall develop, implement and maintain a Quality Program that ensures that service delivery meets or exceeds performance requirements in the PWS. Implement the Quality program IAW a Quality Program Plan (QPP) that provides insight into the following quality processes: internal audits including procedures and oversight, identification of deficiencies, prevention of nonconforming services, and corrective measures if performance requirements are not attained.

1.4.2.1. Quality Program Documentation. The Contractor shall provide Quality Program documentation to the government upon request during the life of the contract. Records shall be maintained intact for the life of the contract.

1.4.2.2. Quality Status Report (QSR). The Contractor shall generate and distribute a QSR (See Appendix 6, R-1.1).

1.4.3. Outside Agency Support. The contractor shall provide technical assistance and advice to all other contractors or government agencies to support design, development, and installation of new facilities, systems, or equipment within the scope of this PWS.

1.4.4. Price Information Report. The Contractor shall submit Price Information Reports detailing prices for services (see Appendix 6, R-1.2).

1.4.5. Contractor Manpower Reporting. The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year.

1.5. PERSONNEL MANAGEMENT. The Contractor shall:

1.5.1. Site Manager. The Contractor shall provide an on-site manager or alternate(s) for continuous daily operation who shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract.

1.5.1.1. Ensure the Site Manager or alternate is available on-site during normal duty hours. After normal duty hours, the site manager or designated representative shall be physically on site to resolve any problems within 2 hours of notification.

1.5.2. Site Commander’s Authority. The Site Commander may direct the Contractor, in writing, to immediately remove any employee from any installation when retention of such employee endangers life, property or security.

1.5.3. Contractor Privileges. The Government retains the right to withdraw privileges authorized herein that are subject to abuse by Contractor employees or their dependents. Upon investigation of facts and circumstances of any incident, services or privileges may be withdrawn on a permanent or temporary basis, at the sole discretion of the site commander.

1.5.4. Contractor Identification. Employees shall identify themselves as contractor personnel by displaying appropriate badging. Contractor shall also identify themselves as contractor personnel in email correspondence, phone discussions and while attending meetings.

1.6. BRIEFINGS, MEETINGS, TOURS, AND ESCORTS. The Contractor shall provide support for the following on a non-interference basis to mission operations:

1.6.1. Participate in and provide briefings at monthly site management meetings with the site commander and staff. The purpose of these meetings is to discuss a broad range of contractual and performance issues. The government and contractor shall mutually agree on the meeting format and content.

1.6.2. The Contractor’s management staff shall support Government conferences, meetings, reviews, Multi-Functional Team (MFT) meetings, site orientations, and other interchanges.

1.6.3. Conduct site briefings and tours when requested by the site commander and provide technical orientation / familiarization briefings.

1.6.4. Provide escort support for Government-sponsored projects and services. Escort support shall be available for up to 8 hours a day, during normal duty hours.

1.7. BUDGET INFORMATION. The contractor shall participate in developing budget information including projected costs for unfunded requirements with justification and impact statements.

1.8. COPIER SUPPORT. The contractor shall provide copier support service for government owned copiers.

1.8.1. The contractor will provide one copier with the following minimum requirements: copy one and two sided; collate and staple; and scan to e-mail.

1.8.2. Maintenance requests are responded to within 1 workday. No copier will be inoperable for longer than 3 workdays, except when awaiting parts.

1.8.3. RESERVED

1.8.4. The Contractor shall provide copier paper and toner cartridges IAW Chapter 6, Supply Support.

1.9. TRAINING. The contractor shall fund all Contractor personnel training unless otherwise stated in the PWS. Government-unique training courses will be made available to Contractor personnel. Contractor shall pay for training expenses when employee turnover causes the need for repetition of Government-provided training within one (1) year of course completion.

1.9.1. Minimum Training. The Contractor shall train all government and contractor employees on the subjects below within the first three months of arrival on site and on annual basis thereafter:

1.9.1.1. Bomb threats, other terrorist threats and force protection training.

1.9.1.1.1. The contractor shall complete Government-provided Force Protection Training either on the Advanced Distribution Learning System (ADLS) or via computer based training at: https://atlevel1.dtic.mil/at/.

1.9.1.2. Hazardous materials and hazardous waste identification, management, storage, and disposal.

1.9.1.3. Work order and other civil engineering customer procedures.

1.9.1.4. Administrative telephone usage.

1.9.1.5. Local Area Network (LAN) usage and Information Condition (INFOCON) procedures.

1.9.1.6. Severe weather training.

1.9.1.7. Physical and communications security training.

1.9.1.8. Visitors to Upper Tier Maximum Permissible Exposure (MPE) Areas. The contractor shall inform visitors they may be entering an environment where the power density levels beyond the entry control point could be expected to exceed those levels normally found in their private domicile, but still within the safe limits for an Electro-magnetic Frequency (EMF) action level environment. Visitors shall be provided training which meets the requirements of AFI 48-109, paragraph 4.4.1.

1.9.1.9. Information Assurance and Awareness Program (IAAP)

1.9.1.10. Installation environmental management program.

1.9.1.11. Supply procedures.

1.9.1.12. Transportation and vehicle usage procedures.

1.9.1.13. RESERVED

1.9.1.14. Hazard Communication (HAZCOM) training (required prior to commencement of work).

1.10. Photo Badging System. Maintain photo badging system equipment and card readers IAW manufacturers’ recommended procedures.

1.11. Installation and Higher Headquarters Directed Exercises. The contractor shall participate in installation or higher headquarters directed exercises. The Site Commander will define the level of participation to meet mission objectives.

PARCS FA2517-09-C-8000

P00135

CHAPTER 2

RADAR OPERATIONS SUPPORT

2.1. GENERAL CONTRACTOR OPERATIONAL REQUIREMENTS. The contractor shall operate, maintain and employ site technical and support equipment to meet operational requirements defined in STRATCOM Directive (SD) 505-1 (S) Volumes (Vol) I and II.

2.2. EQUIPMENT AVAILABILITY. The contractor shall maintain an overall Radar Acc each calendar month of not less than 94% to meet mission operational Acc. Acc is expressed as a percentage (%) and represents that portion of time the system is performing its assigned missions based on Contractor liable downtime (CLD) relative to a specific operating time.

2.2.1. Acc Calculation. The Acc is calculated on a monthly basis as follows:

Where the terms of the equation are defined as follows:

2.2.1.1. Downtime. Any mission degradation that results in Operations Capability (OPSCAP) RED time.

2.2.1.2. Contractor Liable Downtime (CLD). All downtime except for the following:

2.2.1.2.1. Downtime scheduled in the Combat Capability Assessment Schedule (CCAS) and approved by the Installation/Site Commander and higher headquarters as being non-Contractor liable. Scheduled downtime is not counted against the Contractor (See PWS paragraph 2.2.1.3. Operating Time.)

2.2.1.2.2. Downtime caused by a Missile Warning Operations Center (MWOC) military personnel error.

2.2.1.2.3. Downtime due to a higher headquarters priority.

2.2.1.2.4. Spacetrack downtime due to Satellite Correlation Function (SCF) initialization following a normal system recovery, when the SCF initialization delay or the recovery itself is not due to contractor error.

2.2.1.2.5. Downtime due to hardwired delays in the computer initialization process after power is restored following a power outage, not to exceed 30 minutes during Radar Operational Time. Delays in radar and computer system initialization exceeding 30 minutes after restoral of full power will be assessed as contractor liable downtime.

2.2.1.2.6. Downtime caused by events outside the Contractor's control may be determined to be non-Contractor liable by the CO (with inputs from the Installation/Site Commander, MWOC Crew, Quality Assurance Evaluator (QAE), etc.). For example, downtime caused by unobtainable spare parts may be determined to be non-Contractor liable where the Contractor has attempted to keep adequate bench stock while properly planning ahead for parts deficiencies and using the procedures within the Standard Base Supply System (SBSS), but due to problems beyond the Contractor’s control, those parts have not been delivered.

2.2.1.3. Radar Operational Time. The amount of time the mission system is required to be available, defined as Y hours per day times the number of days in the month minus Contractor scheduled downtime.

Example: Month: April (30 days)

2.2.1.4. Acc Example. Using the data in PWS paragraph 2.2.1.3. for Radar Operational Time, and a CLD of 1 hour and 30 minutes (90 minutes) for April, here is the Acc calculation for April:

Acc = Radar Operational Time - CLD x 100 = Y - 90 x 100 = Z% Radar Operational Time Y

2.3. MISSILE WARNING OPERATIONS CENTER (MWOC) SUPPORT REQUIREMENTS. The contractor shall respond to the instruction of the MWOC Crew Commander (CMDR) or MWOC Crew Chief (CCH)

2.3.1. MWOC Support Technician (MST). The contractor establishes verbal communications with the MWOC CMDR for activation of the site reporting loop and responds to all Site reporting events.

2.3.2. Site Equipment. The contractor shall employ site equipment in configuration as directed by the CMDR.

2.3.3. Equipment Failures, Maintenance Actions, and Communications Status. The contractor shall monitor and report to on duty MWOC personnel any equipment failures, maintenance actions, and communications status that could cause system degradation or adversely impact the mission.

2.3.3.1. Provide all essential radar, computer, power and communications equipment status updates and changes affecting the Space Surveillance missions to the MWOC.

2.3.3.2. Coordinate with on duty MWOC personnel on power shutdown, changeover, and system reconfiguration and restoration actions that could impact operations.

2.3.3.3. Respond to on duty MWOC personnel requests for information, and provide direct operating support of the MWOC in areas of system operations and equipment control.

2.3.4. Electro-magnetic Interference. The contractor advises MWOC personnel of system interference and determines if interference is external or internal.

2.3.4.1. Coordinate termination of internal interference with the MWOC.

2.3.4.2. For external interference, the Contractor shall provide signal characteristics, if available, to the MWOC and Installation Spectrum Manager for Electromagnetic Interference (EMI) reporting.

2.3.4.2.1. Notify MWOC personnel, and the Installation Spectrum Manager, when the interference changes or ceases.

2.4. SPACE SURVEILLANCE SUPPORT. The Contractor shall provide space surveillance support to meet requirements of SD 505-1(S), V1& V2.

2.4.1. RESERVED

2.4.2. The contractor shall coordinate with Higher Headquarter agencies to update New Foreign Launch folders and Pre-Planned Launch nominal elements sets within 30 days of contract start and annually thereafter.

2.5. MISSION COMPUTER EQUIPMENT. The Contractor shall operate and maintain computer equipment and peripherals needed to support radar and space operations and operate mission computers in support of Radar Operational Time to ensure uninterrupted missile and space surveillance.

2.5.1. Notify the Crew Commander / Crew Chief (CMDR / CCH) of system malfunctions or anomalies.

2.5.2. RESERVED

2.5.3. Record computer operations events and maintain support data as requested.

2.5.4. Mission Computer Equipment Inventory. The Contractor shall perform inventory control and account for mission computer equipment on the Custody Authorization/Custody Receipt Listing (CA/CRL). The contractor shall provide the Mission Support Officer with a location inventory of mission computer equipment at start of contract and when there are major equipment changes.

2.6. RESERVED

2.7. RESERVED

2.8. INSTALLATION AND HIGHER HEADQUARTERS DIRECTED EXERCISES. Assign a member to the Emergency Operations Center (EOC) during activations for real world events; headquarter inspections or local exercises as determined by the Site Commander based on the situation or exercise objective.

2.9. TESTING. The Contractor shall support mission system capabilities testing and evaluations to include testing, modifying and improving existing hardware, firmware or software; or testing of newly installed hardware, firmware, or software.

2.10. SIMULATION MEDIA. The contractor shall store and maintain all simulation media to include scenario tapes, disks, or other forms of scenario software necessary to perform system checkout / verification, raid simulation, training, or other special interest simulations. The contractor shall control all simulation media during storage, training, evaluation, and testing.

2.10.1. Maintain a current inventory list of all simulation media on file.

2.10.2. Maintain and repair simulator equipment that is a permanent part of the radar computer system.

2.10.3 Maintain and repair simulator equipment hardware and load software used to support Operations Training, Standardization, and Evaluation upon request.

2.11. COORDINATION AGENCY. The contractor shall act as the coordination agency for the performance of on-site validation and investigations of data quality and special tests to include the establishment of precisely controlled test environments and procedures and the gathering of data as required by specific tasks.

2.11.1. Schedule and conduct mission system tests IAW AFSPCI 10-1201V1 & V2.

2.11.2. Provide general liaison and support to USAF agencies and associate contractors for integration, installation, testing, and evaluation of all hardware and software modifications and or upgrades.

CHAPTER 3

ON-SITE OPERATIONAL SYSTEM ANALYSIS

3.1. GENERAL SUPPORT. The Contractor shall perform on-site operational system analysis support of the PARCS and interface with Forward Users to satisfy mission requirements.

3.1.1. RESERVED

3.1.2. RESERVED

3.1.3. Baseline Documentation. Maintain a copy of baseline and support documentation to ensure software documentation reflects the current operational and support baseline.

3.1.4. MWOC Response. Respond within 1 hour to emergency requests for assistance by the MWOC Crew Commander in cases of system or computer problems.

3.1.5. Unit Requirements Validation Board (URVB). Attend the monthly URVB to assist in identifying and prioritizing new requirements for, and changes to, the operational system.

3.1.5.1. Participate in system life-cycle activities such as program management reviews, design reviews, tests, and physical and functional configuration audits.

3.2. METRIC DATA ACCURACY AND SYSTEM CALIBRATION. The contractor shall maintain the PARCS metric and Radar Cross Section (RCS) accuracies within system specifications using System Readiness Verification (SRV) tests, Boresight Verification Evaluations (BVE) of government-furnished satellite passes and Calibrated Sphere Tracking (CST) IAW PARCS OI 21-11.

CHAPTER 4

MISSION SYSTEMS MAINTENANCE

4.1. GENERAL MAINTENANCE. The contractor shall perform all authorized organizational, intermediate, and depot level maintenance. Plan, schedule, direct, organize, coordinate, control, document, report, and execute all actions necessary to maintain mission equipment operability and availability. Maintain logs, records, inspection forms and Maintenance Information Systems (MIS) reflecting equipment status, inspections, and maintenance performed

4.2. COMMUNICATIONS-ELECTRONICS (C-E) MAINTENANCE MANAGEMENT.

4.2.1. Equipment Maintenance and Repair. The contractor shall maintain, calibrate, and repair the communications-electronics equipment, and perform all preventive maintenance.

4.2.2. Equipment or Mission Status Change. Publish a maintenance schedule and make available to the Government for review.

4.2.3. Preventive Maintenance. The Contractor shall load all preventive maintenance data into the Integrated Maintenance Data System (IMDS) database.

4.2.4. IMDS Data Entry. Document all maintenance in the IMDS/Job Documentation Data (JDD) subsystem for all equipment with Maintenance Data Collection (MDC) reportable Standard Reporting Designator (SRD) IAW TO 00-20-2, AFSPCI 21-108 paragraph 1.4.1.

4.2.5. RESERVED

4.2.6. Repairs. The Contractor shall repair equipment at the lowest level of maintenance.

The contractor shall request depot level maintenance when the maintenance required is beyond the scope, capability, and authorization given.

4.2.6.1. Repairable Assets. Site maintenance level authorized for repair is determined by Source, Maintenance and Recoverability (SMR) Codes and Expendability, Recoverability, Repairability Codes (ERRC) assigned to stock listed items IAW TO 0025-195.

4.2.6.1.1. Non-SMR Coded Items. The contractor shall repair items with no SMR code assigned, such as XB items, when it is cost effective or warranted by mission requirements IAW TO 00-20-2, Table 3.2.

4.2.6.1.2. SMR Code Changes. Submit requests for SMR code changes using AFTO Form 22, Technical Improvement Report, IAW TO 00-25-195, paragraphs 4.1. and 4.2.

4.2.6.1.3. Request for Assistance. Draft all requests for Technical Assistance (TA), Engineering Assistance (EA), Emergency Depot Level Maintenance (EDLM) or Urgent Depot Level Maintenance (UDLM) and submit to the 10 SWS/CC.

4.2.6.2. RESERVED

4.2.6.3. Maintenance Turnaround (TRN). The contractor shall accomplish TRN for DIFM-coded item repairs IAW T.O. 00-20-3, paragraphs 3.4 and 3.5.

4.2.7. Life of System Stock (LSS). The contractor shall identify, in writing, to the SBSS Stock Control function, required items that need to be coded as Life of System Stock (LSS) . Examples are items that are critical, unique or obsolete.

4.2.8. C-E Corrosion Prevention and Control. The Contractor shall maintain all assigned equipment using best industry practices to minimize the effects of corrosion on C-E equipment IAW TO 1-1-689 and AFSPCI 21-108 paragraph 10.1.1.1.5.

4.2.9. Equipment Configuration Control. The Contractor shall accomplish equipment configuration control for C-E equipment and maintain histories.

4.2.9.1. Change Orders. The Contractor shall process and document Field Change Orders (FCOs) and Engineering Change Orders (ECOs) and Time Change Technical Order (TCTO), time change items, using the instructions in TO 00-5-15.

4.2.10. Updates. The Contractor shall identify and update diagnostics equipment procedures or unit procedures after a hardware modification.

4.2.11. Line Replaceable Unit (LRU). The Contractor shall repair equipment via LRU replacement or mail-in maintenance. Equipment covered by mail-in maintenance agreements, or items that are not LRU supportable, are identified in the PARCS Electronic Systems Equipment Listing (located in the master library) with an asterisk (*).

4.2.12. Technical Orders. The Contractor shall submit AFTO Form 22s to recommend changes (see Appendix 6, R-4.2).

4.2.13. Engineering Investigation (EI) and Product Quality Deficiency Reports (PQDRs). Identify materiel deficiencies and trends. Depending on deficiency type, develop a EI or PQDR and submit IAW TO 00-35D-54, Chapter 3.

4.3. TEST, MEASUREMENT AND DIAGNOSTIC EQUIPMENT (TMDE).

4.3.1. The contractor shall manage, schedule, and transport TMDE IAW AFSPCI 21-108, para 5.14., 5.14.1., TO 33K-1-100 (series), and TO 00-20-14, Para 3.6 through 3.8. Perform organizational maintenance IAW TO 33-1-27 and TO 33-1-32.

4.3.2. TMDE Coordinator. Appoint a primary and alternate TMDE coordinator and complete PMEL provided coordinator training. Comply with TMDE coordinator responsibilities IAW AFSPCI 21-108, para 5.14.2. and TO 00-20-14, Para 3.6.

4.3.3. New Items. Determine if newly acquired test equipment items are considered TMDE and need to be scheduled into the PMEL for service.

4.4. RESERVED

4.5. MILITARY STRATEGIC, TACTICAL, RELAY SYSTEM (MILSTAR).

The contractor shall provide operational capability and maintain the Site AN/FRC-181, MILSTAR terminals. Initiate restoration actions within 1 hour during (Radar operational time) and 3 hours during Radar non-operational time. Twenty-four (24)-hours-a-day, 7-days-a-week (24/7) continuous manning is not required.

4.5.1. Operational Availability (ACC). IAW para 4.5, the contractor shall operate and maintain the MILSTAR terminal and facility with an Operational Availability Contractor Controlled (Acc) of not less than 97% as calculated by the following formula:

Operating Time

4.5.2. Unscheduled Outages. This is the monthly cumulative total in minutes of unscheduled downtime (OPSCAP RED) of the MILSTAR terminal for which the Contractor is liable.

4.5.2.1. Contractor Liable Downtime. The Contractor shall be liable for downtime except for the following:

4.5.2.1.1. Downtime scheduled in the CCAS and approved by unit commander and higher headquarters as being non-Contractor liable.

4.5.2.1.2. Downtime caused by MWOC military personnel error.

4.5.2.1.3. Downtime due to a higher headquarters priority.

4.5.2.1.4. Downtime caused by events outside the Contractor's control and judged by the unit commander's staff (QAE’s, Government analyst, DO, and MWOC crew) and the unit commander (or a designated representative), and, if necessary, the Contracting Officer as being non-Contractor liable.

4.5.2.1.5. Downtime caused by unobtainable spare parts.

CHAPTER 5

COMMUNICATIONS OPERATIONS AND MAINTENANCE (O&M)

5.1. GENERAL. . The Contractor shall provide Network Management, Information Assurance, Base Telephone Service, Technical Control/Patch and Test Facility support, Land Mobile Radio, Frequency Management, Television Service, Communications Program Management and Communication Center operations and support within the Service Area (not to include individual dorm rooms) and to the Commander and Director of Operations residences for Defense Switched Network (DSN) Secure Telephone Equipment (STE).

5.2. COMMUNICATIONS FOCAL POINT: The Contractor shall manage the operations of the CAFS Communications Focal Point (CFP) to: oversee network operations, help achieve information assurance, and generate visibility into the base network IAW TO 00-33A-1001, Para 3.4.

5.2.1. Network Operations (NetOps). The Contractor shall perform routine operations IAW 690NSGI 33-101, chapters 3 and 4. The Contractor shall perform configuration, maintenance, and fault isolation. Resolve network problems and outages. Provide emergency response to restore normal network operations during non-duty hours.

5.2.1.1. Client Support Administrators (CSA). Contractor CSAs (formally known as the Workgroup Manager) shall have A+, Net+ or Sec+ certification IAW DoD 8570.1-M, Ch 2, pg 16, figure C2.F1, pg 64, Table AP3.T1; and a security clearance IAW AFI 31-501, Sec 3.27 and Attachment 3 (pg 61, Table A3.2).

5.2.1.2. System Administrator. Contractor System Administrators shall perform IAT Level II requirements for Non-Secure Internet Protocol Router Network/Secret Internet Protocol Router Network (NIPRNET/SIPRNET) and maintain certifications IAW DoD 8570.01-M, Tables C3.T1, C3.T4 and AP3.T1. Contractor System Administrator(s) shall have a successfully completed Single Scope Background Investigations (SSBIs) IAW DoDI 8500.2, Table E3.T1.

Note: requirement is for SSBI only, not to fill a Top secret billet or position.

5.2.2. Operation Interruptions. The Contractor shall coordinate all network operation interruptions (for maintenance, modifications, or other such occurrences) with on-Site network users and others who could be affected by a network interruption. Coordinate all Authorized Service Interruptions (ASI) IAW 690NSGI 33-101, para 4.4.

5.2.3. RESERVED

5.2.4. Single Point of Contact. Provide a single point of contact (POC), e.g. help desk, for the resolution of network user problems and questions on a during normal duty hours (See Appendix 2, Definitions, for normal duty hours).

5.2.4.1. Track resolutions using Government-provided trouble ticket tracking software, currently called Remedy.

5.2.4.2. Answer user complaints/questions concerning network applications software, e-mail and Internet external communications and the infrastructure associated with the network.

5.2.4.3. Trouble Call Resolution. Operate and maintain the Government-provided trouble ticket tracking software, for trouble call reporting and resolution.

5.2.4.4. Maintain accurate and timely documentation of all user problems and resolutions for the purposes of trend analysis in the system.

5.2.4.5. Respond to and resolve all network-related trouble tickets and user problems in accordance with industry standards.

5.2.4.6. Report outages and resolutions IAW 690NSGI 33-101, para 4.3.

5.2.4.7. Technical Service. Evaluate and establish validity and technical solutions for network-related C4 System Requirements (current standard is TO 00-33D-3003, Methods and Procedures, Managing the Cyberspace Infrastructure with the Cyberspace Infrastructure Planning System). See TO 00-33D-3003, Chapter 4 Infrastructure Requirements Process.

5.2.4.8. Documentation. Maintain all histories, inventories, documentation, configurations, and network files concerning network systems on file and available for Government review upon request.

5.2.5. Account Management. The Contractor shall establish, manage and track all network user accounts.

5.2.5.1. Establish procedures for users to request new user accounts, modify existing user accounts, and delete user accounts which are no longer needed.

5.3. NETWORK MANAGEMENT. The Contractor shall perform configuration, security and interface requirements IAW AFI 33-113, all paragraphs excluding 1 through 1.8.4., AFI 33-115 Vol I, paragraphs 3.12., 4.5. through 4.7, Ch 5 through 9, and AFI 33-115 Vol II, paragraphs 4.5, 5 and 6.1. through 6.2.1. The Contractor shall manage, operate, and maintain Site network equipment and associated Information Technology Equipment (ITE) and software utilizing commercially available, AFSPC approved products located at https://nosc.afspc.af.mil/reference.asp, and maintain the E-mail system, Websites, File/Print servers, and network infrastructure.

5.3.1. Install, configure, troubleshoot, operate, maintain, monitor, analyze, and upgrade Site servers, operating system(s) and software.

5.3.2. Perimeter Control. Boundary Management/Protection. The Contractor shall ensure security of network assets and information IAW 690NSGI 33-101, para 4.10.

5.3.2.1. Prevent base network exploitation via any known vulnerabilities. Report vulnerabilities to INOSC West, via e-mail (https://nosc.afscpc.af.mil). AFSPC Enterprise Network - Unclassified (AEN-U) contract remotely manages firewalls, external routers and web proxy servers.

5.3.3. RESERVED

5.3.4. Air Force Standard Programs. The Contractor shall integrate and support downward-directed Air Force programs supporting network infrastructure upgrades, including Government-furnished Combat Information Transport System (CITS) equipment. CITS comprises the Information Transport System (ITS), the Network Operations/ Information Assurance (NO/IA), Telecommunications Management System (TMS), and the Voice Switching System (VSS).

5.3.5. Network Back-up and Restoration. The Contractor shall backup & restore all networks in the event of failure. The Contractor shall keep a log of back-ups and restorations performed.

5.3.6. E-mail. The Contractor shall configure and maintain e-mail storage limits and message size limits IAW AFSPC SPIN-1, Appendix M.

5.3.7. Information Technology Equipment (ITE) Management. The Contractor shall appoint a primary and alternate Equipment Custodian (EC) to ensure accountability of ITE.

5.3.7.1. Conduct a physical inventory, at start of contract and annually thereafter, of all ITE within the Contractor’s area of responsibility, document changes and coordinate the signed inventories through the government Equipment Control Officer (ECO).

5.3.8. Security Postures. Implement Information Condition (INFOCON) checklists IAW AFSPC SPIN-1, section 3.2.1. Implement Notice to Airmen (NOTAMs) as directed by the Government IAW AFSPC 690NSGI 33-101, para 3.1.

5.3.9. Virtual Private Network (VPN). The contractor shall install, configure, troubleshoot, maintain and upgrade the VPN client software on laptops.

5.4. NETWORK INFRASTRUCTURE/BACKBONE. The Contractor shall install, configure, and maintain all hardware and software including all routers, switches and hubs.

5.4.1. Install and maintain all data circuits and cable drops of installed workstations.

5.5. INFORMATION ASSURANCE. The Contractor shall update the existing primary LAN and mission systems certification and accreditation (C&A) package System Security Authorization Agreement (SSAA), IAW AFI 33-202, Vol 1, Ch 6, and the Department of Defense Information Assurance Certification and Accreditation (DIACAP).

Note: LAN C&A is due 1 Feb 2010; mission systems C&A is due 20 June 2010.

5.5.1. Submit changes to the 21 SW/IA Office for review and AFSPC Designated Approving Authority (DAA) signature.

5.5.2. Computer Security (COMPUSEC). The Contractor shall appoint an Information Assurance Officer (IAO) responsible for applicable Information Assurance functions, and provide a copy of the appointment documentation to 21 SW IA Office at contract phase-in and as personnel changes occur.

5.5.2.1. Contractor IAO shall perform IAM Level I requirements and maintain certification IAW DoD 8570.01-M, Tables C4.T1, C4.T2 and AP3.T1. Contractor IAO shall have a successfully completed National Agency Check with Local Agency and Credit Check (NACLC), if individual does not have system administration privileges; or SSBI, if individual has system administration privileges, IAW DoDI 8500.2, Table E3.T1.

Note: requirement is for SSBI only, not to fill a Top secret billet or position.

5.5.2.2. Perform as the liaison between the Site and the 21 SW IA Office for COMPUSEC matters, ensuring all users and IAOs (under their purview) receive COMPUSEC training as outlined in AFI 33-200 paragraph 2.27 and subparagraphs Information Assurance (IA) Management. Additionally, the Contractor shall perform the following:

5.5.2.2.1. Report system security incidents, virus attacks, classified message incidents, and identify threats, vulnerabilities, and associated countermeasures using the policies, procedures and reporting formats in AFI 33-138, Ch 5 and 6.

5.5.2.2.1.1. Submit incident status reports IAW AFI 33-138, Table 5.4 and 6.1and provide copies to 21 SW/IA. Clean or sanitize information systems IAW SSAA.

5.5.2.2.2.. Review audit trails of core network services and infrastructure devices for indications of inappropriate or unusual activity. The Contractor shall also analyze and report suspected violations using the security measures in AFI 33-138, Ch 5, paragraph 5.5.

5.5.3. Emission Security (EMSEC). The Contractor shall appoint in writing, at contract start and within 5 calendar days of any changes, an individual (other than the IAO) to perform the following EMSEC manager duties.

5.5.3.1. Request 21 SW/IA perform an EMSEC inspection, after installation, but before operation of any new equipment.

5.5.3.2. Correct all deficiencies identified by an EMSEC inspection and request a re-inspection.

5.5.3.3. Assist the wing EMSEC manager in the evaluation of the EMSEC program and local EMSEC problems during Site visits.

5.5.3.4. After completed EMSEC Inspection, the Contractor shall review all installation, removal, or equipment modification schemes for potential EMSEC vulnerabilities, and notify the Installation Commander and 21 SW/IA of vulnerabilities identified, if any.

5.5.3.4.1. Implement required countermeasures and maintain as-applied or as-installed.

5.5.4. Information Assurance Awareness Program (IAAP). The Contractor shall identify a Site IAAP POC and alternate to operate, manage, conduct and maintain a Site IAAP program as outlined in AFI33-200, para 2-27 for the entire Site. Provide the IAAP POC letter to 21 SW/IA at contract phase-in and as personnel changes occur.

5.5.4.1. Perform IA awareness training and document training completion dates on all users.

5.5.4.2. Contractor shall publish downward directed information forwarded from 21 SW/IA to all network users.

5.5.5. Communications Security (COMSEC). The Contractor shall manage, control, protect and safeguard COMSEC facilities, material, equipment and accounts.

5.5.5.1. COMSEC POC. The Contractor shall identify a COMSEC Account Manager and Alternate COMSEC Account Manager IAW AFKAG-2L (For Official Use Only (FOUO)), paragraph 2.4. via written documentation and provide to the 10SWS/CC at contract phase-in and as personnel changes occur. The Contractor shall ensure appointees meet the requirements in AFKAG-1N, paragraphs 3.5 through 3.5.7.

5.5.5.1.1. Contractor COMSEC Responsible Officer (CRO) shall comply with training and certification requirements IAW AFI 21-109, Sec B through D, and Attachments 2 through 5.

5.5.5.2. Secure Telephone Equipment (STE). The Contractor shall manage STE Key IAW AFI 33-201, Volume 9, paragraphs 1.3.4 through 1.3.4.8, 1.5 through 1.5.4.1.3, 1.6 through 1.14, 1.16, 1.17, Chapters 2 through 5, 9 and Attachments 2, 3, 7, 9, 10, 11, and 14, Modern Key COMSEC Accounting procedures IAW AFKAG-2L (FOUO), Chapter 10, and Secure Data Network System (SDNS) User Representative and COMSEC Account Procedures.

5.5.5.2.1. The contractor shall be on-site within one hour to repair STE Key when requested.

5.5.5.3. Formal Cryptographic Access (FCA). The Contractor shall request FCA into the Cryptographic Access Program (CAP) by completing and submitting AFCOMSEC Form 9 for Contractor personnel meeting the requirements of AFI 33-201, Vol 4, (FOUO).

5.5.5.3.1. Crypto Keying Control. The Contractor shall ensure crypto keying and control. The Contractor shall also provide DD Form 1435, COMSEC Maintenance Training and Experience Record, for Government review upon request; DoD-approved training with certificate may be substituted.

5.5.5.3.2. MILSTAR COMSEC. The Contractor shall perform as a sub-account COMSEC Responsible Officer (CRO) of a MILSTAR COMSEC.

5.5.5.3.3. Keying and Storage. The Contractor shall provide daily crypto keying and shift-change verification for cryptographic equipment, as required in MILSTAR operational documentation.

5.5.5.4. Inspections. The Contractor shall perform and document COMSEC self-inspections.

5.5.5.5. Incident Reports. The CRO shall complete incident reports involving physical, cryptographic, and personnel COMSEC deviations using the process in AFSSI 4212 and submit to the COMSEC Manager.

5.5.5.6. COMSEC Responsible Officer (CRO). The Contractor shall designate a primary and alternate CRO using the procedures in AFI 33-201, Vol 2 (FOUO), paragraph 4. CRO shall perform the following responsibilities:

5.5.5.6.1. Control, safeguard, use, and destroy COMSEC materials as described in AFI 33-201, Vol 2 (FOUO), all paragraphs, excluding 3.2. through 3.2.6. and using any COMSEC instructions provided by the supporting COMSEC account.

5.5.5.6.2. Pick up and deliver COMSEC material from the supporting COMSEC account.

5.5.5.6.3. Disseminate COMSEC information IAW PARCS OI 33-15.

5.5.6. Telecommunications Monitoring and Assessment Program (TMAP). IAO performs TMAP responsibilities IAW AFI 10-712, para 1.4.21.2 to 1.4.21.8, and attachments 3, 5, and 6. Perform annual self-assessments using the SAC A6-2-2 checklist located in the Inspector General's Management Internal Control Toolset (MICT). Make results of inspections available for Government review upon request.

5.5.6.1. RESERVED

5.5.6.2. RESERVED

5.5.6.3. Non-Compliance. Report corrective action and progress made to 21 SW/IA of within ten (10) business days from request.

5.6. BASE TELEPHONE SYSTEM (BTS). The Contractor shall monitor the operations and maintain the BTS IAW industry standards, AFI 33-111, all Chaps and Attachments, excluding Sec A, paragraphs 1 through 8.4.1., Sec B, paragraphs 11.2. through 11.2.2., Sec G, paragraphs 59.1. through 59.1.6., Attachment 2, A2.2. through A2.2.14. Guidelines for on-hook telephone security in AFI 33-220 and security policies and procedures in the Defense Switched Network Security Technical Implementation Guide (DSN STIG) and DoDI 8500.2. within the Service Area (not to include individual dorm rooms) and to the Commander and Director of Operations residences for Defense Switched Network (DSN) Secure Telephone Equipment (STE).

5.6.1. Telephone Control Officer (TCO) and/or Base Communications and Information Systems Officer (CSO). The Contractor shall appoint, in writing, a primary and alternate TCO to perform TCO tasks IAW AFI 33-111, paragraphs 10.1. through 10.3. The Contractor shall also appoint, in writing, a primary and alternate CSO to perform tasks IAW AFI 33-111, paragraphs 9 through 9.13.7. and 11 through 11.1.5. The contractor shall submit the appointment letter to the 10SWS/CC at contract start and within 3 working days of changes.

5.6.2. Mission Critical/Non-Critical System Outages. The Contractor shall respond to outages and begin restoral to mission-critical communication service within 2 hours of notification and restoral of non-mission critical communication service by the next business day.

5.6.3. Maintenance. The Contractor shall install, troubleshoot, change (add/relocate/remove/modify), maintain, calibrate, repair, and perform Preventive Maintenance Inspections (PMI) on all switching equipment and power distribution systems, public address systems, alerting systems, data transmitting systems, base cable plant, and premise wiring within the Service Area (not to include individual dorm rooms) and to the Commander and Director of Operations residences for Defense Switched Network (DSN) Secure telephone Equipment (STE).

5.6.3.1. Maintain and repair equipment IAW manufacturers' directions and industry standards. Utilize Original Equipment Manufacturer (OEM) standards / manuals and Telecommunications Industry Association/Electronic Industries Alliance (TIA/EIA) for in-house wiring and outside cabling.

5.6.4. Trouble Reports. The Contractor shall maintain trouble reports using a Government-provided database (currently ‘Remedy’) management program.

5.6.5. Service Interruptions. The Contractor shall obtain approval from the Site Commander for major system or service outages.

5.6.5.1. Notify customers of scheduled outages whenever service must be interrupted during normal duty hours. (See Appendix 2, Definitions, Normal duty hours)

5.6.6. Defense Red Switch Network…