AFINCC_PWS_Draft_-_13_Sep_12.pdf

Performance-Based Work Statement (PBWS) 26th Network Operations Squadron (26 NOS)

September 2012

PERFORMANCE-BASED WORK STATEMENT

Table of Contents

1 INTRODUCTION

1.1 OVERVIEW

1.2 BACKGROUND

2 SCOPE

3 REQUIREMENTS AND PERFORMANCE STANDARDS

3.1 GENERAL REQUIREMENT

3.2 REQUIREMENTS DESCRIPTION

3.2.1 NETWORK OPERATIONS

3.2.2 SECURITY/BOUNDARY OPERATIONS

3.2.3 DNS OPERATIONS

3.2.4 SUPPORT OPERATIONS

3.2.5 PROJECT INTEGRATION GROUP OPERATIONS

3.2.6 AOL/COOP OPERATIONS

3.2.7 CREW OPRATIONS

4 CONTRACT DELIVERABLES (CDRLs)

5 SERVICE SUMMARY (SS)

6 GOVERNMENT FURNISHED PROPERTY AND SERVICES

7 ADDITIONAL SPECIAL REQUIREMENTS

7.1 SURGE REQUIREMENT

7.2 MEETINGS

7.2.1 POST AWARD

7.2.2 TECHNICAL INTERCHAGE MEETINGS

7.3 TRANSITION PLAN

7.3.1 BEGINNING PLAN

7.3.2 ENDING PLAN

7.4 DATA RIGHTS AND OWNERSHIP

7.5 CONTRACTOR AND GOVERNMENT RELATIONSHIPS

7.6 NON-DISCLOSURE REQUIRED

DRAFT

September 2012

7.7 ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

7.8 STANDARDIZATION AND EVALUATION (STAN/EVAL) & QUALITY ASSURANCE

(QA) 20

7.9 TRAINING AND INSTRUCTION

7.10 KNOWLEDGE/CERTIFICATION REQUIREMENTS

7.11 PERIODS OF PERFORMANCE

7.12 CONTRACTOR TRAINING

7.13 TRAVEL

7.14 SECURITY REQUIREMENTS

7.14.1 PERSONAL SECURITY CLEARANCE REQUIREMENTS

7.14.2 VISIT REQUEST

7.15 SAFETY

8 APPENDICES

26 NOS TOOLS

WORK LOAD COMPUTATION DATA

September 2012 Page 1 of 33

1 INTRODUCTION

The intent of this acquisition is to acquire services supporting the 26th Network Operations Squadron (26 NOS) and its mission to operate, manage and defend the Air Force portion of the Global Information Grid (AF-GIG). This section provides an overview of the requirement and background information about the evolution of the squadron’s mission.

1.1 OVERVIEW

This Performance Based Work Statement (PBWS) describes contractor support required to ensure the mission of the 26 NOS, 26th Network Operations Group, 67th Network Warfare Wing is accomplished 24 hours a day, 7 days a week, 365 days a year (24x7x365). The 26 NOS provides mission assurance to the warfighter through the operation, management and defense of the Air Force portion of the AF- GIG. In the execution of its mission, the 26 NOS operates, manages and defends the Air Force Non- Secure Internet Protocol Routing Network Gateways (AFNGWS) and the Secret Internet Protocol Routing (SIPR) equivalents*; all Service Delivery Point (SDP) routers on both NIPR and SIPR; the Integrated Management Suite (IMS) out of band management networks; the top level Domain Name System (DNS) for the AF (both af.mil and af.smil.mil); Voice Over Internet Protocol/Voice over Secure Internet Protocol(VOIP/VoSIP) and the underlying workstations, servers, storage networks, and systems that are required to do so. Specifically, this PBWS describes contractor support for Network Operations, Security Operations, DNS Operations, Support Operations, Project Integration and Engineering Operations, and the Alternate Operating Location (AOL)/Continuity of Operations Plan (COOP) Operations of the 26 NOS. In addition, this PBWS describes contractor support for Information Assurance, Quality Assurance, Training, and related functions to enable the accomplishment of the 26 NOS mission.

*Note that the SIPR network (SIPRnet) currently does not have Gateways that mirror those on the NIPR network (NIPRnet). There is a SIPR Modernization effort on-going and the operation, management, and defense of the solution delivered through the SIPR Modernization effort will be included in the mission of the 26 NOS. Services proposed in response to this procurement effort should include plans to support the SIPR solution delivered by the SIPR Modernization effort.

1.2 BACKGROUND

In years past, the 26 NOS functioned more as a global tier network control center rather than its current function as a Network Operations Squadron in the Cyberspace domain. The prior role of the 26 NOS enabled it to provide services around the clock, albeit with the most experienced personnel usually concentrated on the day shift Monday through Friday with less experienced and fewer numbers of personnel on the nights and weekend shifts. With the transition to an operational squadron functioning in the Cyber domain, the role of 26 NOS now requires full operational capability 24x7x365. This truly around the clock ops tempo necessitates personnel of sufficient experience and quantities to enable 26 NOS to perform its mission at all times.

September 2012 Page 2 of 33

The 26 NOS is an operational squadron in the 26th Network Operations Group (26 NOG), 67th Network Warfare Wing (67 NWW), 24th Air Force (24 AF). The 24 AF is the Air Force component of the United States Cyber Commander (USCC) and is the Computer Network Defense Services Provider (CNDSP) for the Air Force. The 26 NOS, together with the 33rd Network Warfare Squadron (33 NWS), provide the functional aspects of CNDSP for the 24 AF.

As the operational squadron which operates, manages and defends the AF-GIG the 26 NOS regularly works with the Department of Defense Information Systems Agency (DISA) and with the other Air Force Network Operations (AFNETOPS) squadrons which include the 83rd Network Operations Squadron (83 NOS), the 561st Network Operations Squadron (561 NOS), and the 299th Network Operations Squadron (299 NOS) to provide mission assurance to the warfighter. The 67 NWW is working to provide military personnel to execute the 26 NOS mission with the assistance of qualified government civilians and contractor personnel who provide Subject Matter Expert (SME) level support. This acquisition effort seeks to procure that contractor support for the 26 NOS.

September 2012 Page 3 of 33

2 SCOPE

This section provides an overview of the scope covered by this effort. The section identifies the necessity of 24x7x365 support for the operations of the squadron, provides insight into the major systems supported, identifies a sampling of necessary tasks, delineates some of the networks supported, and provides information about the current operating locations supported by this effort.

2.1 The scope of this effort is to provide the services to support the 24x7x365 operations of the 26 NOS in order to enable the squadron to provide mission assurance to the warfighter.

2.2 The requirements of this effort are to sustain the operations, management and defense of the AFNGWS; their SIPRnet equivalents (see note at the end of Section 1.1); all Service Delivery Point (SDP) routers on both NIPR and SIPR; the Integrated Management Suite (IMS) out of band management networks; the top level Domain Name System (DNS) for the AF (both af.mil and af.smil.mil); and the underlying workstations, servers, storage networks, and systems that are required to do so.

2.3 The tasks necessary to accomplish the requirements of this effort include, but are not limited to, network operations; Air Force Common User Virtual Private Network (AFCUVPN) operations;

security/boundary operations; VOIP/VoSIP Operations; Virtual Teleconference (VTC) Operations;

DNS operations; support operations; project integration group operations; Alternate Operating Location/Continuity of Operations (AOL/COOP) functions; information assurance; Quality Assurance services; Crew Operations; Authorized Service Interruption (ASI) coordination operations; Training operations; asset management and plans and programs.

2.4 The networks and systems supported by this effort include but are not limited to: NIPRnet, SIPRnet, IMS networks, and the laboratory/test networks directly supporting 26 NOS.

2.5 The scope of this effort also includes certain boundary devices on the Global Command and Control System (GCCS) network that are identified in the Requirements and Performance Standards section of this document.

2.6 The effort described herein requires 24x7x365 support for 26 NOS operations at its primary location (Maxwell Air Force Base-Gunter Annex, Alabama) and its AOL/COOP location (Lackland Air Force Base, Texas).

September 2012 Page 4 of 33

3 REQUIREMENTS AND PERFORMANCE STANDARDS

This section provides general requirements of the support called for in this effort. This section also identifies the performance standards expected.

3.1 GENERAL REQUIREMENT

3.1.1 The Contractor shall comply with the Government approved processes in the accomplishment of the requirements identified in this PBWS.

3.1.2 The Contractor shall provide access controls that protect and defend information and information systems (IS) by ensuring their controlled physical access, availability, integrity, authentication, confidentiality, and non-repudiation, including providing for restoration of information systems by incorporating protection, detection, and reaction capabilities.

3.1.3 The Contractor shall monitor and maintain the health of all capabilities defined within the scope of this effort and shall provide status reporting to Government personnel. The Contractor shall work with the Government to define measurements of success, and recommend improvements for metrics/thresholds and processes for collecting metrics. The Contractor shall record and document performance history and comply with the monitoring procedures as directed by the Government (Deliverable A001).

3.1.4 The Contractor shall perform, as required, preventive and corrective maintenance for systems and components operated and managed under terms of this effort, including testing, removing/replacing, aligning, corrosion control, cleaning, inspecting and lubricating.

3.1.5 The Contractor shall assist the Government with the integration of the network environment, as defined in the PBWS with other third-party connections as may be required from time to time.

3.1.6 The Contractor shall make changes/upgrades/patches to infrastructure devices requiring two-person compliance through established change management procedures, as directed by Government personnel. The Contractor shall provide a record of changes/upgrades/patches in accord with AFI 33-138 Chapter 3 (Deliverable A002).

3.1.7 The Contractor shall perform system administration activities for systems and devices operated and managed as part of this effort. These include, but are not limited to, system setup, device configuration and installation, troubleshooting, monitoring, security, infrastructure installation, network protocols, and encryption systems.

3.1.8 The Contractor shall provide fault isolation/resolution services. The Contractor shall provide IT trouble assistance to customers, including remote technical support. The Contractor shall assist the Defense Information Systems Agency (DISA), the other NOSs, the Program Management Office, the 33 NWS, and other entities in the troubleshooting of circuits/trunks/devices. The Contractor shall use applicable DISA, DoD, and AF directives and procedures in fault resolution, circuit/device troubleshooting and layout. Contractor shall implement fault diagnosis, escalation, and resolution procedures as faults occur. As faults are

September 2012 Page 5 of 33 corrected, the Contractor shall document the fault, subsequent testing results, and final resolution in the Government-furnished trouble-ticketing system(s) and knowledge base.

