RSAC-25-001-SVC100 - QASP.pdf

Quality Assurance Surveillance Plan

For

Printer Maintenance for U.S. Army Garrison – Redstone Arsenal, AL

24 April 2025

ACC-RSA QASP Template Version: 20250220

ACC-RSA QASP Template

Version: 20250220

TABLE OF CONTENTS

Subject Page Number

1.0 Overview 3

2.0 Description of Services 4

3.0 Roles and Responsibilities 4

4.0 Contract Quality Requirements 5

5.0 Government Surveillance 6

6.0 Non-Conforming Performance & Corrective Action Requests (CAR) 8

7.0 Data Analysis 10

8.0 Acceptance of Services 10

9.0 COR Status Report (CSR) 10

10.0 Service Contract Reporting (SCR): 11

11.0 Contractor Performance Assessment Reporting System (CPARS) 11

12.0 Combating Trafficking In Persons (CTIP) 11

13.0 COR/Quality Assurance Surveillance Files 11

14.0 QASP Changes 13

15.0 Attachments 13

1.0 Overview.

1.1 Purpose. The purpose of this Quality Assurance Surveillance Plan (QASP) is to identify the methods and procedures the Government will use to ensure it receives the services under this contract as identified in the Performance Work Statement (PWS). This Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate performance for the stated contract. This QASP explains the following:

• What will be monitored?

• How monitoring will take place.

• Who will conduct the monitoring?

• How monitoring efforts and results will be documented.

• When and how often monitoring will take place.

This QASP does not detail how the contractor accomplishes the work. Rather, the QASP is created with the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. It is the Government’s responsibility to be objective, fair, and consistent in evaluating performance. The QASP should recognize that unforeseen and uncontrollable situations may occur.

The contractor is responsible for implementing and delivering performance that meets and/or exceeds contract standards using its Quality Control Plan. The QASP provides the structure for the government’s surveillance of the contractor’s performance to assure that it meets contract standards. It is the government’s responsibility to be objective, fair and consistent in evaluating contractor performance.

The QASP is not part of the contract, nor is it intended to duplicate the contractor’s quality control plan. This QASP is a living document. Flexibility in the QASP is required to allow for an increase or decrease in the level of surveillance necessary based on contractor performance.

Bottom line, the QASP should ensure early identification and resolution of performance issues to minimize impact on mission performance.

1.2 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; and 3) encourage the Contractor to take appropriate steps to control and improve quality.

Accordingly, the Government will perform surveillance on the contract in accordance with this QASP but reserves the right to monitor the contract in any manner necessary, at any time necessary, and at all places necessary to ensure that the rendered services conform to contract requirements. The Government also reserves the right to perform quality assurance at the Subcontractor level and perform quality assurance at the contractor's place of business, if applicable. Resolution of non-conforming services discovered at the Subcontractor level will be addressed with the prime Contractor.

1.3 Authority. Authority for issuance of this QASP is provided under Part 46 of the Federal Acquisition Regulation, Inspection of Services clauses, which provides for inspection, Version: 20250220 acceptance, and documentation of the service called for in the Task Order or contract. This acceptance is to be executed by the contracting officer or a duly authorized representative.

2.0 Description of Services

2.1 Scope of Work. This is a non-personal services contract to provide ongoing, monthly toner inclusive maintenance for seventy-nine (79) existing Multi-Function Devices (MFD) (network printers/copiers/scanners), for the U.S. Army Garrison on Redstone Arsenal, AL. The purpose of the upgrades and maintenance is to provide continued usage of the MFD’s for operational productivity.

2.2 Type of Contract. The Government will award a Firm-Fixed Price (FFP) Contract.

3.0 Roles and Responsibilities.

3.1 Government.

3.1.1 Contracting Officer (KO). The KO is the only person with the authority to enter, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. The KO is the only person who can legally commit to the Government and only the KO, as the Government’s agent, can modify the contract/order.

Assigned KO: Cleveland Crutcher Organization or Agency: ACC-RSA Telephone: 256-955-4919 Email: Cleveland.crutcher.civ@army.mil

3.1.2 Contracting Officer’s Representative (COR). The (COR) will be identified and designated by the KO on a separate COR appointment letter. The COR appointment letter will list specific tasks and functions the COR is required to perform. The COR monitors all technical aspects of the contract and assists 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 aspects of the contract: monitor Contractor's performance and reporting early identification of performance problems to the Contracting Officer and Contractor; coordinate availability of Government furnished property, and provide site entry of Contractor personnel. The COR shall keep a surveillance file in Procurement Integrated Enterprise Environment – Surveillance and Performance Monitoring Application (PIEE-SPM) that accurately documents the contractor’s performance. The COR is required to provide performance assessments to the KO as applicable by uploading in PIEE-SPM. 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 regarding changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

