Attachment_4 _QASP_JBSA-Lackland_Bus_Services.pdf

Attachment #4, QASP, dated 13 March 2015

JOINT BASE SAN ANTONIO

LACKLAND BUS SERVICES

QUALITY ASSURANCE

SURVEILLANCE PLAN (QASP)

This document is for the use of the 502 Logistics Readiness Squadron Contract Officer Representatives and 502 Contracting Squadron.

Date Approved: 13 March 2015

1. OBJECTIVE. This Quality Assurance Surveillance Plan (QASP) will be used by the Contracting Officer’s Representative (COR) to evaluate and document the Contractor’s performance. The Contractor shall provide contract support originating out of Joint Base San Antonio (JBSA) - Lackland, San Antonio, Texas. This contract will provide on-site support of AETC’s mission by providing all directed JBSA student transportation needs not to exceed (NTE) 125 miles from JBSA - Lackland. In providing this support, the Contractor shall interface with relevant members of the JBSA community. Relevant members include but are not limited to: 502 LRS/LGRDO office and 502 CONS.

2. GOALS OF THE MULTI-FUNCTIONAL TEAM (MFT). The purpose of the multi-functional team is to create an environment that shapes and executes an acquisition.

The emphasis is on teamwork, trust, common sense and agility. The goal is to obtain efficiencies, improved performance, and cost savings throughout the acquisition life cycle.

3. MULTI-FUNCTIONAL TEAM MEMBERS & THEIR RESPONSIBILITIES.

The MFT is composed of stakeholders in the acquisition. These stakeholders are responsible for the acquisition throughout the life of the requirement. See QASP signature page for MFT membership.

3.1. Contract Officer Representative (COR): is responsible for monitoring, assessing, recording and reporting on Contractor compliance with the terms and conditions of the contract. The COR will have primary responsibility for completing quality assurance monitoring forms that will be used to document the inspection and evaluation of the Contractor’s performance. The COR will maintain surveillance documentation, notify the Contracting Officer (CO) of any significant performance deficiencies and recommend improvements to the QASP and Performance Work Statement (PWS) throughout the life of the acquisition. See also in AFFARS MP5301.602-2(d) and Designation Memorandum for further clarification of COR duties and responsibilities.

3.1.1. Contracting Officer Representative Tracking (CORT) Tool is the DoD mandatory web-accessible management application designed to nominate, appoint, track and terminate, if necessary, CORs and to serve as the web-based portal for all relevant COR documents to include monthly status reports/surveillance documents on service contracts.

The CORT Tool is located on the Wide Area Work Flow (WAWF) site and requires access to WAWF to register. CORs are required to register in the CORT Tool and upload their COR nomination and surveillance documentation. See the DoD CORT Tool User's Guide for further guidance.

3.2. The Contracting Officer (CO): has overall responsibility for overseeing the Contractor’s performance in the areas of contract compliance, contract administration, cost control and property control; reviewing the COR assessment of the Contractor’s performance; and serves as a liaison between the COR and the Contractor. The CO is the only person with the authority to direct the Contractor in the performance of their duties under the contract and to make interpretations of and changes to the contract. The CO will facilitate Multi-Functional Team meetings. See also AFFARS MP5346.103, Contracting Office Responsibilities and AFFARS MP5301.602-2(d) for further clarification of CO duties and responsibilities.

3.3. The Functional Commander or Functional Director (FC/FD)/COR Management:

Encompasses the FC/FD and the COR Supervisor and has overall responsibility for developing the PWS and the QASP and ensuring they satisfy mission requirements, are performance-based, foster innovation and define metrics. COR Management is also responsible for assigning competent and capable functional experts to the Multi-functional Team who will be available full time or as warranted by the procurement cycle. COR management will assign COR(s) and notify the CO of any changes to this designation. The FC/FD will review Contractor performance documentation, prepared by the COR, on a regular basis to ensure performance is compatible with mission objectives.

See also AFFARS MP5301.602-2(d) for further clarification on COR Management duties and responsibilities.

3.4. The Contracting Squadron Commander (CSC): serves as the Business Advisor to senior leadership; develops and implements acquisition strategies for services acquisitions; provides oversight of the Multi-Functional Team in planning, assessing Contractor performance and managing the acquisition throughout the life of the requirement IAW the FAR, DFARS and AFFARS. The CSC will provide Annual Execution Review (AER) reports on service acquisitions to the MAJCOM for consolidation.

3.5. The Quality Assurance Program Coordinator (QAPC): develops, manages and implements the base Quality Assurance Program; supports the Multi-functional Team in the development of contract requirements, ensuring requirements are clearly stated and enforceable; aids in development of the Service Delivery Summary (SDS) and QASP and provides training to all FC/FD, COR and others that interact with this contract as needed.

3.6. The Contract Administrator (CA): is the focal point for issues regarding the contract; prepares and processes modifications to the contract, assists the CO in ensuring Contractor performance meets contract standards; records and transcribes minutes for meeting.

3.6.1. CA will perform COR assessment on a periodic basis as determined by the CO.

The CA will verify that the COR is accomplishing their surveillance according to the QASP. Observation of one or two checks will be sufficient to verify the COR’s procedures. If deficiencies are discovered in the COR surveillance procedures, the CO will notify the FC/FD and COR Management and provide any assistance requested, such as additional training for COR. The CA will ensure that the COR is documenting their surveillance in a timely manner. A check of the COR files will also be performed on a periodic basis as determined by the CO/CA.

4. PERFORMANCE ASSESSMENT AND SDS TABLE. The following Service Delivery Summary outlines the defined Performance Objectives (PO) for this acquisition with the corresponding goal performance thresholds:

PO

PERFORMANCE

OBJECTIVE

PWS

REFERENCE

PERFORMANCE

THRESHOLD

METHOD OF

SURVEILLANCE

1 Bus Service. Fully serviceable buses without safety defects must arrive at designated pick-up location(s) on time IAW the daily workload schedule.

Marquee must be in use and match the service being provided.

Para 1.2 98% on time arrival with bus marquee on indicating drop-off location being serviced for the month.

Random Sampling

2 Shuttle Bus Service(s) must arrive on time IAW the approved shuttle bus schedule indicated in the Appendices or on the weekly workload schedule. Marquee must be in use and match the service being provided.

Buses must be fully serviceable and not have safety defects while in use.

Para 1.2 96% on time arrival with bus marquee on indicating route being serviced for the month.

Random Sampling

3 Contractor shall maintain general housekeeping for facilities listed in Appendices H.

Para 4.3, 4.6 and 4.7

1 defect per month is acceptable.

Random Sampling

4 The Contractor shall ensure all passengers are properly seated, and bus driver is wearing a seat belt prior to bus being placed into motion.

In addition, bus drivers are responsible for the safe and orderly embarkation/debarkation of passengers from the bus and will ensure emergency flashers are utilized during the loading/ unloading process.

Para 1.2.6 3 defects per month is acceptable.

Random Sampling

5 The Contractor shall ensure all trip data is loaded into OLVIMS when run is complete or prior to submitting the Daily Trip Ticket Report if OLVIMS outages prevent immediate completion.

Para 1.2.11.2 95% of trips reviewed must be documented properly in OLVIMS.

Random Sampling

4.1 The method(s) of performance assessment for each acquisition performance objective is as follows:

SAMPLING GUIDE

JBSA BASE BUS SERVICE

PERFORMANCE OBJECTIVE #1

1. Method of Surveillance: Random Sampling (Monthly Checklist).

2. Lot Size: Number of Provided Bus Service Request Support for the Month.

3. Sample Size: Number of Provided Bus Service inspected for the month.

4. Performance Threshold: Performance is acceptable when 98% or more of the sample size inspected for the month is on-time with bus marquee on indicating drop-off location IAW the daily workload schedule and are without safety defects. Performance is unacceptable when less than 98% of the sample size is not in compliance.

