Atch_3_-_QASP_Amd1.pdf

UNCLASSIFIED

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

FOR

UNITED STATES TRANSPORTATION COMMAND

(USTRANSCOM) COMMAND, CONTROL,

COMMUNICATIONS & CYBER SYSTEMS

DIRECTORATE (TCJ6)

INFORMATION TECHNOLOGY SERVICE

MANAGEMENT (ITSM) ENTERPRISE SUPPORT

23 March 2016

APPROVED:

TBD DAVID Q. SWANEY

Contracting Officer’s Representative Contracting Officer

TCJ6-O TCAQ-D

Quality Assurance Surveillance Plan 20 January 2016 ii

Table of Contents

1. INTRODUCTION

2. PURPOSE

3. ROLES AND RESPONSIBILITIES

3.1 Contracting Officer (CO)

3.2 Contract Specialist (CS)

3.3 Contracting Officer’s Representative (COR)

4. METHODS OF SURVEILLANCE

4.1 Service Delivery Summary (SDS)

4.1.1 Sampling

4.1.2. Third Party Audits

4.1.3 Inspection/Review

4.1.4 Customer/Government Inputs

4.1.5 Management Review

4.1.6 Non-SDS Items

5. EVALUATION METHODOLOGY

5.1 Established Procedures

6. DOCUMENTATION

7. ACRONYMS

APPENDIX A – QUALITY ASSURANCE SURVEILLANCE SUMMARY AND

METHOD

APPENDIX B – DISCREPANCY STATUS REPORT

UNCLASSIFIED

1. INTRODUCTION

This QASP was developed in accordance with USTCI 63-5, Contracting Officer’s Representative (COR)

Program, for work performed to provide technical and functional support services for the

USTRANSCOM, Scott Air Force Base, IL as well as for its Army and Air Force Service Components.

This QASP sets forth the procedures and guidelines to be used by the Government to ensure that the contractor achieves the required performance standards as specified in the Information Technology

Service Management (ITSM) Enterprise Support Performance Work Statement (PWS). The PWS contains a Service Delivery Summary (SDS) that summarizes performance objectives (service required) and performance thresholds (specific standard) contained within the body of the PWS. The SDS does not identify every service required, but only those services considered most important for mission accomplishment. This QASP is based on the premise that the contractor, and not the Government, is responsible for management and quality control actions to meet the terms of the contract. The SDS recognizes that the contractor is not a perfect manager and that unforeseen and uncontrollable problems do occur. Good management and use of an adequate quality control plan will allow the contractor to meet or exceed the performance standards specified in the PWS.

2. PURPOSE

This QASP is designed to accomplish the following:

a. Provide a systematic method to survey and evaluate contractor services to determine conformity with the technical requirements of the contract.

b. Define the roles and responsibilities of participating Government officials.

c. Describe the evaluation methods that will be employed by the Government in assessing the contractor’s performance.

d. Describe the process of performance documentation.

e. Provide copies of the Quality Assurance (QA) monitoring report format that will be used by the

Government in documenting and evaluating contractor’s performance.

3. ROLES AND RESPONSIBILITIES

The Government monitors contractor performance on a continuing basis through the services of a surveillance team. The surveillance team consists of the following members: Contracting Officer (CO), Contract Specialist (CS) and Contracting Officer’s Representative (COR).

3.1 Contracting Officer (CO)

The CO has overall responsibility for contract administration. The CO is responsible for monitoring contract compliance and resolving any and all disagreements regarding interpretation of contract terms and conditions. Payment is authorized based on documented objective evidence provided by the COR that contractor performance meets the performance standards specified. The CO is the only Government official authorized to revise the contract.

3.2 Contract Specialist (CS)

The CS acts as an acquisition consultant and serves as liaison between the Contracting Office and the

Command, Control, Communications & Cyber Systems Directorate (TCJ6) COR.

3.3 Contracting Officer’s Representative (COR)

The COR:

Quality Assurance Surveillance Plan 2 July 2014

UNCLASSIFIED

Serves as a functional expert and is responsible for monitoring, assessing, recording and reporting the technical performance of the Contractor on a continuous basis.

