Exhibit_D_-_Performance_Requirement_Summary_(PRS)_-_Needs_PWS_References.pdf

PERFORMANCE REQUIREMENT SUMMARY (PRS)

THE ACCEPTABLE QUALITY LEVEL (AQL) IS 100 PERCENT UNLESS OTHERWISE STATED.

PWS/

Reference

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Surveillance

PWS Service Transition

There shall not be an interruption in service for specific tasks identified in

PWS.

Contractor shall have approximately 90 calendar days to prepare to take full responsibility effective performance start date.

Services available without interruption on period of performance start date.

Day 1 of POP start date

Availability of services on day 1 of

POP.

PWS OPSEC

Training

Contractor Employees must complete training

Pass Training Class and Provide

Certificate of Completion

Within 30 calendar days of reporting for duty.

Annually thereafter

100% review by COR.

PWS AT Level I Training

Contractor Employees must complete training

Pass Training Class and Provide

Certificate of Completion

Within 30 calendar days of contract start date of reporting for duty.

Annually thereafter

100% review by COR.

PWS Registration in ATCTS & DoD IA Awareness Training

Contractor Employees must complete training

Pass Training Class and Provide

Certificate of Completion

At start of services and/or prior to access to information systems.

Annually thereafter

100% review by COR.

PWS/

Reference

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Surveillance

PWS Program Coordination Services

Contractor authorizes key personnel to respond to Government inquiries for their respective functions.

During a POP, COR has received from the PM, PMO, and FP/FRs less than 3 written complaints that Contractor’s key personnel are not providing adequate and/or timely response.

POP Written complaints.

PWS

Contractor Program Management Plan (PMP)

Contractor submits a PMP addressing how the Contractor shall manage the tasks identified in

PWS.

Plan will adequately address required tasks and will be submitted on time.

Annually: 30 calendar days after each POP start date.

100% review by the COR, PM, and PD.

PWS Staffing Report

Contractor personnel shall be available to start work immediately on performance start date.

Contractor submits PWS Staffing Report identifying Contractor personnel assigned to support specified tasks and technical requirements.

Contractor personnel shall possess all necessary knowledge, skills, and abilities.

Report is accurate and complete— identifying all persons currently hired under PWS.

Annually and upon COR request. Due 7 calendar days after each POP start date.

100% review by

Manpower Reporting

(CMR)

Contractor will report ALL contractor manpower (including subcontractor manpower) required for performance of this contract.

Report is accurate and complete.

Contractor complies with requirement to complete CMR annually.

Annually due 31 Oct each calendar year for preceding fiscal year ending 30 Sep

100% review by the COR on https://cmra.army.mil https://cmra.army.mil/

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Surveillance

Contractor Key Personnel Report

Contractor submits initial Contractor key personnel report and updates as required.

Submitted Contractor key personnel report or update identifies all key personnel or personnel changes and includes the resume for individuals the first time that their name appears on the report.

Annually, as key personnel change and upon COR request. Due 7 calendar days after each

POP start date, after key personnel vacancy or new hire.

100% review by

Organization Report

Contractor submits organization report identifying the Contractor’s organization structure and identifying where “Key Personnel” fit into the structure.

The submitted Contractor Organization Report or update identifies Contractor’s current organization structure and the location of all Key Personnel within the structure.

Annually, as changes occur in organization structure and key personnel or when COR requests. Due 7 calendar days after each

POP start date, after organization change, key personnel change or COR request.

100% review by

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

MODS Service Request (MSR) Status Summary

Contractor shall prepare and update MSR Status Summary identifying the status of all MSRs submitted from the Government to the Contractor for quote.

The Contractor shall:

1) Sort MSR Status Summary data by Performance Period;

2) Utilize MSR Status Codes, Status Code definitions, and MSR data fields as identified by the MODS PMO to the Contractor;

3) Update the MSR Status Summary as changes occur ;

4) Archive the MSR Status Summary once per month;

5) Retain AKO archive file of all MSR Status Summary documents including those for closed POPs;

6) Post the MSR Status Summary to the

AKO MODS

Documentation Library and distribute AKO Alert to MODS Stakeholders as identified to the Contractor by the

MODS PMO.

Contractor maintains and archives MSR Status Summary in AKO MODS Documentation Library utilizing Government defined Status Codes and data fields.

Monthly archived MSR Status Summaries have less than 5% of the MSR line items with inaccurate data or status that is obsolete by more than 5 business days as of the archived date.

Monthly; data as of the 10th calendar day of each month and is due on the 14th calendar day of the month.

Data will be separated by

POP.

100% review by the

COR, PM, PD, TM,

and RQM on due date.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Surveillance

PWS Configuration Management Services

Contractor shall notify the Government MODS Technical Manager (TM) within 5 business days either before or after discussions with other Government or private agencies concerning the use or adaption of MODS system or application software.

Notify Government TM within 5 business days before or after discussion with other Government or private agencies.

As needed Written notification

System Configuration Management Plan (SCMP)

The SCMP shall define how the Contractor will perform the five elements of the configuration process (planning and management, identification, change management, status accounting, and verification and audit) in relation to the MODS system, along with any special conditions, such as security constraints, unique inter-operability constraints, contracting methods, etc., which the Contractor’s CM approach is based.

Project adheres to schedule.

The submitted SCMP ensures that designs are traceable to requirements, change is controlled and documented, interfaces defined and understood, and consistency between product and its supporting documentation and

Annually, 30 calendar days after each POP Start Date

100% review by the

COR, PM, PD, RQM,

and TM.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Configuration Baseline

Twice per year, the Contractor shall take a Configuration Baseline on a date within 9 calendar days prior to the due date and identify the “as of” date to the Government.

System Level

IEEE

documentation shall be prepared in accordance with the IEEE Standard 12207 (Standard for Information Technology - Software Life Cycle Processes).

Twice per year, the Contractor shall take a Configuration Baseline on a date within 9 calendar days prior to the due date and identify the “as of” date to the Government.

Semi-annual:

10 Jan and 10 Jul

100% review by the

COR, PM, PD, RQM,

and TM on due date.

Engineering Plan (SEP)

SEP shall be submitted in a format that addresses the succession of events as a software order moves from technical requirements review, through preliminary design review, critical design review and readiness review.

The submitted SEP will have the required content and is submitted on time.

Annually due 21 calendar days after POP Start Date

100% review by the

COR, PM, PD, RQM,

and TM on due date.

Bundled Release Assessment

The assessment shall assess the Contractor’s release process, experience with monthly bundled release, and Contractor’s recommendation to retain or modify the monthly cycle.

The Bundled Release Assessment shall include all items identified. Report is accurate and complete.

Due 120 calendar days after each POP start date

100% review by the

COR, PM, PD, TM,

and RQM on due

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Interface Control Agreement (ICAs) Status

The Contractor is responsible to document, coordinate, and maintain ICAs (to include Web Service Accessibility Agreements) in existence at the time of contract award and to accomplish and maintain new or revised ICAs added subsequent to contract award. The Contractor shall ensure that all system interfaces remain current and that no interruption or degradation of service shall occur because of an out of date interface. The Contractor posts a copy of current and terminated ICAs to the MODS AKO Documentation Library.

The Contractor shall review active Interface Control Agreements in accordance with documented Life Cycle Maintenance.

The Contractor posts ICAs to the

MODS

Documentation Library within 5 business days after the last approval signature.

The Contractor shall post latest ICA review documents to the

MODS

Documentation Library within 5 business days after the review is completed.

Monthly.

Data current as of last day of the month.

Due 5 business days after start of the month.

100% review by the

COR, PM, PD, TM,

and RQM.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Surveillance

PWS MODS

Documentation Library

The Contractor shall post the final or most recent version of all Requirements documentation (IEEE, ICAs, User Guides, Training materials, test scripts/results, other documents) as MSRs are processed.

Documents, Validation Documents, and specific guidance).

The Contractor uploads applicable documents to the appropriate folder within 5 business days after Government Functional acceptance 99% of the time.

Documents uploaded within 5 business days.

100% review by the COR, PD, TM, and

RQM.

MODS Access Status

Contractor provides timely and complete MODS Access Status report and remote access to “User Management” records. The Contractor shall ensure that the Government PMO has remote access to “select” “User Management” records for view only.

Contractor provides 24 hour 7 day per week Government PMO unrestricted view access to all MODS hardware and software.

Quarterly:

Due 10 Oct, 10 Jan, 10 Apr, and 10 Jul for quarter ending 30 Sep, 31 Dec, 31 Mar, and 30 Jun

100% review by the COR, PD, TM, and RQM on due date.

Application Usage Report

Contractor shall submit an Application Usage Report reporting by Application the number of SQL commits, page loads, and user sessions.

The Contractor shall submit the Application Usage Report with all required data elements and on time

Monthly: Due by the 10th calendar day of the month for the prior calendar month

100% review by the COR, PD, RQM, and

TM.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Administration Load Capacity Report

The Report shall separately identify the server and associated equipment Central Processing Unit (CPU) capacity, Memory capacity, Storage Area Network (SAN) capacity for the Pentagon and Alternate Site both historical and forecast and certify that equipment purchased by the MODS program is being utilized only for third party software purchased for MODS and for Configuration Items listed in the Government MODS Configuration Item Portfolio (CIP) document.

The Report clearly identifies allocated CPU, Memory, and SAN allocated capacities, utilized capacities, utilization growth rate, and future capacity requirements.

Report submitted is accurate and on time.

Quarterly:

Due 10 Oct, 10 Jan, 10 Apr, and 10 Jul for quarter ending 30 Sep, 31 Dec, 31 Mar, and 30 Jun

100% review by the COR, PD, TM, and

Operating

(OS)/Security Patch Management Report

The Contractor shall submit a quarterly OS/Security Patch Management Report identifying operating system or security software full title;

patch number; patch name/title;

applicable version;

manufacturer’s distribution date;

and date patch applied.

