Attachment_4_-_DTRA_ITSS_PWS_for_Task_Order_3_-_Integration_and_Test_Support_Final_Draft.docx

DTRA Agency-Wide Information Technology Support Services Core IT Services Contract –

HDTRA1-18-R-0002

DRAFT Performance Work Statement (PWS) for Task Order 3; Test and Integration Support

1. Introduction: This PWS provides agency-wide test and integration support to ensure modified, upgraded, and new information technology (IT) capabilities and systems are thoroughly tested and fully integrated into the IT infrastructure to provide DTRA and its partners with secure and efficient IT capabilities and services necessary to perform the critical DTRA mission.

1.1. Mission: The DTRA mission is to safeguard the United States and its allies from global weapons of mass destruction and improvised threats by integrating, synchronizing and providing expertise, technologies and capabilities. The DTRA Information Integration and Technology Services Directorate (I2TS)/Chief Information Officer’s (CIO) mission is to provide the IT services and capabilities necessary for DTRA’s business and mission functions and support transforming how the agency uses knowledge, technologies, and capabilities to meet the DTRA mission.

1.2. Background: The I2TS/CIO is responsible for providing Agency-wide information management services, supporting in excess of 5,000 world-wide Agency customers utilizing Unclassified, Secret, and Top Secret/Special Compartmented Information (TS/SCI) Networks (for a more detailed description of the current networks see Attachment 1). DTRA personnel supporting the Agency’s mission require common IT services in areas such as, but not limited to, help desk support, systems administration, networks and application administration and design, engineering, and architecture development and implementation. Although the functional requirements are similar across the DTRA mission, the activities involved vary widely by specific mission area. Various short and long-term efforts must be undertaken to continually modernize, integrate and secure functions and systems. Continuous IT support must meet the needs of the Agency and other internally (including JIDO) and externally supported customers to include first responders, Combatant Commands (COCOMS) and other U.S. Government entities. The intent is to provide seamless and integrated communications among all supported elements, for the purposes of office automation, data collaboration and knowledge management, support of exercises, experimentation and operational support across three principle security domains: Sensitive but Unclassified (SBU), Secret and Top Secret/SCI. The DTRA mission supports a diverse set of customers and unique mission requirements. As the organization evolves, the demands on information technology (IT) and associated cybersecurity controls will increase accordingly.

The DTRA Integration, Test and Engineering Center (DITEC) provides a focal point for IT innovation, providing IT expertise and technology-based information capabilities to the Agency in support of its business, warfighting, and research and development (R&D) missions and the DTRA IT infrastructure. The principle DITEC infrastructure consists of a distributed suite of systems, networks and applications at the Defense Threat Reduction Center (DTRC). Components of the DITEC include the DTRA Experimentation Laboratory (DEL), the R&D support network, the First Principles Computing Capability (FPCC) and the DTRA IT testing infrastructure. Contractor resources provide the necessary engineering expertise to design/bui1d, operate, manage, and provide enhancements for this infrastructure.

1.3. Scope: In support of the DTRA mission and Information Integration and Technology Services (I2TS) Directorate/CIO priorities, the contractor shall provide the full range of technical expertise and resources to ensure modified, upgraded, and new IT capabilities and systems are thoroughly tested, fully integrated, and seamlessly transitioned into the IT infrastructure. The goal is to provide DTRA partners secure and efficient IT capabilities and services necessary to perform the critical DTRA mission. The contractor shall provide the necessary technical expertise to maintain, operate, manage, and provide enhancements to the DITEC infrastructure.

2. Applicable Documents: The contractor shall comply with all documents listed below as “Mandatory”. Documents listed as “Non-Mandatory” are provided as information only and for use at the contractor’s discretion.

2.1. Mandatory Documents:

2.1.1. DoD IT Security Regulation

2.1.2. DTRA Security Regulation

2.2. Non-Mandatory Documents:

2.2.1. DTRA Strategic Plan

2.2.2. DTRA J6, CIO Information Operations Strategic Plan 2017 - 2020

2.2.3. DTRA Cloud Strategy

3. Performance Requirements: This section of the PWS defines the performance requirements and results against which the government intends to measure the contractor’s performance. In direct support of the I2TS, the contractor shall plan for and support the logical and seamless transition and integration of approved system, software, security, and cloud solutions onto the DTRA IT enterprise and into productive usage with the target end user group(s). This objective includes a technical function where performance and security tests are either validated or accomplished, and a change management function that prepares the environment for the deployment of a new service and, thus, accelerates its adoption and usage. The measure of success in this objective will be based on evidence of compliant performance and security testing, the transparency of the introduction of new services, and the rate of adoption of the new services.

3.1. Performance Requirement #1, Task Order Management. The contractor shall provide the necessary resources to effectively oversee the performance of all requirements defined in this task order. The contractors shall assign a Task Order Lead/Manager (Key Personnel) who will be accountable for the overall performance outcomes identified within this task order. Within this responsibility, the contractor shall develop and implement a quality control and management oversight plan to effectively manage the staff and the performance per the standards established herein. The contractor shall develop and deliver a monthly status report (MSR) per CDRL A001. Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 5 below and include timeliness of staff on-boarding, timeliness of deliverables, and consistency in meeting other performance measures within this task order.

