Attachment_1_PWS_(Rev_1,_15_Nov_18)-22_Jun_2018_v5.pdf

FA7022-19-R-0001, US NDC OSS II PWS, 22 Jun 2018 Revision 1, 15 Nov 2018

PERFORMANCE WORK STATEMENT (PWS)

FOR

United States National Data Center (US NDC)

Operations Support and Studies (OSS) II

AFTAC/SDA

22 Jun 2018

Revision Number Date Revision Description

Revision 0 22 Jun 2018 Pre solicitation draft only Revision 1 15 Nov 2018 Correct reference in Paragraph 2.3.2.

1 DESCRIPTION OF SERVICES

1.1 INTRODUCTION

1.2 BACKGROUND

1.3 SCOPE

1.4 PERIOD OF PERFORMANCE

2 SPECIFIC TASKS

2.1 US NDC O&M TASKING STATEMENTS (O&M FUNDED)

2.2 US NDC SCIENTIFIC AND ENGINEERING STUDIES (R&D FUNDED)

2.3 PROGRAM SUPPORT (O&M FUNDED)

3 SERVICES SUMMARY (SS)

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES

4.1 SERVICES

4.2 FACILITIES

4.3 UTILITIES

4.4 EQUIPMENT

4.5 MATERIALS

5 GENERAL INFORMATION

5.1 CONTRACTOR IDENTIFICATION IN THE GOVERNMENT WORKPLACE

5.2 INDUSTRIAL SECURITY

5.3 PHYSICAL SECURITY

5.4 PRIVACY ACT

5.5 LOCATION(S) OF WORK

5.6 HOURS OF OPERATION

5.7 CONSERVATION OF UTILITIES

5.8 RECORDS

5.9 CONTRACTOR MANPOWER REPORTING

5.10 ENVIRONMENTAL CONTROLS

5.11 SAFETY REQUIREMENTS (IF APPLICABLE)

5.12 CONTRACTOR PERSONNEL TRAINING

5.13 SPECIAL TRAINING, CERTIFICATIONS AND QUALIFICATIONS

5.14 PERIODIC PROGRESS MEETINGS

5.15 CONTRACTOR TRAVEL AND OTHER DIRECT COSTS (ODC) (O&M FUNDED).

5.16 DELIVERABLES

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

APPENDIX B - ESTIMATED WORKLOAD DATA

APPENDIX C - APPLICABLE PUBLICATIONS & INSTRUCTIONS

APPENDIX D - MAPS AND/OR SITE PLANS

APPENDIX E – CONTRACTOR SUPPORT STAFF DESCRIPTIONS

APPENDIX F – US NDC STUDY DESCRIPTIONS

SECTION 1

1 DESCRIPTION OF SERVICES.

1.1 Introduction.

This is a non-personal services contract. The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. The contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services. The contractor shall notify the Contracting Officer (CO) immediately if they perceive any actions constitute personal services.

These services shall not be used to perform any Inherently Governmental Functions.

1.2 Background.

1.2.1 The Air Force Technical Applications Center (AFTAC) is tasked with monitoring compliance with existing and future nuclear weapons test ban treaties. To perform this mission, AFTAC uses several different monitoring techniques, each designed to monitor a specific physical domain (i.e., space, atmosphere, oceans, and underground) for nuclear explosions. These techniques together form the United States Atomic Energy Detection System (USAEDS).

1.2.2 The United States National Data Center (US NDC) is comprised of a primary operational subsystem (OPS) with a Remote Operations Center (ROC) and sustainment (SUS) and development (DEVL) subsystems located at Patrick Air Force Base (PAFB), Florida, and an alternate operational subsystem (ALT) at Millington, TN, and a training subsystem located at Goodfellow Air Force Base (GAFB), Texas. Additionally several special purpose and special access standalone subsystems are located at PAFB, FL.

1.2.3 The baseline functions of the operational US NDC are: (1) acquire geophysical (seismic, hydroacoustic, infrasonic) data from multiple sources including the USAEDS data collection networks and the International Monitoring System (IMS) networks; (2) relay raw data, when appropriate or required by international protocols, in near real-time to the International Data Center (IDC); (3) process and analyze the data via a series of software pipelines and fuse the results together into a single product; (4) archive the data and provide it electronically to US researchers;

and (5) provide reports to AFTAC’s customers. The ALT US NDC is the secondary operations location in case of interruption of US NDC capability due to natural or man-made events. The ROC provides a login and analysis capability to the US NDC or the ALT US NDC from another building on Patrick AFB to provide mission coverage during short-term scheduled or unscheduled outages.

1.2.4 The US NDC processes and integrates data and information up to and including the Department of Defense (DoD) TOP SECRET-SCI level.

1.2.5 The Government encourages use of existing non-developmental items, Commercial Off-the-Shelf (COTS) hardware and software, COTS documentation, and open systems architecture concepts.

1.2.6 This acquisition is a follow-on requirement to the United States National Data Center (US NDC) Operations Support & Studies (OSS) contract. This provided operational support services to the Nuclear Treaty Monitoring Directorate of the Air Force Technical Applications Center (AFTAC) from FY 2015 through 2019.

1.3 Scope.