Schedules surveillance activities; evaluates and documents performance by the Contractor;

initiates requests for and evaluates adequacy of the corrective action and reports Contractor performance of contractor requirements.

Is sufficiently trained to perform the required duties and to ensure their knowledge of the terms and conditions of the contract

Is to be objective, fair, and consistent in evaluating contractor performance against standards

Will notify the CO immediately when an evaluation shows that performance does not meet the standards identified in this QASP

Is required to ensure changes in work are not initiated before a written authorization or modification is issued by the CO

Is required to accept delivery of services

Must ensure that all services have been performed before entering the quantity received and digitally signing the receiving report/invoice in Wide Area Work Flow (WAWF)

Has a maximum of seven days after the contractor’s submission of a properly documented receiving report/invoice to accept the quantity and digitally sign the document in WAWF.

Prompt processing of receiving reports/invoices in WAWF increases the Government’s ability to take discounts offered and decreases the likelihood of the Government incurring interest expense for late payment. After digital signature, the signed receiving report/invoice will be routed to

Defense Finance and Accounting Service (DFAS) for scheduling of payment.

Is required to provide an assessment of contractor performance to the CO for input into

Contractor Performance Assessment Report.

4. METHODS OF SURVEILLANCE

4.1 Service Delivery Summary (SDS)

The SDS summarizes the expected service objectives (outcomes) and identifies the metrics that will be tracked to determine whether the outcomes are being achieved at the appropriate levels of performance.

The USTRANSCOM, through the COR, will monitor contractor performance using the surveillance methods described below. In determining the evaluation criteria, USTRANSCOM has considered what the contract specifically calls for, how performance can be surveyed, and if the proposed method of surveillance is adequate to assure the required level of performance has been achieved. Additionally, contractor performance will be a factor affecting application of the plan, i.e., surveillance frequency may be increased or decreased based on contractor demonstrated and documented performance. One or a combination of the following surveillance methods will be used to produce a well-rounded indication of contractor conformance:

a. Sampling (Spot, Periodic and Random Sampling)

b. Third Party Audit

c. Inspection/Review (verification of specific tasks, weekly, monthly, quarterly, semi-annual, annual)

d. Customer/Government Input

4.1.1 Sampling

This is the most appropriate method for frequently recurring tasks. Random sampling is done to determine whether to accept or reject the contractor’s performance of the total lot of a particular task for a given period of time, using the premise that the statistically selected sample is representative of the entire lot. Sampling may be spot, periodic or random.

UNCLASSIFIED

4.1.2. Third Party Audits

Third Party Audits will be conducted by an authorized agent of the Government, federal, state and local agencies (i.e. OSHA, DMV, EPA, Environmental Management etc.).

4.1.3 Inspection/Review

This surveillance type is preferred for those tasks that occur infrequently. It is also used frequently for those tasks having very stringent performance requirements. When this type of surveillance is used, COR must inspect and evaluate the contractor’s performance each time it is performed to determine acceptability.

This type of surveillance consists of the evaluation of samples selected on other than a 100% or statistically random basis. The results of periodic surveillance inspections may be used as the basis for actions against the Contractor. In such cases the Inspection of Services clause becomes the basis for the contracting officer’s actions. This will be done more frequently at the beginning of the contract, and is expected to decrease as standards are consistently met, but may increase if performance falls below standard.

The planned surveillance methods and standards are documented in Appendix A. Contractual requirements are in accordance with (IAW) the PWS.

4.1.4 Customer/Government Inputs

The COR may use customer input to document discrepancies in contractor performance. The CO may use validated customer complaints as the basis for actions against the contractor. In such cases the

Inspection of Services clause becomes the basis for the CO’s actions. It is expected that some customer’s will file complaints directly with the Contractor. The Contractor should attempt to resolve complaints/issues at the lowest level possible. However, the Government acknowledges that some issues require government intervention. In such cases, the Contractor shall request assistance from the COR or

CO.

4.1.5 Management Review

Methods of surveillance can change after contract award based on acceptance of a Contractor’s proposed quality control program or agreement that establishes the metrics to be used. When metrics are used as a method of surveillance through the partnering process, they may be developed after contract award, but prior to the performance start date.

4.1.6 Non-SDS Items

For required tasks not shown on the SDS, including all other tasks in the PWS and any referenced documents, the Government still retains the right to inspect any item included in the contract in accordance with Federal Acquisition Regulation (FAR) Part 46, Inspection of Services clauses.

Inspection of these services will be performed in the same general manner as periodic surveillance items mentioned above. The results of these inspections are documented and, if necessary, are provided to the

CO for action. Should a discrepancy be observed, the CO will handle each documented discrepancy on a case-by-case basis.

5. EVALUATION METHODOLOGY

This QASP comprehensively guides the surveillance team’s activities and has been developed in a format to ensure ease of understanding and implementation. For each performance objective (service required) in the SDS, the specific methods of surveillance and performance thresholds are shown in Appendix A.

The methodology described in the chart shall be used as the basis for performing surveillance of the

UNCLASSIFIED

respective performance objectives.

5.1 Established Procedures

Each Contractor assessment shall follow an established procedure for surveillance, recording, reporting and follow-up, outlined as follows:

Frequency of surveillance will be IAW the COR’s schedule.

Surveillance will be performed IAW Appendix A and results/comments recorded.

Performance/non-performance for a particular task will be entered chronologically by the COR on a historical log of surveyed performance. If no deficiency exists in Contractor performance for this element, no further action is required.

If Contractor performance is deficient, the course of action is dependent on the severity/impact/frequency of the non-performance.

o Re-performance is the first action to resolve deficiencies.

o When the COR determines a deficiency is not Government caused, a Contract

Discrepancy Report (CDR) is initiated.

COR completes the form and sends it to the CO.

CO must evaluate the CDR and, if appropriate, sign and send it to the Contractor.

Contractor must complete blocks 9 and 10 according to the requirements of the contract and return it to the CO within 5 calendar days of receipt.

Upon receipt of the Contractor’s response, the CO, in consultation with the COR, must evaluate the Contractor’s response and take the appropriate action.

CO must document the evaluation (in block 11) and action taken (in block 12) on the CDR.

COR shall submit a Discrepancy Status Report (see attachment 2) and attach a copy of all CDRs for the reporting period.

o When corrective action is reported by the Contractor, the COR will follow up with additional surveillance to verify implementation.

6. DOCUMENTATION

All surveillance activities must be documented to provide the required audit trail to justify Government acceptance and payment. The documented audit trail of the surveillance (DAS) activities is required by

FAR 46.104(c), Contract Administration Office Responsibilities, which states, “Maintain, as part of the performance records of the contract, suitable records reflecting, (1) The nature of Government contract quality assurance actions, including, when appropriate, the number of observations made and the number and type of defects; and (2) Decisions regarding the acceptability of the products, the processes, and the requirements, as well as action to correct defects.”

All documentation resulting from surveillance is made a permanent part of the contract file. The COR must keep the documentation files during the term of the contract and either monthly or at the conclusion of the contract (as directed by the CO); transfer the files to the CO for inclusion in the official contract file. It is the responsibility of the COR to establish and maintain this information in a DAS Folder. The surveillance folder(s) should include as a minimum:

a. Contract including Modifications

b. Task Orders including Modifications

c. QASP

UNCLASSIFIED

d. COR Letter of Designation

e. Invoices

f. Surveillance Records

Written report of all inspections and timelines of deliverables

Written report of any deficiency

Any other written documentation relation to contract performance

g. General Correspondence

7. ACRONYMS

Acronym Definition

CDR Contract Discrepancy Report

CO Contracting Officer

COR Contracting Officer’s Representative

CS Contract Specialist

DAS Document Audit Surveillance

DFAS Defense Finance and Accounting Service

DMV Division of Motor Vehicles

EPA Environment Protection Agency

FAR Federal Acquisition Regulation

O&M Operations and Maintenance

OSHA Occupational Safety and Health Administration

PWS Performance Work Statement

QA Quality Assurance

QASP Quality Assurance Surveillance Plan