Assigned COR: Chad Farley mailto:Cleveland.crutcher.civ@army.mil

Version: 20250220

Organization or Agency: USAG-R Telephone: 520-718-4943 Email: chad.a.farley2.civ@army.mil

3.1.3 Contract Administrator. Reserved.

3.1.4 Property Administrator. Reserved.

3.2 Contractor.

3.2.1 Contract Manager. Reserved.

3.2.2 Project Manager. Reserved.

3.2.3 Quality Manager. Reserved.

4.0 Contract Quality Requirements.

4.1 Contractor’s Quality Control Program. The Contractor’s quality control program (IAW FAR Part 46 and applicable 52.246-(Clause(s))) is how the Contractor assures that work complies with the requirement of the contract. The Contractor shall ensure services are performed in accordance with this PWS. The Contractor shall identify, prevent, and ensure non-recurrence of defective services.

4.2 Government Quality Assurance. The Government shall evaluate the Contractor’s performance under this contract in accordance with this QASP. This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards of the contract. It defines how the performance standards will be applied, the frequency of surveillance and minimum acceptable defect rate(s).

5.0 Government Surveillance. The Government has the right to inspect all contract deliverables at any time before acceptance. Inspections can be announced or unannounced, but they must not unduly delay work, and they must not include directions that would change the contract. The Government also has the right to reject a deliverable that does not meet contract requirements. For acquisitions of commercial items, FAR Subpart 46.202-1 requires the Government to rely on contractors’ quality assurance systems as a substitute for Government inspection and testing before the items are tendered for acceptance (unless customary practices for the supplies being acquired include in-process inspection). Any in-process inspection by the Government must be consistent with commercial practices. For services, the COR can monitor contractor performance by using a variety of inspection methods. Before an inspection, the COR should check the contract for specific inspection and testing requirements. The COR should use a systematic approach and should ensure that the inspection methods do not interfere with the contractor’s progress or at least disrupt that progress only when absolutely necessary and as minimally as possible.

mailto:chad.a.farley2.civ@army.mil

Version: 20250220

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

5.1.1 100% Inspection. Reserved.

5.1.2 Random Sampling. Reserved.

5.1.3 Periodic Inspection. This method, sometimes called “planned sampling," consists planned sampling at specific dates or time intervals. It may be appropriate for tasks that occur infrequently, and where 100 percent inspection or random testing is not desired.

5.1.4 Customer Feedback/Input (Complaints). Although usually not a primary method, this is a valuable supplement to more systematic methods. For example, in a case where random sampling indicates unsatisfactory service, customer complaints can be used as substantiating evidence. In certain situations where customers can be relied upon to consistently providing feedback regarding the quality of performance, e.g., dining facilities, building services, customer surveys and customer complaints may be a primary surveillance method, and customer satisfaction an appropriate performance standard.

In all cases, complaints will be documented. The following procedures will be followed when a complaint is received: The COR will document customer complaints about unsatisfactory performance, the validity of the complaint, time and date the responsible official was notified, and the actions taken to correct the problem. Customer complaints shall be handled in the following manner: When a complaint is received, COR personnel will complete appropriate documentation to record the complaint. The COR shall investigate the complaint to determine contract non-conformance. If after investigation the COR determines the complaint as valid, the COR will inform the Contractor’s Quality Manager, the KO, and the Government’s Quality Assurance Specialist. If the COR determines the complaint as invalid, the COR shall document their findings and notify the complainant. COR personnel will retain the annotated copy of the written complaint for their file. All customer complaints received, valid and invalid, will be documented. Valid complaints should lead to documentation in the form of a Corrective Action Request (CAR).

5.2 Performance Requirements Summary (PRS). The Performance Requirements Summary (PRS) (Attachment 15.1) is the list of performance objectives and standards that must be performed by the contractor. This matrix details the method of surveillance the COR will use to validate and inspect these performance elements. Inspection of each element will be documented on a COR surveillance checklist and uploaded in the COR PIEE-SPM File. The key elements of this process are PWS tasks risk rated as high or moderate, and included in the Performance Requirements Summary (PRS) which provides the performance objective, performance standard, performance threshold and method of surveillance. The COR will perform surveillance and inspect the compliance of PWS tasks monthly. Although the PRS contains only those items considered most important for mission accomplishment, the government retains the right to

