Attachment_2_-_QASP.docx

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

1. Contract or Task Order Title:

Advanced Wireless Services- 3 (AWS-3) Early Entry Portal (EEP) Development, Operations, and Maintenance Support

2. Work Requirements:

QASP Task numbers are aligned with PWS paragraph numbers.

· PWS Paragraph 6.1: Task 1 – Task Order Management

· PWS Paragraph 6.2: Task 2 – EEP Transition and Deployment (Base period Only)

· PWS Paragraph 6.3: Task 3 – EEP Software Development (Option Years Only)

· PWS Paragraph 6.4: Task 4 – EEP Operations and Maintenance

· PWS Paragraph 6.5: Task 5 – Disaster Mitigation Support

· PWS Paragraph 6.6: Task 6 – Equipment Management

3. Roles and Responsibilities:

The following personnel shall oversee and coordinate surveillance activities.

Program/Project Manager (PM) – The PM provides program oversight and supports the COR’s performance assessment activities.

Contracting Officer (KO) – The KO shall ensure performance of all necessary actions for effective contracting, ensure compliance with the contract terms, and shall safeguard the interests of the United States in the contractual relationship. The KO shall also ensure that the contractor receives impartial, fair, and equitable treatment under this contract. Determine the final assessment of the contractor’s performance.

Contracting Officer’s Representative (COR) – The COR is responsible for providing continuous technical oversight of the contractor’s performance. The COR uses the QASP to conduct the oversight/surveillance process. The COR shall keep a Quality Assurance file that accurately documents the contractor’s actual performance. The purpose is to ensure that the contractor meets the performance standards contained in the contract. The COR is responsible for reporting early identification of performance problems to the KO. The COR is required to provide an annual performance assessment to the KO which will be used in documenting past performance. The QASP is the primary tool for documenting contractor performance. The COR is not empowered to make any contractual commitments or to authorize any contractual change on the Government’s behalf.

4. Primary Method of Surveillance:

A mix of random sampling and 100% inspection will be utilized to assess deliverables and outcomes under this effort. Inspection of deliverables will include reviews and assessments by the Government.

Random Sampling is scheduled for monitoring the technical performance of the following items:

· Task Management and Documentation

· Meetings and Reviews

· Transition and Deployment

· NTIA-Deployment

· Software Development

· Operations, System Administration, and Help Desk

· Software Maintenance

· Emergency Release and Deployment

· Disaster Mitigation

· Information Disclosure and Equipment Management 100 Percent Inspection is scheduled for the following items:

· Cost and Schedule monitoring of items whose technical performance is monitored via random sampling

· 100 Percent Inspection. This is usually only the most appropriate method for infrequent tasks or tasks with stringent performance requirements, e.g., where safety or health is a concern. With this method, performance is inspected/evaluated at each occurrence. One hundred percent inspection is too expensive to be used in most cases.

· Random Sampling. This is usually the most appropriate method for recurring tasks. With random sampling, services are sampled to determine if the level of performance is acceptable. Random sampling works best when the number of instances of the services being performed is very large and a statistically valid sample can be obtained. Computer programs may be available to assist in establishing sampling procedures.

Surveillance Matrix

The Surveillance Matrix (Appendix 1) is the list of performance objectives and standards that must be performed by the contractor. This matrix details the method of surveillance the COR will use to validate and inspect these performance elements. Inspection of each element will be documented in the COR file.

Performance objectives define the desired outcomes. Performance Standards define the level of service required under the contract to successfully meet the performance objective. The inspection methodology defines how, when, and what will be assessed in measuring performance. The Government performance surveillance, using this QASP, to determine the quality of the contractor’s performance as it relates to the performance element standards. The AQL performance Standard Table should be used to form the foundation of the COR’s inspection checklist.

5. Performance Standards:

Schedule Requirement: AQL is achieved when acceptable deliverables are provided to the Government per their baseline scheduled delivery date and in accordance with Section 11 of this PWS. Any required revisions are Resolved within one (1) week, unless otherwise stipulated, and accepted by the Contracting Officer and/or COR.

Cost Requirement: AQL is achieved when the cost charged to the TO for the deliverables is equal to or less than the target cost.

· The contractor prepares for and leads meetings, reviews, and conferences.

· Presented material comprehensively responds to the requirement and is understandable by the target audience.

· Prepared materials are accurate and require little or no editorial rework.

· The Kick Off meeting comprehensively covers relevant deployment, planning, scheduling, and Task Order management topics.

· Monthly Customer Status Reviews comprehensively cover relevant development, operations, and maintenance topics.

· Analyses are accurate and meet the DSO’s requirements.

· The contractor executes a comprehensive requirement review for each approved functionality.

· The contractor executes at least one requirement review, test readiness review, and operational readiness review per software release.

Schedule Requirement: AQL performance is achieved when acceptable deliverables are provided to the Government per their baseline scheduled delivery date and in accordance with timelines specified in this PWS. The contractor must conduct a kickoff meeting within forty-five (45) days of staring the period-of-performance.

· Planning: The EEP Transition and Deployment Plan comprehensively plans the complete transition and deployment process.

· Environment: The EEP is deployed in an approved, privately hosted environment, and the contractor provides all required infrastructure, hardware, and other products or services.

· Testing: Testing reveals any insufficiencies and ensures that a high-quality product is deployed.

· Deployment: full EEP functionality is preserved and deployed, including the preservation of existing EEP accounts.

· Artifacts: All required artifacts are updated following deployment.

Schedule Requirement: AQL performance is achieved when:

· Planning: A draft EEP Transition and Deployment Plan is delivered within fifteen (15) days of contract award, and a final EEP Transition and Deployment Plan is delivered ten (10) business days after DSO feedback.

· Transition: EEP is transition begins on a Friday, no earlier than 5pm, the system is fully tested (with completed ORR) NLT 4pm on the sixth following business day, and the system is operational by the start of the seventh business day.

· Artifacts: Any artifacts identified for updates in the EEP Transition and Deployment Plan are provided within thirty (30) days of successful deployment.

Cost Requirement: AQL performance is achieved when the cost charged to the TO for the product is equal to the target cost

· Planning: The Transition-Out Plan comprehensively documents dependencies, contractor cooperation, and transition activities required for successful transition to a follow-on vendor.

· Records: Software, equipment inventories, deliverables, training certificates, deployment test plans, deployment test scripts, deployment test reports, suitability information, security records, and any other documentation relevant to transition are provided to the follow-on vendor.

· Deployment Testing: The contractor participates in the follow-on vendor’s deployment testing, provides meaningful input, and provides timely subject matter expertise throughout the deployment process.

Schedule Requirement: AQL performance is achieved when: a draft Transition-Out Plan is provided ninety (90) calendar days prior to contract end date, a final Transition-Out Plan is provided sixty (60) calendar days prior to contract end date, and records are provided at least sixty (60) calendar days prior to contract end date.

· Planning: The contractor’s NTIA Transition and Deployment Plan addresses all relevant aspects of the NTIA migration, including an implementation plan.

· Implementation: The NTIA deployed instance of EEP meets all documented EEP performance and technical requirements. Additionally, the migrated EEP must meet requirements addressed in the NTIA Transition and Deployment Plan.

Schedule Requirement: AQL performance is achieved when the migration is complete in accordance with the target scheduled completion date. The target completion date will be determined upon option execution. EEP deliverables and technical documentation will be updated no later than five (5) business days after successful deployment.

Cost Requirement: AQL performance is achieved when the cost charged to the DO for the migration is equal to or less than the target cost. Target cost will be determined upon option execution.

· Completeness: the contractor delivers capability in accordance with requirements

· Process: The contractor leads, produced, and documents one major release and one minor release per year from initial requirements analysis through operational deployment. For the third and fourth option years, the contractor shall deliver two minor software releases.

· Development: Software is developed in accordance with the approved Software Development Plan and other relevant documentation.

· Functionality: The application satisfies 100% of the functional and performance requirements set forth in the approved requirements, system requirements specification, and product backlog.

· Usability: The application’s interface is consistent, accessible, and meets documented user needs.

· Testing: AQL performance is achieved when testing is conducted in accordance documented test plans and processes, and testing reveals software deficiencies and ensures a high-quality product is delivered.

· Documentation: Each software release is properly documented and delivered with a complete documentation set in accordance with this PWS, including training materials and user documentation.

· Configuration Management: Robust configuration management and software version control are exercised.

