Attachment_2_-_DTRA_ITSS_PWS_for_Task_Order_1-_Service_Integration_Provision_and_Operations_Final_Draft.docx

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

HDTRA1-18-R-0002

Performance Work Statement (PWS) for Task Order 1; IT Service Integration, Provision and Operations

1. Introduction: This PWS provides IT service integration, provision, transition, and operations to ensure DTRA and its partners have reliable, 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. 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.

1.3. Scope: The DTRA-wide IT service integration, provision, and operations scope includes the full range of support actions and resources necessary to deliver reliable, secure and effective IT capabilities and services as defined in the DTRA Service Catalog (Attachment 2). These operations and support services will be provided within the “as is” and evolving DTRA IT Enterprise, and consistent with industry best practices and the performance standards contained within this PWS. To support the evolving DTRA IT Enterprise new services and capabilities will be added to the IT Enterprise and other services will be retired. The scope of this task order will also support the seamless transition of these new capabilities from the solutions cycle into the operations infrastructure.

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

2.1. Mandatory Documents:

2.1.1. DoD IT Security Regulation

2.1.2. DTRA Security Regulation

2.2. Non-Mandatory Documents:

2.2.1. DTRA Strategic Plan

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

2.2.3. DTRA Cloud Strategy

3. Performance Requirements: This section of the PWS defines the performance requirements and the performance results the government intends to measure the contractor’s performance against. These performance requirements address the full scope of this task order and support the higher-level objective stated in paragraph 1.3 above. They provide the full range of support actions and resources necessary to seamlessly transition new capabilities into the enterprise and deliver reliable, secure and effective IT capabilities and services as defined in the DTRA IT Services Catalog and as needed to meet the critical DTRA mission.

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 performance standards established herein. The contractor shall develop and deliver a monthly status report (MSR) per CDRL A001. Performance measures for this requirement are defined in the Performance Requirements Summary (PRS) in Section 5 below and include timeliness of staff on-boarding, timeliness of deliverables, and consistently meeting performance measures in other performance measures within this task order.

3.2. Performance Requirement #2, IT Operations and Systems Administration. The contractor shall provide the full range of support services required to manage the day-to-day operation and systems administration of the DTRA IT computing and telecommunications infrastructure, ensuring reliable, secure, and efficient availability of the current and evolving catalog of DTRA IT services and capabilities. The DTRA IT infrastructure includes all servers, routers, circuits, firewalls, interconnecting cabling, network security equipment, network monitoring equipment, and end user IT equipment. The DTRA IT Infrastructure supports approximately 5000 users using distributed operations between the National Capital Region (NCR) and DTRA Albuquerque, NM and supporting facilities on Fort Belvoir, VA, as well as sites in Albuquerque, NM, Eglin AFB, FL, and a variety of CONUS and OCONUS locations. The DTRA IT infrastructure includes three separate computer networks configured to support various levels of security classification. The contractor shall plan, manage, troubleshoot, fix/repair, install OEM and security patches and upgrades, and monitor the health of the DTRA IT infrastructure to ensure continuous, secure, and efficient access to the full range of DTRA partners. The contractor shall support the Network Operations and Security Center (NOSC) for the Agency on a 24x7x365 basis, in accordance with requirements for a Defense Agency NOSC and appropriate DoD Directives. Included in this objective the contractor shall maintain real-time situational awareness of the DTRA IT infrastructure and supported environments; shall lead restorative actions to ensure all networks remain up and operational. Additionally, as part of the Systems Administration function, the contactor shall continuously monitor infrastructure equipment and components to support appropriate technical refresh plans. Performance measures for this requirement are defined in the PRS below and focus on network availability, efficiency, and security.

3.3. Performance Requirement #3, 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).

- 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 the Requirement #2.

3.4. Performance Requirement #4, Service Desk. The contractor shall operate an IT Service Desk to provide end-users IT remediation and support to allow DTRA I2TS partners to effectively leverage the full capabilities of the available IT services and capabilities in direct support of the DTRA mission. The Service Desk shall serve as the primary point of contact for delivery of IT services for the Agency by receiving and responding to support requests for hardware/software and systems access. Additionally, the contractor shall provide direct assistance for knowledge management systems under the control of the I2TS, to include Sharepoint and EIS. The contractor shall support the full range of DTRA IT Service Desk functions and responsibilities to include, but not limited to;

· Capture and reporting of IT Service Desk support metrics,

· Installation, configuration, maintenance and troubleshooting for all users of the DTRA systems,

· Maintain a web-based capability for DTRA users to enter, track and escalate Service Desk tickets, as well as available perform self-service actions,

· Remote access configuration and support for DTRA users and external customers as required (supporting telework, off-site travel, and mission or contingency operations)

· Install, configure, maintain and troubleshoot computer peripherals,

· Provide tracking for all deployed IT assets from procurement to disposal to allow real-time accounting of IT assets to both government and contractor personnel,

· Provide end-user software and application support,

· Coordinate security and situational awareness concerns with DTRA NOSC

· Provide technical assistance and customer support in the operations and maintenance of wireless voice and data services.

The contractor shall plan, implement and maintain a customer survey/feedback function to gather feedback directly from the service desk customer regarding their level of satisfaction with the service provided. Survey responses will be voluntary for customers. The survey content will be submitted for review and approval by the government prior to implementing. (CDRL A002) Service Desk requests after normal business hours (0600 – 1800) are currently covered by the NOSC.

Performance measures for this requirement are defined in the PRS below and focus on effectiveness, responsiveness, and overall customer satisfaction.

3.5. Performance Requirement #5, Applications and Asset Management. The contractor shall plan, implement and maintain an effective application and asset management program that integrates people, processes, and technology to allow software licenses and usage to be systematically and accurately tracked, evaluated, and managed. Effective management of the IT Infrastructure applications and assess reduce IT expenditures, human resource overhead and risks inherent in owning and managing software assets. This effort will develop and maintain lifecycle management plans for hardware and software managed by the I2TS. Performance measures for this requirement are defined in the PRS below and focus on consistency and accuracy of applications and asset management reporting.

3.6. Performance Requirement #6, Technical Management. The contractor shall provide the full range of IT technical expertise and technical management support services to ensure DTRA IT infrastructure meets performance requirements stated in paragraphs 3.2 – 3.4 above and the larger enterprise level objectives as stated in paragraph 1.3. The technical management requirement shall provide for technical analysis of network operations, independent evaluation and integration support for new capabilities and applications to be deployed onto the IT networks, and the ability to escalate user or system generated trouble tickets that cannot be resolved in a timely manner by the Service Desk staff. (CDRL A003) As such this requirement is complimentary to and supportive of other requirements in this PWS, and will not be subject to separate performance measurement in the PRS.

3.7. Performance Requirement #7, Cloud Management Support. 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. The contractor shall support the seamless integration and continuing support of the cloud based capabilities without interruption of service capabilities delivered to the DTRA IT customers. The contractor shall coordinate planning and support activities associated with cloud migration with the DTRA Cloud Management Office. 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 systems 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 both security and performance. This task servers 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. 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. This requirement follows the transition analysis performed in paragraph 3.7 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. Performance measures for this requirement were previously defined in 3.8 as 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. (A006) 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 with the required DoD security clearances and certificates, 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 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

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 support outside of standard hours based on loss of service and mission impact or Agency need. The IT Operations and Systems Administration (paragraph 3.2) and IT Service Desk (paragraph 3.3) are 24x7x365 requirements. 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: Currently the majority of these tasks are 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. As mentioned in Paragraph 3.2 above, DTRA relies on distributed operations between the NCR and DTRA Albuquerque, NM. As DTRA becomes more virtualized, and physical space within the DTRA facilities become a premium commodity, support and operations from locations other than DTRA may be necessary to reduce the physical contractor onsite footprint. 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 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 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 (DO Form 441) including the NISPOM and any revision to that manual, notice of which has been furnished to the contractor. Item 13b: The contractor's employees performing work under this contract shall be U.S. citizens and been granted appropriate security clearance, 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 DOD I 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, copier, fax, paper, and other administrative materials on-site for personnel assigned to this contract/purchase order/task order.

9.1. Government Furnished Material 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 Master Government Property List (MGPL) shall be updated at the time any new equipment is issued to the contractor by the government (Base Contract CDRL A006). The MGPL shall include all equipment/property provided to the contract, 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.

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. The contractor shall be liable for Government Property in their possession pursuant to FAR 52.245-1, as applicable.

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

Task Order 1; IT Service Integration, Provision and Operations (DRAFT 2017 12 05)

11. Performance Requirements Summary (PRS)

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

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

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

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

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

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

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

For each network the metric is calculated as follows: Possible Availability = (# of devices)*(seconds in month) Actual Availability = (Possible Availability) - (sum of all outages in seconds for servers as measured in Remedy by taking Asset Outage records and subtracting the Actual Start Time from the Actual End Time) Availability = Actual Availability/Possible Availability

Average time to incorporate = (date installation and checkout is complete – date of receipt of patch/update) / # of patches/updates completed in the period.

Metrics will be separate for patches/updates received as “urgent” and all others.

There will be two AQLs for this performance requirement;

AQL for Urgent patches/updates < 2 days

AQL for other than Urgent patches/updates < 7 days The contract shall maintain a log of the receipt date/time for all patches and updates. The contractor shall calculate this metric each month and include in the MSR.

First Contract Resolution Rate = # of user service restoration incidents (received during performance period) resolved during the initial contact / Total # of user service restoration incidents within the performance period.

Monthly AQL for First Contact Resolution Rate shall be equal to or greater than 75%.

Beginning with the sixth month of performance, a second metric will be added to represent the most recent cumulative 6-month rate. The rolling 6-month cumulative rate AQL shall be greater than 80% The contractor shall collect data to support this metric from their QA program and include the calculated metric in the MSR.

User Service Restoration Mean Time to Restore/Resolve (MTTR) Executive Support; 4 hours or less.

User Service Restoration Mean Time to Restore/Resolve (MTTR) (non-Executive) Work Stoppage; 8 hours or less.

The AQL for these metrics is 90%.

Thus, the contractor shall meet the stated MTTR performance standards 90% of the time as measured within a performance period.

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

Accuracy rate = (# of records inspected - # of errors identified) / (# of records inspected).

Note: an error could be an unverifiable entry, or the failure to have recorded an entry at time of inspection.

The AQL for this measure will be

Accurate rate > 96%

Sample size and frequency of inspection will be at COR discretion This metric will be based on government random inspection of asset management records.

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.

The Seamless New Service Integration Rate

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 onboarded at end of performance period.

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

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