SDS Service Delivery Summary

USTCI United States Transportation Command Instruction

USTRANSCOM United States Transportation Command

WAWF Wide Area Work Flow

UNCLASSIFIED

APPENDIX A – QUALITY ASSURANCE SURVEILLANCE SUMMARY and METHOD

The following items will be utilized for evaluation of performance during the duration of this contract.

Performance

Objective PWS Para Performance Threshold

Surveillance Method

Trip Reports 1.3.1.5

95% of the time Trip Reports are received within five (5) business days after completion of travel and contains all details related to the trip and information on the traveler

Customer/Government

Input

Meeting/Conference

Minutes 1.3.1.6

95% of the time minutes are provided within two (2) business days upon request by the Government and contain all results and impacts of the meeting/conference

Customer/Government

Input

Ticket

Acknowledgement 1.3.2

95% of the time tickets are acknowledged IAW paragraph 1.6 of

PWS

Sampling

Ticket Resolution 1.3.2 95% of the time tickets are resolved IAW paragraph 1.6 of PWS

Sampling

Ticket Assignment 1.3.2

95% of the time tickets are assigned appropriately IAW paragraph 1.6 of

PWS

Sampling

Ticket Missed

Acknowledgment 1.3.2

95% of the time missed acknowledgements notifications are handled IAW paragraph 1.6 of PWS

Sampling

Ticket Proactive

Notification 1.3.2

95% of the time proactive notifications are provided IAW paragraph 1.6 of PWS

Sampling

Ticket Missed

Resolution 1.3.2

95% of the time missed resolutions are escalated IAW paragraph 1.6 of PWS

Sampling

Ticket Escalation 1.3.2

95% of the time tickets are escalated appropriately IAW paragraph 1.6 of

PWS

Sampling

Ticket Notification 1.3.2

95% of the time the Government is properly notified IAW paragraph 1.6 of

PWS

Inspection/Review

On-call Support 1.3.2

IT Ops Center is able to contact the on-call technician nine (9) of every ten (10) attempts made outside of normal duty hours

Customer/Government

Input

Process and Procedure

Documentation 1.3.2

95% of the time, documentation accurately reflects current operational processes and procedures; tool and system references; organizational references and contact information; and policy references.

Inspection/Review

Process and Procedure

Documentation 1.3.2

No more than 1 late document per month and no more than 5 days late. For final

Inspection/Review

UNCLASSIFIED

Performance

Objective PWS Para Performance Threshold

Surveillance Method deliverables, no more than two sets of corrections/edits and all corrections must be accomplished within 2 days or other such time periods as mutually determined between the government and the tasked contractor.

Unplanned Outage

Notification 1.3.2

100% of the time, provide notification to the IT Ops Center for unplanned outages within 15 minutes of detection.

Inspection/Review

On-Call Response Time 1.3.2

95% of the time, on call personnel will begin work within two (2) hour of contact

Inspection/Review

ADPE EC Duties 1.3.2

100% of the time ADPE is properly accounted and controlled in accordance with established policies

Inspection/Review

Service Desk

Performance Metrics

Report

1.3.2.1 95% of the time, reports accurately reflects status.

Inspection/Review

Account issuance and password resets 1.3.2.1.2

95% of the time issued within one (1) business day.

Sampling

First contact resolution by the Service Desk 1.3.2.1.2.1

68% of the time, technicians will resolve issues at first notification (phones, email, chat, etc.)

Inspection/Review

Self-help site resolution 1.3.2.1.2.3 Reduce the number of incidents and service requests a minimum of 25%

Sampling

Known error records updates 1.3.2.3.3

98% of the time updates will be accurate and on-time

Sampling

Hardware and Software

Problem Response 1.3.2.4.4.2

During on-site hours: within 15 minutes of initial report during on-site hours

After duty hours on an on-call basis with a 2-hour response time

Sampling

Workstation Transport to Customers 1.3.2.4.6.2.1

On-site: 1 business day

Off-site: 2 business days

Sampling

Key IT Staff Support 1.3.2.4.7 On-call periods shall be no more than two (2) hours to begin work on-site

