Attch 04 QASP_07012020.docx

QASP

GTS

Quality Assurance Surveillance Plan

For

Gunnery Training Systems (GTS)

Contract #W900KK-D-21-XXXX

01 July 2020

Table of Contents

QUALITY ASSURANCE SURVEILLANCE PLAN

For Gunnery Training Systems (GTS)

OVERVIEW

a. This Quality Assurance Surveillance Plan (QASP) is a Government developed and applied document used to ensure that systematic quality assurance methods are used in the administration of this contract. The QASP will assist the Government in assuring that the Contractor performs in accordance with performance metrics set forth in the contract documents, that the Government receives the quality of supplies and services called for in the contract, and that the Government only pays for the acceptable level of supplies and services received.

b. The QASP is created with the premise that the Contractor is responsible for management and quality control actions to meet the contractual requirements In Accordance With (IAW) the Gunnery Training Systems (GTS) Statements of Work (SOWs), Specifications, and Systems Requirements Documents (SRDs). The QASP details how and when the Government will survey, observe, test, sample, evaluate, and document Contractor performance according to the SOW and Specifications. The role of the Government is quality assurance to ensure contract standards are achieved.

c. The QASP is intended to be a “living document.” The Government may review and revise as circumstances warrant throughout the contract period of performance. However, the Government shall coordinate changes with the Contractor. Updates shall ensure that the QASP remains a valid, useful, and enforceable document. Copies of the original QASP and revisions shall be provided to the Contractor and Government officials implementing surveillance activities.

1.1. Intent. The intent of this QASP is to:

1) Ensure Contractor performance meets or exceeds contract terms, conditions and specifications

2) Hold the Contractor accountable for quality control

3) Encourage the Contractor to take appropriate steps to control and improve quality

4) Ensure all sections of FAR 46 are applied as required and applicable

DESCRIPTION OF SUPPLIES OR SERVICES

2.1. Scope of Work. The contractor shall retrofit, procure, develop, integrate, produce, test, refresh hardware/software, support embedded training, support Risk Management Framework (RMF) certification/ recertification, and upgrade capabilities for the GTS.

2.2. Type of Contract. This will be a single award Indefinite Delivery/Indefinite Quantity (ID/IQ) contract.

ROLES AND RESPONSIBILITIES

The following personnel shall oversee and coordinate surveillance activities.

3.1. Government.

3.1.1. Contracting Officer (KO). The KO is the only person authorized to direct changes in any of the requirements under this contract. In the event the Contractor effects any such change at the direction of any person other than the KO, the change will be considered to have been made without authority, and solely at the risk of the Contractor. No changes in, or deviation from the terms and conditions shall be affected, without a written modification to the contract, executed by the KO authorizing such changes.

3.1.2. Contracting Officer’s Representative (COR). The COR will monitor all technical and performance aspects of the contract, and assist the KO in contract administration. The COR is authorized to perform the following functions:

· Assure that the Contractor performs the technical requirements of the contract

· Perform inspections necessary in connection with contract performance

· Maintain written and oral communications with the Contractor concerning technical and performance aspects of the contract

· Issue written interpretations of technical requirements, including Government drawings, designs, and specifications

· Monitor Contractor's performance and documents and notify both the Contracting Officer and Contractor of all deficiencies

· Coordinate availability of Government furnished property

· Provide site entry for the Contractor

Army Contracting Command (ACC) doesn’t use other acronyms to refer to and describe a COR. Terms such as the “COTR, “Onsite COR”, “TM”, etc. will not be used. Some personnel may be assigned as Alternate CORs (ACORs), but other than a statement to that effect and what actions the KO expects that ACOR to take in the absence of the primary COR, there is no difference between a COR an ACOR, or other government surveillance personnel assigned to conduct contract oversight. Throughout the remainder of this QASP, The term “COR” will be used to refer to all government surveillance personnel assigned to monitor the contractor’s performance on this contract.

A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost, price, or delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

The KO shall use the Department of Defense (DoD) Joint Appointment Module (JAM) to electronically track COR nominations, appointments, terminations, and training certifications for each COR appointed to conduct oversight on this contract. The COR will upload their surveillance documents, such as COR Status Reports (CSR), COR trip reports, correspondence with the contractor, and other miscellaneous documents into the Surveillance and Performance Monitoring (SPM) module within the online contract file. JAM and SPM are available within the Procurement Integrated Enterprise Environment (PIEE) suite of tools at: https://wawf.eb.mil/.