Version: 20250220 inspect all requirements of the contract. The COR may choose to periodically inspect requirements not listed on the PRS. Non-conformance with any contract requirement, whether specifically addressed in the PRS or not, is still considered a non-conformance (See Para 6.0 Non-Conforming Performance). The intent of the surveillance approach is to gain confidence in the contractor's way of doing business and then adjusting the level of oversight to a point that maintains that confidence. With this intent, the surveillance approach may not be one that stays the same throughout the duration of the contract. All Government evaluators should be prepared to periodically update the surveillance approach as required.

Performance objectives define the desired outcomes. Performance Standards define the level of service required under the contract to successfully meet the performance objective. The inspection methodology defines how, when, and what will be assessed in measuring performance. The Government performs surveillance, using this QASP, to determine the quality of the contractor’s performance as it relates to the performance element standards. The PRS should be used to form the foundation of the COR’s inspection checklist(s).

5.3 Surveillance Schedule. The COR shall develop a Quality Assurance Surveillance Schedule (QASS), that correlates with the COR status report frequency, based on the Performance Standards as outlined in the PRS as well as any other critical contractual requirement determined to be higher risk requiring oversight. The completed QASS form shall be uploaded into PIEE-SPM in the Surveillance Documents section as a Surveillance Schedule.

The QASS ensures the KO that the COR has scheduled and documented the specific dates and times contractor surveillance was performed. The surveillance outlined in the schedule will be as detailed and in-depth as necessary to provide the Government with the objective quality evidence required to support acceptance of the services provided by the Contractor. The schedule will identify the method of surveillance, the date of inspection, place of inspection, activity to be monitored, and who will conduct the surveillance (dates and times can be altered without a formal change to the schedule as long as all inspections are performed). The schedule should be completed no later than seven calendar days prior to the beginning of the period it covers, and a copy uploaded into SPM module. Sample COR Surveillance Schedule, Attachment 15.2.

5.4 Surveillance checklist. Checklists will be used to document COR surveillance. The completed checklist will be uploaded in PIEE/SPM module along with the COR status report.

The COR will develop an inspection checklist for all planned inspections. All inspections/observations will be documented and will include as a minimum date and time, who performed the inspection, what was inspected, what standard and the results. Successful or exceptional performance will be documented as well as deficiencies in Contractor performance.

Documentation will be uploaded and maintained for future reference, audit, and proof of inspection and past performance documentation.

5.5 Performance Rating Definitions. In evaluating the quality of contractor’s performance, the following performance ratings IAW FAR 42.1503, Table 42-1will be used.

Performance Rating Criteria

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.

NOTE: To justify an Exceptional rating, identify multiple significant events and state how they were of benefit to the Government. A singular benefit, however, could be of such magnitude that it alone constitutes an Exceptional rating. Also, there should have been NO significant weaknesses identified.

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 were effective.

NOTE: To justify a Very Good rating, identify a significant event and state how it was a benefit to the Government. There should have been no significant weaknesses identified.

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.

NOTE: To justify a Satisfactory rating, there should have been only minor problems, or major problems the contractor recovered from without impact to the contract/order. There should have been NO significant weaknesses identified. A fundamental principle of assigning ratings is that contractors will not be evaluated with a rating lower than Satisfactory solely for not performing beyond the requirements of the contract/order.

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.

NOTE: To justify Marginal performance, identify a significant event in each category that the contractor had trouble overcoming and state how it impacted the Government. A Marginal rating should be supported by referencing the management tool that notified the contractor of the contractual deficiency (e.g., management, quality, safety, environmental deficiency report or letter).

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 a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

NOTE: To justify an Unsatisfactory rating, identify multiple significant events in each category that the contractor had trouble overcoming and state how it impacted the Government. A singular problem, however, could be of such serious magnitude that it alone constitutes an unsatisfactory rating. An Unsatisfactory rating should be supported by referencing the management tools used to notify the contractor of the contractual deficiencies (e.g., management, quality, safety, or environmental deficiency reports, or letters).

6.0 Non-Conforming Performance & Corrective Action Request (CAR). The KO will notify the Contractor in writing each time an unacceptable observation has been recorded and ask the Contractor to correct the problem or re-accomplish the service. All valid non-conformance observed by the Government will be documented! CARs are used to document a contractor’s non-compliance to the contract requirements and generated by the COR, QAS, or the KO but can