Inspection/Review

Availability Rate 1.3.2.5.1.3 99.75% annualized availability rate. Sampling

Implement Approved solutions 1.3.2.5.1.3

90% of the time approved solutions are implemented within ten (10) business days of approval, provided necessary hardware is available

Sampling

Provide Technical

Solutions and Costing

(TS&C) to requests

1.3.2.5.1.3

90% of the time TS&C is provided within three (3) business days of request

Sampling

Trouble Ticket

Response 1.3.2.5.1.3

95% of the time response is received within 15 minutes of initial problem notification during normal duty hours and within two (2) hours if on-site response is required during non-duty

Sampling

UNCLASSIFIED

Performance

Objective PWS Para Performance Threshold

Surveillance Method hours

On-site AV support for

TCCC, TCDC, and

TCCS

1.3.2.6.1.1

100% of the time support is provided on-site for TCCC, TCDC, and TCCS attended briefing events.

Customer/Government

Input

On-site VTC support for TCCC, TCDC, and

TCCS

1.3.2.6.1.2

100% of the time support is provided on-site for TCCC, TCDC, and TCCS attended briefing events.

Customer/Government

Input

Response and on-site correction of system failures

1.3.2.6.1.2

Respond within 30 minutes of notification and provide hourly updates until an agreed upon plan to restore is identified

Sampling

CRO Duties 1.3.2.6.1.4

100% of the time COMSEC materials are properly accounted and controlled in accordance with established policies

Sampling

AV Operator level instructions 1.3.2.6.2.1

95% of the time instructions are published within 20 business days of any changes or upgrades and are 100% error free

Inspection/Review

Preventative maintenance as prescribed by the equipment manufacturer

1.3.2.6.2.1

98% of the time preventative maintenance is accomplished in accordance with the manufacturer’s instructions.

Sampling

Preventative maintenance as prescribed by the equipment manufacturer

1.3.2.6.2.1

98% of the time preventative maintenance is accomplished in accordance with the manufacturer’s instructions.

Sampling

Successful install and programming of

AV/VTC equipment

1.3.2.6.2.1

95% of the time installs are completed as scheduled and are 100% error free

Inspection/Review

VTC Operator level instructions 1.3.2.6.2.1

95% of the time instructions are published within 20 business days of any changes or upgrades and are 100% error free

Inspection/Review

Accurate and timely configuration of test environment resources as required by test plans and customer test requirement

1.3.3.9.3.1

No more than 3 total days delay per month to all customer test activities attributable to improper or late configuration of test environments. All improper configurations identified and corrected within one (1) workday

Customer/Government

Input

Software Failure

Notification 1.3.3.9.3.1

95% of the time notification occurs no later than one (1) business day after failure occurs

Sampling

Effective operation and system administration of test systems, computer and

1.3.3.9.3.2

No more than 15 hours of unplanned network downtime per month due to internal administrative or test network problems (not to include downtime

UNCLASSIFIED

Performance

Objective PWS Para Performance Threshold

Surveillance Method telecommunications

Administrative, and test network environments awaiting replacement parts). No more than two minor non-recoverable data losses per year. System Availability will be 98% or better.

Negative Impacts to

Operational Status 1.3.4.4

95% of the time the Government is notified within one (1) hour of any negative impacts to operational status

Inspection/Review

Outage/Restoral

Messages 1.3.4.5

95% of the time the IT Operations

Management is notified within one (1) hour of awareness of outage/restoral

Sampling

Security Operations 1.3.5.1.1, 1.3.5.1.2

100% of the time, no successful intrusions into the networks under the contractor’s control due to negligence or deviation from established procedures in performing actions specified by this task.

Customer/Government

Input

Software and Operating

System Versions

1.3.5.1.1, 1.3.5.1.2

100% of the time security mechanisms are running supported software versions and are up to date on security vulnerability patches with any exceptions approved by government in writing

Sampling

Uptime for

Cyber/Information

Security Infrastructure

Mechanisms

1.3.5.1.1, 1.3.5.1.2