1.3.1. The scope of work is to provide maintenance, sustainment, configuration management, database and system administration, development, testing and integration of geophysical data processing software, hardware, and geophysical data from both traditional and non-traditional sources into the US NDC system that includes the operational subsystem, alternate subsystem, training subsystem, sustainment/development subsystem, and special purpose/special access subsystems.

1.3.2 The scope of work also is to conduct studies focused on improving and developing the US NDC tools and methodologies for data collection, data analysis, event detection, event association, event location, event magnitude/yield estimation, event classification, seismic signatures repository, and advanced geophysical data processing needed to meet treaty-monitoring and national needs.

1.3.3 This Performance Work Statement (PWS) captures Contractor tasks and responsibilities for the Operations and Maintenance (O&M) of US NDC as well as for studies supporting the O&M efforts as described in the US NDC Phase-3 System Requirements Document (SRD) dated 19 Sep 2007. Upon acceptance of the US NDC Modernization Geophysical Monitoring System (GMS), the US NDC Modernization SRD shall replace the Phase-3 SRD. Specifically, the Contractor tests, integrates, implements, and sustains a data acquisition, data processing, and data archival hardware and software system that meets all the requirements stated in the US NDC SRD.

1.3.4 The non-personal services to be performed under this contract in support of the US NDC are operations support, and Geophysical and Information Technology (IT) studies related to maintaining and sustaining the operational US NDC, as well as improving overall system performance.

1.3.5 The contractor shall provide technical, systems engineering, program management, and logistical services on a task order basis. Services shall include, but not be limited to:

1.3.5.1 24/7 operational system support;

1.3.5.2 Change Request (CR) resolution;

1.3.5.3 CR integration, documentation, test, and promotion;

1.3.5.4 Operational and Alternate system maintenance;

1.3.5.5 Sustainment/Development system maintenance;

1.3.5.6 Training system maintenance;

1.3.5.7 Special purpose/Special access system maintenance;

1.3.5.8 Data services, including;

1.3.5.8.1 Integration of station data onto the US NDC;

1.3.5.8.2 Monitoring data acquisition statistics and addressing discrepancies;

1.3.5.8.3 Maintaining the data distribution software;

1.3.5.8.4 Maintaining the external web-portals and their products;

1.3.5.8.5 Managing data requests;

1.3.5.8.6 Integrating COTS data acquisition software; and

1.3.5.8.7 Performing maintenance on configuration files

1.3.5.9 Systems engineering (SE) process to develop, maintain, refine, and manage the technical approach for US NDC maintenance and sustainment using a comprehensive, iterative and recursive problem solving process, applied sequentially top-down by integrated teams. The four (4) steps that comprise the SE process are Step 1: Requirements Analysis; Step 2: System Analysis Control; Step 3: Functional Analysis/Allocation; Step 4: Design Synthesis;

1.3.5.10 Supportability including depot and organizational hardware and software maintenance, technical manuals, support equipment, Program Parts Lists (PPLs), spares, and training requirements into the total system support effort to minimize system life cycle costs and to ensure system supportability;

1.3.5.11 Research and Development (R&D) studies

1.3.5.11.1 Scientific studies focused on incorporating new and improved software, algorithms and knowledge into the US NDC;

1.3.5.11.2 Engineering studies focused on overall station and sensor tuning and calibrations, system infrastructure improvements, system hardware evaluations, and overall US NDC system performance monitoring.

1.4 Period of Performance.

1.4.1 This is an Indefinite-Delivery Indefinite-Quantity Contract covering a six (6) year ordering period.

1.4.1.1 Task orders for the scope of work identified in this PWS will be issued on an as-needed-basis. The PoPs for each task order will not exceed the performance period allowed for the applicable appropriations, but may exceed the six year ordering period plus a ninety (90) day phase-out period. This does not include any extension(s) of performance under FAR 52.217-8.

SECTION 2

2 SPECIFIC TASKS.

2.1 US NDC O&M Tasking Statements (O&M Funded)

Operations Support

2.1.1.1 24/7 System Support The Contractor shall provide 7 days-a-week, 24 hours-a-day on-call support for maintenance of the operational US NDC system. This support includes hardware and software maintenance support, system administration support, and database administration support. Support shall also be in response to system outages and in response to mission transfers, both actual and exercises.

Incident reports shall be filed for all 24/7 support items using the Configuration Management (CM) tool Rational Team Concert. Some incidents can be handled over the phone; however, on-site support is required if telephone support is not able to resolve the issue. Contractor shall acknowledge all notifications within 15 minutes either via phone call or in person. If an incident cannot be handled over the phone, Contractor shall be on-site within 60 minutes from the time of initial notification. All 24/7 system support incidents shall be worked continuously until resolved.

2.1.1.2 Geophysical Data Processing Software Change Request (CR) Resolution The Contractor shall resolve CRs in accordance with (IAW) the Change Management Board (CMB) Process Guide. The Contractor shall accept CRs and process them in accordance with the Systems Engineering Plan (SEP) and Software Development Plan (SDP). A CR is defined as any change to the US NDC operational baseline that has been approved by the Government. A CR may involve software or hardware or both. CRs may also involve determining optimal parameter settings requiring experience in processing geophysical data. (CRDL A004, SEP; A007, SDP) The Contractor shall:

a) Review and analyze the requirements associated with the CRs,

b) Produce preliminary technical designs,

c) Produce level-of-effort estimates for implementing the necessary changes to aid the

Government’s CMB prioritization process,

d) Implement new and modified software in response to the CRs, moving each CR through a well-defined progression of states as defined in the CMB Process Guide (e.g., submitted, assigned, opened, unit tested, peer reviewed, testbed, verified, validated, operational, post operational verified, post operational validated, closed, hold, evaluate, postponed, duplicate, rejected).

e) As defined in the US NDC CMB Process Guide resolve Urgent CRs within 72 hours of CMB approval.

f) As defined in the US NDC CMB Process Guide resolve station updates CRs for new stations within three (3) days of CMB approval.

g) As defined in the US NDC CMB Process Guide resolve station updates CRs for existing stations within five (5) days of CMB approval.

h) As defined in the US NDC CMB Process Guide complete post operations verification of CRs within one (1) week of promotion of the CR to the operational system.

i) As defined in the US NDC CMB Process Guide complete post operations validation of CRs within thirty (30) day of promotion of the CR to the operational system.

2.1.1.3 CR Integration, Test, and Promotion

The Contractor shall test, document, and execute CR resolutions from a CR branch to the test baseline and then to the operational baseline following the release process in the CMB Guide; this includes patches made to the operational system. As part of CR integration activities, the Contractor shall perform integration, testing, and promotion.

2.1.1.4 CR and DCN Status and Disposition

The Contractor shall present a summary of CRs and Document Change Notices (DCNs) at quarterly Program Management Reviews (PMRs) and weekly CMBs. The presentations shall contain at least the following information: total number of CRs, number of each CR in priority order, number of CRs opened in the period, and number of CRs promoted since the last PMR or CMB. The Contractor shall support the Government’s CMB, making recommendations to the board upon request. The Contractor is not a voting member of any Government board. (A001, Conf Min)

Maintenance

2.1.2.1 Operational/Alternate System Maintenance

The Contractor shall provide software maintenance support and system administration support to sustain the operational and alternate systems to include two special access systems. Software CRs are promoted to the operational and alternate systems on an as-needed basis, nominally monthly, but more or less often as is dictated by necessity. The Contractor shall coordinate their efforts with the Government Operational US NDC system administrators to minimize cost and schedule impacts.

2.1.2.2 Sustainment System Maintenance

The Contractor shall provide organizational and depot maintenance support for the US NDC sustainment system, which consists of: 1) a testbed which is maintained to be as identical as possible to OPS/ALT; 2) a development and research network supporting software development and studies. This system is used to develop and test software CRs prior to promotion to the operational system. This organizational and depot maintenance support includes hardware and software maintenance, computer system administration, and database administration. The Contractor shall coordinate their efforts with the Government Operational US NDC system administrators to minimize cost and schedule impacts.

2.1.2.3 Training System Maintenance

The Contractor shall provide software maintenance support and system administration support to sustain the US NDC Training System at the 312th Training Squadron, Goodfellow Air Force Base (GAFB), Texas, which shall include travel. Updates to the Training System shall be provided by the contractor on an annual basis. The Contractor shall coordinate their efforts with the Training System administrators to minimize cost and schedule impacts.

2.1.2.4 Special Event Analysis Tools (SEATools)

The Contractor shall support the maintenance of the SEATools suite of software; interfacing with users and providing problem report tracking and configuration management through the use of the Configuration Management (CM) tool Rational Team Concert. With the Government historically providing all of the actual software changes, the Contractor support to the Government shall include integration of these changes into the various SEATools baselines, engaging users to prioritize problems and enhancement requests, and the consolidation of the numerous versions of SEATools into a smaller number of versions. Contractor support shall also include configuration management of the field survey laptops; installation of the latest SEATools software version and Linux operating system updates; maintenance of the security accreditation packages; and preparation and recovery of the systems before and after deployments.

2.1.2.5 National Technical Nuclear Forensics (NTNF)

The Contractor shall support the maintenance of the National Technical Nuclear Forensics (NTNF) suite of software on the US NDC system interfacing with users and providing problem report tracking and configuration management through the use of the Configuration Management (CM) tool Rational Team Concert. AFTAC, in executing its part of the NTNF program, will acquire, store and process speed of sound data at the US NDC, followed by independent yield determination for interactively located events of interest.

2.1.2.5.1 NTNF Operational/Alternate System Maintenance

The contractor shall provide software maintenance support and system administration support to sustain the NTNF specific software on the operational and alternate systems. The Contractor shall coordinate their software CR promotion efforts with the Government Operational US NDC system administrators to minimize cost and schedule impacts.

2.1.2.5.2 NTNF Sustainment System Maintenance

The Contractor shall provide organizational and depot maintenance for the NTNF specific software on the US NDC sustainment system. This Organization and depot maintenance support includes hardware and software maintenance, computer system administration, and database administration.

The Contractor shall coordinate their efforts to minimize cost and schedule impacts.

2.1.2.6 Time Dominant Operations Center (TDOC)

The Contractor shall support the maintenance of the TDOC software on the US NDC system and provide problem report tracking and configuration management using the government’s CM tool.

