Attachment_2_PWS_TO_1_-_IT_Solution_Engineering_and_Test_Support_-_Final.docx

DTRA Agency-Wide Information Technology Support Services IT Service Design Contract –

HDTRA1-18-D-0045

Performance Work Statement (PWS) for Task Order 1; IT Solution Engineering and Systems Test Support

1. Introduction: This PWS provides IT Solution Engineering and Systems Test Support to transform how the Agency uses knowledge, technologies, and capabilities to meet the critical mission of safeguarding the United States and its allies from global weapons of mass destruction and improvised threats.

1.1. Mission: The DTRA mission is to enable DoD, the Interagency, and International Partners to counter and deter Weapons of Mass Destruction and Improvised Threat Networks. The DTRA Information Integration and Technology Services (I2TS) Directorate and Chief Information Officer’s (CIO) mission is to transform 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 over 5,000 world-wide Agency customers utilizing Unclassified, Secret, and Top Secret/Special Compartmented Information (TS/SCI) Networks, as well as several coalition networks. DTRA personnel supporting the Agency’s mission require access to reliable mission and business systems as well as core IT services to execute the Agency mission. IT engineering, design, test, integration, security, project management, and technical architecture services are required to provide new IT mission, business and core service capabilities and to modernize existing ones. Although the support requirements are common in nature, the DTRA mission needs are vastly different. Various short and long-term efforts must be undertaken to continually modernize existing systems and implement new capabilities in support of new mission requirements. IT Solution Engineering and Systems Test Support must meet the needs of the Agency and other internally (to include JIDO) and externally supported customers to include first responders, Combatant Commands (COCOMS) and other U.S. Government entities. The I2TS/CIO 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 intent of this task order is to provide the IT engineering services required to field these capabilities. 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 increase accordingly.

Historically, IT Solution Engineering and Systems Test Support has included up to 15 FTE working in direct support of DTRA I2TS. This information is provided, not as a specific staffing level requirement, but to assist in defining the scale and reach of this technical requirement.

1.3. Scope: In support of the DTRA I2TS/CIO goal to, “evolve information technology in support of CWMD Mission performance”, and consistent with the IT industry best practices, the Contractor shall provide the full range of expertise and experience required to continually monitor the IT market space and analyze the evolving DTRA mission requirements to identify and recommend IT solutions to challenges associated with day-to-day service delivery and mission performance. In support of the service design process, the Contractor shall support, as necessary, comprehensive systems level testing. This task order provides engineering support services across the full range of the Software Development Life-Cycle (SDLC). Additionally, the Contractor may be asked to support the Tier III service provider for critical incident resolution for operational systems.

2. Applicable Documents: The following documents are applicable to this PWS and provide background information and governance related to performance of the scope of work defined within this document.

2.1. DoD Directive 5200.01; Information Security Program,

2.2. DTRA Directive 5200.1R; DTRA Information Security Program,

2.3. DoD Instruction 8510.01; Risk Management Framework (RMF) for DoD Information Technology (IT)

2.4. DoD Instruction 8500.2; Information Assurance Implementation Document

2.5. DTRA Strategic Plan, 2016 - 2020

2.6. DTRA J6, CIO Information Operations Strategic Plan 2017 – 2020

2.7. DTRA Cloud Strategy

2.8. DTRA Knowledge Management Strategy, March 4, 2016

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. These performance requirements address the full scope of this task order and support the higher-level goal stated in paragraph 1.3 above. They provide the full range of support actions and resources necessary to identify, recommend, develop, and integrate into the DTRA enterprise, reliable and security IT solutions to challenges associated with current and evolving DTRA business and mission operations.

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. 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 11 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, IT Solution Engineering Support – Requirements Analysis. In support of the DTRA I2TS, the Contractor shall maintain awareness of innovation and emerging IT technologies that may be of use supporting the Agency mission or modernization of current capabilities. The Contractor shall investigate and recommend solutions to problems associated with day-to-day service delivery/provision and gaps in the existing mission or business systems capabilities. The Contractor shall investigate and, upon direction, provide initial feasibility studies and/or demonstrations of recommended actions (CDRL A003). Performance measures for this requirement are defined in the PRS below and focus on the Contractor’s ability to consistently meet short turnaround-time assessments and recommendations based on trending and innovative technologies.