99.9% availability must be maintained for all cyber security defense, and intrusion detection monitoring and incident management services (e.g.

firewall protection service for a specific area of coverage must be operational

99.9% of the time)

Inspection/Review

Unplanned Outage

Notification

1.3.5.1.1, 1.3.5.1.2, 1.3.5.1.4

100% of the time, provide notification to the CyOC for unplanned outages within

15 minutes of detection.

Sampling

On-call Support

1.3.5.1.1, 1.3.5.1.3, 1.3.5.1.4

USTRANSCOM Cyber Operations

Center (CyOC) is able to contact the on-call technician nine (9) of every ten (10) attempts made outside of normal duty hours

Inspection/Review

On-call Response Time 1.3.5.1.1, 1.3.5.1.4

100% of the time, on call personnel will begin work within one (1) hour of contact

Inspection/Review

Incident Detection 1.3.5.1.2

99% of the time, detect all incidents and events identified within available audit logs or by network sensors in the networks under their control.

Sampling

Incident Response 1.3.5.1.2

95% of the time, review all incidents flagged by monitors within 30 minutes of detection.

Sampling

COMSEC Equipment

Accountability 1.3.5.1.4

100% accountability for

USTRANSCOM Controlled

Cryptographic Items (CCI)

UNCLASSIFIED

Performance

Objective PWS Para Performance Threshold

Surveillance Method

COMSEC Practice

Dangerous to Security

(PDS) Notification

1.3.5.1.4

100% of the time, provide notification to the Government of any COMSEC PDS within 1 hour of detection

Inspection/Review

COMSEC Training 1.3.5.1.4 100% training accomplished for all

CROs/SVROs

Inspection/Review

Process and Procedure

Documentation 1.3.5.2

95% of the time, documentation accurately reflects current operational processes and procedures; tool and system references; organizational references and contact information; and policy references.

Customer/Government

Input

Process and Procedure

Documentation 1.3.5.2

No more than 1 late document per month and no more than 5 days late. For final deliverables, no more than two sets of corrections/edits and all corrections must be accomplished within 2 days or other such time periods as mutually determined between the government and the tasked contractor.

Customer/Government

Input

Reporting Accuracy and Timeliness: Prepare written products

(letters, plans, vulnerability/scanning reports, briefings, presentations, schedules, and other documentation) in an accurate and timely manner.

1.3.5.2

No more than 1 late document per month and no more than 5 days late. For final deliverables, no more than two sets of corrections/edits and all corrections must be accomplished within 2 days or other such time periods as mutually determined between the government and the tasked contractor. All draft material provided at least 2 working days prior to meetings or review boards. Final, security reviewed copies of all briefings/ presentations provided at least 1 working day prior to presentation

Customer/Government

Input

Security Assessments of USTRANSCOM 1.3.5.2

100% of the time, satisfactory ratings are achieved during assessments of

USTRANSCOM security on all activities defined within this task

Inspection/Reviews

Accurate and timely security assessments, in prescribed format, in accordance with the engineering principles outlined in NIST SP

800-27 and requirements of the

DoD RMF

1.3.5.2.1

Content: No more than 1 deviation per month from established principles and directives. 100% of assessments will address all required elements and consider security functionality from existing DoD and USTRANSCOM layered architectures.

Format: No more than 1 late document per month and no more than 5 days late.

For final deliverables, no more than two sets of corrections/edits and all corrections must be accomplished within

Inspection/Reviews

UNCLASSIFIED

Performance

Objective PWS Para Performance Threshold

Surveillance Method

2 days or other such time periods as mutually determined between the government and the tasked contractor

Security Support for

TCCs and Cyber

Security Service

Provider Subscribers

1.3.5.2.1.1

Optional

100% of the time, for incident response, contractor FTE is on site within 24 hours of notification. Assessments/incident response activities accomplished in accordance with DoD directives and standard accepted practices of security engineering

Customer/Government

Input

Accurate and timely configuration of vulnerability management and scanning environment resources as required by vulnerability management plan and government requirement

1.3.5.2.2

No more than 3 total days delay per month to all vulnerability management activities attributable to improper or late configuration of environments. All improper configurations identified and corrected within 1 workday

