Attch_1b_-_TO_0002_-_PWS_-_AVAC-17May17.pdf

ATTACHMENT 1b

Contract: MS&A for Space and Cyberspace Capabilities (MSCC)

Task Order: Air Force Space Command (AFSPC) Virtual Analysis Capability (AVAC) System Management and Support Task Order (TO)

Period of Performance:

Base Yr - 1 June 18 - 31 May 19 Opt Yr 1- 1 June 19 - 31 May 20 Opt Yr 2- 1 June 20 - 31 May 21 Opt Yr 3- 1 June 21 - 31 May 22 Opt Yr 4- 1 June 22 - 31 May 23 Opt to Extend Services- 1 June 23 – 30 November 23

Organization: HQ AFSPC/A9XY Address: 150 Vandenberg St, Suite 105, Peterson AFB, CO 80914-4570 Date: 17 May 2017

EXECUTIVE SUMMARY

This work is to be performed in accordance with (IAW) this TO Performance Work Statement (PWS) the Basic IDIQ PWS, section 3.7 is in support of Headquarters AFSPC. It is Requirement 7, section 3.7, on the Basic Indefinite Delivery/Indefinite Quantity (IDIQ) contract PWS. Unless otherwise stated, work shall be in accordance with this PWS and the Basic IDIQ PWS.

1. PURPOSE/DESCRIPTION OF SERVICES

1.1 The overall purpose and objective of this task order is to obtain non-personal services to manage, operate, sustain and provide logistical and general support for the AVAC system as identified in the Basic IDIQ PWS.

1.2 BACKGROUND INFORMATION. The HQ AFSPC Virtual Analysis Capability (AVAC) system is a stand-alone network which provides a crosscutting technology capability to conduct, support, and report analysis. The AVAC network provides AFSPC analysts with a variety of hardware (HW) and software (SW) options from Windows based systems to Linux based systems which includes many different analytic models and tools across a number of stand-along and networked classified and unclassified systems.

1.3 The contractor shall deliver all tasks identified in this task order in accordance with the specific tasks in this PWS as well as adhering to the Basic IDIQ PWS.

1.4 The contractor shall provide professional, administrative, technical, Operations and Maintenance (O&M) Information Technology (IT) support for the AVAC network supporting HQ AFSPC and their customer’s analytical needs. The IT services, as identified in this PWSand the Basic IDIQ PWS, are ultimately the responsibility of the contractor for day-to-day operational effectiveness of the AVAC network. The primary location of this support is Building 1, with additional support to Building 1470, Peterson AFB, Colorado, 80914.

2. SCOPE

2.1 To provide AVAC Operation and Maintenance (O&M) services. The Contractor shall provide non-personal services to manage, operate, sustain and provide technical, logistical and general support for IT services and service assets. To include: Integration of capabilities across a number of stand-alone and networked classified and unclassified systems; Procure Hardware/ Software (HW/SW) for the AVAC network; Install HW/SW; Operate, Maintain, Troubleshoot, and diagnose problems on the AVAC network. The Contractor shall provide System/Network Administration, IT Planning, Network Management and Operations, Information Protection (IP), Information Assurance (IA) and Help Desk (HD) services.

2.2 The Contractor shall provide all levels of AVAC maintenance and support. Contracted specific services include: help desk support; operations and maintenance; technical management and applications management; IT design, test and validate; component installation; system diagnostics and troubleshooting; system component repair/replacement; HW/SW handling and accountability; technical refresh/lifecycle replacement; network, systems, and storage administration; network and security operations; configuration control and management;

IA/cybersecurity; user training; asset inventory accountability; maintenance for AFSPC assets not covered by vendor warranty; information security mechanisms and execute Information Protection (IP) processes for AFSPC to include detection and correction of viruses and other security hazards. The Contractor shall work with the Government in a partnership relationship to achieve operational requirements and functional excellence while complying with all government laws, directives, instructions, Standard Operating Procedures (SOP), checklists and guidance.

(See Attached Technical Library).

3. REQUIREMENTS

3.1 GENERAL REQUIREMENTS