· Deployment: AQL performance is achieved when each software release is deployed with correct configurations, complete release capabilities, maintenance of existing EEP accounts, proper connectivity, and results in successful operational status.

· Training: Training events provide guidance on EEP changes and use.

Schedule Requirement: AQL performance is achieved when acceptable software is delivered to the Government in accordance with the baseline scheduled delivery date and EEP capabilities are made operational within five (5) days of a successful ORR.

Cost Requirement: AQL performance is achieved when the cost charged to the DO for the product is equal to or less than the target cost.

· Help Desk: Help Desk is maintained Monday through Friday during core hours of 9am-5pm Eastern Time.

· Defects: For suspected defects, root causes are determined and defects are resolved through the agile development process.

· Infrastructure: The privately hosted environment is properly maintained and does not impact EEP operations (e.g., software licenses, hardware maintenance, or spare procurement).

· User Account Management: User account management enables access by the EEP user community.

· Case Management: Case withdrawals and status changes are executed when directed by the DSO and cases are rolled back, based on backed-up database information.

· Database Management: EEP retains a robust database capable of providing automated status tracking and warehousing of Coordination Requests, Satellite Operations Cases, Deployment Plans, and other relevant documents throughout the coordination process.

· Accessibility: EEP is never down for more than two consecutive business days.

· Availability: EEP is available 98% of the time, on an annual basis.

Schedule Requirement: AQL Performance is achieved when:

· Account Management: New accounts are created within ten (10) calendar days of submission from the DSRMT

· Help Desk: Help Desk acknowledgement is submitted within one (1) hour of receiving the call/email during core hours, or one (1) hour of the next business day if the call is received outside of core hours.

· Defects: Non-defect related help desk calls are resolved in one (1) business day.

· Case Management: Case withdrawals and status changes are completed within two (2) business days.

· Outages: Planned outages are announced at least one week prior to the outage and unplanned outages are announced at least one (1) hour) prior to the outage.

Cost Requirement: AQL is achieved when the cost charged to the TO for the product is equal to the target cost.

· Functionality: The EEP tool is successfully maintained and continues to meet documented requirements in AWS-3 process documents, the product backlog, and the system requirements specification.

· Deficiencies: AQL is achieved when any identified deficiencies are addressed in accordance with the Software Development Plan, Operations and Maintenance Plan, and other program documentation. Deficiencies impacting operations are swiftly resolved, with a minimum impact to operations. System satisfies requirements described in the approved product backlog, system requirements specification, and approved requirements.

· System Maintenance: system checks for bugs, defects, viruses, and other abnormalities identify issues without impacting operations.

· System Security: confidentiality, integrity, availability, authenticity, secure access control, survivability, and non-repudiation of information is assured within EEP.

· Software Updates: AQL is achieved when database, application, operating system and model software updates are completed and meet documented requirements.

Cost Requirement: AQL performance is achieved when the cost charged to the TO for the product is equal to the target cost.

· Emergency releases are deployed and EEP functionality is restored with minimal operational impacts.

· Defect corrections and EEP features and functions are integrated and tested in accordance with the SDP.

· DM capabilities and services are provided in accordance with the DM Plan. These include establishing a physical DM location, verifying backup of EEP capabilities (such as the development environment), creating and executing recurring backups of the contractor’s capabilities, providing DM scenarios to test, testing and verifying DM capabilities, and reporting lessons learned and process improvements.

· DM backup occurs on a reoccurring basis not to exceed twenty-four (24) hours between backups.

· Non-public information is properly handled and non-disclosure agreements are properly executed.

· Contractor Furnished Equipment employed for remote access to a Government network meets or exceeds the equivalent GFE cyber security computing requirements.

6. Documenting Performance:

Acceptable Performance.

The Government shall document positive performance. A Performance Assessment Report (PAR) template is attached (Appendix 2). Any report may become part of the supporting documentation for fixed price payments, award/incentive fee payments, Contractor Performance Assessment Reporting System (CPARS) entries, or other actions. Government acceptance of services permits the contractor to invoice for the service fee.

Unacceptable performance.

Unacceptable contractor performance can be identified by customer complaints (Appendix 3) or upon schedule surveillance evaluations. When unacceptable performance occurs, the COR shall inform the contractor. This will normally be in writing unless circumstances necessitate verbal communication. The COR shall document the discussion and place it in the COR file and provide a copy to the KO.