The TDOC program is to provide operational analysis using treaty monitoring analytical tools focused on enhancing capabilities by:

a) Evaluating improvements to standard automatic process capabilities for subsurface data;

b) Evaluating new analytical techniques to improve the confidence level of current automatic processing capabilities; and

c) Evaluating incorporation of new and non-traditional data sources into the automatic processing capabilities at multiple classification levels.

2.1.2.6.1 TDOC System Maintenance

The contractor shall provide maintenance support, testing, development, tech support, and system administration support to sustain the TDOC specific software on the operational, alternate, sustainment, and special access systems. The Contractor shall provide organizational and depot level maintenance for the TDOC specific software and hardware on the US NDC system. This organizational and depot maintenance support includes hardware and software maintenance, computer system administration, and database administration. The Contractor shall coordinate their software CR promotion efforts with the Government Operational US NDC system administrators to minimize cost and schedule impacts.

2.1.2.7 Performance Monitoring

The Contractor shall monitor the performance of the operational system on a routine basis which includes: network processing, station processing, station availability, station quality (e.g., maintain and periodically update probabilistic noise power spectral density (PSD) plots), data availability, data quality control metrics, and trend analysis of hardware/software performance. In addition, the Contractor shall identify performance issues that adversely affect operations and implement or recommend corrective actions. The Contractor shall construct and maintain a web based display for disseminating current performance monitoring information and shall present system performance evaluations at performance monitoring meetings and PMRs.

2.1.2.8 Operational System Support

The Contractor shall provide engineering and scientific support to Government and Government-contracted support personnel, analysts, and evaluators using the operational systems. Additionally, and on a non-interference basis with support to the operational system, the contractor shall provide engineering and scientific support to Government and Government-contracted researchers using the development systems. Support shall include providing the Government with mechanisms for insight into understanding the operations and specialized applications of the system.

2.1.2.9 Data Services

The Contractor shall provide data services support which includes the integration of station data onto the US NDC; monitoring data acquisition statistics and addressing discrepancies; maintaining the data distribution software; maintaining the external web-portals and their products; managing data requests; integrating COTS data acquisition software; and performing maintenance on configuration files as the field system evolves. "Data services" primarily refers to the input and output of data and products.

Cross-Domain Transfer Services The contractor shall provide data management support, including technical support, testing, lifecycle management and system administration, to maintain and sustain the cross-domain data transfer subsystems critical to the operation of the US NDC. The contractor shall accomplish daily monitoring of the data flow processes used to transfer data to and through the cross-domain transfer systems. The contractor shall support troubleshooting, configuration, documentation, and testing of the data flow processes used to transfer data to and through the cross-domain transfer systems. The contractor shall support the architecture and lifecycle management of the cross-domain transfer systems under the US NDC hardware replacement and procurement process. The contractor shall provide data custodian and management services to ensure and enforce AFTAC and Air Force data transfer and data management policies and procedures are adhered to for all data flow through the cross domain transfer subsystems.

Systems Engineering The Contractor shall manage the US NDC program from a systems engineering (SE) viewpoint.

2.1.4.1 Systems Engineering Process

The Contractor shall develop, maintain, refine, and manage the technical approach via the following systems engineering planning and process documents: Systems Engineering Plan (SEP) and the Software Development Plan (SDP). The Contractor shall propose updates to these documents and submit them for Government approval and contractual implementation. The Contractor shall report on work in progress in accordance with the SEP and SDP at Government review meetings and PMRs. (A001, Conf Min; A004, SEP; A007, SDP)

2.1.4.1.1 Technology

As part of the Contractor’s on-going SE processes, the Contractor shall identify obsolete concepts and components and make upgrade recommendations with explicit rationale provided for each recommendation. The Contractor shall present this information to the Government at review meetings and PMRs. (A001, Conf Min)

2.1.4.1.2 Configuration Management

The Contractor shall assist the government in changing the baseline configuration of the US NDC system IAW the CMB Process Guide, by providing a series of software builds (i.e., promotion of CR fixes to the operational baseline). Each build augments previous US NDC functionality and performance. The Contractor shall use the Government-provided configuration management tools as documented in the Configuration Management Plan (CMP) and the US NDC CMB Process Guide. The Contractor shall make data supporting the change process available to the Government for audit upon request. The Contractor shall work with the government to incorporate any changes to the technical documentation in the operational baseline documentation. The Contractor shall help identify any problems not resolved upon completion of a build. (A009, SVD; A012, ICD)

2.1.4.1.3 System-Wide Requirements

The Contractor shall manage all System/Subsystem Specification (SSS) level requirements across the entire US NDC system using the Government-provided requirements management tool. The Contractor shall work with the Government to prioritize and allocate SSS requirements across all OPS Support and Studies activities.

2.1.4.1.4 System-Wide Configuration Items (CIs)

The Contractor shall maintain and document all CIs, both Hardware Configuration Items (HWCIs) and Computer Software Configuration Items (CSCIs) for the US NDC program. The Contractor shall capture CI identification information for the System/Subsystem Design Description (SSDD), Database Design Description (DBDD) and Interface Control Document (ICD). Updates to the SSDD and DBDD shall be submitted to the Government in accordance with document change procedures contained in the US NDC CMB Process Guide. (A012, ICD)

Supportability

2.1.5.1 Support Planning

The Contractor shall factor supportability considerations, including depot and organizational hardware and software maintenance, technical manuals, support equipment, Program Parts Lists (PPLs), spares, and training requirements into the total system support effort to minimize system life cycle costs and to ensure system supportability. The Contractor shall maintain documentation for system supportability, including a PPL with parts, spares, and support equipment. The Contractor shall maintain and document program parts in a top-down breakdown sequence and recommend Forward Supply Point (FSP) and bench stock supply levels (part number and quantity) in the PPL. The PPL shall include the following: Commercial and Government Entity (CAGE) Code; Item Name; Quantity Per End Item; Part Number – Vendor Part Number; Maintenance Level—(1) Organizational Level or (2) Depot Level; Cost – Purchase Price; FSP Level – Quantity Recommended for Forward Supply Point; Critical –Yes, if failure causes data loss; and Remarks Additional Information. The Contractor shall identify and recommend support equipment for operations, maintenance, and testing. The Contractor shall minimize the need for specialized equipment. The Contractor shall document support equipment in the PPL and Logistics Management Information (LMI) products. The Contractor shall present this information as requested by the Government Program Manager or Contracting Officer's Representative

(PM/COR). (A014, PPL)

2.1.5.2 Technical Instruction Manuals

The Contractor shall provide updates to the existing Technical Instruction (TI) manuals to support organizational maintenance and operation of OPS, ALT, ROC and Training Systems. Updates to TIs shall be submitted to the Government in accordance with document change procedures contained in the US NDC CMB Process Guide.

2.1.5.3 System Training

2.1.5.3.1 Operational Training

The Contractor shall provide training, using existing staff that concentrates on major differences between the current operational system and changes or upgrades made due to CRs. The training may include both classroom instruction and hands-on use of the equipment. Historically 5% of CRs have required training lasting approximately 4 hours per CR. The Contractor shall provide annual training to Government instructors at GAFB, TX, on changes specific to operations and maintenance of the delivered training system. (A001, Conf Min; A013, Tech Report)

Program Management The Contractor shall promote full and open communication between AFTAC personnel and personnel from the Contractor and associate Contractors. The Contractor shall perform management tasks to plan, organize, control, integrate, and execute contractual requirements.

(A002, MSR)

2.1.6.1 Program Management Reviews (PMRs)

The Contractor shall conduct formal PMRs every three months. In these reviews, the Contractor shall identify on-going tasks with associated schedules and expenditures to date, planned actions, staffing information and any difficulties encountered in performing work. The Contractor shall provide a draft agenda and draft presentation materials to the Government no later than three business days prior to each PMR. (A001, Conf Min)

2.1.6.2 Status Reporting

The Contractor shall prepare and deliver monthly program status reports (MSR). The status report shall include a description of all work efforts performed during the month for all PWS tasks. The MSR shall include a status of all data deliverables for the reporting period. The MSR shall include a status of all studies in progress or anticipated to begin within the next twelve months. (A002, MSR)

2.1.6.3 Risk Management

The Contractor shall develop and implement a Risk Management Plan (RMP). The Contractor shall identify, evaluate, and assess program risk and report this information, along with risk mitigation strategies and results, at PMRs and in MSRs. (A008, RMP)

2.1.6.4 Data Management

The Contractor shall implement and maintain a data delivery and tracking system as documented in a Contractor Data Management Plan (DMP) and IAW paragraph 2.1.6.5. The Contractor shall conduct internal data reviews to ensure all deliverable data conforms to Government Contracts Deliverable Requirements List (CDRL) requirements. The Contractor shall make all technical data available for review by the Government Contracting Officer’s Representative (COR). The Contractor shall prepare data for delivery to the Government. The Contractor shall supply technical documentation to the Government identified with (at a minimum) title, document number, revision, and date. The Government will have unlimited rights to use, duplicate or disclose all deliverable data, in whole or in part. (A003, DAL)

2.1.6.5 Records Management

Records management oversight of a Contractor’s records is necessary to ensure Air Force records keeping requirements are met. All records created as a result of processes prescribed in the PWS shall be maintained in accordance with AFMAN 33-363, Management of Records, AFI 33-364, Records Disposition-Procedures and Responsibilities, the Air Force Electronic Records Management Solution, AFTAC’s supplements to each of the fore mentioned publications, and are disposed of in accordance with the Air Force Records Disposition Schedule. At the conclusion/termination of this effort, all records shall be returned to the Air Force Office of Primary Responsibility (OPR) for proper disposition. Contractors who create and receive official records on behalf of the Air Force and are performing records management support are referred to as records professionals. Contractor records professionals shall be appointed in writing to the AFTAC Records Manager and shall meet the training and performance requirements identified in AFI 33- 322, Records Management Program and applicable AFTAC supplement. Contact the AFTAC Records Manager for specific guidance and procedures.

2.1.6.6 Quality