5. Inspection Procedures: The CORs will annotate on the monthly checklist, the pick-up location, bus number with marquee properly/improperly illuminated indicating drop-off location, time arrived, and if service was safe and acceptable/unacceptable for Bus Service. The CORs can randomly pick any time of the day to check Performance Objective #1.

6. If the CORs determine that service was unacceptable, they must inform the Contractor Project Manager or on-site representative that service was unacceptable and request his or her acknowledgement via email for the defective service.

SHUTTLE BUSES MUST ARRIVE ON TIME IAW PWS APPENDICES OR

ANNOTATED ON THE CONTRACTOR WEEKLY WORKLOAD SCHEDULE

PERFORMANCE OBJECTIVE #2

2. Lot Size: Number of Arrival Times available to be inspected monthly.

3. Sample Size: Number of shuttle arrivals inspected for the month.

4. Performance Threshold: Performance is acceptable when 96% or more of the sample size inspected for the month arrives on-time at the bus stop with bus marquee properly illuminated indicating route being serviced and is fully serviceable with no safety defects. Performance is unacceptable when less than 96% of the sample size inspected for the month is not in compliance.

5. Inspection Procedures: The CORs will annotate on the monthly checklist indicating the bus number, time arrived, bus marquee properly or improperly illuminated indicating route being inspected and if service was safe and acceptable/unacceptable for the Shuttle.

The CORs can randomly pick any time of the day to check Shuttle Stop(s) times to ensure that the Contractor is maintaining proper shuttle times IAW the Appendix’s in the PWS or on the Contractor Daily Workload Schedule.

6. If the CORs determine that service was unacceptable, they must inform the

GENERAL HOUSEKEEPING FACILITIES/GROUNDS

PERFORMANCE OBJECTIVE #3

2. Lot Size: Number of days per month.

3. Sample Size: Three inspections for the month.

4. Performance Threshold: Performance is acceptable when one (1) defect is discovered per month. Performance is unacceptable when two (2) or more defects are discovered per month.

5. Inspection Procedures: The CORs will annotate on the monthly checklist, if the facilities and grounds are maintained in a clean manner.

6. If the CORs determine that service was unacceptable, they must inform the

OPERATE VEHICLE IN SAFE MANNER

PERFORMANCE OBJECTIVE #4

2. Lot Size: Number of trips per month.

3. Sample Size: Number of trips inspected for the month.

4. Performance Threshold: Performance is acceptable when 3 defects per month is acceptable. Performance is unacceptable when contractor receives more than 3 defects per month.

5. Inspection Procedures: The CORs will annotate on the monthly checklist indicating the bus number being inspected and if service is acceptable/unacceptable, to ensure all passengers are properly seated and bus driver is wearing a seat belt prior to bus being placed into motion. In addition, bus drivers are responsible for the safe and orderly embarkation/debarkation of passengers from the bus and will ensure emergency flashers are utilized during the loading/ unloading process. The CORs can randomly pick any time of the day to check Operate Vehicle in Safe Manner to ensure that the operator is in compliance with Performance Work Statement.

6. If the CORs determine that service was unacceptable, they must inform the

OLVIMS DATA INPUTS

PERFORMANCE OBJECTIVE #5

2. Lot Size: Number of trips days per month.

3. Sample Size: 200 trips per month (using OLVIMS confirmation numbers) spread across the month throughout the operating hours for the month.

4. Performance Threshold: Performance is acceptable when 95% of trips reviewed are documented properly and completed at run completion or before Daily Trip Ticket Report is submitted if documented OLVIMS outages prevent immediate complete. Less than 95% indicates unacceptable performance.

5. Inspection Procedures: The CORs will annotate on the monthly checklist, the confirmation number in OLVIMS which was being inspected and if service is acceptable/unacceptable. The CORs shall inspect that all data fields have been completed accurately and in a timely manner on the confirmation number as long as it has been 24 hours since completion of service to ensure the Contractor are in compliance with the PWS.

