Attachment_4_Sample_PWS_TO_3_-_GCC_Collaboration_Tool.docx

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

HDTRA1-18-D-0045

DRAFT Performance Work Statement (PWS) for (Sample Task Order 3) Combatant Command Collaboration Tool

1. Introduction: This PWS provides IT Service Design necessary to define, analyze, design, test, integrate, deploy, and support a collaborative capability in support of 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 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 (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. DTRA personnel supporting the Agency’s mission require common IT support services in areas such as, but not limited to, networks and application administration and design, engineering, and architecture support. 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, integrate and secure these systems. Continuous IT 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 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.

A Global Combatant Command (GCC) tracks activities and entities on a WMD-related topic that affects one or more countries in their Areas of Responsibility (AOR). This is a persistent topic that the GCC is responsible to monitor and take action, as needed. Other organizations within the US Government (e.g., Department of Defense, Intelligence Community, Law Enforcement, and Interagency stakeholders to include Department of Commerce, Department of State, Department of Energy, Department of Treasury, and Department of Homeland Security) also have roles in monitoring or affecting the WMD-related topic and need a way to maintain awareness and collaborate with the GCC.

1.3. Scope (Problem Statement): The GCC staff needs a more efficient and effective way, on a classified network, to collaboratively work on a WMD-related topic, update status information on activities or entities, and share a comprehensive view of the topic and related activities with GCC leadership and other organizations outside of the GCC. Currently, the GCC staff share information via files passed back and forth by email. This process is inefficient and results in information not being updated as often as needed, information being missed, inaccessibility of the information to other interested organizations, and more time spent maintaining the information and providing summary updates of the WMD-related topics of interest to GCC leadership.

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

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. In direct support of the DTRA I2TS-SA, the Contractor shall provide the full range of technical support necessary to define, design, test, integrate, deploy, and support a collaborative capability to organize and display information so that GCC leadership can have current and accurate situational awareness of relevant activities, track progress against the activities, and are able to make informed decisions regarding WMD-related topics.

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 quality control and management oversight necessary to effectively manage the staff and the performance per the standards established herein. Included in this requirement, the Contractor shall develop, for Government review and approval, a detailed project development and path-to-production integration schedule. (CDRL A002) 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, Develop and Deliver IT Solutions. The Contractor shall implement appropriate IT Service Design methods and techniques, working collaboratively with the DTRA I2TS-SA team to develop functional requirements, features, and interfaces; design effective and efficient IT solutions; test these solutions (functional and security tests); integrate solutions into the GCC-operated IT environment; and outline any required recurring maintenance or support requirements. (CDRL A003) The Contractor shall document and deliver to the Government the collaboration tool design description documents. (CDRL A007) The IT solution will be guided by the following design objectives and constraints;

3.2.1. The resulting collaboration tool shall be web-based and easily accessible so different types of users from multiple locations and organizations can view and update it,

3.2.2. Feature analysis and solution development will be accomplished collaboratively with the DTRA I2TS-SA team and selected GCC user representatives

3.2.3. The resulting collaboration tool shall reside on a classified network

3.2.4. The resulting collaboration tool shall have a user-friendly/simple way for users to input and update information within it. Design solutions shall assume no specialized user or maintenance training is necessary for users to effectively use this tool.

3.2.5. The resulting collaboration tool shall be able to store and use different types of data: structured data, text documents, and geospatial data

3.2.6. The resulting collaboration tool shall have a map component in order to display data geospatially

3.2.7. The resulting collaboration tool shall have the ability to pull in data from REST APIs

3.2.8. An initial prototype of the collaboration tool shall be delivered NLT 45 business days after task order Kick-off Meeting.

Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 11 below and include interim deliveries consistent with the project schedule, and (to be proposed).

3.3. Performance Requirement #3, Integration and Transition Support. The Contractor shall coordinate with the GCC’s J6 to plan for and support the full transition and integration of the resulting GCC Collaboration Capability (tool) into the GCC’s IT Enterprise. The Contractor can only successfully complete this task order when the capability is fully integrated into the GCC’s IT Enterprise. Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 11 below and (to be proposed).

3.4. Performance Requirement #4, Initial Operations and Support Services. The Contractor shall plan for and support the initial operations of the resulting tool for up to 12 months after full integration onto the GCC IT Enterprise. Contractor Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 11 below and include (to be proposed), and user satisfaction.

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.

Deliverables Summary Table

5. Period of Performance. The period of performance will be defined in two phases. The design and delivery phase (PWS 3.1, 3.2 and 3.3) will be consistent with the proposed delivery schedule. The operations and support phase will start with the final integration of the resulting tool into the GCC’s IT Enterprise and continue for 12 months thereafter (PWS 3.1 and 3.4).

6. Support Hours The Contractor shall provide support during the core Government hours. The standard schedule must encompass the DTRA core hours of 9 AM to 3 PM (0900 – 1500). 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. For situational reasons, Contractor personnel may work at an alternate location/worksite using Government Furnished Equipment (GFE) with COR approval.

7.2. Travel: Contractor travel will be required based to GCC and DTRA facilities world-wide in order to collaborate on requirements and gather user feedback. The Contractor shall provide a detailed estimate of any desired travel in advance to the COR in writing via memorandum or email. All 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, 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 listed below as GFP and the Contractor shall report any changes on a monthly basis via the Master Government Property List. (CDRL A006)

9.1. Government Furnished Property for Contractor Use

DTRA may provide GFE and/or GFM 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 The design for this GCC Collaboration Tool shall be developed consistent with requirements established by Section 508 of the Rehabilitation Act of 1973.

Sample Task Order 3; CC Collaboration Tool, PWS (DRAFT) 2018 06 25

11. Performance Requirements Summary (PRS) The Contractor shall add to the table below any appropriate performance standards, metrics and AQLs consistent with the proposed solution design approach and proposed levels of quality and user experience.

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 COR will review the project schedule for consistency with the performance standard.

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