The Contractor shall perform quality reviews as defined in the Contractor’s Quality Management Plan (QMP). The Contractor shall ensure that the persons conducting quality control evaluations are not the persons who developed the product, performed the activity, or are responsible for the product or activity. This does not preclude such persons from taking part in these evaluations. The Contractor shall ensure that the persons responsible for ensuring compliance with the contract shall have the resources, responsibility, authority, and organizational freedom to permit objective quality evaluations and to initiate and verify corrective actions. (A010, QMP)

2.1.6.7 Proprietary and Licensed Items

The Contractor shall identify to the Government, prior to incorporation into the US NDC system, any software or hardware without unlimited rights. The Contractor shall not use or deliver any proprietary computer hardware or software for the integration, operation, or maintenance of the US NDC system without prior written Government PM or COR approval. The Contractor shall obtain and furnish to the Government copyright releases for all COTS products and provide copyright releases for all US NDC software and documentation generated by the Contractor as a result of this contract. The Contractor shall not incur any license fees, agreements, or other limitations on the use of proprietary resources without prior Government PM or COR approval.

The Contractor shall identify proprietary and licensing material at PM reviews. (A001, Conf Min;

A003, DAL)

2.1.6.8 Data Accession List (DAL)

The Contractor shall supply additional data in Contractor format as a DAL item. (A003, DAL)

2.1.6.9 Security

The Contractor shall provide updates for the Information System Accreditation Documentation in the form of a System Security Authorization Agreement as defined by the Department of Defense Information Technology Security Certification and Accreditation Process and AFSSI 5024 Volumes I, II, and III. The updates include:

a. Engineering drawings: updates and changes provided to the Government prior to the changes occurring to support system accreditation

b. System software (COTS, GOTS, and developed) configuration documentation; updates and changes provided to the Government prior to the changes occurring to support system accreditation

c. Interface control information: updates and changes provided to the Government prior to the changes occurring to support system accreditation.

The Contractor will be provided access to prior security accreditation efforts and documentation undertaken by the Government on the US NDC system. The Contractor shall implement security requirements based upon the current operational mode of the system and the requirements given by the appropriate Designated Approving Authority (DAA) for the system. The Contractor shall provide support to the Government in developing or modifying the Operations Security (OPSEC) plan for US NDC. The Contractor shall present results of their security efforts at meetings or formal Government reviews. (A001, Conf Min; A003, DAL; A011, PDAL)

2.2 US NDC Scientific and Engineering Studies (R&D Funded)

Scientific Studies The Contractor shall work closely with the Government to develop and implement studies requirements. Studies shall include scientific studies including liaison for incorporating third party algorithms, software and knowledge into the US NDC and for participating in scientific and technical meetings and workshops. The Contractor shall produce estimates for developing and implementing the individual studies requirements. Upon completion of a study, the Contractor shall provide technical reports covering activities performed under the study. (A013, Tech Report)

Engineering Studies The Contractor shall work closely with the Government to develop and implement studies requirements. Studies shall include engineering studies related to system hardware replacement or upgrade evaluations and recommendations; operational system software upgrade evaluations and recommendations; system tuning evaluations; system calibration evaluations; system infrastructure improvements; and overall system performance monitoring. The Contractor shall produce estimates for developing and implementing the individual studies requirements. Upon completion of a study, the Contractor shall provide technical reports covering activities performed under the study. (A013, Tech Report)

2.3 Program Support (O&M Funded)

Transition

2.3.1.1 Phase-In (Transition from Incumbent)

2.3.1.1.1 Responsibilities

This Phase-In period shall not to exceed 90 days from start of performance, to allow the incoming Contractor to attain system competence. The Phase-In period shall be utilized by the incoming Contractor to hire, train and familiarize personnel with the US NDC system. During the Phase-In period the incoming Contractor shall receive orientation training from the incumbent Contractor for up to twenty (20) employees, shall perform accountability of the Government inventory, and shall transfer assignment of Government assets, i.e. computers, software, access codes/passwords, from the incumbent to the incoming Contractor. All personnel shall be hired, trained, and in place by completion of this Phase-In period. The incoming Contractor shall provide updated versions of the SEP, SDP, QCP and CMP for Government review during the Phase-In period.

2.3.1.1.2 Transition Meeting

An on-site transition meeting shall be conducted not later than 14 days after notification of contract award to discuss the incoming Contractor's Phase-in Transition Plan and the respective responsibilities of all parties. (A001, Conf Min)

2.3.1.1.3 Pre-Contract Start Date Meeting

A Pre-Contract Start Date meeting shall be conducted ten (10) days before the actual performance start date, and shall include the discussions on the Contractor's readiness and capability to assume full responsibility. (A001, Conf Min)

2.3.1.2 Phase-Out (Transition to Successor)

If the Contractor performing under this contract award is the unsuccessful offeror in a subsequent contract for these services, or if this contract is terminated for any reason, the Contractor shall (before the expiration of this contract) provide all reasonable support to the Government and the successor Contractor to ensure an orderly transition and minimize any impact on operational readiness. This Phase-Out period shall not exceed three (3) months, but shall be no less than one

(1) month, unless specified otherwise by the Government. The Contractor shall provide the successor Contractor access to the site and to all technical documentation and publications on a non-interference basis during the phase-out period. The successor Contractor shall also be permitted to observe the Contractor performing the support services and equipment operations on a non-interference basis during the phase-out period. The incumbent Contractor shall retain full responsibility for all services and equipment in accordance with the PWS until completion of the phase-out period.

