Attachment_4_TO_3_PWS_-_Transition_and_Integration_Support_Services.docx

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

HDTRA1-18-R-0002

Performance Work Statement (PWS) for Task Order 3; Test, Transition, and Integration Support Services

1. Introduction: This PWS provides agency-wide test, transition and integration support services (T2IS2) to ensure modified, upgraded, and new information technology (IT) capabilities and systems are thoroughly analyzed and tested, and methodically 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 configured and maintained to represent the DTRA production environment. Complementing the DITEC to support testing and proof of concept activities, are the DTRA Experimentation Laboratory (DEL), the R&D support network, and the DTRA IT testing infrastructure. (See paragraph 3.5 below for scope information regarding the DEL). 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 analyzed and tested 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. In support of the I2TS Directorate, the contractor will provide integration and transition support, and will support the government configuration management process for any new or updated capabilities, systems, or services to be added to the DTRA IT environment. The contractor shall provide the necessary technical expertise to maintain, operate, manage, and provide enhancements that may be integrated into the DTRA IT environment.

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 Directive 5200.01; Information Security Program,

2.1.2. DTRA Directive 5200.1R DTRA Information Security Program,

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

2.1.4. DoD Instruction 8500.2 Information Assurance Implementation Document

2.1.5. DRAFT J6 DTRA Core Services Engineering Review Board (ERB) Charter

2.1.6. DRAFT J6 DTRA Core Services Configuration Control Board (CCB) Charter

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 appropriate DTRA user population for the deployment of a new service and 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 contractor 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 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, IDIQ Contract Management. Since this task order represents the “point of entry” for all new IT capabilities or changes to the production baseline, and has responsibility for the entire DTRA IT environment configuration management, this order shall also serve as the central management point for the IDIQ. As such, the contractor shall provide the necessary resources to effectively oversee and integrate the performance of all task orders issued under the IDIQ. The contractor shall establish an integrated management structure within this task order to support an effective integration of the combined work authorized in the IDIQ. This shall include, as a minimum, the assignment of an IDIQ Program Manager (Key Personnel) to serve as the single point of contact with the government technical program manager, the IDIQ COR, and the contracting officer. Within this responsibility, the contractor shall develop and implement an overarching quality control and management oversight plan to effectively manage the staff and the performance per the standards established within the individual task orders. The contractor shall develop and deliver a consolidated monthly status report (MSR) per CDRL A001 to reflect the overall status of support across all active orders. Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 11 below and include timeliness of deliverables, and consistency in meeting other performance measures for the entire IDIQ.

3.3. Performance Requirement #3, Test Support Services. Consistent with the established DITEC Resource Request (DRR) process, the contractor shall validate or, if necessary, conduct system level performance and security testing to ensure new or modified systems and capabilities 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. This requirement also includes support to periodic testing in support of functional upgrades and security patches introduced into the baseline configuration. The contractor’s test results and recommendations shall be documented and delivered per CDRL A003. 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 previous testing/certification or a combination of validation of previous 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.4. Performance Requirement #4, DITEC Operations, Maintenance, and 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. The contactor shall follow strict configuration management and change management to ensure the DITEC remains compliant with information assurance and cybersecurity requirements for test & development networks to include applicable security controls, patching, compliance with Security Technical Implementation Guides (STIGs) and authorization and accreditation requirements and associated artifacts. 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. This includes appropriate technology refreshment activities on test/development networks as required to include lifecycle replacement of infrastructure components such as servers, networking devices and storage components. 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.5. (OPTIONAL REQUIREMENT) Performance Requirement #5, DEL Operations, Maintenance and Support Services. The contractor shall provide the full range of technical expertise and experience maintain and operate the DEL to support the unique and specific requirements of the Research and Development Directorate’s (formerly J9) mission. This requirement includes maintaining and managing the configuration control of the DEL to ensure the DEL is capable and available to support DTRA’s R&D concept validation, proof of concept, analytics, experimentation, and other R&D mission requirements. This includes appropriate technology refreshment activities on test/development networks as required to include lifecycle replacement of infrastructure components such as servers, networking devices and storage components Additionally, the contactor shall follow strict configuration management and change management to ensure the DEL remains compliant with information assurance and cybersecurity requirements for test & development networks to include applicable security controls, patching, compliance with Security Technical Implementation Guides (STIGs) and authorization and accreditation requirements and associated artifacts. Performance measures for this requirement (if exercised) are defined in the PRS below and focus on contractor’s ability to maintain the DEL in the required configuration and with the necessary availability to meet the demands of the R&D experimental and proof of concept schedules.