6. If the CORs determine that service was unacceptable, they must inform the Contractor Project Manager or on-site representative that service was unacceptable and request his or her acknowledgement via email for the defective service and follow-up e-mail once the defect is corrected in OLVIMS.

4.2. CERTIFICATION OF SERVICES. At the end of each contract payment period as defined in the resulting award of this acquisition, the COR shall certify the services were received in accordance with contract payment terms and conditions.

4.3. UNACCEPTABLE SERVICES. The COR shall determine the cause of Contractor unacceptable services.

4.3.1. If any Government action, or lack of action, caused or contributed to the unacceptable performance, the performance will not be counted against the Contractor.

The COR will take steps to ensure the Government does not interfere with the Contractor’s performance in the future.

4.3.2. If Contractor caused, the COR shall document the occurrence in accordance with (IAW) the methods of surveillance outlined in this QASP. IAW contract terms and conditions, the Government reserves the right to inspect any services that have been tendered for acceptance. The Government may require re-performance of nonconforming services at no increase in contract price. If re-performance will not correct the defects or is not possible, the Government may seek an equitable price reduction or adequate consideration for acceptance of nonconforming supplies or services. Disputes between the COR and the Contractor on the validity of a performance assessment shall be referred to the CO.

5. PERFORMANCE MANAGEMENT. The following outlines the approach, methods and tools to be used by the MFT to manage this acquisition upon award:

5.1. COR(s) shall evaluate and document Contractor’s performance in accordance with the procedures outlined in this QASP and maintain resulting surveillance documentation.

The results of surveillances shall be maintained as Past Performance information and utilized to prepare and support annual Contractor Performance Assessment Report System (CPARS) reporting, if required. Information will also be used to complete reporting requirements in accordance with AFI 63-138, Acquisition of Services, Chapter 6.4., Initial Contract Performance Review, which shall take place within 30 days after the Contractor assumes full performance responsibilities (i.e. after completion of transition/mobilization). Also, paragraph 5.2., Annual Execution Reviews (AER) which shall assess annual execution review from the CPARS.

5.2. The Contractor shall implement and maintain a Quality Control Plan (QCP) to ensure the contract services conform to the requirements of the PWS. The QCP shall be submitted with the Contractor’s proposal for evaluation and acceptance.

5.3. The United States Government has adopted a zero tolerance policy regarding trafficking in persons. Additional information about trafficking in person may be found at the website for the Departments of State’s Office to Monitor and Combat Trafficking in Person at http://www.state.gov/g/tip.

http://www.state.gov/g/tip

5.3.1. IAW FAR 52.222-50 and DFARS PGI 222.17, Combating Trafficking in Persons, CORs must monitor the Contractor’s performance regarding trafficking in persons such that non-compliance with stated regulatory guidance is brought to the immediate attention of the CO. CORs must inform the CO if the Contractor, Contractor personnel, subcontractor, or subcontractor personnel have failed to comply with the requirements of this clause and PGI.

5.3.2. The CO shall, through the CO’s local commander or other designated representative, immediately notify the Combatant Commander for the geographical area in which the incident has occurred. The Unified Combatant Command DefenseLINK website at http://www.defenselink.mil/specials/unifiedcommand/, identifies each command’s area of responsibility.

5.3.3. The Contractor shall take appropriate action should a violation occur. For corrective procedures and remedies for non-compliance see contract clause

FAR 52.222-50.

5.4. SAF/AQ Policy Memo, Implementation of FY 11 NDAA Section 8108, Contractor Inventory, 13 Nov 12, requires contractors to report labor hours via the Contractor Manpower Reporting Application (eCMRA) located at http://www.ecmra.mil.

5.4.1. CORs shall ensure contractor labor hours and contract data entry requirements are properly loaded in the eCMRA. See CMRA Contractor Manpower Reporting Full User Guide for further guidance.

5.5. The MFT shall continue to meet after award as necessary to ensure high levels of contractor performance, foster a synergistic partnership, and support mission requirements.

6. COR MAINTAINED DOCUMENTATION. CORs will organize their files so they can easily locate essential information when needed. These records are subject to inspections by the FD or FC, CO, Quality Assurance Program Coordinator, Auditors, etc., and can be used to support either the Government’s or Contractor’s position in disputes. The list provided below indicates items that should be on file:

a. A copy of the COR(s) nomination/appointment letter and copies of all training certifications.

b. A copy of the contract including all attachments such as special reports required to be submitted by the Contractor, technical specifications too voluminous to incorporate in contract.

c. A copy of all modifications to the contract.

d. Copies of all receipts and acceptance documents processed.

e. Correspondence to and from the CO and Contractor. This correspondence could http://www.defenselink.mil/specials/unifiedcommand/ http://www.ecmra.mil/ include special instructions from the CO, interpretation of the terms and conditions of the contract from the CO, or questions on interpretations of terms, conditions, and specifications from the Contractor.

f. A copy of memoranda for record to document:

(l) Telephone conversation with the Contractor’s representative and the CO.

(2) Pre-work or pre-performance conference meetings.

(3) Any other conversations or meetings with the Contractor, CO, CORs, and the FD or FC.

(4) Records of the Contractor’s inspection system, if obtained from the Contractor.

(5) Records of inspections describing how, when, and where the inspections were accomplished and the results of those inspections.

(6) Samples, photographs, witness statements, and other factual data to support documentation.

(7) Records of unusually severe weather conditions. An example of severe weather conditions which could affect or delay performance on a service contract would be a severe snowstorm that closed the entire installation.

(8) Names of individuals who are functioning as technical and administrative assistants. These individuals could be inspectors or clerks who are responsible for typing or drafting receiving reports or setting up your filing system.

(9) Applicable test reports, if any.

(10) Copies of deficiencies.

(11) Copies of any other data as may be required by the contract provisions.

(12) A copy of all AF Forms 9, Request for Purchase, funding obligations for the contract.

(13) A copy of all forms and letters containing surveillance and evaluation data applicable to the contract.

6.1. DISPOSITION OF THE CONTRACT FILES. When the contract is completed, under no circumstances shall the COR files be disposed of. The COR shall send all files to the CO’s office.

6.2. SUSPENSE FILES. A suspense system should be established to advise the CO in a timely manner of the Contractor’s failure to complete acceptable performance or delivery in accordance with the contract schedule or provisions.

6.3. CORRESPONDENCE. COR reports constitute an important historical part of any contract file. By maintaining a daily log of performance, a sequence of events is registered and made part of the file. When completing written documentation, be sure it contains the contract number and date; be as specific as possible in describing the events or conditions; give specific contract references, and be sure to sign the document.

7. COR SURVEILLANCE. The COR will prepare a monthly evaluation schedule for performance objectives 1 through 5 listed in Performance Work Statement (PWS) Paragraph 3 Service Delivery Summary. This schedule shall not be shown to the Contractor. The COR must give one copy of the schedule to the CA before the start of the surveillance period. Changes to the monthly schedule will be posted and changes will be provided to the CA.

7.1. ACTUAL SURVEILLANCE. Actual surveillance should be comparable to the Monthly Evaluation Schedule established by the COR. These documents then become the official Air Force record of the Contractor’s performance. When surveillance observation results in an unacceptable rating, record it in the applicable column labeled “unacceptable”. Once the Contractor is notified of any unacceptable service, the Contractor should correct the cause of the unacceptable service or re-perform the service if practical. Any defects corrected by the Contractor shall still count as defective and reported on the Contractor Monthly Performance Assessment Report.

7.1.2 During the month the COR may receive customer complaints about the quality of the service. Additionally, the COR may observe unacceptable performance by the Contractor other than during an inspection. These complaints and observations will be noted as observations and included with the monthly evaluation report which is used to reinforce the accuracy of the Contractor’s performance. Only one surveillance method may be used during an inspection period for each Performance Objective (PO) listed in the Service Delivery Summary Table.