Personnel The Contractor shall have a TOP SECRET-SCI facility clearance with SECRET safeguarding, but the Contractor’s facility does not have to be cleared for classified discussions. The ability to obtain and maintain TOP SECRET-SCI security clearances for all Contractor personnel shall be required to work in the AFTAC facility Building 10989, Patrick AFB, FL. US Citizenship is required for all personnel supporting the contract. Personnel identified as key personnel under Appendix E – Contractor Support Staff Descriptions shall have and maintain a TOP SECRET-SCI security clearance. The primary location for technical work is the AFTAC facility located at Patrick AFB, FL.

2.3.2.1 Program Management

A Program Manager and alternate(s) shall be designated by the Contractor, in writing, to the Procurement Contracting Officer (PCO) and shall be responsible for contract performance and ensuring proper communication between Contractor and Government. The Program Manager shall be an employee of the Prime Contractor.

2.3.2.2 Contractor Program Support Staff

The Contractor shall provide and manage a program staff that provides the required skill sets, expertise and qualifications appropriate to the mission and scope of work. Multiple persons and their experience may be combined to provide a program staff area of expertise. All Contractor personnel shall have and maintain a TOP SECRET-SCI security clearance.

IAW AFM 33-285 and DoD 8570.01-M, program staff shall possess a DoD approved cybersecurity baseline certification commensurate to category and level of the assigned position. The DoD approved listing can be found at this link: http://iase.disa.mil/iawip/Pages/iabaseline.aspx. The DoD approved certification must cover knowledge areas in the secure software development life cycle (e.g. secure software requirements and design, secure coding techniques, and secure software deployment strategies) (T-1).

2.3.2.3 Appearance and Conduct

The Contractor shall be responsible for the supervision and conduct of employees. Contractor personnel shall conduct themselves in a proper and efficient manner at all times and wear the type http://iase.disa.mil/iawip/Pages/iabaseline.aspx of clothing worn by their counterparts in business and industry. A Government-furnished security badge shall be displayed and worn at all times.

Performance of Services During Crisis Declared by the National Command Authority or Overseas Combatant Commander

Contractor shall remain at fully operational status during any crisis declared by the National Command Authority or Overseas Combatant Commander according to DoDI 1100.22. The Contractor shall develop contingency plans for use during declared crises or natural disasters. In the contingency plans, the Contractor shall identify employees with military mobilization recall commitments and document procedures for replacing those employees in the event of mobilization.

(A004, SEP)

SECTION 3

3 SERVICES SUMMARY (SS).

The contract service requirements are summarized in performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimally acceptable levels of service required for each requirement. The Services Summary (SS) provides information on contract requirements and the expected level of contractor performance to be successful.

These thresholds are critical to mission success. Procedures as set forth in the applicable Inspection clause in the contract will be used to remedy all deficiencies. The Government retains the right to inspect any item included in the contract.

Performance Objective PWS PARA Performance Threshold

SS # 1.

Timely response to call for 24/7 on-call support responding to call within 15 minutes

2.1.1.1 Quarterly: 90% of the time within 15 minutes.

The remaining 10% within 30 minutes.

SS # 2.

Resolution of 24/7 on-call support problems within 60 minutes of initial notification

2.1.1.1 Quarterly: 95% of the time, issue is resolved via

phone or contractor is on site working the problem within 60 minutes. The remaining 5% within 90 minutes.

SS # 3.

Timely response to Urgent CRs resolving within 72 hours of approval notification

2.1.1.2;

2.1.1.3

Quarterly: 100% of the time, unless otherwise authorized by the COR.

SS # 4.

Timely response to station update (SU) CRs for new stations development within three (3) business days of approval to work notification.

2.1.1.2;

2.1.1.3

Quarterly. 80% of the time. The remaining 20%, complete development within five (5) business days. In the event of more than one (1) new station SU CR per week, the PM/COR will provide a priority and the contractor shall complete at least one CR per each successive three (3) business day period.

SS # 5.

Timely response to station update (SU) CRs for existing stations used in Automated Processing (Spotlight or Pipeline), development within five (5) business days of approval to work notification.

2.1.1.2;

2.1.1.3

Quarterly. 80% of the time. The remaining 20%, complete development within seven (7) business days. In the event of more than one (1) update existing automated processing SU CR per week, the PM/COR will provide a priority and the contractor shall complete at least one CR per each successive five (5) business day period.

SS # 6.

Timely CR Post Operations Verification, complete post operations verification within one

(1) week of promotion to the operational system.

2.1.1.2;

2.1.1.3

Quarterly. 50% of the time. The remaining 50%, complete post operations verification with two (2) weeks of promotion of the CR to the operational system.

SECTION 3

Performance Objective PWS PARA Performance Threshold

SS # 7.

Timely CR Post Operations Validation, complete post operations validation within 30 days of promotion to the operational system

2.1.1.2;

2.1.1.3

Quarterly. 50% of the time. The remaining 50%, complete post operations validation within 60 days of promotion of the CR to the operational system.

SS # 8.

Timely submission of all Data Deliverables in accordance with PWS and CDRL schedule. CDRLs A001 – A014.