3.1.2.1 Alternate Contracting Officer’s Representative (ACOR). The ACOR is an employee of the U.S. Government provided by the Requiring Activities (RA) and appointed by the KO to provide additional surveillance personnel in monitoring and documenting the contractor’s performance. These alternate surveillance support personnel may serve as on-site representatives of the COR in performance of actual contract surveillance, if they meet all COR training and experience requirements and are appointed by the contracting officer as ACORs in the JAM. This term will apply to other Government surveillance personnel as defined in Army Regulation 70-13, paragraph 2-2 g.

3.1.3. Contract Administrator. The official Government representative delegated authority by the KO to administer a contract. This individual is normally a member of the appropriate Contracting/Procurement career field and advises on all technical contractual matters.

3.1.4. Property Administrator. An authorized representative of the KO appointed in accordance with agency procedures responsible for administering the contract requirements and obligations relating to Government property in possession of a Contractor.

3.2. Contractor.

3.2.1. Contract Manager.

3.2.2. Program Manager. The Contractor responsible for running the program. May supervise the program team and manage conflicts within different departments. Plans and sets program goals and milestones and develops risk management strategies. Defines resources and schedules for the implementation of the program. Clearly defines requirements and sets targets accordingly. Recognizes areas for internal improvement and develops plans for implementing the improvements.

3.2.3. Quality Manager. The Contractor responsible for promoting quality achievement and performance improvement throughout the organization. Develops, implements, communicates and maintains a quality plan to bring the Contractor’s Quality Systems and Policies into compliance with quality system requirements. Directs the activities of Contractor quality personnel to measure key quality characteristics of products and services delivered and processes from inception to completion.

For quick access, the contact information for the performance of this QASP is provided:

Government Personnel:

Contractor Personnel:

Contract Manager

Project Manager

Quality Manager

Table 1; Key Positions for Contract Administration

CONTRACT QUALITY REQUIREMENTS

4.1. Contractor’s Quality Control Plan/Program (QCP). The Government will evaluate the adequacy of the Contractor’s Quality Control Plan (QCP) performance under this contract in accordance with this QASP.

The QCP is the means by which the Contractor assures itself that all work complies with the requirements of the contract SOW. It is essential that Government Surveillance Personnel understand that Quality Control (QC) is the responsibility of the Contractor, and not the Government.

As such, the Government will focus their efforts on validating whether the Contractor is maintaining an adequate quality control inspection system that ensures the Contractor maintains evidence that products and services provided conform to contract quality requirements. The Contractor shall provide inspection data to the Government on request for validation.

The Contractor’s QCP shall include a process that can identify, prevent, and ensure non-recurrence of defective products or services.

4.2. Government Quality Assurance. This QASP describes what the Government will do to ensure that the Contractor has performed in accordance with the performance standards within the SOW.

This QASP describes:

· How the performance standards will be applied:

· The Performance Standard for each requirement in the SOW will be applied as prescribed in the SOW. Ensure that each Performance requirement within the SOW includes a measurable performance standard in terms of quality, timeliness, or quantity.

· Ensure the method of assessing Contractor performance against performance standards is included in this QASP.

· Ensure each Performance Requirement includes an Acceptable Quality Limit (AQL). AQL is the worst tolerable performance that is still considered acceptable.

· Which performance elements will be surveilled (Surveillance Checklist, attachment 3)

· All performance activities will be surveilled throughout the Period of Performance, using a risk-based approach. The selected items will be populated on the Monthly Checklist and placed on the Surveillance Schedule for each period surveilled.

· When the surveillance will be scheduled (Surveillance Schedule, attachment 2)

· Selected items for each month will be placed on the Surveillance Checklist and scheduled surveillance on the Monthly Schedule. Surveillance may be scheduled on a daily, weekly, or monthly frequency. However, each contractor requirement must be audited for compliance prior to invoice payment being made.

· The Acceptable Quality Limit (AQL)

· The AQL will be determined by the RA, i.e., the COR, and referenced in attachment 1, Performance Requirements Summary for each Performance requirement.

· The nature of Government contract quality assurance actions that include the number of observations made and the number and type of defects (defect rate)

· Personnel conducting Contractor performance surveillance will use attachment 3, Surveillance Checklist, or equivalent to answer the Performance question asked, and provide comments in the area provided on the checklist. These comments and metrics from the Checklist will be included on each CSR submitted during the Period of Performance.

GOVERNMENT SURVEILLANCE

5.1. Methods of Surveillance. The following Methods of Surveillance may be utilized in monitoring the Contractors’ performance:

1. 100% Inspection will be reserved for the highest risk areas where consequence of failure may affect life or limb, or there is likelihood of mission failure.

1. Random Sampling will be used when a products or service is performed on a frequent basis and a statistically valid sample can be selected for audit. This is most appropriate method for frequently recurring tasks.

1. Periodic Inspection will be used when planned sampling of a product or service is at a specific predetermined date and time. This is most appropriate for tasks that occur infrequently, yet on a scheduled basis.

1. Customer Feedback is not a valid method of surveillance, but a good indicator of areas where surveillance should be conducted or intensified. Customer Feedback will be obtained via IPTs, program milestone events, and engagement with the LCCS contractor.

5.1.1 Surveillance Procedure:

a. The COR will evaluate the Contractor’s performance monthly against Performance Standards established in the contract. Evaluations will be to the extent practical to assure the Contractor provides quality products or services IAW the requirements of the contract.

b. The COR will utilize the attached checklist(s) to track and document surveillance.

c. The COR will perform evaluations/validation of Contractor supplied performance data.

d. The COR will review the Contractors’ supplied reports and validate 100% of the data accuracy supplied within.

e. All project deliverable milestone dates met. The COR will verify against the schedule and the deliverables received date.

5.2. Surveillance Schedule. (Required) A Surveillance Schedule (Attachment 2) will be created each month. Locally generated equivalent is acceptable. The schedule is “FOR OFFICIAL USE ONLY” and is not releasable to anyone other than authorized Government personnel. Each Month’s Surveillance Schedule will be completed at the beginning of each month during the Period of Performance (PoP) to schedule the upcoming month surveillance activity. Completed Surveillance Schedules will be filed in the online SPM module located within (https://wawf.eb.mil) for this contract, either as an attachment to the CSR or uploaded separately in the Miscellaneous Documents Section.

5.3. Surveillance Checklists. (If Applicable) A Surveillance Checklist (Attachment 3) will be created each month. Locally generated equivalent is acceptable. The Checklist is “FOR OFFICIAL USE ONLY” and is not releasable to anyone other than authorized Government personnel. Each Month’s Surveillance Checklist will be completed with the Surveillance Schedule. Completed Surveillance Checklist will be filed in the online SPM module located within (https://wawf.eb.mil) for this contract, either as an attachment to the CSR or uploaded separately in the Miscellaneous Documents Section.

5.4. Surveillance Documentation. Each months’ Completed Surveillance Documentation, to include the CSR must be filed in the online SPM module located within (https://wawf.eb.mil) for this contract. The CSR (Smart Form) must be utilized, supporting documentation can be uploaded as an attachment.

NON-CONFORMING PERFORMANCE

A non-conformance occurs when the Contractor fails to meet the terms, conditions and/or specifications of the Contract/Task Order. All instances of non-conformance must be documented by the COR. The COR will provide the details of the non-conformance using the Contractor Nonconformance Report (CNR), Attachment 4 to the KO, who will notify the Contractor of each non-conformance occurrence, unless the KO has authorized the COR to submit directly to the contractor, and copy the KO. Resolution of any non-conformance discovered at the subcontractor level will be addressed with the prime Contractor.

Non-conformances are classified as either: Level I (Minor); Level II (Major); or Level III (Critical).

6.1. Level I (Minor). Level I non-conformance is not likely to materially reduce the usability of products or services for their intended purpose or is a departure from established standards having little bearing on completing the contract requirement. Minor non-conformances can usually be corrected on the spot and can be issued to the Contractor through either a verbal or written CNR. However, the Government is required to document verbal Level I CNRs. The COR may issue verbal Level I CNRs directly to the appropriate level of Contractor management. The COR will notify the KO as soon as practical when a verbal Level I CNR is issued and document them in their Monthly Reports. If the non-conformance cannot be corrected on the spot, the Contractor shall be given a suspense date to correct the deficiency. The KO will issue and sign written Level I CNRs, Attachment 4.

6.2. Level II (Major). Level II non-conformance is likely to result in failure of the services to meet contract requirements. Also, repeated discrepancies, a large number of documented Level I CNRs and trends indicating failure of the Contractor’s quality control program can be classified as Level II CNRs. The KO issues all Level II CNRs in writing, Attachment 4. The COR will notify the KO as soon as practical when a major non-conformance is identified.

6.3. Level III (Critical). Level III non-conformances result in hazardous or unsafe conditions due to the manner in which the product or services are performed; prevent or impact a vital agency mission as a result of performance; or are for repeated or uncorrected Level II CNRs. The Contracting Office Director or Deputy Director issues written Level III CNRs. The COR is responsible for notifying the KO immediately upon discovery of a critical non-conformance.

6.4. Documenting CNRs. The COR will provide the details of the non-conformance using the CNR, Attachment 4. If the RA prefers to issue a locally developed CNR, documentation must include as a minimum: the Contract or Task Order number; reference to the specific contract requirement; the specific discrepancy to the requirement; where it was discovered; the date and time it was discovered; Contractor representative who was notified; and the suspense date for Contractor response/corrective action.

6.5. Tracking and Resolving CNRs. All CNRs, verbal and written, regardless of issuer will be included in the COR’s Monthly Report. The COR and KO shall track CNRs to ensure the Contractor identifies and takes appropriate corrective action to the root cause and the specific non-conformance is corrected within the required timeline. The KO will make a final written determination of the Government’s remedies if the non-conformance is not corrected by the Contractor after receiving notice and a reasonable opportunity to correct the work.

DEDUCT PLAN

This acquisition does not include a Deduct Plan.

DATA ANALYSIS

Data Analysis will be performed to identify trends in cost, schedule and/or performance risks. The results of Data Analysis will be documented in CSR and may be used to make adjustments to surveillance schedules and/or checklist items to increase or decrease surveillance, based on performance trends. Negative trends noted using Government data/observations could result in issuing a CNR. Trends noted using Contractor data will not result in a CNR unless the Contractor has not addressed the negative trend. QASP changes based on Data Analysis will be coordinated with the KO for approval.

ACCEPTANCE OF PRODUCTS OR SERVICES

When all products or services have been deemed acceptable and there is documented, objective, quality evidence to support acceptable performance, the COR will accept the product or services provided and authorize payment to the Contractor. Acceptance and payment will be made by approving the Contractor’s Receiving Reports in Wide Area Workflow at https://wawf.eb.mil/ as an iRAPT Inspector, and/or Acceptor.

COR STATUS REPORT

CSRs will be submitted on a monthly basis to the KO via the SPM module. CSRs must be uploaded into the SPM module using the “Smart Form”. CSRs will be due NLT the 10th day of the month following the month of surveillance. CSRs will provide a synopsis of the Contractors’ performance for the inclusive dates of the report. The synopsis must contain a summary of surveillances performed, Customer Feedback if any, CNRs if any, an analysis of the Contractors’ performance, recommended adjustments to surveillance schedules, any other pertinent contract information IAW FAR 46.104, and the COR Appointment Letter. Completed Surveillance Checklists and CNRs, if any, will be included as attachments to the CSRs. See para 5.4.

CONTRACTOR MANPOWER REPORTING APPLICATION (CMRA)

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report all Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor shall completely fill in all the information in the format using the following web address: https://www.ecmra.mil.

The required information includes the following:

a. Contracting Officer (KO), Contracting Officer’s Representative (COR) name;

b. Contract number, including task and delivery order number;

c. Beginning and ending dates covered by reporting period;

d. Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data;

e. Estimated direct labor hours (including subcontractors);

f. Estimated direct labor dollars paid this reporting period (including subcontractors);

g. Total payments (including subcontractors);

h. Predominant Federal Service Code (FSC) reflecting product or services provided by Contractor (and separate predominant FSC for each subcontractor if different);

i. Estimated data collection cost;

j. Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information);

k. Locations where the Contractor and subcontractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

l. Presence of deployment or contingency contract language; and number of Contractor and subcontractor employees deployed in theater this reporting period (by country).

While inputs may be reported any time during the Fiscal Year, the COR shall ensure the Contractor submits all data shall no later than October 31 of each calendar year. The COR shall verify that the Contactor has complied with the required Contractor manpower reporting annually and document the results in the COR’s online SPM module, CMRA section. KOs shall ensure that the requirement to report Contractor manpower is included in all contracts where there is a defined requirement for services, task/delivery orders and modifications.

CONTRACTOR PERFORMANCE ASSESSMENT REPORTING SYSTEM (CPARS)

Documented surveillance data (CSRs, Completed Surveillance Checklists, Customer Feedback and CNRs, if any) will be used to support CPARS ratings. CPARS will be completed in accordance with AFARS, Subpart 5142.15 – Contractor Performance Information.

COMBATING TRAFFICKING IN PERSONS (CTIP)

In accordance with PGI 222.17 and FAR 52.222-50, the KO will be notified immediately of any information from any source that alleges a Contractor employee, subcontractor and/or subcontractor employee has engaged in conduct that violates the United States Government zero tolerance policy regarding trafficking in persons.

COR/QUALITY ASSURANCE SURVEILLANCE FILES

The official COR/Quality Assurance Surveillance Files will be maintained in the online JAM and SPM module IAW DoDI 5000.72, and DFARS PGI 201.602-2.

QASP CHANGES

This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications by the KO, etc. The COR will send any recommended changes to the KO for approval and the KO must approve all changes.

DOCUMENT REVISION HISTORY

This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

1.0

Scott Turner

Attachments:

1. Performance Requirements Summary (PRS)

2. Surveillance Schedule DA Form 5475 (Optional)

3. Surveillance Checklist DA Form 5476 (Optional)

4. Contractor Nonconformance Report (CNR) DA Form 5479

Attachment 1

PERFORMANCE REQUIREMENTS SUMMARY

Acceptable Quality Level (AQL) Performance standard ratings are outlined in Table 1-1. Performance standards define desired outcomes. The Government performs quality assurance surveillance to determine if the Contractor exceeds, meets or does not meet these standards.

The following surveillance methods may be used by the COR in the administration of this QASP. Regardless of the surveillance method, the Assistant Program Managers shall contact the Contractor’s program manager when a defect is identified and inform the manager of the specifics of the problem. The COR is responsible for monitoring the Contractor’s performance in correcting the problem.

The Statement of Work for the GTS contract delineates the tasks required by the Government. These tasks shall be subject to the following performance standards listed in the table below (Table 1-1).

Table 1-1 Performance Standards, Tasks and Methods of Quality Assurance

Standard

Surveillance Frequency

Application of appropriate metrics and life cycle management processes to maintain conformance of evolving products with contract. GFE/GFI is tracked, maintained and secured.

3.5 Integrated Testing

3.1.15.3, 3.1.15.4, 3.1.15.6, 3.1.15.7, 3.1.15.9, 3.2.5.6, 3.8 Antiterrorist / OPSEC Security/TARP/IA/CS/AT Awareness for Overseas travel, and Common Access Card

METHODS OF QUALITY ASSURANCE SURVEILLANCE

Various methods exist to monitor performance. The COR shall use the surveillance methods listed below to populate the Methods of Surveillance column of Table 1-1 in the administration of this QASP.

Regardless of the surveillance method, the COR shall always contact the Contractor's task manager or on-site representative when a defect is identified and inform the manager of the specifics of the problem. The COR, with assistance from the Contract Specialist, shall be responsible for monitoring the Contractor’s performance in meeting a specific performance standard/AQL.

a. Direct Observation. (Can be performed periodically or through 100% surveillance.)

b. Management Information Systems (MIS). (Evaluates outputs through the use of management information reports. Best used for general surveillance and may need to be supplemented by periodic inspections.)

c. Periodic Inspection. (Uses a comprehensive evaluation of selected outputs. Inspections will be as required.)

d. Progress or status meetings.

e. Analysis of Contractor's progress reports. (Evaluate cost, schedule, etc.)

f. Performance reporting. (Evaluate metrics for a specific time period. Develop metrics or use metrics found in MIS.)

RATINGS

Metrics and methods are designed to determine if performance exceeds, meets, or does not meet a given standard and acceptable quality level. A rating scale shall be used to determine a positive, neutral, or negative outcome.

Surveillance results may be used as the basis for actions (to include payment deductions) against the Contractor. In such cases, the Inspection of Services clause in the Contract becomes the basis for the KO’s actions. Additionally, surveillance results may be used to prepare Performance Assessment Reports through the Contract Performance Assessment Reporting System (CPARS).

AQL Ratings will be documented using the Department of Defense standard colors for Performance Assessments. The standard colors, with their definitions, are as detailed in Table 1-2:

Table 1-2 AQL Performance Standard Ratings

DOCUMENTING PERFORMANCE

a. Acceptable Performance. The Government shall document positive performance. Any report may become a part of the supporting documentation for fixed fee payments or other actions. Additionally, surveillance results may be used to prepare Performance Assessment Reports in CPARS.

b. Unacceptable Performance. When unacceptable performance occurs, the COR shall inform the Contracting Officer and the Contractor. This will normally be in writing unless circumstances necessitate verbal communication. In any case the COR shall document the discussion and place it in the COR file.

The Contractor shall acknowledge receipt of the issue in writing. If necessary, the Contractor is required to prepare a corrective action plan to document how the Contractor shall correct the unacceptable performance and avoid a recurrence. The Government will also state how long after receipt the Contractor has to present this corrective action plan to the COR and Contracting Officer. The Government shall review the Contractor's corrective action plan to determine acceptability.

Any documentation detailing unacceptable performance may become a part of the supporting documentation for contract payment deductions, fixed fee deductions, award fee nonpayment, or other actions deemed necessary by the KO. Additionally, surveillance results may be used to prepare Performance Assessment Reports in CPARS.

FREQUENCY OF MEASUREMENT

a. Frequency of Measurement. During contract/order performance, the COR shall take periodic measurements as specified in the AQL column of the Performance Standards Summary Matrix, and shall analyze whether the negotiated frequency of measurement is appropriate for the work being performed.

b. Frequency of Performance Assessment Meetings. At a minimum, the COR shall meet with the Contractor on a bi-weekly basis via teleconference sessions and quarterly at the Contractor’s facility to assess performance and shall provide a written assessment.

Attachment 2

SURVEILLANCE SCHEDULE

Attachment 3

SURVEILLANCE CHECKLIST(S)

COR SURVEILLANCE CHECKLIST Template

COR Name:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments summary, to include, positive trends, negative trends, concerns, customer comments, and any additional COR comments:

To populate the checklist, find in the SOW: "The Contractor Shall...”, Then, make that requirement a checklist item by converting the requirement to a question: “Did the contractor…" Each "Yes" can be graded as a 1, and each NO graded as a 0. Once the checklist is complete, the COR may generate a quantifiable performance rating using these numbers as metrics.

Attachment 4

CONTRACTOR NONCONFORMANCE REPORT

image1.emf image2.emf image3.emf

DATE

COR/QAE SURVEILLANCE SCHEDULE

For use of this form, see DA PAM 5-20; the proponent agency is ACSIM.

When completed stamp "FOR OFFICIAL USE ONLY"

DA FORM 5475, MAR 2008 APD PE v1.00

SERVICE

PREVIOUS EDITIONS ARE OBSOLETE.

image4.emf

DA FORM 5475_Surveillance Sechedule.pdf

DATECOR/QAE SURVEILLANCE SCHEDULE

When completed stamp "FOR OFFICIAL USE ONLY"

DA FORM 5475, MAR 2008 APD LC v1.00

SERVICE

COR/QAE SURVEILLANCE SCHEDULE

For use of this form, see DA PAM 5-20; the proponent agency is ACSIM.

When completed stamp "FOR OFFICIAL USE ONLY"

DA FORM 5475, MAR 2008

APD LC v1.00

DATE

PREVIOUS EDITIONS ARE OBSOLETE.

SERVICE

1.00

DA FORM 5475-R, NOV 1985

COR/QAE SURVEILLANCE SCHEDULE

APD

DATE:

SERV_A:

DATE_A:

SERV_A_1:

DATE_A_1:

SERV_A_2:

DATE_A_2:

SERV_A_3:

DATE_A_3:

SERV_A_4:

DATE_A_4:

SERV_A_5:

DATE_A_5:

SERV_A_6:

DATE_A_6:

SERV_A_7:

DATE_A_7:

SERV_A_8:

DATE_A_8:

SERV_A_9:

DATE_A_9:

SERV_A_10:

DATE_A_10:

SERV_B:

DATE_B:

SERV_B_1:

DATE_B_1:

SERV_B_2:

DATE_B_2:

SERV_B_3:

DATE_B_3:

SERV_B_4:

DATE_B_4:

SERV_B_5:

DATE_B_5:

SERV_B_6:

DATE_B_6:

SERV_B_7:

DATE_B_7:

SERV_B_8:

DATE_B_8:

SERV_B_9:

DATE_B_9:

SERV_B_10:

DATE_B_10:

SERV_B_11:

DATE_B_11:

SERV_C:

DATE_C:

SERV_C_1:

DATE_C_1:

SERV_C_2:

DATE_C_2:

SERV_C_3:

DATE_C_3:

SERV_C_4:

DATE_C_4:

SERV_C_5:

DATE_C_5:

SERV_C_6:

DATE_C_6:

SERV_C_7:

DATE_C_7:

SERV_C_8:

DATE_C_8:

SERV_C_9:

DATE_C_9:

SERV_C_10:

DATE_C_10:

SERV_C_11:

DATE_C_11:

SERV_D:

DATE_D:

SERV_D_1:

DATE_D_1:

SERV_D_2:

DATE_D_2:

SERV_D_3:

DATE_D_3:

SERV_D_4:

DATE_D_4:

SERV_D_5:

DATE_D_5:

SERV_D_6:

DATE_D_6:

SERV_D_7:

DATE_D_7:

SERV_D_8:

DATE_D_8:

SERV_D_9:

DATE_D_9:

SERV_D_10:

DATE_D_10:

SERV_D_11:

DATE_D_11:

SERV_E:

DATE_E:

SERV_E_1:

DATE_E_1:

SERV_E_2:

DATE_E_2:

SERV_E_3:

DATE_E_3:

SERV_E_4:

DATE_E_4:

SERV_E_5:

DATE_E_5:

SERV_E_6:

DATE_E_6:

SERV_E_7:

DATE_E_7:

SERV_E_8:

DATE_E_8:

SERV_E_9:

DATE_E_9:

SERV_E_10:

DATE_E_10:

SERV_E_11:

DATE_E_11:

SERV_F:

DATE_F:

SERV_F_1:

DATE_F_1:

SERV_F_2:

DATE_F_2:

SERV_F_3:

DATE_F_3:

SERV_F_4:

DATE_F_4:

SERV_F_5:

DATE_F_5:

SERV_F_6:

DATE_F_6:

SERV_F_7:

DATE_F_7:

SERV_F_8:

DATE_F_8:

SERV_F_9:

DATE_F_9:

SERV_F_10:

DATE_F_10:

SERV_F_11:

DATE_F_11:

SERV_G:

DATE_G:

SERV_G_1:

DATE_G_1:

SERV_G_2:

DATE_G_2:

SERV_G_3:

DATE_G_3:

SERV_G_4:

DATE_G_4:

SERV_G_5:

DATE_G_5:

SERV_G_6:

DATE_G_6:

SERV_G_7:

DATE_G_7:

SERV_G_8:

DATE_G_8:

SERV_G_9:

DATE_G_9:

SERV_G_10:

DATE_G_10:

SERV_G_11:

DATE_G_11:

SERV_H:

DATE_H:

SERV_H_1:

DATE_H_1:

SERV_H_2:

DATE_H_2:

SERV_H_3:

DATE_H_3:

SERV_H_4:

DATE_H_4:

SERV_H_5:

DATE_H_5:

SERV_H_6:

DATE_H_6:

SERV_H_7:

DATE_H_7:

SERV_H_8:

DATE_H_8:

SERV_H_9:

DATE_H_9:

SERV_H_10:

DATE_H_10:

SERV_H_11:

DATE_H_11:

image5.emf

DA FORM 5476_Surveillance Checklist.pdf

CONTRACT

REQUIREMENT

PARAGRAPH

NUMBER

METHOD OF

SURVEILLANCE

ACCOMPLISHED

WHERE

ACCOMPLISHED

COMPLIANCE

SURVEILLANCE ACTIVITY CHECKLIST

DA FORM 5476, MAR 2008 APD LC v1.00PREVIOUS EDITIONS ARE OBSOLETE.

REQUIREMENT

CONTRACT

PARAGRAPH

NUMBER

METHOD OF

SURVEILLANCE

DATE

ACCOMPLISHED

WHERE

ACCOMPLISHED

COMPLIANCE

SURVEILLANCE ACTIVITY CHECKLIST

For use of this form, see DA PAM 5-20; the proponent agency is ACSIM.

DA FORM 5476, MAR 2008

APD LC v1.00

PREVIOUS EDITIONS ARE OBSOLETE.

1.00

DA FORM 5476-R, NOV 1985

SURVEILLANCE ACTIVITY CHECKLIST

APD

DATE:

CONT_REQ:

CONT_REQ_1:

CONT_REQ_2:

CONT_REQ_3:

CONT_REQ_4:

CONT_REQ_5:

CONT_REQ_6:

CONT_REQ_7:

CONT_REQ_8:

CONT_REQ_9:

CONT_REQ_10:

PARA_NO:

PARA_NO_1:

PARA_NO_2:

PARA_NO_3:

PARA_NO_4:

PARA_NO_5:

PARA_NO_6:

PARA_NO_7:

PARA_NO_8:

PARA_NO_9:

PARA_NO_10:

METHOD:

METHOD_1:

METHOD_2:

METHOD_3:

METHOD_4:

METHOD_5:

METHOD_6:

METHOD_7:

METHOD_8:

METHOD_9:

METHOD_10:

DATE_ACC:

DATE_ACC_1:

DATE_ACC_2:

DATE_ACC_3:

DATE_ACC_4:

DATE_ACC_5:

DATE_ACC_6:

DATE_ACC_7:

DATE_ACC_8:

DATE_ACC_9:

DATE_ACC_10:

WHERE:

WHERE_1:

WHERE_2:

WHERE_3:

WHERE_4:

WHERE_5:

WHERE_6:

WHERE_7:

WHERE_8:

WHERE_9:

WHERE_10:

COMPLY:

COMPLY_1:

COMPLY_2:

COMPLY_3:

COMPLY_4:

COMPLY_5:

COMPLY_6:

COMPLY_7:

COMPLY_8:

COMPLY_9:

COMPLY_10:

image6.png image7.emf

DA FORM 5479_Contractor Nonconformance Report.pdf

6.

2. 3.

PREPARED ORAL NOTIFICATION RETURNED BY CONTRACTOR ACTION COMPLETE

4. DISCREPANCY OR PROBLEM (Describe in Detail: Include reference in PWS / Directive: Attach continuation sheet if necessary.)

5. SIGNATURE OF CONTRACTING OFFICER

7.

8. CONTRACTOR RESPONSE AS TO CAUSE, CORRECTIVE ACTION AND ACTIONS TO PREVENT RECURRENCE. ATTACH

1. CONTRACT NUMBER

9. SIGNATURE OF CONTRACTOR REPRESENTATIVE 10. DATE

11. GOVERNMENT EVALUATION (Acceptance, partial acceptance, rejection: attach continuation sheet if necessary)

12. GOVERNMENT ACTIONS (Payment deduction, cure notice, show cause, other.)

CONTRACT DISCREPANCY REPORT

TO: (Contractor and Manager Name)

DATES

CLOSE OUT

CONTRACTOR

NOTIFIED

NAME AND TITLE SIGNATURE DATE

QAE

CONTRACTING

OFFICER

CONTINUATION SHEET IF NECESSARY. (Cite applicable Q.A. program procedures or new A.W. procedures.)

DA FORM 5479, MAR 2008 APD LC v1.01ES

FROM: (Name of QAE)

TO: (Contracting Officer) FROM: (Contractor)

6.

2.

3.

PREPARED

ORAL NOTIFICATION

RETURNED BY CONTRACTOR

ACTION COMPLETE

4. DISCREPANCY OR PROBLEM

(Describe in Detail: Include reference in PWS / Directive: Attach continuation sheet if necessary.)

5. SIGNATURE OF CONTRACTING OFFICER

7.

8. CONTRACTOR RESPONSE AS TO CAUSE, CORRECTIVE ACTION AND ACTIONS TO PREVENT RECURRENCE. ATTACH

1. CONTRACT NUMBER

9. SIGNATURE OF CONTRACTOR REPRESENTATIVE

10. DATE

11. GOVERNMENT EVALUATION

(Acceptance, partial acceptance, rejection: attach continuation sheet if necessary)

12. GOVERNMENT ACTIONS

(Payment deduction, cure notice, show cause, other.)

CONTRACT DISCREPANCY REPORT

For use of this form, see DA PAM 5-20; the proponent agency is ACSIM.

TO:

(Contractor and Manager Name)

DATES

CLOSE OUT

CONTRACTOR

NOTIFIED

NAME AND TITLE

SIGNATURE

DATE

QAE

CONTRACTING

OFFICER

CONTINUATION SHEET IF NECESSARY.

(Cite applicable Q.A. program procedures or new A.W. procedures.)

DA FORM 5479, MAR 2008

APD LC v1.01ES

FROM:

(Name of QAE)

TO:

(Contracting Officer)

FROM:

(Contractor)

PREVIOUS EDITIONS ARE OBSOLETE.

1.01

DA FORM 5479, MAR 2008

CONTRACT DISCREPANCY REPORT

APD

CONTRACT:

TO_A:

FROM_A:

PREPARED:

ORALNOTE:

RETURN:

ACTION:

PROBLEM:

SIGN_A:

signature_BUTTON1:

TO_B:

FROM_B:

CONTRACTR:

SIGN_B:

signature_BUTTON2:

DATE_A:

GOVERNMNT:

GOVMTACTN:

NAME_A:

signature_BUTTON3:

SIGN_C:

DATE_B:

NAME_B:

signature_BUTTON4:

SIGN_D:

DATE_C:

NAME_C:

signature_BUTTON5:

SIGN_E:

DATE_D: