W81K04-18-R-0005_MODS_Amendment_0004.pdf

PDF 570 KB Posted May 18, 2018

Attached to: MEDICAL OPERATIONAL DATA SYSTEMS
Solicitation number: W81K04-18-R-0005
Issued by: Department of the Army Medical Command

About this file

Written by GovTribe AI · Dec 30, 2023

This award notice solicits proposals for Medical Operational Data Systems support services. The U.S. Army Medical Command seeks to award an IDIQ contract to provide sustainment and modernization services for the MODS system from July 2018 through June 2023. MODS is a government-owned, contractor-operated system that supports medical readiness, force health protection, and human capital functions. The contractor will operate and maintain the MODS infrastructure and applications at locations including the Pentagon and alternate sites. The contractor must have CMMI level 3 certification and will perform tasks including systems engineering, database administration, help desk support, configuration management, and incident management. Proposals are due by May 21, 2018 and should be delivered to the Health Readiness Contracting Office at Fort Sam Houston, Texas.

From the source

W81K04-18-R-0005 Amendment 0004

View the file

Other files

File	Type	Posted
W81K04-18-R-0005_MODS_Amendment_0006.pdf	PDF	Jun 1, 2018
Amendment_W81K04-18-R-0005-0001_(SF_30).pdf	PDF	May 29, 2018
Amendment_W81K04-18-R-0005-0002__(SF_30).pdf	PDF	May 29, 2018
MODS_Questions_and_Answers_(24_May_2018)_(Final).pdf	PDF	May 29, 2018
Amendment_W81K04-18-R-0005-0003_(SF_30).pdf	PDF	May 29, 2018
Amendment_W81K04-18-R-0005-0004_(SF_30).pdf	PDF	May 29, 2018
Amendment_W81K04-18-R-0005-0005_(SF_30).pdf	PDF	May 29, 2018
W81K04-18-R-0005_MODS_Amendment_0005.pdf	PDF	May 21, 2018
W81K04-18-R-0005_MODS_Amendment_0005_(Conformed).pdf	PDF	May 21, 2018
MODS_Questions_and_Answers_2_of_2__(16_May_2018).pdf	PDF	May 16, 2018
Amendment_W81K04-18-R-0005-0003_(Conformed).pdf	PDF	May 16, 2018
MODS_Questions_and_Answers_1_of_2_-_11May2018_Final.pdf	PDF	May 11, 2018
W81K04-18-R-0005-MODS_Amendment_0002_(Conformed).pdf	PDF	May 11, 2018
Amendment_W81K04-18-R-0005-0001.pdf	PDF	Apr 25, 2018
PWS_Attachment_4_-_MODS_2017_Help_Desk_Analysis_2_12_18.pdf	PDF	Apr 25, 2018
PWS_Attachment_1_-__MODS_Interface_Control_Agreements.pdf	PDF	Apr 25, 2018
PWS_Attachment_2_-_Configuration_Item_Portfolio___(CIP)_28feb2018.pdf	PDF	Apr 25, 2018
RFP_-_WK8104-18-R-0005_-__MODS_(Final_-_19_April_2018).pdf	PDF	Apr 19, 2018

Show all 18

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

- The purpose of this amendment is to make changes to the PWS on paragraph 1.1.9.

- Make changes to Exhibit B - PRS table section 5.5.4. - removed the w ord "and" and replace w ith a period.

- Make changes to Attachment 5 - QASP table section 5.5.4 - removed the w ord "and" and replaced w ith a period.

- Changes have been highlighted in yellow .

SEE SUMMARY OF CHANGES

1. CONTRACT ID CODE PAGE OF PAGES

S 1 70

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 18-May-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W81K04-18-R-0005

X 9B. DATED (SEE ITEM 11)

19-Apr-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

18-May-2018

CODE

W40M USA HLTH CONTRACTING ACT

CTR FOR HEALTH CARE CONTR

2199 STORAGE ST BLDG 4197 STE 68

JBSA FT SAM HOUSTON TX 78234-5074

W81K04 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W81K04-18-R-00050004 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

ATTACHMENT 5

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

Medical Operational Data System (MODS)

1. INTRODUCTION

This Quality Assurance Surveillance Plan (QASP) is pursuant to the requirements listed in the Performance Work

Statement (PWS) for Medical Operational Data System (MODS). This performance-based plan sets forth the procedures and guidelines the United States Army Medical Command (MEDCOM) will use in evaluating the technical performance of the MODS contractor.

2. PURPOSE

The purpose of the QASP is to describe the systematic methods used to measure performance and to identify the reports required and the resources to be employed. The intent is to ensure that the Contractor performs in accordance with performance metrics set forth in the contract documents, and that the Government receives the quality of services called for in the contract. The QASP provides a means for evaluating whether the contractor is meeting the performance standards identified in the PWS.