Inspection/Reviews

Effective operation and system administration of scanning and vulnerability management systems

1.3.5.2.2

Timeliness: No more than 12 hours of unplanned network downtime per month due to due to negligence or deviation from established procedures in performing actions specified by this task.

(not to include downtime awaiting replacement parts). No more than one minor non-recoverable data loss per year.

System availability will be 98% or better.

Inspection/Reviews

Security Operations 1.3.5.2.2

100% of the time, no successful intrusions into the networks under the contractor’s control due to negligence or deviation from established procedures in performing actions specified by this task.

Customer/Government

Input

Software and Operating

System Versions 1.3.5.2.2

100% of the time security mechanisms are running supported software versions and are up to date on security vulnerability patches with any exceptions approved by government in writing

Customer/Government

Input

Unplanned Outage

Notification 1.3.5.2.2

100% of the time, provide notification to the CyOC for unplanned outages within

15 minutes of detection.

Sampling

DoD PPSM 1.3.5.2.3

98% of the time, required

USTRANSCOM DoD PPSM actions are accomplished by the suspense date established by the government; 100% of

PPSM actions completed in accordance

UNCLASSIFIED

Performance

Objective PWS Para Performance Threshold

Surveillance Method with DoD policy eMASS Entries 1.3.5.2.3 98% of the time, eMASS entries are accurate and complete.

Inspection/Reviews

Accurate and timely production of materials required to obtain AO approval of SIPRNET burn documentation

1.3.5.2.4

No more than 1 late document per quarter and no more than 5 days late.

For final deliverables, no more than two sets of corrections/edits and all corrections must be accomplished within

2 days or other such time periods as mutually determined between the government and the tasked contractor.

All documentation submitted in accordance with timelines established by

AF AO for approvals

Customer/Government

Input

Accurate and timely production of materials required to assess software security posture of

USTRANSCOM

applications and software.

1.3.5.2.5

Content: No more than 1 deviation per month from established principles of secure software engineering

Format: No more than 1 late document per quarter and no more than 5 days late.

For final deliverables, no more than two sets of corrections/edits and all corrections must be accomplished within

2 days or other such time periods as mutually determined between the government and the tasked contractor.

All documentation submitted in accordance with timelines established by

USTRANSCOM authorizing official

(AO) for approvals

Customer/Government

Input

Technical and application support to configure primary and secondary services supporting Web shop managed portals (both development and production); for classified and unclassified networks;

for public and private domains.

1.3.6.3

The contractor shall ensure 96% availability.

APPENDIX B – DISCREPANCY STATUS REPORT

DISCREPANCY STATUS REPORT

MEMORANDUM FOR: USTRANSCOM/TCAQ-DPO

Attn: _______________Contracting Officer

FROM: USTRANSCOM/TCAQ-M

Building 1990, 508 Scott Drive

Scott Air Force Base

IL, 62225

SUBJ: USTRANSCOM/ITSM - HTC711-16-R-D001 (Month)

1. Period Covered: (First to last day of the reporting period, i.e. 1-31 October 2016)

2. Area Covered: (Performance Objective, PWS paragraph, Task Descriptor, i.e. Support Desk, 1.2.1.1.)

3. Overview of Performance:

a. Summary - (Summary of what was done by the COR to assure contract compliance, i.e. audits, data review, and surveillance)

b. Contract Discrepancy Reports (CDRs) - List all CDRs documented during the reporting period.

Provide status of all open CDRs. Attach copies of CDRs to the monthly report.)

c. Corrective Action Follow Up - (Report any follow-up actions performed during the reporting period.)

4. Performance Analysis: (State your analysis of the contractor's performance.) Include positive and negative areas.

5. Areas of Concern: (Identify in narrative form ANY problem(s) or potential problem areas which may impact contract performance to PWS requirements or any aspect of the program.)

6. COR O&M Status: (Indicate current COR listing and their O&M status - Phases I and II; and any information regarding COR changes planned - new personnel requiring training, etc.)

JOHN Q. PUBLIC

Contracting Officer’s Representative (COR)

Attachment:

CDRs