The Contractor applies OS/Security software patches within 10 calendar days after manufacture release date (within 3 calendar days for Information Assurance Vulnerability Alert (IAVA).

Quarterly:

Due 10 Oct, 10 Jan, 10 Apr, and 10 Jul for quarter ending 30 Sep, 31 Dec, 31 Mar, and 30 Jun

100% review by the

ISSM ,

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

MODS

Portability Plan –

MODS Portability Plan will address will address Part One though Part IV as outlined in the PWS subparagraphs.

Contractor submits MODS Portability Plan on time and provides all required data information

Annually: 30 calendar days after each POP start date and after delivery of new equipment, change of equipment host or equipment disposal.

100% review by the COR, PD, and TM

Contingency Operations Plan (COOP) Site Assessment

The Contractor shall prepare and submit COOP Site Assessment to report COOP site status, server capacity, and to assess the capability of the Site to sustain MODS operations in the absence of Pentagon mainframe or Pentagon MODS server support.

Contractor submits COOP Site Assessment identifying all required data elements.

Annually:

Due 120 calendar days after each POP Start Date.

100% review by the

COR, PM, PD, RQM,

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

COOP Test Plan

The Contractor shall prepare a COOP Test Plan to demonstrate the extent to which MODS applications and modules can operate from the COOP site independent from Pentagon mainframe and Pentagon MODS server support. The Test Plan shall address COOP site equipment; system data interface links;

communication links with worldwide users; method(s) to assess the degree of lost application functionality;

capture lessons learned; and the plan for issue mitigation and recommended actions.

Contractor submits COOP Test Plan identifying all required data elements.

Annually:

Due 120 calendar days after each POP Start Date.

100% review by the COR, PD, and TM.

Database Availability Report

The Contractor shall report all database scheduled and unscheduled outages to the Government in a Database Availability Report.

The Report shall include date and time of outage, duration of outage and reason for outage.

MODS data stored on the Enterprise server shall be available 24 hours per day, 7 days a week, except for scheduled outages. There shall be no more than 3 hours of unscheduled down time for any

MODS

application per month.

Monthly: Due by 10th calendar day of each month for the prior month report.

100% review by the

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Unscheduled Outage

At the time of occurrence, the Contractor shall report a Database Unscheduled Outage by e-mail to the Government for those outages that have exceeded 20 minutes.

MODS data stored on the Enterprise server shall be available 24 hours per day, 7 days a week, except for scheduled outages. There shall be no more than 3 hours of unscheduled down time for any

MODS

application per month. Reports are accurate and submitted on time as identified in Section X of the

PWS.

Due within 30 minutes after start of an unscheduled outage if the outage exceeds 20 minutes.

100% review by the COR, PD, and TM, on due date.

Disaster Recovery Plan

The Contractor shall submit a Database Disaster Recovery Plan identifying actions for recovery at the Pentagon and actions for recovery involving the MODS alternate site. The Plan shall address minimum nightly incremental backups with minimum once weekly full backup, alternate site backup data age, capability to route external data system interfaces to the alternate site, and the process to update MODS databases backlogged from external sources during the period of recovery.

In the event of a Pentagon site disaster with loss of data and expected lack of operability exceeding 24 hours, the Contractor shall establish MODS operational capability at the alternate site within 24 hours.

Annually: 30 calendar days after each POP Start Date.

100% review by the ISSM PD, and TM, on due date.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Recovery Progress Report

In the event of an actual disaster, the Contractor shall submit a minimum daily Recovery Progress Report to the Government Report shall contain:

actions Contractor needs from the Government to enable the Contractor to bring MODS system back into operational status, CI not operational, Attempted CI recoveries that failed indicating full or partial loss of functionality, and estimated time to bring all CIs into operational status.

Contractor shall submit an After Action Report (AAR) within 30 days after recovery to: explain steps taken to recover the MODS system and Database(s), identify primary obstacles, provide analysis of significant problems and how to mitigate in the future, and identify contractor personnel who played major roles in recovery process.

In the event of a Pentagon site disaster with loss of data and expected lack of operability exceeding 24 hours, the Contractor shall establish MODS operational capability at the alternate site within 24 hours.

Daily reports are submitted during the disaster and an AAR is submitted within 30 days after recovery. Reports are accurate and on time as identified in the

CDRL.

Daily in event of actual disaster After Action Report (AAR) due within 30 calendar days after recovery

ISSM PD, and TM.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Database Load Capacity Report

The Contractor shall manage the Database allocated server and storage area capacity. The Contractor shall submit to the Government a Database Load Capacity Report.

The Report shall separately identify the allocated Database server and storage area capacity for both Pentagon and Alternate Site.

The Report shall show the monthly utilized capacity for the current month and preceding eleven months to assist in trend analysis. The Report shall certify that Database storage utilization includes only applications listed in the Government

MODS

Configuration Item Portfolio (CIP) document.

The Database Load Capacity Report accurately identifies allocated server and storage area capacity, utilized capacity, and monthly utilized growth rate

Quarterly:

Due 10 Oct, 10 Jan, 10 Apr, and 10 Jul for quarter ending 30 Sep, 31 Dec, 31 Mar, and 30 Jun

100% review by the COR, TM, and on due date.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

DBA Patch Management Report

The Contractor shall perform Patch Management to ensure the update of all MODS Government owned third party commercial Database software at the Pentagon and Alternate Site. The Contractor shall submit a quarterly DBA Patch Management Report identifying database software full title;

patch number; patch name/title;

applicable version;

manufacturer’s distribution date;

and date patch applied.

The Contractor applies database software patches within 10 calendar days after manufacture release date (within 3 calendar days for IAVA).

Quarterly:

Due 10 Oct, 10 Jan, 10 Apr, and 10 Jul for quarter ending 30 Sep, 31 Dec, 31 Mar, and 30 Jun

100% review by the ISSM, and TM, on due date.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Certification and System Security Report

The Contractor shall submit a quarterly Certification and System Security Report identifying Contractor task compliance actions (such as timely IAVA compliance), copy of current certification/ DOD Information Assurance Certification and Accreditation Process (DIACAP)/and Tenant in Good Standing documents, and upcoming actions required to maintain certification and system security compliance.

DIACAP and CoN will be current and complete 100% of the time.

Coordination and provision of key documentation to the hosting site will be timely 100% of the time, to ensure accreditation standards do not jeopardize MODS system operation.

MODS

successfully protects patient and sensitive data from unauthorized access and use 100% of the time.

Research and apply IAVA’s within 3 calendar days after receipt.

Annually:

Due 30 calendar days after each POP start date

ISSM and TM, Incident Categories Request

Contractor shall submit for approval to the MODS PMO a Service Desk Incident Categories Request. The Request shall identify the categories and sub categories to report Service Desk Incidents.

The request identifies incidents against specific MODS applications and improve applications to drive down Service Desk incidents.

30 calendar days after contract Award with updates due prior to implementing change.

100% review by the

COR, PM, PD, RQM,

Incident Severity Classification Request

The Contractor shall submit for approval to the MODS PMO a Service Desk Incident Severity Classification Request.

The Service Desk Incident Severity Classification Request uses severity levels in

PWS C.5.1.4.1.

30 calendar days after contract Award with updates due prior to implementing change.

100% review by the COR, PD, TM, and

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Customer Contact Report

Contractor shall submit a monthly Customer Contact Report identifying and analyzing the type and quantity Customer Contacts (telephone, email, and fax) to Tier I Service Desk.

Customer Contract Report is submitted on time and contains information outline in PWS.

Monthly: Due on 7th calendar day of each month for the prior calendar month.

100% review by the COR, PD, RQM and

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Service Desk Top Ten Mitigation

The Contractor shall submit a monthly Service Desk Top Ten Mitigation report to analyze and recommend mitigation actions for those Configuration Items, system areas, or mainframe areas that generated the highest incoming customer contact.

Contractor submits Top Ten Mitigation report on time with required PWS.

Contractor is creating a separate Ticket for first appearance incidents 99% of the time.

A Service Desk person answers 98% of all incoming calls within 20 seconds after the initial ring or within 20 seconds after selection to speak to a Service Desk person as evaluated by Contractor self-inspection.

Callers who remains in the hold queue without hanging up are answered in less than 5 minutes 98% of the time as evaluated by Contractor self-inspection.

Service Desk Tier I staff properly classifies and escalates incidents 95% of the time.

Monthly: Due 14th calendar day each month to report prior calendar month.

100% review by the COR, PD, RQM and

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Call Closure Report

Contractor shall submit a monthly Call Closure Report identifying the number of new incidents by Severity Level and the number of calls and percent of calls closed by severity level within the respective specified threshold.

Call Closure Report identifies Tier III closure of Severity 1 incidents within 24 hours after initiation 99% of the time; Severity 2 incidents within 48 hours 97% of the time; Severity 3 incidents within 72 hours 95% of the time; and Severity 4 incidents within 4 hrs. 80% of the time.

Monthly: Due on 7th calendar day for prior month.

Attached within WAWF invoice.

100% review by the COR, PD, RQM, and

Call Abandonment Report

The Contractor shall submit a monthly Call Abandonment Report identifying the number of Service Desk inbound calls placed “on-hold” and the number and percent of those calls that “hang up” prior to the Service Desk taking the caller off of hold.

The Call Abandonment Report identifies less than 4% of callers placed on hold hang-up prior to completing their incident report to a Service Desk person. Report received on time as identified in the PWS.

Monthly: Due 7th calendar day of each month for the prior month.

100% review by the

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Customer Satisfaction Report

The Contractor shall submit a monthly Customer Satisfaction Report identifying the number of Service Desk customers surveyed; number and percent of customers responding with a positive evaluation of their Service Desk experience; a listing of negative comments;

Contractor actions to mitigate negative comment recurrence; and Contractor recommendations for Government action.

Customer Satisfaction Report identifies that 85% of the respondents express positive satisfaction with Service Desk support. Report received on time as identified in the PWS.

Monthly: Due 7th calendar day of each month for the prior month.

100% review by the COR, PD, RQM, and

Tier III Incident - Severity 1

The Contractor shall submit an e-mail Tier III Incident Escalation – Severity 1 report to the Government for all Incidents escalated to Tier III.

The report shall identify for each incident:

Ticket number, reported problem, and Severity classification, proposed action and assessment of root cause. Interim report filed when ticket closes to include assessment of trends, recommended Contractor or Government action for permanent solution.

Initial report to MODS PM and PMO within 30 minutes after Ticket opened;

interim reports appropriate to the situation; and final report when incident is closed;

99% of the time.

As required.

E-mail within 30 minutes after Ticket initiated

100% review by

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Incident – Severity 2

The Contractor shall submit an e-mail Tier III Incident Escalation report – Severity 2 to the Government for all Incidents escalated to Tier III. The report shall identify for each incident:

Ticket number, reported problem, and Severity classification, proposed action and assessment of root cause. Interim report filed when ticket closes to include assessment of trends, recommended Contractor or Government action for permanent solution.

Initial report to

MODS PMO

within 1 hour after Ticket opened and final report when incident is closed;

97% of the time.

As required.

E-mail within 1 hour after Ticket initiated.

100% review by

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Incident – Severity 3

The Contractor shall submit an e-mail Tier III Incident Escalation report – Severity 3 to the Government for all Incidents escalated to Tier III. The report shall identify for each incident:

Ticket number, reported problem, and Severity classification, proposed action and assessment of root cause. Interim report filed when ticket closes to include assessment of trends, recommended Contractor or Government action for permanent solution.

Initial report to

MODS PMO

within 24 hours after Ticket opened and final report when incident is closed;

95% of the time.

As required.

E-mail within 24 hours after Ticket initiated.

100% review by the COR, PD, RQM, and

Transition Startup Report

Contractor will have a Transition Startup period of approximately 90 days to obtain transition training from the incumbent vendor. The Contractor shall submit a weekly assessment of progress and problems in a Transition Startup Report.

The Report contains substantive data accurately identifying the progress and problems in transitioning MODS support from the incumbent vendor to the incoming Contractor.

Contractors’ staff are trained and prepared to perform on performance start date. Report is on time as identified in the PWS.

Weekly: Due 7 calendar days after contract award until base period performance start date.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Transition Transfer Report

During this PWS final POP, there will be a transition transfer from the incumbent Contractor to a new Contractor (unless the incumbent Contractor wins the follow-on contract).

The transition will be approximately 90 days. During this transition, the Contractor shall ensure that all Contractor employees provide all MODS documentation and all essential procedural processes to employees of the new Contractor.

The incumbent Contractor performing under this PWS shall submit a weekly assessment of progress and problems in a Transition Transfer Report.

The Contractor shall provide sufficient experienced personnel during Transition Transfer to maintain performance under this contract at the required level of proficiency.

The Contractor report contains substantive data accurately identifying the progress and problems in transitioning MODS support to a new vendor and the report is on time as identified in the PWS.

Weekly: Due beginning 7 calendar days after date of follow on contract award to new vendor until the incumbent Contractor’s final day in

POP.

Required Service

Performance Measures

Acceptable Quality Level (AQL) Delivery Date Method of

Data Artifacts Delivery

The incumbent Contractor shall complete a Data Artifacts Delivery to the new Contractor not later than 14 calendar days prior to the incumbent Contractor’s last period of performance end date. Data Artifacts Delivery shall include all types of MODS records in any media form prepared by the incumbent Contractor under this PWS.

System functions as specified without exceptions.

One Time: 14 calendar days prior to incumbent last period of performance end date.

100% review by the COR and TM on due