Attachment_0002_QASP_10_March_2017.doc

DOC document 94 KB Posted

Attached to
Logistics Automation (LOGAUTIO) Services
Solicitation number
W52P1J-16-R-0050
Issued by

View the file

Other files

File Type Posted
W52P1J16R0050-0005.pdf PDF
Attachment_0016_QA_Matrix_20170510.xlsx XLSX spreadsheet
W52P1J16R0050-0004.pdf PDF
Attachment_0016_QA_Matrix_20170509.xlsx XLSX spreadsheet
Attachment_0016_QA_Matrix_2017428.xlsx XLSX spreadsheet
W52P1J16R0050-0003.pdf PDF
W52P1J16R0050-0001.pdf PDF
Attachment_0016_QA_Matrix_20170420.xlsx XLSX spreadsheet
Attachment_0001_LOGAUTO_PWS_20170420.docx DOCX document
Attachment_0003-_SECTION_L_PROPOSAL_INSTRUCTIONS_20170420.docx DOCX document
Attachment_0001_LOGAUTO_PWS.pdf PDF
Exhibit_C_ASG-KU_DES_Form_190-16.01Enclosures_1A-2-3-4-6-7-8.pdf PDF
Attachments_0009_-_0015_Portfolio_(LOGAUTO).pdf PDF
Exhibit_H_CDRL_PORTFOLIO.pdf PDF
Exhibit_F_ASG-KU_DES_FORM_190-16.05_Enclosure_10.xlsx XLSX spreadsheet
Exhibit_D_ASG-KU_DES_Form_190-16.01_Enclosure_1.xlsx XLSX spreadsheet
Attachment_0007_GFE_List.xlsx XLSX spreadsheet
Attachment_0003-_SECTION_L_PROPOSAL_INSTRUCTIONS_10_March_2017.pdf PDF
W52P1J16R0050_20170407.pdf PDF
Attachment_0008_-_Additional_Performance_Directives_10_March_2017.pdf PDF
Exhibit_E_ASG-KU_DES_Form_190-16.02_Enclosure_9.xlsx XLSX spreadsheet
Attachment_0005_DD254_LOGAUTO.pdf PDF
Exhibit_B_ASG-KU_DES_Form_190-16.01_IA_Application.xlsx XLSX spreadsheet
Attachment_0016_QA_Matrix.xlsx XLSX spreadsheet
Exhibit_A_Contract_Data_Requirements_List_Matrix.xlsx XLSX spreadsheet
Attachment_0004_-_SECTION_M_EVALUATIONS_OF_PROPOSALS_10_March_2017.pdf PDF
Attachment_0006_-_LOGAUTO_Cost-Price_Matrix.xlsx XLSX spreadsheet
Exhibit_G_ASG-KU_DES_Form_190-16.04_Enclosure_11.doc DOC document
Show all 28

On GovTribe

Work with this file

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

Text version

Attachment 0002

QUALITY ASSURANCE SURVEILLANCE PLAN

FOR: Contractor TBD

1.0 INTRODUCTION

1.1. Purpose. This Quality Assurance Surveillance Plan (QASP) has been developed to identify the methods and procedures the Government will use to evaluate contractor performance while concurrently determining the contractor is meeting the mission essential elements of the Performance Work Statement (PWS). It is designed to provide an effective surveillance method by monitoring contractor performance for each listed performance objective in the Performance Requirements Summary (See Section 7).

1.1.1. This QASP provides a systematic method to evaluate the services the contractor is required to perform as specified in the PWS and the contract proposal.

1.1.2. This QASP was developed by the 316th ESC, Logistics Automation Branch. It was designed to provide direction to personnel performing contractor surveillance activities. Personnel surveying the contract terms and conditions and PWS requirements will periodically review the QASP throughout the life of the contract.

2.0. ROLES AND RESPONSIBILITIES.

2.1. Government. The role of the Government in quality assurance is to ensure the contractor is performing in accordance with the contract requirements and contract standards are achieved.

2.2. Contracting Officer (KO). The KO is responsible for safeguarding the interests of the United States Government in contractual relationships. Only the KO is authorized to bind the Government and then, only to the extent of the authority entrusted to them through the issuance of a warrant.

2.2.1. The KO designates authority for inspection and/or acceptance responsibilities to the COR, or delegates authority to another certified acquisition professional in accordance with the Federal Acquisition Regulation & Defense (FAR/DFARS). This documented authority allows the COR or other certified acquisition professionals to act on the KO’s behalf.

2.2.2. The KO informs the contractor of the names, duties, and limitations of authority for all quality assurance personnel assigned to the contract.

2.3. Contracting Officer Representative. The COR when designated:

i. develops and creates the QASP

ii. serves as the eyes and ears for the KO at the contractor’s site

iii. monitors contractor performance to ensure contract requirements are met for: Performance, Cost, and Schedule

iv. ensures that contract quality requirements, provisions, standards, and thresholds are defined, practical, enforceable, necessary, and verifiable.

v. evaluates and documents contractor performance in accordance with this QASP and the PWS.

vi. notifies the KO of any significant performance deficiencies using a Contractor Discrepancy Report with supporting documentation.

vii. maintains surveillance documentation.

viii. recommends improvements to the QASP and PWS throughout the life of the contract.

3.0. DESCRIPTION OF SERVICES

3.1. Scope of Work. The scope of this contract is to provide customer assistance for the Army’s Logistics Information Systems, including software, functional, technical, communications and limited hardware. Also, this contract provides training to unit personnel and staff assistance on the use and implementation of TLS platforms throughout the command. 1st TSC requires contracted support to augment the automated logistical infrastructure and military personnel within the Theater. This requirement is critical for efficient support to Operation Enduring Freedom.

4.0. QUALITY REQUIREMENTS

4.1.

Quality Control Program. The contractor, not the Government, is responsible for management and quality control actions to meet the terms of the contract. Details of these controls will be documented (when required) in the contractor’s Quality Control Program document.

5.0 SURVEILLANCE. The COR will perform monthly surveillance based on the quality and effectiveness of the contractor’s data deliverables as well as the services provided. Regardless of the surveillance method, the COR shall always contact the contractor's quality manager or on-site representative when a defect is identified and inform the manager of the specifics of the problem. The COR, when designated, shall be responsible for monitoring the contractor’s performance in meeting a specific performance standard/acceptable quality level (AQL).

5.1 Unacceptable Performance. If the number of complaints/defects exceeds the performance threshold for any objective, the COR will determine the possible cause of this unacceptable performance. Government-caused complaints/defects will not be counted against the contractor. The same applies to any other requirement of the contract when Government-caused complaints/defects are the cause of unacceptable contractor performance. If the contractor’s performance is judged unacceptable for any requirement by the COR, the COR will document the discrepancy as a non-conformance and inform the KO (if needed) for resolution. Significant (major non-conformance) performance deficiencies must be submitted to the KO using a Contractor Discrepancy Report and include supporting documentation.

6.0

DOCUMENTATION REQUIREMENTS.

6.1 Monthly Reports in the Contracting Officer Representative Tracking (CORT) Tool

6.2 First Article / Test / Progress or Procedure Reports - as required (monthly, quarterly, etc.)

6.3 Contract Data Requirements List (CDRL) documents - as required

6.4 Discrepancy Reports - as required

7.0

PERFORMANCE REQUIREMENTS SUMMARY (PRS)

7.1 Overview. The PRS details and identifies the contractor requirements by performance objectives that relate directly to mission essential elements from the PWS. The performance threshold describes the minimum acceptable levels of service required for each contractor requirement. These thresholds define minimum acceptance standards critical to mission success. Various methods of surveillance exist to monitor performance; see note 2 below.

7.2 Performance Evaluation. Performance of a service will be evaluated to determine whether or not it meets the performance threshold. Revising and resubmitting the documentation at no cost to the Government is the preferred method for correcting unacceptable performance. The contractor shall provide the Government a written response as to why the performance threshold was not met, how performance will be returned to acceptable levels, and how recurrence of the cause will be prevented in the future.

7.3 Performance Objectives, Indicators, Thresholds, and Surveillance Methods. The services required by the contractor are summarized into performance objectives and indicators, along with the minimum standards that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of quality or service required for each requirement. These thresholds are critical to mission success.

PERFORMANCE REQUIREMENTS SUMMARY

Performance Objective / PWS Reference Para
Performance Indicator
Standard
Performance Threshold
Method of Surveillance
Remedy

PWS Para:

4.0 – 4.9.5

All contract employees will produce staff products (Papers, Reports, Briefings, Plans, Orders, SOPs) and attend Command and Staff Conferences and Meetings
Determine all suspense's were met and quality documentation is maintained.

Random visual inspection.

Conducted monthly IAW COR surveillance schedule.

Nonconformance report issued to contractor.

PWS Para: 4.3.2.1
(IA) Vendor Patches and Anti-virus Software Deployments
Determine compliance no later than 30 days after PEO EIS release.
95% NLT 30 days after PEO EIS release
Customer complaints
Nonconformance report issued to contractor

PWS Para:

4.3.2.2

(IA) Network Architecture Teleconferences
Determine participation; weekly

Random telephonic inspection.

Nonconformance report issued to contractor

PWS Para:

4.3.2.3

(IA) SharePoint Postings of IA Teleconference Minutes
Determine weekly posting.

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.3.2.4

(IA) Theater Standard Network Architecture Smart book
Determine it was updated NLT 5th each month

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.3.2.5

(IA) Network Architecture Diagrams SharePoint Postings
Determine it was updated NLT 5th of each month

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.3.3.1

(IA) Comprehensive Database for all VSATs
Determine it was updated weekly

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.5.1.2/3/4

TLS Trend Reporting, System Outage, Corrective Actions
Determine it was posted NLT 5th each month

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.5.3.1

TLS (CONOPS) SCP/ICP Test & Deployment Plan
Determine it was posted 7 days after SCP/ICP release

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.5.3.2

TLS SCP/ICP CONOPS Testing
Ensure that testing was completed within 14 days of PEO EIS release date

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.5.3.6

Produce TLS Messages, Plans, and Execution Orders
Ensure completion as required

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.5.4

TLS Customer Assistance Visits Schedule
Ensure completion 60 days from start of Performance; the 90th day thereafter

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.5.5

Training Materiel & Services
Ensure completion as required

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.6.1

Publish Command Guidance on Property Accountability and Supply Procedures
Ensure completion 60 days after start of Performance; update as required

Visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.6.1.1

Publish Property Accountability SOP
Ensure completion 60 days after contract award; update as required

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.6.2

Property Accountability Baseline Listing
Ensure completion 30 days after contract award; 5th each month
Acceptable Quality Level = 100%
Visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.6.3

Property Accountability Customer Hand Receipt(s)
Ensure that it is updated quarterly; returned by 10th of the month

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.6.5

Property Accountability Units Clearing AOR Spreadsheet
Ensure completion 30 days after contract award; updated monthly

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.6.9.1

Property Accountability Reconciliations with FRA
Weekly

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.9.1

Training After-Action Reviews
Within 3 calendar days after completion of training / event
Acceptable Quantity of Student AAR's = 50% of students / users
Visual Review of email submitted with attached AARs.

Nonconformance report issued to contractor

PWS Para:

4.9.3

Conduct TLS Gunneries at Camp Buehring
As required

Random visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.9.4

TLS TTPs
As required; NLT 5th of each month

Visual inspection.

Nonconformance report issued to contractor

PWS Para:

4.9.5

TLS Training POIs (Initial)
NLT 60 days after contract award

Visual inspection.

Nonconformance report issued to contractor

Note 1. The evaluation ratings are as follows:

a. Very Good - Performance meets contractual requirements and exceeds some to the Government’s benefit. The contractual performance of the task and sub-task being assessed was accomplished with some minor problems for which corrective actions taken by the contractor were effective.

b. Satisfactory - Performance meets contractual requirements. The contractual performance of the task and sub-task contain some minor problems for which corrective actions taken by the contractor appear or were satisfactory.

c. Marginal - Performance does not meet some contractual requirements. The contractual performance of the task and sub-task being assessed reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented.

d. Unsatisfactory – Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance of the task or sub-task contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

Note 2. Surveillance methods

The COR must use at least 1 of the surveillance methods listed above in the administration of this QASP.

a. PLANNED - DIRECT OBSERVATION. (Can be performed periodically or through 100% surveillance.)

b. PERIODIC INSPECTION. (Uses a comprehensive evaluation of selected outputs. Inspections may be scheduled [Daily, Weekly, Monthly, Quarterly, or annually] or unscheduled, as required.)

c. PERIODIC SAMPLING. (Variation of random sampling. However, sample is only taken when a deficiency is suspected. Good follow-up to MIS analysis. Sample results are applicable only for the specific work inspected. Since sample is not entirely random, it cannot be applied to total activity performance.)

d. RANDOM SAMPLING. (Designed to evaluate the outputs of the award requirement by randomly selecting and inspecting a statistically significant sample. Highly recommended for large quantity repetitive activities with objective and measurable quality attributes.)

e. CUSTOMER COMPLAINTS. (Relies on the user of the service to identify deficiencies. Complaints are then investigated and validated. Highly applicable to services provided in quantity and where quality is highly subjective.)

f. 100% INSPECTION. (Evaluates all outputs. Most applicable to small quantity, but highly important services. May be used where there are written deliverables and stringent requirements such as tasks required by law, safety, or security.)

Note 3. Performance Threshold ratings are as follows:

The contractor (PM) will be evaluated on each performance measure using the following scale:

a. EXCEPTIONAL (5) = No problems or delays in achieving contract requirements.

b. VERY GOOD (4) = Does not impact achievement of contract requirements.

c. SAT (3) = Requires minor agency resources to ensure achievement of contract requirements

d. MARGINAL (2) = Requires major agency resources to ensure achievement of contract requirements.

e. UNSATISFACTORY (1) = Achievement of contract requirements is compromised.

f. N/A (None) = Not Applicable or do not know.

CDRL

TYPE OF REPORTS
PARA
DURATION
COMPLIANCE
COMMENTS
1
Transition Project Plan
4.2.1
Within 5 days after contract award
2
Quality Assurance Surveillance and Evaluation
4.2.2
Format within 30 days of start of PWS; Submit by 5th of each month
3
Management Plan
4.2.3
Within 30 days start of PWS
4
Status Report (Quality Control Plan)
4.2.4
NLT 10th each month
5
(IA) Compliance and Trend Analysis Reports
4.3.2
Bi-weekly
6
TLS Maintenance Handling Report
4.4.4
NLT 5th each month
95%
7
TLS Rebuild Report Process Plan/SOP
4.4.5
NLT 30 days after start of PWS; update as needed
8
Trend Reporting
4.5.1.2/3/4
9
TLS SCP/ICP CONOPS Report
4.5.3.4.3
3 days after testing completed
10
Property Accountability TPE Location Report
4.6.2.3
5th day of subsequent month
11
Project Status Report
4.7.3
5th each month
12
Class No-Show Report
4.9.1
Last day of class

Note(s): Quarterly=NLT the last day of the following months: Dec, Mar, Jun, Sep.

Solicitation W52P1J-16-R-0050 14 March 2017

File details come from the government source that posted it. Updated .