3.3. Performance Requirement #3, IT Solution Engineering Support – Assessments and Reviews. In support of the DTRA I2TS, the Contractor shall provide in-depth evaluation of IT solutions and technologies, requirements, plans, architectures and designs of operational systems and environments. The Contractor shall provide support to the Government in understanding the impact of a solution or technology selection on mission, business and IT activities and performance metrics, helping to develop a business case or measure the return on investment (to include Analysis of Alternative (AoA) reporting when required). The Contractor shall support the Government evaluation of Commercial off-the-Shelf (COTS), Government off-the-Shelf (GOTS) and custom solutions to existing and emerging business problems faced by the Government (CDRL A003). These solutions to be assessed and reviewed may emerge internally from efforts under PWS paragraph 3.2, or they may come from other DTRA organizations, or third-party sources. Performance measures for this requirement are defined in the PRS below and focus on the thoroughness and completeness of the assessments performed and the degree to which recommendations are supported with logic and reason consistent with the DTRA Enterprise Architecture (IT Roadmap) and strategic plans for the evolving IT enterprise.

3.4. Performance Requirement #4, IT Solution Engineering Support – IT Solution Development and Development Support. In support of the DTRA I2TS, the Contractor shall provide the full range of IT service design, and solutions support, consistent with the industry standard SDLC, to enable rapid reaction services for emerging needs within the Agency. To support this requirement, the Contractor shall provide support services across all phases of the SDLC. The outcomes of this support requirement include engineering and IT design/development support to the IT service design process, or the full implementation of the IT services design/development process (ie, for enhancements to legacy systems or capabilities). In cases where the Contractor performs the capabilities design, testing, and transition to deployment the contractor shall develop and deliver a project schedule (A002) to support the activities, and document the design and all IA artifacts and transition to operations using CDRL A007. In selected cases the Contractor may identify critical requirements for a proof of concept system and translate those requirements into a functional prototype using the tools and processes in place at the Government site. This proof of concept shall demonstrate capabilities and convey to stakeholders the feasibility of a particular project. The Contractor shall present this proof of concept to stakeholders (CDRL A003) and defend the feasibility of the development effort. Furthermore, when directed by the COR, the Contractor shall provide the full range of resources and expertise required to develop and mature a proof of concept, incorporate lessons-learned, and to support a smooth and accelerated path to production. Within the IT Solution Development requirement, and in full collaboration with the DTRA IT Operations team, the Contractor may be asked to support the Tier III service provider for critical incident and outage response. Performance measures for this requirement are defined in the PRS below.

3.5. Performance Requirement #5, IT Solution Engineering Support – Incidental Procurement to Support Proof of Concept or Rapid Prototyping. Upon Government direction and with the approval of the COR, the Contractor shall procure hardware, software licensing, and maintenance to support proof of concept projects. Generally, procurements under this task will be approved by the COR with Contracting Officer (KO) concurrence and documented with a memorandum for record (MFR). There will be no specific performance measure for this incidental procurement task.

3.6. Performance Requirement #6, IT Systems Testing Support Services. In support of the DTRA I2TS, the Contractor shall provide rigorous testing services for technical solutions. This includes creation of test plans (CDRL A004), execution of those plans and incorporation of the test results into the iterative development process. The Contractor shall implement this test methodology through the development lifecycle. This end-to-end testing shall include: Requirements analysis and testing; Design testing; Functional testing; Code testing; System testing; and User acceptance testing. Performance measures for this requirement are defined in the PRS.

3.7. Performance Requirement #7, 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.8. Performance Requirement #8, 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 The Contractor shall provide support during the core Government hours 52 weeks a year. The standard schedule must encompass the DTRA core hours of 9 AM to 3 PM (0900 – 1500). Additionally, the Contractor may be required to provide support outside of standard hours based on loss of service and mission impact or Agency need. Standard work hours shall be Monday through Friday during normal duty hours 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 will 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 (SSBI) 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. The Government will issue the items identified above as GFP and the Contractor shall report any changes on a monthly basis via the Master Government Property List. (CDRL A006) DTRA may provide Government equipment to the Contractor for use offsite. The Contractor shall comply with the contract clauses for management and accountability of Government Property in its possession.

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 A006)

10. Section 508 This service Contractor does not have requirements established by Section 508 of the Rehabilitation Act of 1973.

Task Order 1; PWS for IT Solutions Engineering and Systems Test

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 on boarded 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.

To Be Proposed based on proposed solution

To Be Proposed based on proposed solution

To Be Proposed based on proposed solution

To Be Proposed based on proposed solution

To Be Proposed based on proposed solution

To Be Proposed based on proposed solution

To Be Proposed based on proposed solution

To Be Proposed based on proposed solution