Version: 20250220 only be approved and issued by the KO to the contractor to drive corrective action and contractual compliance. A CAR is not a contract action, contract remedy, nor punitive in nature but more of a tool used to document contractor nonconformance on all contracts administered by ACC. In addition, CARs are used in evaluating the contractor’s corrective action, determine if an appropriate root cause has been assigned, and verify that timely corrective action has taken place by the contractor to prevent or reduce recurrence in the same or other similar services or products. Refer to ACC Acquisition Instruction Attachment 46.2 “Corrective Action Request Procedures” for direction on how to document and manage CARs. There are four levels of CARs which are used and issued to the contractor. CARs must be submitted to the contractor in a timely manner after non-conforming performance has been identified. If the number of non-conformances/discrepancies exceeds the performance threshold for any item in the PRS, approved Government representatives will determine the possible cause of this unacceptable performance. Government-caused defects/discrepancies shall not be counted against the contractor. If the contractor’s performance is judged unacceptable on the PRS items or any other requirement of the contract by the appointed COR, they will inform the contractor’s on-site representative immediately and notify the KO and the ACC-RSA Quality Assurance (QA) Office. If the contractor disputes the results of surveillance, the COR will refer the contractor to the KO for resolution.

7.0 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 the COR Status Report(s) and may be used to make adjustments to surveillance schedules, increase or decrease surveillance, if deemed appropriate. Negative trends noted using Government data/observations could result in issuing the Contractor a CAR. Trends noted using Contractor data will not result in a CAR unless the Contractor is not addressing the negative trend.

8.0 Acceptance of Services. When all services have been deemed acceptable and there is documented objective quality evidence to support acceptable performance the COR will accept the services provided and authorize payment of the Contractor. This is accomplished by approving the Contractor’s Receiving Reports in PIEE - Wide Area Work Flow, https://wawf.eb.mil/.

9.0 COR Status Report (CSR). No later than the 7th of the month after previous reporting period, the COR will document the contractor’s performance by completing a CSR in PIEE-SPM for the previous surveillance period. CSRs, along with a surveillance checklist will provide a synopsis of the Contractors performance for the inclusive dates of the report. The synopsis will contain a summary of: surveillances performed; Customer Feedback, if any; CARs, if any; an analysis of the Contractors performance; recommended adjustments to surveillance schedules;

and any other pertinent contract information. The CSR will not be considered finalized until reviewed and approved by the contracting officer.

10.0 Service Contract Reporting (SCR): Defense FAR (DFARS) 204.1703(a), Reporting Requirements Thresholds, states that SCR is required in the System for Award Management (SAM) when a contract or order has both a total estimated value, including options, that exceeds $3 million and is for services in the service acquisition portfolio groups listed in Procedures, Guidance, and Information (PGI) 204.1703. The Printer Maintenance Contract does not meet the https://wawf.eb.mil/

Version: 20250220 threshold at DFARS 204.1703(a)(i), and its Product Service Code (PSC), DD01, is not listed in PGI 204.1703 and therefore SCR is not required.

11.0 Contractor Performance Assessment Reporting System (CPARS). Documented surveillance data (CSRs, Completed Surveillance Checklists, Customer Feedback and CARs, if any) will be used to support CPARS ratings. CPARS will be completed in accordance with AFARS, Subpart 5142.15 – Contractor Performance Information. The COR shall document that CPARS, if required, was completed in PIEE-SPM.

12.0 Combating Trafficking In Persons (CTIP). CTIP is mandatory in all solicitations and contracts. If this is a requirement on the COR Appointment Letter, the COR shall perform the following:

Read and understand the CTIP FAR clause 52.222-50 in the basic contract or at FAR | Acquisition.GOV and describe how you will monitor the contractor's performance regarding trafficking in persons (CTIP). Document surveillance results on the CSR, surveillance checklist, or the COR CTIP Checklist. Bring any potential issue in this area to the immediate attention of the KO before engaging the contractor in reference to these activities. Document any validated non-compliance on a CAR IAW paragraph 6.0 of this QASP.

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.

13.0 COR/Quality Assurance Surveillance Files. The official COR/Quality Assurance Surveillance File will be maintained in PIEE-SPM, IAW DoDI 5000.72, DoD Standard for COR Certification. At a minimum, the CORs PIEE-SPM file(s) contents will include:

Copy of contract and mods Current QASP COR appointment letter (if originally appointed outside of PIEE) COR training certificates COR Status Reports Surveillance Checklist / records of inspections Copy of the contractor’s Quality Control Plan Evidence of Funds/Expenditure tracker (If other than Firm Fixed Price Contract) Correspondence to contractor pertaining to cost, schedule and performance CARs (if applicable) Evidence of required documentation IAW PWS (CDRLs) Evidence of SCR data validation (if applicable) Evidence of CPARS data validation (if applicable) Evidence of Quality Assurance Surveillance Schedule (QASS) for each reporting period Customer feedback/surveys Memoranda for record of minutes of any meeting, telephone conversations and discussions with the contractor or others pertaining to the contract or contract performance https://www.acquisition.gov/browse/index/far https://www.acquisition.gov/browse/index/far

Documentation pertaining to acceptance of services, reports or data

Note: All such records will be retained for the life of this contract.

14.0 QASP Changes. 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 KO for approval and the KO must approve all changes. Once approved, the COR will upload the newest version into SPM module.

15.0 Attachments.

15.1 Performance Requirements Summary (PRS)

15.2 Quality Assurance Surveillance Schedule (QASS)

15.3 Deliverables Table (CDRLs)

15.4 COR CTIP Checklist

Attachment 15.1

Performance Requirements Summary (PRS)

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective (The Service required—usually a shall statement)

Standard Performance Threshold (This is the maximum error rate. It could possibly be “Zero deviation from standard”)

Method of Surveillance

PRS#1 – The Contractor shall develop and maintain an effective QCP (PWS para.

1.5.1)

The contractor shall ensure services are performed IAW this PWS.

Customer complaints shall not exceed 3 per month.

Periodic Inspection

PRS#2 – The Contractor shall provide support between the hours of 0700 to 1630, days Monday through Friday. (PWS para. 1.5.4.1)

The Contractor shall always maintain an adequate workforce, for the uninterrupted performance of all tasks defined within this

PWS.

95% Compliance; no more than 2 discrepancies found per month, etc.

Periodic Inspection

PRS#3 – The Contractor shall provide ongoing toner inclusive maintenance (PWS para. 5.1 and 5.2)

The Contractor shall comply with all listed tasks and specified regulations.

95% Compliance; no more than 2 discrepancies found per month, etc.

Scheduled Inspection and customer feedback

Attachment 15.2

Quality Assurance Surveillance Schedule (QASS)

ACC-RSA Contract Surveillance Schedule

A non-personal services contract to provide ongoing, monthly toner inclusive maintenance for seventy-nine (79) existing Multi-Function Devices (MFD) (network printers/copiers/scanners), for the U.S. Army Garrison on Redstone Arsenal, AL.

Organization: USAG – RSA

Location:

4488 Martin Rd Redstone

Arsenal, AL 35898

Contractor

Contract:

Printer Maintenance Contract # TBD

TO/DO:

Audit Type

Contract /

PWS

Reference

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Nov

Dec

Phase In

X

1.5.1

X

1.6.1 X

1.6.6 X

1.6.8 X

1.6.9 X

1.6.15 X

1.9 X

1.17 OCI As Applicable

1.18 X

1.19 Safety As Applicable

1.19.2 Medical Treat. As Applicable

1.19.3 Accident As Applicable

Attachment 15.3

DELIVERABLES TABLE (CDRLS)

Deliverable Frequency # of Copies Medium/Format Submit To A001 Quality Control Plan (QCP) (PWS para. 1.5.1)

Once within 10 days after contract award and no later than 30 days prior to any anticipated changes.}

One each Electronic delivery via email using Microsoft Office Word or Power Point 2013}

COR and then to the KO

A002 Antiterrorism Level 1 Training (PWS para. 1.6.1)

Must be completed within 30 calendar days of award and afterward within 15 days of new employees

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR

A003 iWatch Training (PWS para. 1.6.6)

Must be completed within 30 calendar days of award and afterward within 15 days of new employees

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR

A004 OPSEC Training (PWS para. 1.6.8, 1.6.9)

Must be completed within 30 calendar days of award and afterward within 15 days of new employees

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR

A005 TARP Training (PWS para.

1.6.15)

Must be completed within 30 calendar days of award and afterward within 15 days of new employees

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR

A006 Key Personnel – Provide Name of Program Manager (PWS para. 1.9)

Must provide the name and contact information of a Program/Contract Manager or Alternate responsible for performance of work within five (5) business days

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR

Version: 20250220

A007 Organizational Conflict of Interest (OCI) (PWS para.

1.17)

Must notify Contracting Office immediately whenever it becomes aware

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR and then to the KO

A008 Phase In/Phase Out (PWS para. 1.18)

Must prepare and submit a phase in/phase out plan within 10 days of contract award

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR and then to the KO

A009 Safety (PWS para. 1.19)

Must notify Contracting Office immediately whenever it becomes aware

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR and then to the KO

A010 Emergency Medical Treatment (PWS para. 1.19.2)

Must notify Contracting Office immediately whenever it becomes aware

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR and then to the KO

A011 Accident Reporting (PWS para. 1.19.3)

Must notify Contracting Office immediately whenever it becomes aware

One each Electronic delivery via email using Microsoft Office Word Or Power Point 2013

COR and then to the KO