3.2. Performance Requirement #2, Test Support Services. The contractor shall validate or, if necessary, conduct system level performance and security testing to ensure new or modified systems and capability function as designed and include all DTRA required security features. The objective is to ensure new and modified IT systems/capabilities introduce no new security risks or vulnerabilities, and no performance degradation to the existing DTRA IT infrastructure. The contractor’s test results and recommendations shall be documented and delivered per CDRL A002. It is intended this requirement will be fulfilled by comprehensive testing during the design and development phase of any application/system. However, in selected circumstances, this task may be performed by validation of pervious testing/certification or a combination of validation of pervious testing/certification and in-house testing/validation. Performance measures for this requirement are defined in the PRS below and focus on the number of technical, functional or security related errors discovered during the initial 90 days post deployment.

3.3. Performance Requirement #3, Integration Support Services. The contractor shall support the timely and seamless integration of new or modified capabilities or IT systems into the IT infrastructure. Using an appropriate mix of analysis of the subject design, performance requirements, test results, and, when necessary performing systems level integration testing, the contractor shall ensure new IT systems, if introduced onto the IT infrastructure, will (1) perform as designed, (2) introduce no new security vulnerabilities, and (3) cause no system level performance degradation or interruption. This systems integration may include integrating systems solutions involving multiple performers, suppliers, or developers, and may require integration of systems at geographically disparate locations (CONUS and OCONUS). Integration analysis and recommendations shall be documented and delivered using CDRL A002. Performance measures for this requirement are defined in the PRS below and focus on the number of technical, functional or security related errors discovered during the initial 90 days post deployment.

3.4. Performance Requirement #4, Transition Support Services. In direct support of the IT Services Division, the contractor shall provide the full range of planning and support to effectively transition new capabilities and IT systems introduced to the IT infrastructure. This transition support includes all the resources, planning, and communications (CDRL A003 and A004) needed to support efficient and timely adoption of new capabilities by the targeted end users. This is a support function for the transition and integration services provided in Task Order 001 and will not be independently measured in this task order.

3.5. Performance Requirement #5, DITEC Operations and Maintenance Support Services. The contractor shall maintain and operate the internal unclassified and the R&D test environments. The objective of this requirement is to ensure these test environments continue to appropriately represent the operational DTRA IT environment such that testing in the test environment can be technically and functionally representative. Additionally, the contractor shall ensure the internal unclassified and R&D test environments are reliable and available as needed to support the testing mission requirements. The operations and maintenance of other test environments within the DITEC are outside the scope of this task order. Performance measures for this requirement are defined in the PRS below and focus on contractor’s ability to keep the test environments current relative to the DTRA operational infrastructure, and meet the demands of test schedules based on system availability.

3.6. Performance Requirement #6, Task Order Transition In. The contractor shall plan for and execute a transition-in strategy to provide for the on-boarding of appropriately qualified personnel, with the required DoD security clearances and eligibilities, needed to support a smooth and seamless transition from the incumbent support team to “full performance” within 60 calendar days of task order award. Transition-in includes all staffing activities, as well as the necessary knowledge transfer and capture to ensure “work-in-progress” is smoothly transitioned, and mission support is not interrupted. Performance measures for the first 60 days will be recorded and reported for monitoring purposes, but they will not be used as performance indicators until the completion of the 3rd month of performance. The exception to this suspension of performance measures will be measures associated with this transition-in requirement. The performance measure for this requirement is defined in the PRS below and focuses on the on-boarding of support staff per the transition-in plan included in the contractor proposal.

3.7. Performance Requirement #7, Task Order Transition Out. The contractor shall plan for and support the smooth and seamless transition-out at the end of the performance period. The contractor shall develop and deliver a transition-out plan (CDRL A004) defining their knowledge transfer plan with specific emphasis on transiting work-in-progress. The contractor shall coordinate with the incoming workforce (government or contactor) as necessary to enable a seamless transition with minimum interruption of mission support. The contractor shall remain accountable for performance consistent with the PRS below until the end of the contract period of performance.

4. Deliverables: In support of the requirements in this PWS, the contractor shall develop and deliver a variety of reports, analyses, recommendations, and plans. The specific requirement for content, format, and delivery timing for each deliverable is defined in the Contract Data Requirements Lists (CDRL; DD Form 1423) which will be specifically associated with the PWS paragraph for the corresponding work scope. Unless specifically stated otherwise in the CDRL, all deliverables shall be submitted electronically in either a MS Office compatible or PDF format. The specific format for each deliverable shall be at the contractor’s discretion unless otherwise specified in the CDRL. The following table summarizes the contract deliverables associated with this PWS.

4.1. Deliverables Summary Table

5. Period of Performance. The period of performance will be one base-year with four one-year options.

5.1. Base: Task order award + 12 Months

5.2. Option 1: To be specified at award

5.3. Option 2: To be specified at award

5.4. Option 3: To be specified at award

5.5. Option 4: To be specified at award