3.1.1 The Contractor shall possess required clearances, up to TOP SECRET-SENSITIVE COMPARTMENTALIZED INFORMATION (TS-SCI), on contract start date. The Contractor shall provide all personnel, training, transportation and any other items and services necessary to perform O&M under the contract unless defined in this PWS as Government provided.

3.1.2 The Contractor shall procure, install, and provide life-cycle maintenance of Personal Computers (PCs), servers, peripherals, storage systems, data backup systems, virtual systems, Local Area Network (LAN) network connectivity equipment, drivers, operating systems, and other software. The Contractor shall integrate Windows servers and Linux servers with Windows PCs. The Contractor shall perform complex software/hardware (sw/hw) troubleshooting to include communications skills to escalate to manufacturers/IT vendors technical staff, as required. The Contractor shall implement current trends/best practices in Information Technology to analyze systems, develop & evaluate alternatives, and implement solutions. The Contractor shall implement Active Directory domain management and services.

3.1.3 The Contractor system administrator shall possess a current Security+ IA certification level, at a minimum, on contract start.

3.1.4 The Contractor shall interface with other contractors and Government agencies in support of issues surrounding the evolution and operation of the AVAC’s classified and unclassified networks and systems including administrative network support. In the performance of this task, the Contractor shall support AFSPC and their customers on a day-to-day basis in the areas of information sharing strategy, information technology services, and information exchange and interchange.

3.1.5 The Contractor shall provide all required aspects of support: To include, depending on the nature of the task and the customer, support of each instance. These functional categories/instances include, but not limited to, helpdesk support, system and network management, network security, collaboration, performance management, voice, enterprise management, configuration management, and training. All phases or functional areas contained above are part of the continuing effort to manage life cycle information technology.

3.1.6 The Contractor shall maintain and update all documentation contained within the Technical Library as changes occur and shall make the Technical Library available to the Government at any time, upon request.

3.1.7 The Contractor shall provide all reports and plans referenced in the PWS as being made available to the applicable Government, Functional Commander (FC), applicable Contracting Officer’s Representative (COR) or Contracting Officer (CO) upon request.

3.1.8 The Contractor shall attend meetings, if needed or as directed, and 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. These meetings include, but are not limited to the following: weekly O&M meetings; meetings to address day-to-day issues, requirements and priorities; meetings to review, discuss and receive approval for new requirements. In addition, Quarterly Program Management Reviews (PMRs) shall be briefed by the Contractor to provide the Multi-Functional Team (MFT) an overall status of the contract, including performance metrics, work in progress, any open issues that need resolution, contract expenditure/funding status, and meetings with customers to discuss requirements and issues. The Contractor shall document the actions listed above in the quarterly PMR reports. (CDRL A100: Technical Report-Study/Services).

3.2 SPECIFIC REQUIREMENTS

3.2.1 SUBTASK 1 – Information Technology Planning.

3.2.1.1 Lifecycle. The Contractor shall coordinate development and implementation of a life-cycle management plan. The Contractor shall support future budget analysis, recommendations on HW/SW upgrades, and implement Government-approved annual Technology Refresh.

(CDRL A008: Contractor Configuration Management Plan)

3.2.1.2 Manage AVAC IT request actions. The contractor shall interface with customers on a day-to-day basis, regarding IT requests, initiate work orders, and ticket status of all IT requests.

The Contractor shall follow-up with the appropriate customer for each IT request and document status in the AVAC ticket system.

3.2.1.3 Prepare Network Migration and Upgrade. The Contractor shall prepare network migration and upgrade plans. These plans may be required to support downward directed requirements by DoD or Higher Headquarters (HHQ) and be coordinated with the COR. The Contractor shall update these plans and make them available to the COR for review prior to implementation. The Contractor shall implement these plans upon the Government’s decision to execute. (CDRL A008: Contractor Configuration Management Plan)

3.2.1.4 Identify Future Network Requirements. The Contractor shall coordinate with the Government to define and develop plans to include cost, schedule, and technical data for improving the capability to meet the needs of the AVAC network, customers and downward-directed objectives. The Contractor shall update these plans as needed and make them available to the COR upon request. (CDRL A008: Contractor Configuration Management Plan)