When the COR determines formal written communication is required, the COR shall prepare a Corrective Action Report (CAR). The CAR is forwarded to the KO for dissemination to the contractor. A CAR template is attached to this QASP (Appendix 4).

The contractor shall acknowledge receipt of the CAR in writing. The CAR will specify if the contractor is required to prepare a corrective action plan to document how the contractor shall correct the unacceptable performance and avoid a recurrence. The CAR will also state how long after receipt the contractor has to present this corrective action plan to the KO and COR. The Government may withhold payment for services until corrective action is taken. The Government shall review the contractor's corrective action plan to determine acceptability. Upon Government acceptance of the corrected services the contractor will be permitted to invoice for the service fee.

Any CAR may become a part of the supporting documentation for contract payment deductions, fixed fee deductions, award fee nonpayment, CPARS or other actions deemed necessary by the KO.

7. Mandatory or regulatory compliance items:

The contractor will provide initial proof of compliance with regulatory and compliance items contained in the contract. The Contracting Officer's Representative (COR) and the Contracting Officer (KO) will evaluate the initial submission and will conduct ad hoc reviews of the contractor's compliance throughout the remainder of the contract. The contractor will monitor compliance to all statutory and regulatory compliance items, including, but not limited to, combatting trafficking in persons, Equal Employment Opportunity, wage determination, and intellectual property, as required, and report any issues to the KO.

8. Acceptable Quality Level (AQL):

The AQLs for this project are defined in Section 6 of this document, and all deliverables must meet the quality specifications defined in Section 6 of this document.

9. Evaluation Method:

The COR will review documents and deliverables to ensure AQL’s have been achieved. The COR will ensure that transition activities meet the required AQLs by reviewing deliverables and documentation; additionally, the COR may conduct discussions with the contractor, users, and other stakeholders, as required. The COR will ensure software development, operations, and maintenance activities meet required AQLs by reviewing deliverables and documentation; additionally, the COR may conduct discussions with the contractor, users, and other stakeholders, as required.

10. Performance Rating

In evaluating the quality of contractor’s performance, the following performance ratings may be used (same as CPAR ratings).

(If your organization requires that you use a different rating mechanism, insert it here.)

Performance Rating Criteria

Enclosure 6, Page 1 of 6 Pages 17Jul2013/Version 2

Encl 4, QASP 23Jun2017/v3

Appendix 1 - Surveillance Matrix

Performance Standards Acceptable Quality Levels Methods of Calculation

Ratings

Task Management and Documentation Minimum Acceptable:

95% of deliverables contain the required information, are technically and grammatically correct, and do not require multiple returns to the contractor for editorial rework.

95% of deliverables are provided to the Government per their baseline scheduled delivery date and in accordance with Section 10 of this PWS. 100% of deliverables are no more than 7 days late.

Required revisions or rework must be completed and submitted within 7 calendar days.

Measurement Period – The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00on the last day of the month.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor Method of Surveillance – Random sampling of deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - Reporting to commence upon Contract Award and continue throughout the Period of Performance.

Exceptional Very Good Satisfactory Marginal Unsatisfactory

The contractor executes at least one requirement review, code quality demonstration, and test readiness review per software release. A comprehensive requirement review is executed for each approved functionality. 100% of meetings and reviews comprehensively respond to the requirement and is understandable by the target audience. Kick Off meeting comprehensively covers relevant deployment, planning, scheduling, and task order management topics and is complete within 45 calendar days of contract award. 100% of analyses are accurate.

95% of meetings and reviews are provided to the Government per their baseline scheduled delivery date and in accordance with Section 10 of this PWS. 100% of deliverables are no more than 7 days late.

Measurement Period – The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00on the last day of the month.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor Method of Surveillance – Random sampling of meeting and review deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - Reporting to commence upon Contract Award and continue throughout the Period of Performance.

Exceptional Very Good Satisfactory

· Full EEP functionality is preserved and deployed, including the preservation of existing EEP accounts.

· A draft EEP Transition and Deployment Plan is delivered within fifteen (15) days of contract award, and a final EEP Transition and Deployment Plan is delivered ten (10) business days after DSO feedback.

· Transition begins on a Friday, no earlier than 5pm, the system is fully tested (with completed ORR) NLT 4pm on the sixth following business day, and the system is operational by the start of the seventh business day.

· Artifacts identified for updates in the EEP Transition and Deployment Plan are provided within thirty (30) days after successful transition.

· Operational status, with full EEP functionality transitioned, must be declared within sixty (60) days of contract award.

Calculation – Analysis of EEP Deployment Test Report, EEP Transition and Deployment Plan, EEP Deployment ORR Materials, and EEP Deployment Memo

Analysis of EEP portal accessed through the world wide web.

Measurement Interval – The measurement interval starts at contract award and ends thirty (30) calendar days following successful EEP transition Measurement Period – The Measurement Period begins at 00:01 on the first day of performance and ends at 23:59 on the thirtieth (30) day after successful transition.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor and from COR access of the EEP application Method of Surveillance – Random sampling of transition deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - One time

Exceptional Very Good Satisfactory

· Planning: The Transition-Out Plan comprehensively documents dependencies, contractor cooperation, and transition activities required for successful transition to a follow-on vendor. Final Transition-Out Plan shall be provided no less than sixty (60) calendar days prior to contract end date.

· Records: Software, equipment inventories, deliverables, training certificates, deployment test plans, deployment test scripts, deployment test reports, suitability information, security records, and any other documentation relevant to transition are provided at least sixty (60) calendar days prior to contract end date.

· Deployment Testing: The contractor participates in the follow-on vendor’s deployment testing, provides meaningful input, and provides timely subject matter expertise throughout the deployment process.

Calculation

Analysis of deliverables to determine that no deliverables are missing in handing over to follow-on vendor

Required delivery timelines are met Measurement Interval – The measurement interval starts 180 days prior to PoP completion and ends on the last day of the PoP Measurement Period – The Measurement Period begins at 00:01 on the 180th day prior to PoP completion and ends at 24:00 on the last day of the PoP Source of Measurement Data – Data will be collected from deliverables provided by the contractor Method of Surveillance – Random sampling of Transition-Out deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - One time

Exceptional Very Good Satisfactory

· NTIA Transition and Deployment Support Plan addresses relevant aspects of the NTIA migration, including contractor actions, risks, and dependencies.

· NTIA Deployment and migration activities are not negatively impacted by the contractor’s actions, inactions, or failure to communicate with stakeholders.

Calculation Analysis of EEP deliverables provided with transitioned EEP Measurement Interval – The measurement interval consists of the option Period-of-Performance Measurement Period – The Measurement Period begins at 00:01 on the first day after option award and ends at 24:00 on the fifth day after the option’s period of performance ends.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor and from EEP users using EEP support logs.

Method of Surveillance – Random sampling of Transition-Out deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - One time

Exceptional Very Good Satisfactory

· Capabilities satisfy 100% of the functional and performance requirements set forth in the approved requirements, system requirements specification, and product backlog.

· One major and one minor release are produced and documented per year. For the third and fourth option years, the contractor shall deliver two minor releases.

· Software is developed in accordance with the approved Software Development Plan

· The application’s interface is consistent, accessible, and meets documented user needs.

· Testing ensures a high-quality product is delivered (no major defects) and is conducted in accordance with documented test plans and processes

· Each release is properly documented and delivered with a complete documentation set in accordance with this PWS, including training materials and user documentation.

· Each software release is deployed in accordance with the baselined schedule and results in successful operational status. Each release with correct configurations, complete release includes maintenance of existing EEP accounts, proper connectivity, and results in successful operational status.

· Training events provide guidance on EEP changes and use.

Calculation Analysis of EEP release deliverables, EEP maintenance and help desk logs, and ad-hoc interviews with EEP users.

Measurement Interval – The measurement interval is sixty days.

Measurement Period – The Measurement Period begins at 00:01 on the thirtieth day prior to the baselined schedule release delivery date and ends month and ends at 24:00on the last day of the month.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor and ad-hoc user interviews Method of Surveillance – Random sampling of deliverables and interviews for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - Twice per year. Reporting to commence upon Contract Award and continue throughout the Period of Performance.

Exceptional Very Good Satisfactory

· EEP is never down for more than two consecutive business days.

