Attachment_4_Consolidated_Sample_Task_Order-_Final.docx

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

HDTRA1-18-D-0045

DRAFT Performance Work Statement (PWS) for (Consolidated Sample Task Order)

1. Introduction: This PWS includes three representative requirements for IT Service Design necessary to define, analyze, design, test, integrate, deploy, and support specific DTRA IT capabilities critical to the 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. 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.

1.3. Scope: This is a Sample Task Order representing three unique requirements defined in Section 3.0 below. The unique background and high-level scope stated for each unique sample requirement is defined in paragraphs 3.1, 3.2, and 3.3 below.

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 paragraphs 3.1, 3.2, and 3.3 below. The Contractor shall provide the full range of technical support necessary to define, design, test, integrate, deploy, and support the IT capability defined in the following three unique representative tasks.

3.1. Develop and Support Combatant Command Collaboration Tool. 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.

Background: 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.

Scope: 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.

3.1.1. Performance Requirement 1.1, Task Order Management. The Contractor shall provide the necessary resources to effectively oversee the performance of all requirements defined in this PWS section (3.1). 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.1.2. Performance Requirement 1.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.1.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.1.2.2. Feature analysis and solution development will be accomplished collaboratively with the DTRA I2TS-SA team and selected GCC user representatives

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

3.1.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.1.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.1.2.6. The resulting collaboration tool shall have a map component in order to display data geospatially

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

3.1.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.1.3. Performance Requirement 1.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.1.4. Performance Requirement 1.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.

3.2. Develop and Support a Strategic Accountability for Special Weapons (SASW) inventory and tracking system. In direct support of the Defense Stockpile Management System (DSMS), the Contractor shall provide the full range of technical support necessary to define, design, test, integrate, deploy, and support a refined SASW business process application to support the DSMS mission.

Background: The Defense Threat Reduction Agency (DTRA) is the executive agent for DoD nuclear weapons stockpile management. A Division under the Nuclear Enterprise Support Directorate is assigned the responsibility for maintaining the DoD’s national nuclear weapons stockpile database.

Support for Defense Stockpile Management System (DSMS) includes maintaining, modifying and enhancing all DTRA-managed nuclear weapons design/development, stockpile and legacy databases/systems to include, the Joint Application Design Environment (JADE), Nuclear Management Information System (NUMIS), Nuclear Inventory Management and Cataloging System (NIMACS); Government Acceptance Testing (GAT), the Defense Integration and Management of Nuclear Data Services (DIAMONDS) system, and DIAMONDS Accountability Training System (DATS). System classification ranges from unclassified up to and including Top Secret.

Scope: The scope of this requirement includes two phases. Phase 1 will facilitate and support the Business Process Re-engineering (BPR) efforts to gather and analyze DSMS business process requirements. The second phase will use the Government’s prioritized requirements of the DSMS business processes resulting from the BPR effort to design, develop, test, integrate and deploy (to appropriate host environment) an IT application representing a “ground-up” redesign of the DSMS business practices specifically designed to achieve functional process streamlining and improvement.

3.2.1. Performance Requirement 2.1, Task Order Management. The Contractor shall provide the necessary resources to effectively oversee the performance of all requirements defined in this PWS section (3.2). 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 schedule clearly defining the activities and tasks associated with Phase 1 and Phase 2 of this requirement. (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.2. Performance Requirement 2.2, Phase 1, Business Process Re-engineering (BPR). In direct support of and in collaboration with the DTRA Nuclear Enterprise – Nuclear Logistics Technical Systems Division (NE-NLT), the Contractor shall plan, facilitate, and document a comprehensive BPR review of the DSMS future business process goals, objectives, structures, workflows, systems and roles for the purpose of defining the technical requirements for a ground-up redesign of business practices to achieve functional process streamlining and improvement. The Contractor shall plan, coordinate, facilitate and document Joint Application Design/Rapid Application Development (JAD/RAD) session(s) with users to understand and document future operations, validate user and system requirements, investigate options for improving information flow and work flow, identify requirements for implementation into the DSMS environments, present candidate system options to users and iteratively receive feedback. The Contractor’s requirements review and analysis shall include engineering and technical interoperability analysis of Commercial-Off-the-Shelf (COTS) system capabilities and performance. The Contractor shall document the resulting BPR findings in a detailed technical report including tradeoff recommendations for Government review and consideration (CDRL A003).

Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 11 below and (to be proposed but focuses on quality and thoroughness of the requirements analysis process).

3.2.3. Performance Requirement 2.3, Phase 2, Application Development. The Contractor shall design, develop, test, integrate and deploy into the DTRA IT Environment, an IT application representing a “ground-up” redesign of the DSMS business practices specifically designed to achieve functional process streamlining and improvement. This application development effort will follow the BPR activity in Phase 1 and will be guided by the requirements priorities established by the DTRA NE team after review of the Phase 1 technical report. The resulting DSMS business process application shall comply with all DTRA IT integration, security, and cybersecurity requirements, and the transition to deployment shall comply with all DTRA IT governance and policies. Integration and transition shall be coordinated with the DTRA IT Operations team and will require technical interactions with the DTRA IT Support Services IT Core Services provider. The Contractor shall provide for a brief period of post deployment application technical support and plan for the transition to organic technical support after this brief support phase.

Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 11 below and (to be proposed but focuses on effective interaction between design, development, test, and integration processes, and the degree to which the resulting application appropriately satisfies the Governments prioritized requirements).

3.3. Open Skies Management and Planning System (OSMAPS) Application Support. In direct support of the DTRA Division for Arms Control Information Systems (DTRA OB-IS), the Contractor shall provide the full range of OSMAPS application operations and maintenance (to include Technical Refresh) necessary to DTRA’s mission responsibilities in support of the Treaty on Open Skies.

Background: The Open Skies Management and Planning System (OSMAPS) and related systems provide mission management and mission planning services to the U.S. Government organizations chartered with execution of the Treaty on Open Skies (hereafter the “Treaty”). The Defense Threat Reduction Agency (DTRA) is the organization responsible for implementation of the regimes of the Treaty. As the responsible organization, DTRA will employ program management and PM/COR responsibility for maintaining the reliability of the systems and their responsiveness to mission requirements. Inclusive in the program management responsibility is the DTRA requirement to provide operations and maintenance and life cycle support to the systems to maintain uninterrupted mission planning and analysis services under the auspices of the Treaty.

The Treaty requires the integration of various systems to execute the treaty requirements for mission management, planning and analysis. For the purposes of this requirements this system of systems includes the follow applications;

Open Skies Management and Planning System (OSMAPS): The OSMAPS provides mission management and planning services for the execution of the Treaty. The OSMAPS consists of three functional variations:

1) Active Overflight System (AOS) – provides the Government with the ability to plan U.S. missions over other countries

2) Passive Overflight Module (POM) – used by DTRA to analyze other countries missions over the U.S. in order to provide notifications to U.S. facilities and provide past mission analysis functions

3) Operational Planning Systems (OPS) – used by DTRA to analyze missions for Treaty compliance, safety of flight and operational feasibility, as well as generating crew mission materials for flight crew members.

Treaty Notification System (TNS)/Multi-Means Messaging System (MMS -future): The TNS provides semi-automated notifications to sites desiring advanced notification of possible overflights of their facilities. The messages are provided via voice, pager, e-mail or facsimile. This capability will likely be upgraded to a modern, digital notification system in the near future (Multi-Means Messaging System).

Transportable Operational Planning System (TOPS): The TOPS is a transportable version of OSMAPS that allows operators to update missions in the field and produce treaty required reports. The TOPS also records all flight path and sensor event data and displays all sensor and flight path data on a moving map display.

Integrated Data Annotation, Recording, and Mapping System (IDARMS): The IDARMS is an on-board subsystem which provides annotation data to all sensors, monitors and records all flight path and sensor event data and displays all sensor and flight path data on a moving map display. The USAF manages IDARMS; however, interfaces with this system are critical to the Government's execution of the Open Skies mission. The IDARMS system is expected to be replaced by the follow-on Digital Visual Imaging System (DVIS) in 2019.

Data Preparation Facility (DPF): The DPF is the storage source of all common data for synchronizing of all systems. The DPF identifies anomalies and reformatting of cartographic data. DPF supports and exports refined data for updating OSMAPS, TOPS, and IDARMS.

Scope: The scope of this requirement includes the full range of OSMAPS application operations and maintenance necessary to support DTRA’s mission responsibilities regarding the Treaty on Open Skies.

3.3.1. Performance Requirement 3.1, Task Order Management. The Contractor shall provide the necessary resources to effectively oversee the performance of all requirements defined in this PWS section (3.3). 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 summary level project 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.3.2. Performance Requirement 3.2, OSMAPS Software and Hardware Maintenance Support. The Contractor shall identify any system abnormalities, document and correct deficiencies, and test implementation of corrective action taken. The contractor shall maintain and refine the system software and associated hardware, as identified in accordance with the sub-tasks listed below.

Operating System and Commercial-off-the-Shelf (COTS) Software and Hardware Maintenance: The contractor shall monitor and maintain the operating systems, databases, Government-off-the-Shelf (GOTS), and Commercial-off-the-Shelf (COTS) software to keep the systems fully functional. Generally, the OSMAPS applications are supported by MySQL database, Java Programming, and Windows Secure Host Baseline (SHB).

Modifications: The contractor shall recommend technological advances to improve efficiency and effectiveness of the system (CDRL A003). The Government will evaluate these recommendations and determine which, if any, shall be implemented.

Once approved and as directed by the COR, the contractor shall plan for and implement these changes. The Open Skies aircraft will transition to a modern and more capable digital sensor suite in the coming years. The contractor shall implement all the necessary software changes to all systems to produce the required program and product updates for the Open Skies mission worldwide.

OSMAPS Software Maintenance: The contractor shall maintain OSMAPS software by correcting problems and providing refinements identified by the Government. The Contractor shall develop and submit recommended maintenance content changes (CDRL A003) for the DTRA COR review and approval. Approved changes shall be delivered in two block releases per year. The contractor shall host two Government Acceptance Tests (GAT) a year at a location determined by the DTRA COR. This effort shall include integrating and testing of third-party software when modifications are made to OSMAPS. Such third-party software includes, but is not limited to, Open Map, and MySQL. The contractor shall implement engineering work-arounds for deficiencies in third-party products. This effort shall include the complete testing of Open Skies systems to include OSMAPS, TOPS, IDARMS/DVIS, DPF, TNS, and ACES interoperability testing. IDARMS/DVIS and ACES are systems that are not part of this contract and would have to be worked by coordination with other contractors. The IDARMS/DVIS, OSMAPS, TOPS, and DPF systems are tightly coupled and changes or modifications to the output products shall require thorough interoperability testing.

TOPS Software Maintenance: The contractor shall maintain TOPS software by correcting problems and responding to requests and recommendations identified by the Government. The changes within scope shall be prioritized by the DTRA COR. This effort shall include interoperability testing with the OSMAPS, IDARMS, DPF, and TNS systems.

Treaty Notification System (TNS) or Multi-Means Messaging System Software Maintenance: The contractor shall be responsible for providing direct support to the Government to ensure all interfaces conform to the current Interface Control Documents (ICDs) for all subsystems. This effort shall include complete testing of the TNS (or a Multi-Means Messaging System or other similar utility) software to include interoperability testing with OSMAPS.

System Software Testing: The contractor shall plan and conduct of functional tests and operational exercises to ensure that the fielded systems operate as designated and changes to the systems do not impact the system's ability to support the Treaty requirements. The contractor shall provide logistical and administrative support to Government personnel and/or their representatives in the conduct of Government Acceptance Testing.

Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 11 below and (to be proposed but focuses on quality and thoroughness of the application maintenance).

3.3.3. Performance Requirement 3.3, IT Security Compliance. The contractor shall make all necessary upgrades or modifications to all systems within the scope of this paragraph 3.3 of this PWS to meet DTRA security requirements. Specifically, the Contractor shall modify the software in the areas of data encryption and database security, as required. The contractor shall ensure that all DoD Security Technical Implementation Guides (STIGs), and other/future software security guidelines, that apply to software development or are otherwise related to OSMAPS application, are incorporated into the OSMAPS code, tested and deployed within established guidelines.

Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 11 below and (to be proposed but focuses on compliance with security requirements).

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, for planning purpures, for these representative requirements are defined below.

For PWS Paragraph 3.1 Combatant Command Collaboration Tool, the period of performance will be defined in two phases.

· The design and delivery phase (PWS 3.1.1, 3.1.2 and 3.1.3) will be consistent with the proposed delivery schedule, but not to exceed 12 months.

· 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.1 and 3.1.4).

For PWS Paragraph 3.2 DSMS, the period of performance will be defined in two phases.

· Phase 1 – Requirements Analysis (PWS 3.2.2) will be consistent with the proposed delivery schedule, but not to exceed 6 months.

· Phase 2 – Application Development and Implementation (PWS 3.2.3) will be consistent with the proposed delivery schedule, but not to exceed 12 months.

For PWS Paragraph 3.3 OSMAPS, the period of performance will be defined as follows;

· Sustaining O&M support for a one-year base and a one-year option period.

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 to mission stakeholder locations 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, 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 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 resulting design solutions shall be developed consistent with requirements established by Section 508 of the Rehabilitation Act of 1973.

All 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).

Sample Task Order Performance Work Statement (PWS)

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

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