3.2.2 SUBTASK 2 – AVAC O&M Network Services. The Contractor shall provide the following non-personal services/support actions:

3.2.2.1 Integrate the AVAC capabilities in support of AFSPC analysis and administrative duties.

Maintain the AVAC networks and systems backbone necessary to promote efficient AVAC operations.

3.2.2.2 Provide HW configuration and maintenance services, network communication services, and system administration services.

3.2.2.3 Integrate and provide system/network and administrative support for newly acquired HW/SW to the AVAC network.

3.2.2.4 Configure software applications to work within each workstation environment.

3.2.2.5 Perform installations, operations, maintenance, and troubleshooting and upgrade of systems/network to include computer HW, domain name service, directory services, file/print service, operating systems, and their peripherals in support of the M&S capabilities.

3.2.2.6 Respond to outages/degradations and coordinate any maintenance actions to bring the system/network back to full functionality and restore services IAW thresholds in the Service Summary.

3.2.2.7 Schedule AVAC equipment to support demonstrations, tests and analysis for update, modification, and maintenance with COR prior approval.

3.2.2.8 Identify and report schedule conflicts to the COR for resolution.

3.2.2.9 Conduct weekly AVAC backups and provide retrieval of data as necessary IAW thresholds in the Service Summary.

3.2.2.10 Configure SW tools to make use of multi-central processing unit processors as well as assistance with input/output setup for programs that make use of environment variables.

3.2.2.11 Provide training and application for AVAC HW/SW, backup system, and any other system used in or with the AVAC network.

3.2.2.12 Submit configuration changes to the AFSPC Configuration Control Board (CCB) IAW Service Summary performance threshold. This will vary due to configuration requirements changing daily. CCB will be at the discretion of COR.

3.2.2.13 Tear-down, stand-up, and provide system/network administration support to portable decision-aiding/collaborative networks.

3.2.2.14 Create and carry out security procedures IAW Air Force security requirements, AFI 16-1404 Information Security Program Management, 29 May 2015, and AFI 33-202 Computer Security, 30 August 2001, for each AVAC system/network.

3.2.2.15 Ensure the integrity of centrally managed servers and data. Manage, store, dispose, restore, test backups, and maintain backup systems.

3.2.2.16 Maintain the AVAC filing/retrieval system for information, data, and reports.

3.2.2.17 Provide complete assessment and authorization documentation/artifacts, assistance, inputs, and support to the Information Assurance Officer (IAO) for the certification, accreditation and re-accreditation (C&A) process to obtain an Authorization to Operate (ATO) for the AVAC network for existing and new systems per DoD regulations and Risk Management Framework construct. Documentation for systems includes, but is not limited to servers, infrastructure, devices/equipment for existing/new systems that include at a minimum Security Technical Implementation Guide (STIG) review and findings, vulnerability scans, security (Information Assurance (IA)) controls, risk assessment to include business impact, scorecard, system identification plan, topologies, implementation plan, and other documentation as required per the Government and DoD guidance. (CDRL A008: Contractor Configuration Management Plan)

3.2.2.18 Deliver a Monthly Status Report (MSR) in the form of a Word document highlighting activities completed in the previous month and project activities in the upcoming month and include showing purchases utilizing AVAC funds. (CDRL A048: Contractor’s Progress Status and Management Report)

3.2.3 SUBTASK 3 – AVAC Network Configuration Management (Classified and Unclassified). The Contractor shall provide the following services/support actions:

3.2.3.1 Perform network configuration modeling and develop a network switching/routing plan to ensure AVAC mission priorities are taken into consideration. (CDRL A008: Contractor’s Configuration Management Plan)

3.2.3.2 Manage, configure, install, troubleshoot, maintain, and upgrade Government-approved trouble ticket systems, servers, and databases. The applicable COR or designated government representative shall review database structures and require additional fields of information as processes change. The Contractor shall make the trouble ticket system and database available for Government access, use, and review at all times.

3.2.3.3 Identify, resolve, or propose solutions for systems problems that may affect communications, processing, or efficiency.

3.2.3.4 Perform and monitor change management procedures as established for the network.

Perform and monitor system modifications, which have been approved by the CCB. Schedule, track, and coordinate all network changes through the COR. These changes shall include, but not be limited to: modifications to update the network configuration and new services implementation and installations. Record the status of these actions in the Technical Library.

3.2.3.5 Support the configuration change control process to ensure architecture or system modifications do not negatively impact the performance of Enterprise IT systems that support operational AVAC requirements.

3.2.3.6 Provide recurring modeling and simulation support.

3.2.4 SUBTASK 4 - Information Protection. The Contractor shall provide the following services/support actions:

3.2.4.1 Monitor system/network event and error logs to identify weak configurations and security vulnerabilities. Report all anomalies and make recommendations on the level of any threat posed and any actions that may be necessary to correct the anomalies and correct unsatisfactory conditions caused by these anomalies. Provide mitigation actions/activities as required to address findings annotated during remote vulnerability scans and remote compliance assessment scans to address at a minimum Category (CAT) 1 findings fixed/mitigated within 30 days of notification. (CDRL A008: Contractor’s Configuration Management Plan)

3.2.4.2 Immediately report any system/network abuse discovered to the IAO. The Contractor shall not take any action to notify the abuser, collect additional information on the abuser, or to correct abusive activities without specific authorization from the COR for each case.

3.2.4.3 Protect the AVAC network on a weekly basis from malicious code. Install current anti-virus software, updates, patches, and definitions on every information system and device.

3.2.4.4 Change administrator passwords on Government computer systems and network communications systems every 60 days. The passwords shall be made available to the Government at all times.

3.2.5 SUBTASK 5 - Help Desk. The Contractor shall provide the following services/support actions:

3.2.5.1 Provide helpdesk, incident, and problem management services. Provide trouble assistance to customers, including remote technical support.

3.2.5.2 Provide help desk support to resolve problems/issues on the AVAC networks. The contractor shall provide help desk coverage from 0730am to 1630pm, Monday through Friday, excluding observed federal holidays or unless otherwise specified. The Contractor shall open trouble tickets for problems within the AVAC network. All user problems not resolved within one (1) business day will be briefed daily to the government IT lead and/or COR, until resolved.

3.2.6 SUBTASK 6 - Equipment Control. The Contractor shall provide the following services/support actions:

3.2.6.1 Provide equipment accountability and asset management. Support the AFSPC Information Technology Equipment (ITE) custodian in conducting an annual physical Inventory of ITE equipment associated with the AVAC network and ensure the update is reflected in the Technical Library.

3.2.6.2 Upon receipt of deliveries, identify all accountable items and provide documentation and serial number information to the government for input into the Asset Inventory Management System (AIMS). The government shall provide AIMS barcode labels to the Contractor.

3.2.7 SUBTASK 7- Software Licenses and Inventories. The Contractor shall provide the following services/support actions:

3.2.7.1 Procure and update all software licenses and inventories and ensure the update is reflected in the Technical Library.

3.2.7.2 Joint Inventory. Participate in a joint inventory of documentation in at least each functional area listed below and ensure, if applicable, any updated inventory is reflected in the Technical Library:

• Management/Operations Files/Documentation/Libraries

• Software and System Analysis

• Equipment Maintenance and Management

• Supply

• Security

• Quality Control Inspections

• Project Folders

• Outstanding trouble tickets

4. CONTRACTUAL REQUIREMENTS (Reference the Basic IDIQ PWS, section 4, in addition to this TO)

4.1. CONTRACTOR PERSONNEL

4.1.1. The Contractor shall appoint a Task Lead (TL) who shall coordinate with the COR,Alternate COR or CO to obtain and clarify contract requirements. This shall be the individual who coordinates with the Government on matters of contract or contractor performance. The Contractor TL shall interface daily with the government technical lead, COR, alternate COR or designated individual for the day-to-day operations, actions, and priorities of the AVAC system. In the absence of the Contractor TL, the designated alternate, shall have full authority to act for the Contractor on all matters relating to the day-to-day operation of this contract.

4.1.3 The Contractor, along with the government technical lead, COR or alternate COR, shall ensure their personnel do not perform any inherently governmental activities. The Contractor shall ensure their personnel do not attempt to represent the Government of the US or AFSPC to any other person or entity, U.S. or foreign, except for delivering a government-approved message or position. The Contractor shall, under government guidance, may coordinate with other contractors during the performance of this contract. The Contractor shall ensure their personnel identify themselves as contractors when coordinating with government employees or other contractors.

4.2 TRANSITION OF EFFORT

4.2.1 The main objective of the transition effort is to ensure continuity of services and operations identified in this PWS. During the transition period, the successor contractor shall become familiar with the existing network resources, processes/procedures, and the day- to-day services performed by the incumbent contractor. The successor contractor shall not impede the performance of the incumbent contractor.

4.2.2 Phase-In

4.2.2.1 To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the contractor shall have personnel on-site during the phase-in period.

During the phase-in period, the contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

4.2.2.2 Initial Transition Assessment. The contractor shall perform a complete assessment of the AVAC IT Environment to gain an understanding, contractual responsibilities, state of services and IT infrastructure, current transition work flow/processes and volumes (e.g.

incidents/ requests), projects status, and service provider organization relationships. The contractor shall provide an initial transition assessment 14 calendar days after contract award to the COR that addresses all actions necessary to ensure a seamless transition. Details of Government expectations will be covered during the Contract Award Pre-brief. (CDRL A008:

Contractor’s Configuration Management Plan)

4.2.2.3 Transition Activities required, but not limited to:

4.2.2.3.1 Coordinate the transition schedule with the incumbent and identify schedule conflicts.

4.2.2.3.2 Obtaining all system and network diagrams and ensuring accuracy with incumbent contractor, identify any missing information to perform a successful Technical/Application Management transition.

4.2.2.3.3 Along with the incumbent Contractor, perform a physical inventory of all systems/ equipment against appropriate accountability documents.

4.2.2.3.4 Transfer of system accounts and administrative passwords.

4.2.2.3.5 Provide listing of security badging requirements by individual.

4.2.2.3.6 Identify all outstanding work orders.

4.2.2.3.7 Identify all points of contact for HW/SW maintenance/license renewals.

4.2.2.3.8 Obtain all combinations to cipher locks, padlocks, safes, vaults, and push-button door locks from the Government. Obtain keys to Government-furnished offices, buildings, storage cabinets, desks, and padlocks from the incumbent.

4.2.3 Phase-Out

4.2.3.1 The Contractor, shall develop and implement a transition plan prior to the end of the final performance period. The Period of Performance (PoP) for the transition should be approximately thirty (30) days from award of follow-on contract. In the event the follow-on contract is awarded to other than the incumbent, the incumbent contractor shall cooperate to the extent required to permit an orderly transition to the successor contractor.

4.2.3.2 Coordinate the transition schedule with the successor and identify schedule conflicts.

4.2.3.3 Along with the successor Contractor, perform a physical inventory of all systems/ equipment against appropriate accountability documents.

4.2.3.4 Identify all outstanding work orders to the successor.

4.2.3.5 Identify all points of contact for HW/SW maintenance/license renewals.

4.2.3.6 Transfer all Government owned supplies, equipment, materials, and auditable records to the successor.

4.2.3.7 Along with the successor Contractor, jointly inventory and transfer classified materials.

4.2.3.8 Terminate long-term Contractor Visitor Security Agreement (VSA) with appropriate security office.

4.2.3.9 Provide successor Contractor with combinations to cipher locks, padlocks, safes, vaults, and push-button door locks. Provide keys to Government-furnished offices, buildings, storage cabinets, desks, and padlocks.

4.2.3.10 Coordinate exchange of all applicable passwords with successor Contractor.

4.2.3.11 Return all restricted area badges to the Government security manager and schedule a security debrief with the HQ AFSPC/SSO office.

4.3 PLACE OF PERFORMANCE (Reference the Basic IDIQ PWS, section 4.4, in addition to this TO)