7.1.3. If the number of defects recorded on the Monthly Inspection Checklist exceeds the performance threshold listed on the Service Delivery Summary Table the COR will notify the CO for appropriate action. The CO is the only person authorized to take action against the Contractor when performance thresholds are not met.

7.1.4. Periodic Surveillance Methods. These items are inspected using periodic surveillance (daily, weekly, monthly). The results of the periodic surveillance inspections may be used as the basis for CO actions against the Contractor. In such cases the Inspection of Services clause becomes the basis for the CO’s actions.

7.1.5. Other Surveillance Methods. Service surveyed by methods other than periodic shall be documented on a Monthly Checklist, Customer Complaint Form, or a locally generated form. The COR will complete blocks 1-5, and 7 of the Customer Complaint

Form only after validating each complaint. Once validated the COR shall complete appropriate blocks and ensure that the PWS reference is placed in block 5 prior to sending to the Contractor. Block 6 of the Customer Complaint Form will be completed by the Contractor. All complaints must be documented with the information required on the form and forwarded to the CO/CA. The 502 LRS/LGRDO/Vehicle Operations Element Chief will determine if Customer Complaints should be routed through the FD or FC for comments/coordination prior to forwarding to the CO. These complaints will become a permanent part of the COR surveillance records.

7.1.6. Informing Project Manager. The COR must always inform the Contractor’s Project Manager or on-site representative of any discrepancies found in surveillance items via email. Receipt of the emailed checklist indicates the Contractor is only acknowledging that he or she was informed of the discrepancy. When the Contractor does not reply to the COR, the COR must note and initial on the back of the checklist where the defect is recorded, the time, and the method of notification.

8. ANNUAL CONTRACTOR PERFORMANCE ASSESSMENT RATING.

Contractor’s Performance Assessment Rating (CPAR) is applicable to all service contracts valued over $1,000,000. Guidance on CPARS is available from the Department of the Air Force CPARS Guide and the 502 CONS/CPARS representative.

9. CONTRACTOR MONTHLY PERFORMANCE ASSESSMENT REPORT.

Monthly, the COR’s will assess the Contractor performance for Performance Objectives listed in the Services Summary Table. The Vehicle Operations Element Chief will ensure the ratings of the monthly performance assessment report are reflected in the monthly health of the squadron slides presented to the LRS Commander. Monthly performance assessments will be forwarded to the CO by the 5th work day of the month. The five (5) rating definitions are:

9.1. Exceptional. Performance meets contractual requirements and exceeds many to the Government’s benefit. The contractual performance of the element or sub-element being evaluated was accomplished with few minor problems for which corrective actions taken by the Contractor were highly effective.

9.2. Very Good. Performance meets contractual requirements and exceeds some to the Government’s benefit. The contractual performance of the element or sub-element being evaluated was accomplished with some minor problems for which corrective actions taken by the Contractor was effective.

9.3. Satisfactory. Performance meets contractual requirements. The contractual performance of the element or sub-element contains some minor problems for which corrective actions taken by the Contractor appear or were satisfactory.

9.4. Marginal. Performance does not meet some contractual requirements. The contractual performance of the element or sub-element being evaluated 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.

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

10. CONTRACTOR SERVICE PAYMENT. The COR is required to accept Contractor services and determine payment due. At the completion of each contract payment period (usually monthly), the COR will certify the services actually received under the contract.

11. REVISION TO THE QUALITY ASSURANCE SURVEILLANCE PLAN.

Revisions to this plan are the joint responsibility of the FC, the CO, the CA, and the CORs.

12. LIST OF APPENDICES

A. Monthly Inspection Checklist B. Customer Complaint

APPENDIX A.

Acc Unacc

01 Location: Bus # Time:

02 Location: Bus # Time:

03 Location: Bus # Time:

04 Location: Bus # Time:

05 Location: Bus # Time:

06 Location: Bus # Time:

07 Location: Bus # Time:

08 Location: Bus # Time:

09 Location: Bus # Time:

Acc Unacc

01 Location: Bus # Time:

02 Location: Bus # Time:

03 Location: Bus # Time:

04 Location: Bus # Time:

05 Location: Bus # Time:

06 Location: Bus # Time:

07 Location: Bus # Time:

08 Location: Bus # Time:

09 Location: Bus # Time:

NOTES

Name:

Total:

Task # Task Description Name:

Name:

Total:

NOTES

PO #2 JBSA-LAK SHUTTLE BUS SERVICE +/-5 MINUTES (REF PWS PARA 1.2)

Name:

Name:

PO #1 JBSA-LAK PROVIDE SCHEDULE BUS SERVICE (REF PWS PARA 1.2)

Task # Task Description Name:

POC: 502 LRS/COR COR DAILY CHECKLIST Date: 6-Jan-15 Service Number/Description: JBSA-LAK BUS SERVICE CONTRACT

Acc Unacc

01 Location: Bldg 5004 02 Location: Bldg 5004 03 Location: Bldg 5004 04 Location: Bldg 5004 05 Location: Bldg 5004 06 Location: Bldg 5004 07 Location: Bldg 5004 08 Location: Bldg 5004

Acc Unacc

01 Location: Bus # Time:

02 Location: Bus # Time:

03 Location: Bus # Time:

04 Location: Bus # Time:

05 Location: Bus # Time:

06 Location: Bus # Time:

07 Location: Bus # Time:

08 Location: Bus # Time:

09 Location: Bus # Time:

Acc Unacc

01 OLVIMS Confirmation # 02 OLVIMS Confirmation # 03 OLVIMS Confirmation #

Total:

NOTES

Task # Task Description Military COR

PO #5 OLVIMS DATA (REF PWS PARA 1.2.11.2)

Name:

Total:

NOTES

Name:

Total:

NOTES

PO #4 OPERATE VEHICLE IN SAFE MANNER (REF PWS PARA 1.2.6)

Task # Task Description Name:

Contractor maintaining Bldg. 5004 in a neat/orderly manner?

Task # Task Description Name:

Is the carpet/tile area clean ?

Is the work area/break area clean?

Has the carpet been shampooed semi-annually?

Bathroom/tile areas been mopped weekly?

Is the office and restrooms clean?

Has all trash/paper been disposed of properly?

Bathrooms have toilet paper/soap/ hand towels?

POC: 502 LRS/COR COR DAILY CHECKLIST Date: 6-Jan-15

PO #3 MAINTAIN GENERAL HOUSEKEEPING FACILITIES (REF PWS PARA 4.3, 4.6, AND 4.7)

Appendix B.

EXAMPLE

CONTRACT CUSTOMER COMPLAINT NUMBER:_______

CUSTOMER NAME:_________________________DATE:________________PHONE:_______________

1. CONTRACT NUMBER:

2. DATE:

3. TO:

4. INVESTIGATION COR:

5. NATURE OF COMPLAINT:

6. ACTION TAKEN BY CONTRACTOR:

7. COR COMMENTS:

8. PWS REFERENCE

QASP SIGNATURE PAGE

REQUIREMENT TITLE: JBSA-Lackland Bus Services

DATE:__________________________

Name: TODD DEANE Name: SSgt JUSTIN D. CANADAY 502 LRS Functional Commander Title: Primary COR

Name: JOSE LlANES Jr. Name: CHARLES H. BRANCH Title: Alternate COR Title: Alternate COR

Name: CALVIN E. SULTEMEIER Name: SSgt JAMES E. STARCHER II Title: Alternate COR Title: Alternate COR

Name: JOSE A. FARIAS Name: MICHAEL DARGAN Title: Contracting Officer Title: Contract Specialist

Name: MARIA C. LAMBERT Title: Quality Assurance Program Coordinator