2.1 – 2.2.2;

2.3.3;

4.4; 5.12

Quarterly. 95% of the time. The remaining 5% submitted no more than five (5) business days after established due date.

SS # 9.

All final Data Deliverables are delivered on time and require no administrative or technical clarifications or corrections. CDRL A001 – A014

2.1 – 2.2.2;

2.3.3;

4.4; 5.12

Quarterly. 95% of the time. The remaining 5% delivered, clarified or corrected, within 5 business days of due date.

SS#10.

The contractor shall develop and provide study reports.

The contractor shall develop and provide comprehensive study reports identifying areas of conflict, on time with no clarifications or corrections required for Government acceptance.

2.2.1 – 2.2.2

Quarterly. 90% of the time. The remaining 10% of the time final reports require only minor revisions and submitted within ten (10) business days.

SECTION 4

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES.

4.1 Services.

The Government will provide Government Furnished Services as outlined in individual task orders.

The Government will provide the necessary services for the contractor staff to provide the services outlined in individual task orders to include help desk support, IT security, trash, janitorial, and other services that are provided to Government personnel in AFTAC.

4.2 Facilities.

The Government will provide access to and use of Government facilities as outlined in individual task orders. The Government will provide the necessary workspace for the contractor staff to provide the services outlined in individual task orders to include desk space, telephones, computers, and other items necessary to maintain an office environment, if the services provided are on-site (AFTAC headquarters). If the services are being performed at the contractor facility, no facilities will be provided.

4.3 Utilities.

The Government will provide access to and use of Government utilities as outlined in individual task orders.

4.4 Equipment.

The Government will provide access to and use of Government equipment sufficient to carry out contractual functions. The Contractor shall monitor all assigned equipment in accordance with the terms of the contract and report any changes or updates to the Government Equipment Custodian.

(A006, Status of GFE Report)

4.5 Materials.

The Government will provide access to and use of Government material sufficient to carry out contractual functions. The Government will provide Government Furnished Material as outlined in individual task orders.

SECTION 5

5 GENERAL INFORMATION.

5.1 Contractor Identification in the Government Workplace.

When conversing with Government personnel during business meetings, over the telephone or via electronic mail, the contractor shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. The contractor shall identify themselves on any attendance sheet or any coordination documents they may review.

Electronic mail signature blocks shall identify their company affiliation.

5.2 Industrial Security.

DD Form 254. Overarching security requirements and contractor access to classified information will be as specified in the DD Form 254, Department of Defense Security Classification attached to the contract. The contractor shall have a final U.S. Government issued TOP SECRET-SCI security clearance and be DCID 6/4 eligible with a current SSBI.

5.3 Physical Security.

The contractor shall safeguard all Government property provided for contractor use. At the close of each work period, Government facilities, property, and materials shall be secured.

5.3.1 Key Control. The contractor shall establish and implement methods of ensuring that all keys and key cards issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons.

5.3.1.1 The contractor shall immediately report the occurrences of a lost or duplicate key to the

COR.

5.3.1.2 In the event keys, other than master keys, are lost or duplicated, the total cost of rekeying or the replacement of the lock or locks shall be deducted from the monthly payment due the contractor. In the event a master key is lost or duplicated, all locks and keys for that system will be replaced by the Government and the total cost shall be deducted from the monthly payment due the contractor.

5.3.1.3 The contractor shall prohibit the use of keys issued by the Government by any persons other than the contractor’s employees. The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor’s employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the COR.

5.3.2 Combinations and Codes. The contractor shall establish and implement methods of ensuring that all combinations and codes are not revealed to unauthorized persons. The contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations.

5.3.2.1 Access lock combinations are “For Official Use Only” and shall be protected from unauthorized personnel.

5.3.2.2 Combinations to security containers, secure rooms, or vaults are classified information and shall properly safeguarded. Only the contractor employees with proper security clearance and need-to-know will be given combinations to security containers, secure rooms, or vaults.

5.3.2.3 Security alarm access codes are “For Official Use Only” and shall be protected from unauthorized personnel. Security alarm access codes will be given to contractor employees who require entry into areas with security alarms. The contractor shall properly safeguard alarm access codes to prevent unauthorized disclosure.

5.4 Privacy Act.

Work on this contract requires the contractor to have access to Privacy Information. The contractor shall adhere to the Privacy Act, Title 5 of the US Code, Section 552a and applicable Agency rules and regulations.

5.5 Location(s) of Work.

The work to be performed under this contract shall be performed at AFTAC HQ (Address Below) or contractor facility. This requirement shall be defined at in individual task orders and via the

DD254.

AFTAC HQ

Building 10989 1020 South Patrick Drive Patrick AFB, FL 32925

5.6 Hours of Operation.

Normal Hours of Operation.

5.6.1.1 The contractor shall perform the services required under this contract during the following hours: Monday - Friday, 0600-1800, except federal holidays. The contractor shall have the flexibility to manage their workforce within the hours of 0600-1800 Monday – Friday in order to provide the services specified in the PWS and in individual task orders.

24/7 Hours of Operation

5.6.2.1 For activities under PWS Paragraph 2.1.1.1,…