4.3.1 Work in support of the requirements on this TO shall be performed at 150 Vandenberg St, Ste 1105 (Bldg 1), and 250 S. Peterson Blvd (Bldg 1470), Peterson AFB, Colorado 80914.

4.4 DUTY HOURS

4.4.1 Work hours are weekdays (Monday-Friday) from 0730-1630, unless otherwise specified.

Circumstances may require the Contractor provide services after normal duty hours. Overtime hours will not be authorized.

5. SERVICE SUMMARY (Reference the Basic IDIQ PWS, section 5, in addition to this TO)

Performance Objective PWS Ref Performance Threshold

Maintain AVAC network and infrastructure availability

3.2.2.6 Respond to outages and degradations

within 24 duty hours.

Coordinate maintenance actions for external support

3.2.2.6 Restoration is satisfied by repair, replacing or by assumption of functionality within 24 duty hours

Perform AVAC backups 3.2.2.9 Weekly Provide CCB configuration changes 3.2.2.12 As required for configuration change Compliance with DD254, Contract Security Classification Specification, to include proper handling, storage, transmission, and destruction of classified materials

9 No security violations

6. GOVERNMENT-FURNISHED PROPERTY/INFORMATION (GFP/GFI) (Reference the Basic IDIQ PWS, section 6, in addition to this TO)

6.1 The contractor shall be provided up to two (2) workspaces in Bldg 1 and/or 1470, Peterson AFB; this includes desk space, chair, and computers connected to the NIPRNET/SIPRNET and AVAC networks, and use of telephones, copier and fax machines. Any additional personnel may be required to work at the Contractor’s facility.

7. CONTRACTOR IDENTIFICATION (Reference the Basic IDIQ PWS, section 7, as needed for this TO)

8. DOCUMENTATION AND DATA MANAGEMENT (Reference the Basic IDIQ PWS, section 8, as needed for this TO)

9. PERSONNEL SECURITY (Reference the Basic IDIQ PWS, section 9, as needed for this

TO)

10. ACCESS TO GOVERNMENT PROPERTY AND FACILITIES (Reference the Basic IDIQ PWS, section 10, as needed for this TO)

11. CONTRACTOR SPECIAL COMPARTMENTED INFORMATION FACILITY (SCIF)

– Not Applicable for this TO

12. SECURITY ISSUES (Reference the Basic IDIQ PWS, section 12, as needed for this TO)

13. SYSTEM AND NETWORK AUTHORIZATION ACCESS REQUESTS (Referencethe Basic IDIQ PWS, section 13, as needed for this TO)

14. TRAVEL – No travel is expected for this TO

15. MATERIALS AND OTHER DIRECT COSTS (ODCs) (Reference the Basic IDIQ PWS, section 15, in addition to this TO)

15.1 The Contractor may be required to purchase reimbursable items costing less than $3,500.

Reimbursable purchases must be approved by the COR, in writing prior to purchase. Items exceeding $3,500 requires COR recommendation and written Contracting Officer approval. The Contractor shall not break up a purchase to meet this threshold. All Automated Data Processing equipment (computers, printers, copiers, fax, NIPRNET/SIPRNET e-mail accounts, etc.) associated with the performance of this TO will be procured by the Contractor, unless otherwise coordinated. In addition, the software associated with the performance of this TO will be procured by the Contractor.

16. TRAINING (Reference the Basic IDIQ PWS, section 16, as needed for this TO)

17. DATA DELIVERABLES (Reference the Basic IDIQ PWS, section 17, in addition to this

TO)

CDRL Requirement Description CDRL A008 Req 1 (3.2.1.1, 3.2.1.2, 3.2.1.3, 3.2.2.17, 3.2.2.18, 3.2.3.1, 3.2.4.1, 4.2.2)

Contractor’s Configuration Management Plan

CDRL A048 Req 1 (3.2.2.19) Contractor’s Progress, Status and Management Report

CDRL A100 Req 1 (3.1.7) Technical Report – Study/Services

Appendix A – Technical Library Appendix B – Publications – Reference Basic IDIQ contract as needed for this TO Appendix C – ACRONYMS – Reference Basic IDIQ contract as needed for this TO