6. Support Hours This task will routinely be performed during normal DTRA business hours although support may be required outside of standard hours based on loss of service and mission impact or Agency need. Normal business hours are Monday through Friday, 8:00 AM to 5:00PM except for the following Federal Holidays:

7. Place of Performance/Travel

7.1. Place of Performance: The majority of these tasks will be performed at the defense Threat Reduction Center, 8725 John J. Kingman Road, Fort Belvoir, VA 22060-6201; however, DTRA maintains a global mission and contractor personnel may be required to work at locations other than the NCR. For situational reasons, contractor personnel may work at an alternate location/worksite using Government Furnished Equipment (GFE) with COR approval.

7.2. Travel may be required based on Agency requirements to any DTRA facility world-wide. The Contractor shall provide a detailed estimate of any desired travel in advance to the COR via memorandum or email. Travel costs shall not exceed on a daily basis the maximum per diem rates in effect at the time of travel as set forth in the Federal Travel Regulation. All travel shall be approved by the COR in writing via memorandum or e-mail prior to the contractor incurring any travel expenses and prior to any departure.

8. Security: (Reference DD Form 254, DoD Contract Security Classification Specifications) The contractor employees working on this program must be U. S. citizens, and they will require a minimum of a DoD SECRET clearance in order to provide the required support. Selected individuals may require Top Secret or higher clearances (SCI Access). Rationale: All employees performing services on this contract have the potential to access classified systems up to TS-SCI (JWICS) as a normal requirement in the performance of their duties.

The contractor shall comply with the Security Agreement (DD Form 441) including the National Industrial Security Program Operating Manual (NISPOM) and any revision, notice of which has been furnished to the contractor. The contractor's employees performing work under this contract shall be U.S. citizens and be granted appropriate security clearances based on the need for access to specific classified information. That is SECRET clearance based on favorably adjudicated National Agency Check with Law and Credit Check (NACLC) or a TOP SECRET clearance based on Single Scope Background Investigations favorably adjudicated by the Defense Security Service, Defense Industrial Security Clearance Office.

All contractors in privileged user positions must have a completed single scope background investigation (SSB I) in accordance with DODI 8500.2 prior to filling the position. Privileged users are defined as, but not limited to, persons in the following roles or positions: Information Assurance Managers/Officers, supervisors of IT positions, systems administrators, and maintainers of IA-enabled products.

9. Government Furnished Property, Equipment or Material (GFP/GFE/GFM) The Government will provide office space, desks, computers, use of telephone, copiers, faxes, paper, and other administrative materials on-site for personnel assigned to this task order.

9.1. Government Furnished Property for Contractor Use

DTRA may provide Government equipment to the contractor for use offsite. The contractor shall comply with the contract clauses for accountability of Government Property in the possession of contractors.

The contractor shall update the Master Government Property List (MGPL) when any new equipment is issued to the contractor by the government. The MGPL shall include all equipment/property provided to the contractor, including equipment transferred between projects, broken and obsolete equipment, and items purchased outside the United States. The MGPL shall be delivered electronically in a spreadsheet using Microsoft Office Excel. Abbreviations are not allowed. Ninety (90) days prior to contract expiration, the Contractor shall submit a final MGPL suitable for close-out purposes containing use/disposition recommendations. (CDRL A005)

10. Section 508 Contract Data Requirements List (CDRL) deliverables, in Section 4 above, should meet applicable accessibility requirements and should not adversely affect accessibility features of existing EIT technologies. Information, documentation, and support requirements from 36 CFR part 1194 Subpart D have been determined to apply to this acquisition. Solicitation respondents must describe how the information, documentation, and support proposed for Contract Services deliverables will meet at least those information, documentation, and support requirements identified as applicable in the attached Government Product/Service Accessibility Template (GPAT).

11. Performance Requirements Summary (PRS)

After the initial transition period, the contract shall ensure staffing is available as required to meet performance requirements, and unplanned staff vacancies are held to a minimum.

Staff Transition Metric = # of planned staff positions fully on-boarded at DTRA / # of staff positions scheduled to be onboarded at end of performance period.

Average Staff Availability Metric (Key Personnel) = (Total hours accumulated within period for Key Personnel) / (# of key personnel positions X available workhours in period) Average Staff Availability Metric (Non-Key Personnel) = (Total hours accumulated within period for Non-Key Personnel) / (# of key personnel positions X available workhours in period) 1st Month AQL > 85% 2nd Month AQL > 95% 3rd Month AQL > 98%

Metric begins after transition period AQL for Key Personnel > 95%

AQL for Non-Key Personnel > 90% Data will be collected from Monthly Status Report and compared to Staffing Plan in the Proposal. Metrics will be as of the cut-off date of the MSR. Metric can be validated using DTRA security records.

Data will be collected from MRS and will be as of the cut-off date of the MSR for each period.

NOTE: on-time deliverable assumes the item is accepted as compliant by the government reviewer. A rejected deliverable will be withdrawn from the delivered count and the metric will be recalculated.

The standard availability for this metric is 0 times within any 30 day window.

Task Order 3; DRAFT PWS for Test and Integration Support (DRAFT 2017 12 05)