3.1.9 The Contractor shall provide network address management through industry-standard management of Active Directory (AD) domain, DHCP, WINS, DNS and other applicable services.

3.1.10 The Contractor shall provide support for enterprise network modifications by providing technical evaluations/solutions and changes to the Integrated Master Schedule (IMS) (Deliverable A003, A004).

3.1.11 The Contractor shall assist the Government with the execution of the existing/future operations and contingency plans within the Contractor’s Area of Responsibility (AOR).

3.1.12 The Contractor shall, to the maximum extent possible, minimize the number, duration, and impact of scheduled/maintenance outages, particularly for critical IT assets that support the operational or enterprise mission.

3.1.13 The Contractor shall provide exercise and major event support within the Contractor’s AOR.

The current estimate of exercises to be supported is three (3) major and four (4) minor annually per MAJCOM. Minor Exercise - limited to the base or hosting unit (i.e. Local squadron as a part of an ORI) Major Exercise - includes not only the hosting base or unit, but other MAJCOMs and potentially COCOMs (i.e. Red Flag, Cyber Nexus, etc.). This includes providing administrator or equivalent-level access to equipment or other support as required to personnel authorized by the Government conducting installation, implementation, investigation, analysis, compliance, or assessment activities. An example is the AF “SCOPE EDGE” network analysis and compliance team.

3.1.14 The Contractor shall participate in and provide inputs to Government tasks and process improvement efforts, including providing analysis of operations within the Contractor’s AOR, and answering data calls pertaining to the Contractor’s AOR (Deliverable A005, A006).

3.1.15 The Contractor shall analyze IT and network shortfalls and deficiencies, provide performance analysis, and identify candidate improvements and/or technology insertions. The Contractor shall analyze trends to isolate problems/issues and assist the Government in the determination future requirements (Deliverable A007).

3.1.16 The Contractor shall monitor and track Automated Data Process Equipment and software.

The Contractor shall notify and provide corrective recommendations to the Government of any equipment, software, or service which has exceeded its life-cycle, is failing, or otherwise requires Government funding or action to maintain the contractual service level, including lack of redundant paths or systems. This notification shall be accomplished as required, but no less than on a monthly basis. The Contractor shall implement any or all of their recommended modifications only after the Government has approved those items and notified the Contractor to proceed with implementation. The Government will purchase all necessary hardware and software unless the Contractor is requested to do so as an Other Direct Cost (ODC) including a basis of estimate to include their assessment of price reasonableness (i.e. Include 3 GSA/Open Market sources) (Deliverable A008).

September 2012 Page 6 of 33

3.1.17 The Contractor shall, upon completion of assessments/analyses, document candidate procedural corrective measures and candidate technology insertions, and provide high-level estimated costs (Deliverable A009).

3.1.18 The Contractor shall conduct trend analyses from historical data based on communications circuits and hardware resource utilization for all supported systems. The Contractor shall analyze data to identify trends and make fault projections and compare to mission requirements. The Contractor shall document the analyses, highlight threshold deviations, and identify potential corrective measures with high-level estimated costs. The Contractor shall deliver trend analysis/historical reports monthly and a consolidated rollup semi-annually (Deliverable A010).

3.1.19 The Contractor shall participate in meetings as necessary to perform the requirements of the PBWS as directed by the Government. Some meetings might require travel.

3.1.20 The Contractor shall assist the Government in conducting periodic Program Management Reviews (PMRs). Topics to be discussed may include performance metrics, recommended efficiencies, personnel updates, status of on-going projects, and any open issues that need resolution. The Contractor shall provide briefings, as required, by the Government (Deliverable A011).

3.1.21 The Contractor shall provide Weekly Activity Reports (WARs) including significant events/issues (Deliverable A012).

3.1.22 The Contractor shall assist the Government to prepare written procedures for the situations identified where current directives and policies do not provide sufficient instructions or guidance to meet performance thresholds and/or detail the order of events/executions (Deliverable A013).

3.1.23 The Contractor shall assist the Government in the maintenance and support of all documentation such as, but not limited to: Memorandums of Agreement (MOA), Memorandums of Understanding (MOU), Letters of Agreement (LOA) and/or Services Level Agreements (SLA) pertaining to IT infrastructure and downward-directed initiatives in accordance with AFI 33-115v1, Attachment 2. The Contractor shall review all MOAs, MOUs, LOAs, SLAs at the time of development and at least annually thereafter, and provide recommended changes as directed by the Government (Deliverable A014).

3.1.24 The Contractor shall support shift operations and rotating schedule and ensure Continuity of Operations (COOP). While routine operations should be 24x7x365 at both primary and AOL/COOP locations, there may be surge requirements during contingencies, exercises, or other events.

3.1.25 The Contractor shall assist the Government in managing and maintaining its electronic information and records repository in accordance with disposition instruction for documents and artifacts received by the Government.

3.1.26 The Contractor shall assist the Government in the development and implementation of a schedule management system (Microsoft Project preferred) and a common repository that

September 2012 Page 7 of 33 consolidates all schedules into a master schedule. These schedules include, but are not limited to: backups, training, Enterprise Information Management (EIM) implementation, system upgrades, equipment inventories, and individual project schedules.