This QASP is designed to define roles and responsibilities, identify the performance objectives, define the methodologies used to monitor and evaluate the contractor’s performance, describe quality assurance reporting, and describe the analysis of quality assurance monitoring results.

3. AUTHORITY

Authority for issuance of this QASP is provided under FAR 37.604 and FAR 46.401.

4. SCOPE

The QASP is put in place to provide Government surveillance oversight of the Contractor’s quality control efforts to assure that they are timely, effective and are delivering the results specified in the contract or task order. The QASP is not a part of the contract nor is it intended to duplicate the Contractor’s Management Plan.

5. PERFORMANCE MANAGEMENT STRATEGY

The contractor’s internal quality control system will set forth the procedures for self-inspecting the quality, timeliness, responsiveness, customer satisfaction, and other performance requirements in the PWS. The contractor will utilize its internal quality control system to assess and report their performance to the designated Government representative.

The Government representative will monitor performance and review performance reports furnished by the contractor to determine how the contractor is performing against communicated performance objectives. The

Government will make decisions based on performance measurement metric data and notify the contractor of those decisions. The contractor will be responsible for making required changes in processes and practices to ensure delivery of the required performance.

6. GOVERNMENT ROLES AND RESPONSIBILITIES

The following definitions for Government resources are applicable to this plan:

a. Contracting Officer (KO) - A person duly appointed with the authority to enter into, administer, or terminate contracts and make related determinations and findings on behalf of the Government.

b. Contracting Officer’s Representative (COR)/Alternate Contracting Officer’s Representative (ACOR) -

An individual designated in writing by the Contracting Officer to act as the KO’s authorized representative to assist in administering a contract. The source and authority for a COR is the

Contracting Officer. COR limitations are contained in the written letter of appointment.

The Government resources shall have responsibilities for the implementation of this QASP as follows:

c. Contracting Officer – The Contracting Officer ensures performance of all necessary actions for effective contracting, ensures compliance with the terms of the contract, and safeguards the interests of the United States in the contractual relationship. It is the Contracting Officer that assures the

Contractor receives impartial, fair, and equitable treatment under the contract. The Contracting Officer is ultimately responsible for the final determination of the adequacy of the Contractor’s performance.

d. Contracting Officer’s Representative (COR) – Pursuant to DFARS 201.602-2, the COR/ACOR is responsible for technical monitoring or administration of the contract and assures proper Government surveillance of the Contractor’s performance. Any changes that the Contractor deems may affect contract, price, terms, or conditions shall be referred to the Contracting Officer for action.

7. METHODOLOGIES TO MONITOR PERFORMANCE

The below listed methods of surveillance shall be used in the administration of this QASP.

a. Program Reports – Contractor completion of service requirements and status reports will be submitted and reviewed. Reports will be used by the COR, Program Management Office and

Functional/Technical Representatives to monitor contractor performance.

b. Invoice acceptance, rejection, and resolution - The COR will review all Contractor invoices submitted into Wide Area Work Flow (WAWF) to ensure that there is a record of Government Functional acceptance and/or Government Technical acceptance. Acceptance indicates that performance thresholds and requirements have been met. The COR will periodically review the results of QASP surveillance to validate that the Government is receiving the services ordered and that the associated invoices are therefore appropriate for payment. When the applicable acceptances are on record and

QASP evaluations indicate acceptable Contractor performance, the COR will release the invoice to the

Defense Finance and Accounting System (DFAS) for processing and payment. Rejection: If delivered work has not met “Performance Measure Thresholds,” the MODS PM or Functional Proponent will disapprove and provide the COR with supporting justification

c. Customer Feedback – Feedback may be obtained from help desk tickets and customer comments.

Customer complaints, to be considered valid, must set forth clearly and in writing the detailed nature of the complaint, and must be signed.

d. Inspections – Each phase of the services rendered under the contract is subject to Government inspection during the Contractor’s operations and after completion of a task. Inspections may be routine functions performed by the COR. Government inspections may be conducted in an unannounced manner by the COR or ACOR. The COR shall maintain a Contract Discrepancy Report

(CDR), a copy of which will be provided to the Contractor. Within three business days, the Contractor shall reply in writing to a CDR(s) by stating reason(s) for unsatisfactory performance(s) and shall identify the corrective action(s) that will be taken to prevent recurrence(s).

8. ANALYSIS OF QUALITY ASSURANCE MONITORING

The Government shall use the observation methods cited to determine whether the Acceptable Quality Levels

(AQLs) have been met. If the contractor does not deliver timely corrective action, the Government shall take action to adjustment the contractor’s monthly payments.

The KO may require the contractor’s project manager, or a designated alternate, to meet with the KO and other