3.6. Performance Requirement #6, Incidental Hardware/Software Procurement. The contractor shall analyze and recommend hardware upgrades and replacements, and with the government contracting officer’s approval, implement the replacement actions consistent with the following constraints:

- Procure hardware and software and/or systems required to accomplish the tasks specifically defined in the contract to maintain current operations (i.e. bench stock items and/or mission critical items that are in-service, fail/failing, and specialized equipment necessary to support proof of concept decisions and activities).

- Enable a critical function. The enablement of a critical function is an item that supports provision of service to the existing infrastructure or poses a critical risk to Agency mission such as enhanced security, storage capacity (i.e. disk space), etc.

- Support time sensitive mission requirements.

The performance measures for this incidental procurement requirement will not be measured separately but will instead be evaluated as part of PWS paragraphs 3.3, 3.4 and 3.5.

3.7. Performance Requirement #7, Cloud Management Support. In support of the DTRA Cloud Management Office (CMO) the contractor shall plan for and support the integration and management of cloud services and capabilities that become part of the DTRA IT Enterprise. As cloud solutions are approved, these solutions must be fully integrated in the DTRA IT Enterprise and included in the management and oversight functions of the overall Service Operations umbrella. In close coordination with the CMO, contractor shall support the seamless integration of the cloud-based capabilities without interruption of service capabilities delivered to the DTRA IT customers. Performance measures for this requirement are defined in the PRS below and focus on the seamless integration of and transition to full usage of cloud services and capabilities.

3.8. Performance Requirement #8, New Service Transition Analysis. The contractor shall provide the full range of transition analysis necessary to prepare for the successful deployment of new capabilities and services from either a Service Design project, or some other approved source. This requirement includes performing appropriate transition risk analysis to anticipate challenges and potential impacts during the transition period, and formulation of necessary and appropriate risk mitigation strategies. Potential transition risks could include security risks, interface/compatibility risks, denial of access risks, or performance risks. (CDRL A003) Performance measures for this requirement are defined in the PRS below and focus on the thoroughness of the transition analysis to help minimize realized transition impacts.

3.9. Performance Requirement #9, Service Validation. The contractor shall coordinate system functional and security testing as required to ensure new systems (services or capabilities) have satisfied all necessary security certifications and functional validations prior to deployment onto the DTRA IT Enterprise. This specific requirement recognizes that new capabilities/systems may evolve through non-standard solution processes, and this PWS requirement is intended to ensure that, regardless of the solution and development process, all new services or capabilities introduced for deployment onto a DTRA network has been fully validated for security, interoperability and performance. This task serves as a final validation opportunity to either verify compliance through inspection of appropriate validation records, or perform any and all necessary validation activities before the service or capability enters the network. Performance measures for this requirement are defined in the PRS below and focus on consistent application of validation requirements for newly introduced services or capabilities.

3.10. Performance Requirement #10 Transition and Change Management. Consistent with DTRA IT governance and with the Engineering Review Board and the Configuration Control Board charters, the contractor shall plan for and support the transition of new systems (services or capabilities) introduced to the DTRA network(s) to ensure a smooth deployment of the new system and efficient user adoption of the new system. The contractor shall maintain the change management documentation library and manage the Requirements Review Board, Engineering Review Board and Change Control Board (RRB, ERB, and CCB). This requirement follows the transition analysis performed in paragraph 3.8 above. The contractor shall develop transition change management plans as appropriate to identify the key stakeholders, develop and implement the required information and educational materials necessary to properly prepare the end user stakeholders to efficiently adopt the new system with minimum disruption of mission effectiveness. (CDRL A004) Informational and educational materials should be commensurate with the transition risks and the numbers of stakeholders potentially impacted. (CDRL A005) Performance measures for this requirement are defined in the PRS below and focus on the effectiveness of change management efforts and the speed of adoption of new systems.

3.11. Performance Requirement #11, Support Integration and Transition. The contractor shall plan for and support the integration and transition of new systems, capabilities, and applications into the IT enterprise. The contractor shall leverage the efforts of paragraphs 3.8, 3.9, and 3.10 above and the lessons learned (paragraph 3.12), to provide low risk, seamless integration and transition of these new systems and a swift end user adoption such that the benefits of the new systems can be quickly realized. 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 A003. 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 and the Seamless New Service Integration Rate in the PRS below.