3.1.27 The Contractor shall prepare and maintain an event-based Integrated Master Schedule (IMS) (Deliverable A004).

3.1.27.1 The Contractor shall include in the IMS all projects/activities defined in/by the

PBWS.

3.1.27.2 The Contractor shall identify key events that support contract milestones in the schedule and shall identify critical paths.

3.1.27.3 The Contractor shall, to the maximum possible, de-conflict projects/events in the

IMS.

3.1.27.4 The Contractor shall maintain the IMS current within 15 days of Government notification of projects and key events.

3.1.28 The Contractor shall perform configuration management, including configuration changes, installation and management of IT devices. The Contractor shall adhere to 26 NOS change management procedures and shall create implementation plans (i-Plans) for all non-routine changes and Field Change Orders (FCOs) for changes affecting the system baseline.

Changes/upgrades/patches require two-person compliance and must be documented in accordance with AFI 33-138 Section 3D, 3.17 (Deliverable A002).

3.1.29 The Contractor shall coordinate with Air Force other organizations to troubleshoot and maintain levels of service identified and defined by the Government.

3.1.30 The Contractor shall only use Government provided hardware, software, and tools.

3.1.31 The Contractor shall ensure that all personnel are properly certified in accordance with AFI 33-115v2, Department of Defense (DoD) 8570.01, and other appropriate directives in accordance with Appendix A.

3.1.32 Other hardware/software certifications may be required in order for maintainers not to violate written or implied warranties and/or representations of the vendor/manufacturer of the equipment. In those cases, the Contractor shall only attempt to fix or maintain the equipment if they have the necessary certifications. If not, the Contractor shall identify those deficiencies to the Government who may seek alternative means of repair/maintenance, or authorize the Contractor to seek repairs through the purchases of extended warranties or repair actions as Other Direct Costs. Only the Procuring Contracting Officer may authorize such purchases /expenditures. The Contractor must, in those cases, provide a basis of estimate to include their assessment of price reasonableness.

3.1.33 All Contractor personnel shall have a minimum of a SECRET clearance. Specified positions at 26 NOS will require Contractor personnel to have Top Secret with Special Compartmented Information (SCI) access.

September 2012 Page 8 of 33

3.1.34 By direction of the Government, the Contractor shall apply all Notice to Airmen (NOTAMs), Time Compliance Network Orders (TCNOs), Time Compliance Technical Orders (TCTOs), or other Higher Headquarters (HHQ) directed configuration changes within the time frame designated by the I-NOSC, in accordance with AFI 33-138, Chapter 3.

3.1.35 The Contractor shall comply with all applicable NOTAMs, TCNOs, NTOs, MTOs released by the 624th Operations Center (624 OC) within the specified timeframe. The Contractor shall accomplish status reporting in accordance with the most current AF directives. The primary tool for tracking is the TCNO tracker website.

3.1.36 The Contractor shall assist the Government in development of Network Task Orders (NTOs)/Maintenance Task Orders (MTOs)/NOTAMs as necessary.

3.1.37 The Contractor shall assist the Government in the protection of IT systems from malicious code and network attacks. The Contractor shall install current anti-virus software, updates, patches, and definitions on every computer, information system, network, and stand-alone computing devices within the Contractor’s AOR. The Contractor shall obtain all anti-virus products from the DoD Computer Emergency Response Team (CERT). When AFNetOps directs emergency compliance with new anti-virus software updates within a shorter timeframes, the Contractor shall comply with the shorter AFNetOps mandated timeframe.

3.1.38 The Contractor shall not publish or disclose in any manner, without written consent of the AF, the details of any security safeguards designed, developed, or implemented by the Contractor under this contract, or any other security related information to which the Contractor may gain access. Contractor personnel will have to sign non-disclosure agreements with the Government.

3.1.39 The Contractor shall not install any equipment that does not meet DISA Security Technical Installation Guidance (STIG) requirements. In cases where operational necessity dictates an exception to this requirement, the Contractor shall supply a Plan of Action and Milestones (POA&M) to the Government describing how and when the exception will be remediated. The Contractor shall obtain approval from the government prior to implementing the exception.

3.2 REQUIREMENTS DESCRIPTION

This section provides a description of the requirements for each of the major operations within the 26 NOS. The 26 NOS operations include Network Operations; Security/Boundary Operations; DNS Operations; Support Operations; Project Integration Group Operations; AOL/COOP Operations; and Crew Operations. Table 1 provides a high level matrix of functions/tasks and the mission element in which they are performed.

Net

Ops Sec Ops

DNS

Ops

Support Ops

Prod Int Grp Ops

AOL/Coop Ops

Crew Ops

Load configs X X X X X X

Load patches X X X X X X

Config devices X X X X X X

September 2012 Page 9 of 33

Secure devices X X X X X X

Update/upgrade devices X X X X X X

Monitor devices & performance

X X X X X X

Analyze data X X X X X X

Analyze traffic & performance

X X X X X X

Provide reports (Performance/ Utilize Etc)

X X X X X X

Troubleshoot X X X X T3 X

Resolve app issues X X X X X X

Understand mission systems

X X X X X X

Ensure compliance X X X X X X

Manage ASI X X X X X X

Infra: Install, Config, M&M X X

EITSM X X X X X X

Intel SPT/Liaison X X

Policy review/report X X

DNS design X