Government personnel as deemed necessary to discuss performance evaluation. The COR will define a frequency of in-depth reviews with the contractor, however if the need arises, the contractor will meet with the KO as often as required or per the contractor’s request. The agenda of the reviews may discuss:

Monthly performance measured by the metrics and trends

Issues and concerns of both parties

Projected outlook for upcoming months and progress against expected trend

Recommendations made by the COR based on contractor information

Issues arising from independent reviews and inspections

In addition to QA monitoring, the COR will use the information contained in the contractor’s reports to assess the contractor’s level of performance for each objective measured in this QASP. The COR must coordinate and communicate with the contractor to resolve issues and concerns of marginal or unacceptable performance. The contractor will discuss with the KO/COR satisfaction ratings receiving a “less than acceptable” rating. For such cases, the contractor should highlight the contractor’s perspective on factors driving customer satisfaction and present plans to adjust service levels accordingly to bring the satisfaction rating up to an acceptable level.

The KO/COR and contractor should jointly formulate tactical and long–term courses of action. Decisions regarding changes to metrics, thresholds, or service levels should be clearly documented. Changes to service levels, procedures, and metrics will be incorporated as a contract modification at the convenience of the KO.

Contractor Performance Assessment Reporting System (CPARS).After each contract Period of Performance (POP), the COR shall request from the Government Task Managers their assessment (positive and/or negative) of the

Contractor’s performance in the period just ended. The COR shall enter the resulting assessments into the

Government CPARS to establish a record in the Past Performance Information Retrieval System (PPIRS).

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

1.3.5 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.

1.4 Contractor

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://www.e cmra.mil/Defa ult.aspx

1.6.1 and

1.6.3

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.

100% review by COR.

1.7.1 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

100% review by COR.

1.13 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.

1.13.4 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.

https://www.ecmra.mil/Default.aspx https://www.ecmra.mil/Default.aspx

Reference

Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

1.15 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.

1.15.3.2 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.

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

1.15.4.2 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 prepared by the incumbent

Contractor under this

PWS.

Full and Current

Configuration Baseline is provided to incoming vendor

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

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

Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

1.15.4.3 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.

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

5.1.1 System

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.

5.2.1 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 COR, PD, RQM, and TM.

Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

5.2.2 Database

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.

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

20 minutes.

100% review by the PD and

TM on due date.

5.2.3 Database

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.

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

Surveillance

5.2.4 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.

Daily in event of actual disaster

After Action

Report (AAR) due within 30 calendar days after recovery

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

Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

5.2.5 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, 31Mar, and 30 Jun

100% review by the PD and

5.2.6 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.

5.4.5.1 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 PD, RQM, and TM.

Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

5.4.6 System

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 PD, TM, and RQM on due date.

5.4.7 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 PM, PD, RQM and TM.

5.4.7 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, Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

5.5 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 to the TM and

COR

5.5.1.1 Configuration

Baseline

Twice per year, the

Contractor shall review, update and deliver the

System’s Configuration

Baseline

The Contractor shall ensure the entire Configuration

Baseline of system documents (outlined in the approved Vendor SCMP) are current; meaning all of the documents show the current and validated state of the system, its components and applications. All documents will be uploaded to AKO

MODS documentation

Library NLT 1 February and 1 September of each calendar year.

The entire set of current

MODS source code is delivered to the MODS

PMO via SFTP NLT 1

February and 1 September of each calendar year.

Semi-annual:

NLT 1 February and 1 September of each calendar year.

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

Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

5.5.4 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.

Annually, 30 calendar days after each POP

Start Date

100% review by the PM, PD, RQM, Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

5.5.9 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:

(b) Sort MSR Status

Summary data by

Performance Period;

Codes, Status Code definitions, and MSR data fields as identified by the

MODS PMO to the

Contractor;

(d) Update the MSR Status

Summary as changes occur ;

(e) Archive the MSR Status

Summary once per month;

(f) Retain AKO archive file of all MSR Status

Summary documents including those for closed

POPs;

(g) 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; 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

5.6 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 PM, PD, TM, and RQM.

5.7 MODS

Documentation

Library

The Contractor shall post the final or most recent version of all

Requirements documentation (System

Technical/Architectural

Documents, 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 of MSR 99% of the time

Documents uploaded within

5 business days.

100% review by the PD, TM, and

RQM.

Required

Service

Performance Measures Acceptable Quality Level

(AQL)

Delivery Date Method of

Surveillance

5.8.4 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

RMF documents, and upcoming actions required to maintain certification and system security compliance.

MODS RMF

Accreditation remains current and complete 100% of the time.

Coordination and provision of key documentation to the hosting site/eMASS and

ACAS 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

100% review by the ISSM and TM,

5.8.7.1 Operating

System

(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 MODS

PMO ISSM

5.9.10 Incident