3.12. Performance Requirement #12, Transition Lessons Learned. The contractor shall plan for, develop and maintain a transition lessons learned repository or library to collect and reuse the positive and negative lessons learned with previous transition activities. (CDRL A007) Successful and efficient organizations are learning organizations. The intent of this requirement is to intentionally capture, catalog and reuse the positive and negative transition and integration lessons, to allow continual process improvements and greater efficiencies. The performance measure for this requirement is defined in the PRS below and focuses on consistent capture of lessons learned from each transition activity, and evidence of intentional reflection on the collection of lessons learned as each new transition opportunity is introduced.

3.13. Performance Requirement #13, 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.14. Performance Requirement #14, 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

The MSR for PWS 3.2 will be a consolidated view of all active task orders. The intention is not to repeat the information from the individual task order MSRs, but to summarize the performance and financial data to report at the IDIQ level.

Monthly delivery; NLT 5th working day of the month

5. Period of Performance. The period of performance will be a one-year base with up to four one-year options, if exercised.

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 for on-site 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 A006)

9.2. Contractor Purchased Government Material

If the contractor is required to purchase any Government Furnished Material, all purchases of hardware and software shall be in accordance with the procedures of Federal Acquisition Regulations (FAR) Part 45 and Defense Federal Acquisition Regulations (DFAR) and shall be approved to purchase, by the Contracting Officer’s Representative (COR), and shall be considered Government Property. As such, all care, maintenance, and consideration apply, and the same as it would for GFE hardware or software (CDRL A006). The contractor shall be liable for Government Property in their possession pursuant to FAR 52.245-1, as applicable.

10. Section 508 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).

11.

Task Order 3; PWS for Test, Transition and Integration Support Services

12. Performance Requirements Summary (PRS)

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) Metric begins after transition period AQL for Key Personnel > 95% AQL for Non-Key Personnel > 90% 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 goal availability for this metric is 0 instances within any 30 day window.

The goal availability for this metric is 1 instances within any 30 day window.

The Seamless Cloud Integration Rate = (Number of users who access the new cloud service or application - # of users reporting issues with root cause determined to be integration issues) / Number of users who access the new cloud service or application within the first 60 day.

The performance standard for the Seamless Cloud Integration Rate is 95% and will be calculated for each new cloud service added to the Enterprise.

Note: the intent is to exclude service tickets associated with user error or unfamiliarity with new or replacement service.

The Seamless New Service Integration Rate = (Number of users who access the new service or application - # of users reporting issues with root cause determined to be integration issues) / Number of users who access the new service or application within the first 60 day.

The performance standard for the Seamless New Service Integration Rate is 95%, and will be calculated for each new service added to the Enterprise.

Note: the intent is to exclude service tickets associated with user error or unfamiliarity with new or replacement service. This metric will include new cloud services as well as non-cloud services.

Service Validation Consistency rate = (# of new systems presented - # of new systems rejected) / # of new systems presented for deployment within the period of performance. (note: since the rate of introduction will vary, this metric will be calculated on actions within the previous 3-month period)

Contractor shall develop and deliver for government approval, the customer survey before initiating the survey.

End User Adoption Rate = # of unique identifier hits per month / # of new system users defined in the transition analysis.

End User Adoption Rate should grow steadily in the early months after deployment and stabilize when anticipated user volume is reached.

AQL for End User Adoption rate will grow in monthly increments where;

AQL > 35% at end of month 1 (after deployment);

AQL > 50% at end of month 2 AQL > 75% at end of month 3 AQL > 90% after month 4 The contractor shall collect data to support this metric from their QA program and include the calculated metric in the MSR for each new system deployed.

After the 4th month, or when the rate equals 90% or more, the metric will only be monitored and reported quarterly.

Lessons Learned Capture Rate = # of documented post-transition “retrospectives” / total number of new service transitions from start of task order.

Metric will be a cumulative to date measure.

AQL=95%

This is a cumulative measure and recognizes that not all transitions may not complete the post-transition retrospective but most will.

The contractor shall collect data to support this metric from their QA program and include the calculated metric in the MSR.

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.

1st Month AQL > 85% 2nd Month AQL > 95% 3rd Month AQL > 98%

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.

Overall QA Performance Metric = (sum of all performance metrics in this PRS met or exceeded during the performance period) / Total number of active performance metrics within this PWS during the performance period)