· EEP is available 98% of the time, on an annual basis.

· Help Desk is maintained Monday through Friday during core hours of 9am-5pm Eastern Time. Help Desk acknowledgement is submitted within one (1) hour of receiving the call/email during core hours, or one (1) hour of the next business day if the call is received outside of core hours. Non-defect related help desk calls are resolved in one (1) business day.

· For suspected defects, root causes are determined and defects are resolved through the agile development process.

· The privately hosted environment is maintained and does not adversely impact EEP operations (e.g., software licenses, hardware maintenance, or spare procurement).

· User account management enables access by the EEP user community. New accounts are created within ten (10) calendar days of submission from the DSRMT

· Case withdrawals and status changes are executed when directed by the DSO and cases are rolled back, based on backed-up database information. Case withdrawals and status changes are completed within two (2) business days.

· EEP retains a robust database capable of providing automated status tracking and warehousing of Coordination Requests, Satellite Operations Cases, Deployment Plans, and other relevant documents throughout the coordination process.

· Planned outages are announced at least one week prior to the outage and unplanned outages are announced at least one (1) hour) prior to the outage.

Calculation Analysis of EEP deliverables and EEP maintenance and help desk logs.

Measurement Interval – The measurement interval is one month.

Measurement Period – The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00on the last day of the month.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor Method of Surveillance – Random sampling of deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - Reporting to commence upon Contract Award and continue throughout the Period of Performance.

Exceptional Very Good Satisfactory

· Identified deficiencies are addressed in accordance with the Software Development Plan, Operations and Maintenance Plan, and other program documentation. Deficiencies impacting operations are swiftly resolved, with a minimum impact to operations. System satisfies requirements described in the approved product backlog, system requirements specification, and approved requirements.

· System checks for bugs, defects, viruses, and other abnormalities identify issues without impacting operations.

· Confidentiality, integrity, availability, authenticity, secure access control, survivability, and non-repudiation of information is assured within EEP.

· Database, application, operating system and model software updates are completed and meet documented requirements.

Calculation Analysis of EEP deliverables and EEP maintenance and help desk logs.

Measurement Interval – The measurement interval is one month.

Measurement Period – The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00on the last day of the month.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor Method of Surveillance – Random sampling of deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - Reporting to commence upon Contract Award and continue throughout the Period of Performance.

Exceptional Very Good Satisfactory

· Emergency releases are deployed and EEP functionality is restored with minimal operational impacts.

· Defect corrections and EEP features and functions are integrated and tested in accordance with the SDP.

Calculation Defects are resolved and functionality is restored. Verified through analysis of EEP help desk logs and EEP emergency release deliverables Measurement Interval – The measurement interval is one month.

Measurement Period – The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00 on the last day of the month.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor and reports from user stakeholders Method of Surveillance – Random sampling of deliverables for quality.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - Reporting to commence upon Contract Award and continue throughout the Period of Performance.

Exceptional Very Good Satisfactory

· DM capabilities prevent data loss

· DM backup occurs on a reoccurring basis not to exceed twenty-four (24) hours.

Calculation 100% of DM capability uses prevent catastrophic data loss. Random sampling of EEP deliverables to determine backup currency.

Measurement Interval – The measurement interval is one month.

Measurement Period – The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00on the last day of the month.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor Method of Surveillance – Random sampling of deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - Reporting to commence upon Contract Award and continue throughout the Period of Performance.

Exceptional Very Good Satisfactory

· Non-public information is properly handled and non-disclosure agreements are properly executed.

· Contractor Furnished Equipment employed for remote access to a Government network meets or exceeds the equivalent GFE cyber security computing requirements.

Calculation Percent of personnel with Non-Disclosure agreements on-file.

Number of unauthorized releases of non-public information Measurement Interval – The measurement interval is six months.

Measurement Period – The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00on the last day of the month.

Source of Measurement Data – Data will be collected from deliverables provided by the contractor and any reports of unauthorized disclosure.

Method of Surveillance – Random sampling of deliverables for quality. 100% inspection for delivery timelines.

Timing of Measurement – Measurements are taken within ten (10) days of the end of the Measurement Period.

Reporting Frequency: - Reporting to commence upon Contract Award and continue throughout the Period of Performance.

Exceptional Very Good Satisfactory