Engineer design X

Backup & recovery X X

Operate & manage storage

X

QA program X X X

Information assurance X X X X X X X

Training support X X X X X X

Tech writing X X X

Project management X X

Coop documentation X

C2 X

Enterprise SA X

Event Management X

Reporting X

Ticket Management X

September 2012 Page 10 of 33

SPOC X

KM X

Notification (Outage, weather etc)

X

Table 1. Matrix of typical tasks and the mission elements in which they are performed.

3.2.1 NETWORK OPERATIONS

The 26 NOS Network Operations requirement is a 24x7x365 mission that requires subject matter expertise (SME) level support from the contractor every hour of every day of the year. Contractor SME support for 26 Network Operations must provide senior network engineers on all shifts every day to accomplish the mission of operating, managing and defending all routers, switches, Wide Area Network (WAN) acceleration devices, appliances, and other network devices involved in the execution of the 26 NOS mission. On-call support is not sufficient to satisfy the requirement of 24x7x365 support to the Network Operations element of the 26 NOS mission. Typical Network Operations activities accomplished by the contractor include, but are not limited to, loading configurations and patches onto network devices; configuring network devices; securing network devices; patching network devices; updating/upgrading network devices; monitoring network devices and their performance; analyzing network device performance data; analyzing network traffic and utilization; providing reports for network devices, performance, utilization, etc; troubleshooting and resolving complex issues for applications and mission systems that traverse the network;

troubleshooting and resolving network performance issues; operating, managing and defending the VOIP/VoSIP systems supported or used by 26 NOS; troubleshoot with all mission partners such as DISA, 561 NOS, 83 NOS, 299 NOS, 33 NWS, federal and DoD agencies; and ensuring network devices managed by 26 NOS comply with Air Force and Department of Defense regulations such as the Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG).

The 26 NOS Network Operations requirement also requires 24x7x365 support from the contractor for Authorized Service Interruption (ASI) scheduling and coordination. The contractor must provide information technology specialists capable of working with entities across the Department of Defense to schedule, manage, and coordinate ASIs for circuits within the 26 NOS area of responsibility.

The 26 NOS Network Operations requirement also requires 24x7x365 support from the contractor for Infrastructure installation, configuration, management, and maintenance. The Infrastructure support provided by the contractor will involve work at both the primary 26 NOS location and the Alternate Operating Location (AOL)/Continuity of Operations (COOP) location, as well as management of the infrastructure devices at the AFNGWS and their SIPR equivalents (see Note at the end of Section 1.1).

The SMEs supporting 26 NOS Router Operations will track all activity through the Enterprise Trouble Ticketing System.

3.2.2 SECURITY/BOUNDARY OPERATIONS

The 26 NOS Security/Boundary Operations requirement is a 24x7x365 mission that requires subject matter expertise (SME) level support from the contractor every hour of every day of the year.

Contractor SME support for 26 NOS Security Operations must provide senior security systems engineers on all shifts every day to accomplish the mission of operating, managing and defending all AFNGWS’s, their SIPR equivalents(see Note at the end of Section 1.1), the Boundary devices managed by the 26 NOS, the IMS Boundary devices, and the related Boundary/Security systems

September 2012 Page 11 of 33 managed by and used by the 26 NOS. On-call support is not sufficient to satisfy the 24x7x365 support requirement for the Security Operations elements of the 26 NOS mission. Typical Security Operations activities accomplished by the contractor include, but are not limited to, loading configurations and patches onto boundary devices; configuring boundary devices; securing boundary devices; patching boundary devices; updating/upgrading boundary devices; monitoring boundary devices and their performance; analyzing boundary device performance data; analyzing boundary devices and network traffic and utilization for security related purposes; providing reports for boundary devices, performance, utilization, etc; troubleshooting and resolving complex issues for applications and mission systems that traverse the network; troubleshooting and resolving network performance issues that may be associated with or impacted by boundary devices; and ensuring boundary devices managed by 26 NOS comply with Air Force and Department of Defense regulations such as the Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG).

The senior security systems engineers supporting the 26 NOS must interact daily with personnel from various Intelligence Community entities to receive and pass on information of intelligence value, and to recommend courses of action for 26 NOS leadership based on intelligence received. Contractor support for the Intelligence activities at 26 NOS include but are not limited to collecting, analyzing and reporting on intelligence data; maintaining awareness of global events and assessing their relevance to and impact on 26 NOS; providing leadership recommendations for course(s) of action based on intelligence data; and other tasks associated with the Intelligence activities of the 26 NOS.

3.2.3 DNS OPERATIONS

The 26 NOS DNS Operations requirement is a 24x7x365 mission that requires subject matter expertise (SME) level support from the contractor every hour of every day of the year. Contractor SME support for 26 DNS Operations must provide senior DNS administrators and DNS Systems Analysts on all shifts every day to successfully manage, administer, secure and defend the top level domains for the Air Force, including deployed domains, af.mil and af.smil.mil, in order to support the mission of operating, managing and defending all AFNGWS’s, their SIPR equivalents(see Note at the end of Section 1.1), the SDP routers managed by the 26 NOS, the IMS networks and systems, and the underlying workstations, servers, storage networks, and systems of the 26 NOS. On-call support is not sufficient to satisfy the 24x7x365 support requirement for the DNS Operations elements of the 26 NOS mission. Typical activities performed by the DNS Operations SMES include, but are not limited to establishing, maintaining and defending the domains; operating, maintaining and defending appliances, servers, and systems providing DNS services; interacting with other entities(government, military, and commercial) to ensure proper DNS operations; monitoring DNS performance; analyzing and reporting on DNS performance; troubleshooting and resolving complex DNS related issues;

providing AF leadership recommendations on DNS matters; reviewing, drafting and authoring DNS documentation and technical papers; and other related tasks.

3.2.4 SUPPORT OPERATIONS

The 26 NOS Support Operations requirement is a 24x7x365 mission that requires subject matter expertise (SME) level support from the contractor every hour of every day of the year. Contractor SME support for 26 NOS Support Operations must provide senior system administrators, senior storage engineers, senior back up/restoral engineers, and senior configuration/change management specialists on all shifts every day to accomplish the mission of operating, managing and defending all servers, clients, appliances, storage systems, backup and recovery systems, applications and tools** involved in the execution of the 26 NOS mission. On-call support is not sufficient to satisfy the 24x7x365 support requirement for the Support Operations elements of the 26 NOS mission. Typical

September 2012 Page 12 of 33

Support Operations activities accomplished by the contractor include, but are not limited to, system administration for Windows, Linux, Unix, Solaris servers and clients; storage environment administration, management, maintenance, and security; administration, management and performance of the squadron’s backup and recovery systems; operation and administration of the configuration/change management program within the 26 NOS; administration, enhancement and operation of the Knowledge Management program within the 26 NOS; direct and indirect support the Quality Assurance (QA) program within the 26 NOS as required by AFI 33A-1001 and AFI 33-150;

and related tasks necessary to ensure 26 NOS mission is executed 24x7x365.

The Support Operations requirement includes contractor support for the Information Assurance (IA) functions performed within 26 NOS. These functions include, but are not limited to an Information Assurance Officer; and Information Assurance Manager; and Senior Information Assurance engineers and analysts to carry out the 26 NOS IA functions.

The Support Operations requirement includes contractor support for the Training portion of the 26 NOS mission. The contractor SMEs assigned to Training support will ensure that all 26 NOS personnel (military, government civilian, and contractor) meet the required training objectives and certifications to comply with 26 NOS, Air Force and Department of Defense regulations.

The Support Operations requirement includes contractor support for Technical Writing in support of 26 NOS mission requirements. Technical Writing functions will typically be performed during normal duty hours (0730-1630 Central Time Zone) Monday through Friday of each week. The Technical Writing requirement will support the production of top quality reports, narratives, whitepapers, and other materials required to accomplish 26 NOS mission.

** Note that some of the “tools” currently used by the 26 NOS are identified in Appendix B. Also note that the list of “tools” is representative rather than all inclusive. “Tools” used by the 26 NOS may change based on mission needs, Contractor suggestions, etc.

3.2.5 PROJECT INTEGRATION GROUP OPERATIONS

The 26 NOS Project Integration Operations requirement is a 24x7x365 mission that requires subject matter expertise (SME) level support from the contractor every day of the year. On-call support during nights, weekends, and holidays may be appropriate in normal circumstances, but the Contractor should be prepared to provide the required support at any time during the performance period of the contract. Contractor SME support for 26 NOS Project Integration Operations must provide senior level systems engineers (network systems engineers, security systems engineers, Voice over Internet Protocol(VOIP)/Voice over Secure Internet Protocol(VoSIP) engineers) and senior level systems analysts (web application programming skills, scripting language skills, coding skills) on all shifts every day to accomplish the mission of operating, managing and defending all AFNGWS’s, their SIPR equivalents(See Note at the end of Section 1.1), the SDP routers managed by the 26 NOS, the IMS networks and systems, and the underlying workstations, servers, storage networks, and systems of the 26 NOS. Typical activities performed by the SMEs in Project Integration Operations at 26 NOS include but are not limited to working with Router Operations, Security Operations, DNS Operations, Support Operations, and the AOL/COOP Operations to troubleshoot and resolve complex issues including issues associated with VOIP/VoSIP systems manage by or used by 26 NOS. The Project Integration Operations SMEs will lead pilot efforts to evaluate new solutions (such as IPv6 and others) and gear; perform technical evaluations of proposed solutions and gear; provide detailed reports on all evaluations and pilots conducted; lead the development, design, testing, and implementation of technical solutions; provide analysis and reports of traffic, data, September 2012 Page 13 of 33 utilization, circuits, applications, trends, and other information to support Circuit Actions and Course(s) of Action recommendations as required.

The Project Integration Operations requirement includes contractor support for the Weapons and Tactics activities of the 26 NOS as well as for the Project Management Program in 26 NOS.

Contractor support for Weapons and Tactics includes providing SMEs with senior level knowledge of how to apply lessons learned in operations to new tactics, techniques and procedures that can be applied consistently by the operators in the performance of 26 NOS mission duties. The Contractor shall develop appropriate documentation and training to ensure lessons learned are socialized within the organization and across the other squadrons to help prevent repeating mistakes. Contractor support for the Project Management Program in 26 NOS requires project management professionals who can lead project teams and manage multiple projects simultaneously while effectively managing resources and budget.

3.2.6 AOL/COOP OPERATIONS

The 26 NOS Network Operations requirement is a 24x7x365 mission that requires subject matter expertise (SME) level support from the contractor every hour of every day of the year. Contractor SME support for 26 NOS AOL/COOP Operations must provide senior network engineers on all shifts every day to accomplish the mission of operating, managing and defending all routers, switches, appliances, and other network devices involved in the execution of the 26 NOS mission. On-call support is not sufficient to satisfy the requirement of 24x7x365 support to the AOL/COOP Operations element of the 26 NOS mission. Typical AOL/COOP Operations activities accomplished by the contractor include, but are not limited to, the same tasks and functions performed by the Network Operations, Security Operations, DNS Operations, Support Operations, and Crew Operations.

During normal operations, the 26 NOS AOL/COOP personnel will act as an additional and supporting element of the Network Operations, Security Operations, Support Operations, and Crew Operations elements of the 26 NOS mission. In contingencies, emergencies, designated exercises and at such other times as authorized by the 26 NOS Commander, Director of Operations, or Technical Advisor, the 26 AOL/COOP Operations will perform the primary mission elements of the 26 NOS (not including Project Integration and Engineering Operations) and may be augmented by additional personnel relocating from the Gunter Annex, Maxwell Air Force Base, Alabama, facility to the Lackland Air Force Base, Texas facility. The Contractor will, in cooperation with the Security Operations Flight Commander of the 26 NOS, develop and maintain a written Continuity of Operations Plan that will facilitate the implementation and execution of the AOL/COOP Operations requirement of this PBWS (A015).

3.2.7 CREW OPRATIONS

The 26 NOS Crew Operations requirement is a 24x7x365 mission that gives the 26 NOS Commander the ability to command and control (C2) squadron operations around the clock. The Crew, led on each shift by a Crew Commander, serves as the entry point into and out of the squadron concerning all operations matters. Crew Commanders are assisted in their duties by Operations Controllers and Event Managers. Operations Controllers provide the Crew Commander with technical and administrative support; conduct research into present and past operations; prepare reports;

participate in meetings; and other duties as directed by the Crew Commander, Director of Operations, Squadron Commander or other authority as determined by 26 NOS Commander. Event Managers assist the Crew Commander through ticket management; trend analysis reporting on tickets;

coordinating single point of contact (SPOC) duties; and other tasks as directed by the Crew Commander, Operations Controller, or other authority approved by the Squadron Director of Operations. Crew Commanders and Operations Controllers are typically military or government

September 2012 Page 14 of 33 civilian. Event Managers may be either military, government civilian, or Contractor personnel qualified to carry out the duties as required. Contractor personnel assigned to Crew Operations must be able and authorized to work shifts that parallel those of the Crew to which they are assigned.

September 2012 Page 15 of 33

4 CONTRACT DELIVERABLES (CDRLs)

This section identifies the contract deliverables (CDRLs) required by this PBWS. The main deliverable is the 24x7x365 support to the 26 NOS mission as specified in the PBWS. The CDRLs identified in this section are the specific reports, data, documents, schedules and other materials that are required by the PBWS. Each CDRL is identified by a number consisting of the letter “A” and three digits (A001 for example) as well as a descriptive title (Weekly Activity Report for example). Table 2 summarizes the CDRLs, their descriptive title, whether format or template is provided by the Government or the Contractor, frequency required, and date due.

CDRL TITLE FORMAT FREQUENCY DUE

A001 Capabilities Health/Performance Report Contractor Monthly 5th of Month A002 Record of Changes/Upgrades/Patches Government Monthly 5th of Month A003 Technical Evaluation/Solutions Report Government As needed As needed A004 Integrated Master Schedule Government Monthly 5th of Month A005 Analysis of Operations Report Contractor Quarterly 15th of Month A006 Data Call Response Government As needed As needed A007 IT/Network Trend Analysis Report Contractor Quarterly 15th of Month A008 ODC Estimate and Assessment Contractor As needed As needed A009 Technology Insertion Recommendation Contractor As needed As needed A010 Semi-Annual Trend Analysis Report Contractor Semi-Annually 20th of Month A011 Project Management Review Brief Government Quarterly 10th of Month A012 Weekly Activity Report Government Weekly Wednesdays A013 Procedures/Guidance Drafts Government As needed As needed A014 Agreement Review/Recommendation Government Annually 1st of Feb

Table 2. List of Contract Deliverables (CDRLs)

September 2012 Page 16 of 33

5 SERVICE SUMMARY (SS)

Performance Objectives

PBWS

Par.

Performance Threshold

Method of Surveillance Remedy

September 2012 Page 17 of 33

6 GOVERNMENT FURNISHED PROPERTY AND SERVICES

The government will furnish on-site contractor personnel physically working in the 26 NOS facilities the necessary space, computer equipment, software tools/licenses, telephones and office supplies needed to accomplish requirements identified in the PBWS. The aforementioned items are provided for official Government authorized purposes only and shall not be used for any other reason. The contractor is responsible and accountable for the property and must establish and maintain a system to control and protect the property. They must also be adequate to assure that the government property will be used only for those purposes authorized in the contract.

September 2012 Page 18 of 33

7 ADDITIONAL SPECIAL REQUIREMENTS

7.1 SURGE REQUIREMENT

The Contractor shall meet Government unanticipated requirements for surge support in a timely manner, if directed in writing by the Government Contracting Officer (PCO). If a requirement and/or deadline cannot be met with existing contractor resources, the PCO shall determine if the requirement falls within the scope of this order. If it falls within the scope, the Government shall utilize that order as the vehicle for procuring this additional support. Upon such a determination, the PCO shall request from the Contractor a proposal to meet the requirement. Upon receipt of the Government's Request for Proposal (RFP), the Contractor shall identify within ten (10) working days any additional qualified personnel and funding needed to meet the requirement.

7.2 MEETINGS

7.2.1 POST AWARD

The contractor shall meet with Government representatives within 10 workdays after the contract award to reach a common understanding of task order requirements, deliverables, and Government expectations. This meeting will be performed at no additional cost to the Government via telecom or on-site at the contractor’s own expense. A copy of current operating procedures will be available after contract award. Contractor shall review and make any necessary changes to the operating policies and submit to the Government for concurrence within 60 days from contract award.

Contractor shall provide updates to the procedures when required by 26 NOS operations.

7.2.2 TECHNICAL INTERCHAGE MEETINGS

When major projects require 26 NOS participation in Technical Interchange Meetings (TIM), the Contractor shall provide technical expertise for all technical reviews and meetings. An example of this type requirement is a TIM to discuss the projected rollout of a new technology across the Air Force Enterprise such as Voice over Secure Internet Protocol (VoSIP).

7.3 TRANSITION PLAN

7.3.1 BEGINNING PLAN

Work with incumbent contractor during overlapping periods of performance. During the start up period the new contractor shall shadow the incumbent contractor staff, observing all system maintenance, sustainment, and surveillance activities for a period up to 14 days; during the transition, the incumbent shall retain complete responsibility of the 26 NOS requirements as stated in PWBS. At the conclusion of the shadowing and mentoring period, the new contractor shall assume complete responsibility for the performance of the work detailed within this PBWS.

September 2012 Page 19 of 33

7.3.2 ENDING PLAN

If a subsequent task order is awarded to another Contractor, the incumbent Contractor shall work with the new Contractor during any overlapping periods of performance to ensure a smooth transition.

The intent of the startup transition is to minimize the risk associated with and potential disruption of service resulting from transferring responsibility from a long-term incumbent to a new staff. In the event, that contract is awarded to the incumbent no transition costs shall be allowed.

7.4 DATA RIGHTS AND OWNERSHIP

The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

7.5 CONTRACTOR AND GOVERNMENT RELATIONSHIPS

Contractor personnel shall work with Government personnel primarily in Government facilities.

Contractor personnel will require daily access to government documents, computer software, computer hardware, and media, as it relates to support of this effort. Contractor shall dictate its employees’ compensation, benefits and rewards. The Government and the Contractor understand and agree that the services to be delivered under this contract by the contractor to the Government are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the contract between the Government and the Contractor's personnel. It is, therefore, in the best interest of the Government to afford both parties a full understanding of their respective obligations.

Contractor personnel under this contract shall not: (1) Be placed in a position where they are under the supervision, direction, or evaluation of a Government employee. (2) Be placed in a position of command, supervision, administration or control over Government personnel, or over personnel of other Contractors under other contracts, or become a part of the Government organization. (3) Be used in administration or supervision of Government procurement activities. The services to be performed under this contract do not require the Contractor or his/her personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor. Inapplicability of employee benefits this contract does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply. Government employees are required to keep the relationship with contractors above reproach.

7.6 NON-DISCLOSURE REQUIRED

Contractor personnel shall be exposed to information covered under the Privacy Act of 1974, and shall comply with all applicable safeguarding and handling of requirements associated with Privacy Act information and preventing the unauthorized disclosure of Confidential Information.

September 2012 Page 20 of 33

7.7 ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

An OCI is the existence of a set of circumstances in which a contractor may be unable to render impartial advice to the government, or might have impaired objectivity in performing contracted work; or may obtain an unfair competitive advantage in the marketplace when competing for government offered work where that unfair advantage is obtained during performance of a government contract. This unfair advantage can be introduced when the contractor sets the “ground rules” of procurement thereby biasing a future competition.

7.8 QUALITY ASSURANCE (QA)

The contractor shall ensure personnel with privileged access to the network be bound by the requirements of QA MAJCOM, NAF, 67 NWW, 26 NOG, and 26 NOS guidance.

7.9 TRAINING AND INSTRUCTION

The Contractor shall:

7.9.1 Provide Initial Qualification and Mission Qualification training to any newly assigned 26 NOS and support personnel to further enhance their organizational, analytical and functional knowledge of computer security, system vulnerabilities, exploits, hacking patterns, and countermeasures. This training shall be done in accordance with MAJCOM, NAF, 67 NWW, 26 NOG and 26 NOS training guidance and directives.

7.9.2 Document and maintain training plans for all 26 NOS flights.

7.9.3 Provide technical advice and knowledge transfer to individuals assigned to the 26 NOS.

7.10 KNOWLEDGE/CERTIFICATION REQUIREMENTS

Contractor personnel shall have minimum knowledge and certifications identified in Appendix A of

PBWS.

7.11 PERIODS OF PERFORMANCE

The anticipated period of performance is as follows:

Base Period: 9 September 2014 – 8 September 2015

Option Period 1: 9 September 2015 – 8…