Appendix D1 Sustainment 20200714.pdf

AT/FP Ashore Sustainment Contracts

Data Requirements Checklist and DED Package

Appendix D1

09 March 2020

Data Item Title of Data Item Date of 1st

Submission Date of

Subsequent Submission

DED

Version Date Notes

A002 Program Schedule and Progress Report 30 DACA Monthly In

AIM 20200309 V5

A009 Accident Prevention Plan 30 DACA None 20190416 V5 3 A010 Quality Control Plan 30 DACA None 20200710 V3

A017 Maintenance Plan 90 DACA None 20190329 V4

A018 Configuration Management Plan 60 DACA None 20190411 V2

A020 Supportability Strategy Plan 90 DACA None 20200309 V3

A030 Environmental Plan 30 DACA None 20190329 V3 3

A033 Completed Asset Data Template ASREQ ASREQ 20190411 V4 1, 4 A041 Closeout Package ASREQ None 20190329 V3 2, 4

A042 Information Assurance Vulnerability Alert (IAVA) –IA Related Requirements for Sustainment Administration

ASREQ ASREQ 20191203 V4

A043 Trend Analysis Reports 120 DACA Tri-annually 20190709 V4

A045 Government Property Inventory Report 30 DACA Semi-annually 20190813 V1

A046 Financial Expenditures for the Performance of Sustainment

60 DACA 180 DACA;

Semi-annually thereafter

20200213 V1

Note 1 – Single document containing all Task Order Projects at a Base/Site and submitted in Remedy for each Project Name at that Base/Site.

Note 2 – Single document containing all Projects on the Task Order and submitted in Remedy for each Task Order Project Name.

Note 3 – Single document for each Region and a single document containing all Projects at a Base/Site for each Base/Site and submitted in

Remedy for each Project Name in that Region and at that Base/Site.

Note 4 – Data Item A033 and A041 contains the submittal requirements for Sustainment Contracts/Task Orders such as ECPs, Technical

Refreshment/Upgrades, New Installations, and for Sustainment Contractor turnovers. In addition, A033 will provide requirements for Random Spot Checks, and Asset Inventory Reports.

Last BMT Approval Date 20200309

CHANGE

RECORD

20200309 All DEDs Updated to Latest Version.

ASREQ – As Required SOVT – System Operational Verification Test

DACA – Days After Contract Award

20200309 D1 DED Cover Sheet

AT/FP Internally Originated Document

Deliverable Expectation Document (DED) for AT/FP Ashore

Program Contract CDRL A002 Program Schedule and Progress Report

DED A002

Document Change History Record

Date Pages Section Ver. Reason for Change Entered by

2/3/12 1 Initial Release. A. Martin

12/16/14 2 Multiple Updates. J.

Youkhanna

6/30/14 1, 2, 3, 4, 5, and 9

2.2.1, 2.2.2, 3.0, and Table 2 3

Updated requirements for Program Schedule submissions regarding Execution and Sustainment Contracts. Removal of unnecessary Schedule Milestones.

W. Azzinari

12/18/15 2,3,4,5,6,9,10 ALL 3 Multiple Administrative Updates. W. Azzinari

2/9/16 ALL ALL 4 BMT Review and Approval W. Azzinari

4/11/19 ALL ALL 4 Updated by Follow-on Contracts Working Group.

A. Rock

12/4/19 2, 6 & 9 2.0, 2.4, 2.4.2, & 2.4.6

5 Incorporated A020 summary updates

T. Cullison

2/24/20 8 2.4.3 5 Expanded and clarified content of IAVM reporting

T. Cullison

3/09/20 9 2.4.6 5 Added clarifying detail to content of obsolescence reporting

T. Cullison

1.0 INTRODUCTION

This document provides acceptance criteria for the Program Schedule and Progress Report Contract Data Requirements List (CDRL) deliverable to be submitted by the Contractor as required by the AT/FP Ashore Program Contract Performance Work Statement (PWS) or, if applicable, Task Order PWSs. The acceptance criteria define the requirement for the Government acceptance of the deliverable. This document also clarifies the expected content of the CDRL deliverable and recommends a format to ensure the CDRL deliverable submittal meets the requirements and specifications derived from the AT/FP Ashore Program Contract PWS and Task Order PWSs.

2.0 DELIVERABLE DESCRIPTION

The Program Schedule and Progress Report deliverable shall provide a comprehensive Program Schedule which is updated on a monthly basis and a Monthly Progress Report.

2.1 Applicable Standards

Not applicable to this deliverable.

2.2 Program Schedule Deliverable Requirements

The following requirements are individually applicable to the specific type contract being executed under the AT/FP Ashore Program.

2.2.1 Program Schedule Requirements for the AT/FP Ashore Execution Contracts/Task Orders, i.e., AT/FP Ashore C4I/EM and CBRN Systems Contracts/Task Orders and AT/FP Ashore PS/AC Systems Contracts/Task Orders

The Program Schedule shall track the progress and critical milestones of the Contract or, if applicable, Task Order projects.

The Program Schedule shall be a single document containing a single Contract project or, if applicable, Task Order project at an individual site and submitted in the AT/FP Ashore Remedy System for each project name at that site.

The Program Schedule shall indicate the order in which the Contractor proposes to perform the work and the dates on which the Contractor contemplates starting and completing tasks.

The Program Schedule shall reflect the updated project progress as percent complete values for each project task.

The Program Schedule shall be in the form of a progress chart and indicate task dependencies.

The Program Schedule shall include all on-site work performed and shall clearly show that the work will not interfere with normal Government business.

The Program Schedule shall be baselined at the time of initial submittal and be re-baselined only upon Government approval.

The Program Schedule shall be limited to a total of 50 Milestones. At a minimum, the milestones shown in Table 1 shall be included in the deliverable. The major milestones, indicated in bold type with an asterisk (*) in Table 1, must be spelled exactly as shown (less the asterisk) in the deliverable. Note: Depending on the specific project, the chronological order of the milestones in Table 1 may vary.

The Contractor’s initial submission of the Program Schedule shall be submitted as a CDRL into the AT/FP Ashore Remedy System. Upon approval by the Government, the Contractor’s initial Program Schedule submission will become the approved baseline schedule in accordance with the Contract PWS and, if applicable, Task Order PWSs. Once approved, the Contractor shall synchronize the approved Program Schedule with the AT/FP Information Module (AIM) Portal via Microsoft Project version 2010 (or newer).

The Contractor shall thereafter, on a monthly basis, update the Program Schedule on the AT/FP Information Module (AIM) Portal to reflect the Contractor’s progress as it pertains to the Contract or, if applicable, Task Orders; however, this update does not change the approved baseline schedule that the Contractor is required to be in compliance with in accordance with the Contract PWS and, if applicable, Task Order PWSs. The approved baseline schedule can only be changed through a formal Contract modification or, if applicable, Task Order modification issued by the Contracting Officer.

Table 1 Minimum Required Program Schedule Milestones for Execution Contracts/Task Orders, i.e., AT/FP Ashore C4I/EM and CBRN Systems Contracts/Task Orders and AT/FP Ashore PS/AC Systems Contracts/Task Orders.

(* Indicates Major Milestone)

Milestone

PR

E-

A W

A R

D

Site Approval Submission* (Obtain date from the Government)

Site Approval* (Obtain date from the Government)

Contract Award* (Means Contract Award or Task Order Award as applicable)

PO

ST

-A W

AR

D

Kick-Off Meeting

Submission of A002 Program Schedule and Progress Report

Submission of A009 Accident Prevention Plan (Site Health and Safety Plan)

Submission of A010 Quality Control Plan

Submission of A030 Environmental Plan

Submission of A005 35 Percent *

Submission of A006 System Testing Plans

Equipment Purchase Start*

Submission of A005 100 Percent Pre *

Submission of A005 100 Percent Final

Start of Facility Improvements*

Facility Improvements Complete

Functional System Demonstration / Pre-installation Testing

Submission of A040 Certification & Accreditation (C&A)/Fleet Readiness Certification Board (FRCB) Package

System Installation Start Date*

Certification & Accreditation (PRA)*

System Installation Complete

IUID Tagging Complete

Submission of A033 Completed Asset Data Template

Remedy Loaded with Project Assets Complete

Milestone

SOVT*

SOVT Completion (After Equipment Acceptance)

Submission of A008 System Operations, Maintenance and Training Manuals

Punch List Completion

Submission of A007 As-Built Drawings

Approval of A007 As-Builts*

Submission of A041 Closeout Package

Closeout Package Approved*

Period of Performance Completion*

2.2.2 Program Schedule Requirements for AT/FP Ashore Sustainment Contracts The Program Schedule for Sustainment Contracts shall be used to plan and track Preventive Maintenance activities for the duration of the contract.

One Program Schedule shall be prepared and submitted that includes at a minimum the milestones shown in Table 2. The Preventive Maintenance Schedule milestone shall incorporate all sustained projects included in the contract. Each Project listed within the Preventive Maintenance Schedule milestone shall include tasks that describe the associated preventive maintenance activities and individual scheduled events, duration of each event, and the planned start and end date of each event.

Each task shall indicate the periodicity of the event.

The initial Project Schedule for Preventive Maintenance Schedule shall be included in the CDRL A017 Maintenance Plan submittal as well as in the CDRL A002 Program Schedules and Progress Report submittal. Monthly updates to the Project Schedule for Preventive Maintenance shall be submitted in subsequent monthly CDRL A002 submissions.

The Sustainment Contractor shall prepare and submit an update to the Project Schedule for Preventive Maintenance as an update to the CDRL A002 Program Schedule submission and in addition shall incorporate this new update to the Project Schedule for Preventive Maintenance and an update to the Preventive Maintenance Checklist into the Sustainment Contractor’s Maintenance Plan in accordance with DED A017 when modifications are awarded to the base AT/FP Ashore Program Sustainment Contract. Subsequent monthly updates to the Project Schedule for Preventive Maintenance shall be submitted with the Sustainment Contractor’s monthly CDRL A002 submission.

The Sustainment Contractor shall prepare and provide the following reports from Remedy which shall be submitted as embedded documents with the monthly CDRL A002 submission, Program Schedule and Progress Report submissions: Preventive Maintenance Scheduled, but not preformed; Help Desk Tickets;

Preventive Maintenance Due for Current and Next Month; and the A002 Program Schedule.

Table 2 Minimum Required Schedule Milestones for Sustainment Contracts

Milestone

Award / (MOD) Date

Submission of first A002 Program Schedule and Progress Report

Submission of A009 Accident Prevention Plan (Site Health and Safety Plan)

Submission of A010 Quality Control Plan

Submission of A018 Configuration Management Plan

Submission of A030 Environmental Plan

Submission of first A043 Trend Analysis Reports

Preventive Maintenance Schedule

In accordance with the Sustainment Contract PWS, the Sustainment Contractor shall notify the Navy 311 Help Desk at least 30 days in advance of a preventive maintenance action, in order to have a service call created and assigned back to the Sustainment Contractor. This service call shall be used by the Sustainment Contractor to document work performed during the maintenance activity in the AT/FP Ashore Remedy System. The Sustainment Contractor shall update the Work Log and resolve the service call per the PWS. The Sustainment Contractor shall refer to Appendix B, Contractor User Guide for the AT/FP Ashore Remedy System and AT/FP Information Module (AIM) Portal for specific instructions for updating Work Log entries. Monthly updates to individual tasks within the Program Schedule shall include the associated service call number that was created in the AT/FP Ashore Remedy System.

The Sustainment Contractor’s initial submission of the Program Schedule shall be submitted as a CDRL into the AT/FP Ashore Remedy System. Upon approval by the Government, the Sustainment Contractor’s initial Program Schedule submission will become the approved baseline schedule in accordance with the Sustainment Contract PWS. Once approved, the Sustainment Contractor shall synchronize the approved Program Schedule to include the Preventive Maintenance Schedule with the AT/FP Information Module (AIM) Portal via Microsoft Project version 2010 (or newer). The Sustainment Contractor shall thereafter, on a monthly basis, update the Program Schedule to include the Preventive Maintenance Schedule on the AT/FP Information Module (AIM) Portal to reflect the Sustainment Contractor’s progress as it pertains to the Sustainment Contract; however, this update does not change the approved baseline schedule that the Sustainment Contractor is required to be in compliance with in accordance with the Sustainment Contract PWS. The approved baseline schedule can only be changed through a formal Sustainment Contract modification issued by the Contracting Officer.

2.3 Progress Report Deliverable Requirements for AT/FP Ashore Execution Contracts/Task Orders, i.e., AT/FP Ashore C4I/EM and CBRN Systems Contracts/Task Orders and AT/FP Ashore PS/AC Systems Contracts/Task Orders

The Contractor shall submit the Monthly Progress Reports. The Progress Report shall be a monthly narrative document that details the status of performance of work with respect to the Contract PWS or, if applicable, Task Order PWSs and explains the Contractor’s intended methods and resources for performing the proposed tasks.

The Progress Report shall be cross-referenced to the proposed tasks in the Program Schedule.

The Progress Report shall identify the major milestones/activities and critical path items for work performed during the reporting period and anticipated during the next reporting period including major accomplishments, major milestones achieved, critical path items completed, and CDRLs delivered on the Contract PWS or, if applicable, Task Order PWSs.

The Progress Report shall identify any risks including any issues related to scheduling, cost, and technical or administrative problems, and the steps being taken to mitigate them.

The Progress Report shall include any significant changes to the Contractor’s organization, method of operation, or project timeline.

The Progress Report shall include a summary and status of Engineering Change Proposals (ECPs) and Requests for Information (RFIs).

The Progress Report shall also include any safety and quality issues, current status, and any removal/ demolition planned during the current reporting period and any anticipated in the next reporting period.

2.4 Progress Report Deliverable Requirements for Sustainment Contracts The Progress Report for Sustainment Contracts shall contain the following seven (7) sections:

• SECTION 1 GENERAL

• SECTION 2 SUSTAINMENT ACTIVITIES AND MILESTONES

• SECTION 3 INFORMATION ASSURANCE VULNERABILITY MANAGEMENT

• SECTION 4 PROGRAM RISKS AND CHANGES

• SECTION 5 SAFETY AND QUALITY

• SECTION 6 SUPPORTABILITY STRATEGY SUMMARY UPDATES

• SECTION 7 MEETING MINUTES

2.4.1 Requirements for SECTION 1 GENERAL

This Section shall provide an introduction, scope, and purpose of the Sustainment Contract.

2.4.2 Requirements for SECTION 2 SUSTAINMENT ACTIVITIES AND MILESTONES This Section shall provide the following:

a. Milestones – a narrative description of the major milestones of the Sustainment Contract and a table showing the status of the Minimum Required Schedule Milestones (Table 2 above) for the current reporting period.

b. Sustainment Activities – a narrative description of the Preventive Maintenance (PM) and Corrective Maintenance (CM) activities accomplished during the reporting period. The following items shall be addressed in tabular form in this section:

1. The number of Help Desk PM tickets, CM tickets, and Total tickets opened during the reporting period including the current status of these tickets (Resolved/Closed, Working, or Canceled).

2. The Time Period (Regular Hours, Afterhours, and Weekend) that the tickets were opened during the current reporting period listed by Region and Total.

3. The number of CM Tickets assigned during the reporting period and the number of those tickets that were reassigned during the reporting period listed by Region and Total.

4. The number of PM tickets opened during the reporting period listed in a matrix of Family of Systems (FoS) by Region.

5. A table of all individual PM tickets opened during reporting period listed by Incident Identification and including the following headers based on Remedy Data Fields:

Incident ID

CNIC Incident ID

Submit Date

Last Resolved Date

Summary

Project Name

Project Region

Base (Site)

FoS

6. The number of CM tickets opened during the reporting period listed in a matrix of Family of Systems (FoS) by Region.

c. CDRL Deliverable Activities – A tabular list of all CDRL deliveries this reporting period. The table shall include the Data Item Number, Title, Remedy Entry Number, and Remedy Submittal Date.

d. Response and Resolution Performance Metrics

1. The Response Metric is a narrative and tabular representation of the number of tickets and percentage of tickets that were responded to within the contract required response time during the reporting period versus the number of tickets and percentage of tickets that were not responded to within the contract required response time. The Response Time is measured from the time a ticket is assigned in Remedy until the Remedy Status is changed to “In Progress”. The table shall include the following headers for each Priority Category of ticket:

• Total Number of Tickets

• Number of Tickets within contractual response time

• % of Tickets within contractual response time

2. The Resolution Time Metric is a narrative and graphical representation of the number and percentage of tickets that were resolved within the contract required resolution time during the reporting period. The Resolution Time is measured from the time a ticket is assigned in Remedy until the Remedy Status is change to "Resolved." The table shall include the following headers for each Priority Category of ticket:

• Total Number of Tickets

• Number of Tickets within contractual resolution time

• % of Tickets within contractual resolution time

3. The Family of System (FoS) Resolution Time Metric is a tabular representation of the Resolution Time Metric listed by all Family of System categories applicable to the contract. The table shall include the following headers for each applicable FoS:

• Total Number of Tickets

• Number of Tickets within contractual response time

• % of Tickets within contractual response time

• Number of Tickets within contractual resolution time

% of Tickets within contractual resolution time

2.4.3 Requirements for SECTION 3 INFORMATION ASSURANCE VULNERABILITY

MANAGEMENT (IAVM)

This Section shall provide the following information for the applicable reporting period:

a. A summary of the Information Assurance support efforts accomplished, including remediation efforts for CAT-1 scan findings and incomplete patching.

b. Administrative and training tasks performed.

c. A table and narrative description of the Vulnerability Scans completed by Region and Systems Targeted, to also include:

1. Date scan was scheduled and date scan was completed,

2. Total number of hosts requiring scanning,

3. Total number of hosts successfully scanned,

4. Total number of hosts failing to scan,

5. Number of findings less than 30-days old (with criticality),

6. Number of findings older than 30-days old (with criticality),

d. A table and narrative description of the Patching completed by date, Region and

Systems Targeted, to also include:

1. Total number of assets requiring specified patch,

2. Deadline for each patch,

3. Date patching completed,

4. Percentage of assets successfully patched,

5. Percentage of assets that failed to patch successfully.

e. A description of the IAVM Communication Task Order efforts performed.

f. A table of IAVM Program meetings attended including date, time, attendees invited, and discussion topics.

2.4.4 Requirements for SECTION 4 PROGRAM RISKS AND CHANGES

This Section shall provide the following information for the applicable reporting period:

a. A description and recommended mitigation for all Program Schedule Risks.

b. A description and recommended mitigation for all Program Technical Risks.

c. A description of any significant Program changes.

d. A table listing of the active ECPs, PDRs, and RFIs including related ticket number if any, date, title, and NAVFAC and general comments.

2.4.5 Requirements for SECTION 5 SAFETY AND QUALITY

This Section shall provide the following information for the applicable reporting period:

a. A description of all safety related events held and inspections conducted.

b. A description of any quality initiatives taken and process improvements implemented.

c. A table of Safety incidents to include a description of the incident, and actions taken to resolve the problem and steps taken for prevention.

2.4.6 Requirements for SECTION 6 SUPPORTABILITY STRATEGY SUMMARY UPDATES This Section shall provide the following information for the applicable reporting period:

a. A table identifying any changes to the locations of forward supply points and the inventory of supply parts maintained at each location,

b. An updated list of support positions required under the applicable contract, identifying positions added or removed by location, and any change of personnel assignments to existing positions,

c. Updates, if any, to the initial list of critical system operations and implemented strategies to prevent potential failures that will cause critical system outages,

d. Updates, if any, to tracking of technology (hardware and software), and associated licenses and Service Level Agreements (SLAs) identified as obsolete and/or due for renewal, predicted issues that will result from technology obsolescence, and developed solutions that extend the viability of the AT/FP Ashore Systems/Equipment into the foreseeable future.

Updates shall be provided in a timely manner so as to provide the government sufficient time to review and approve proposed solutions, in accordance with program processes, prior to implementation,

e. Updates, if any, to the list of business relationships established and maintained with Original Equipment Manufacturers (OEMs),

f. A summary list of Cybersecurity/Risk Management Framework Assessment & Authorization actions in relation to STIG checks/assessments completed, with their respective outcomes,

g. An updated list of all Engineering Change Proposals (ECPs) submitted for processing, with their current status.

2.4.7 Requirements for SECTION 7 MEETING MINUTES

This Section shall provide the following information for the applicable reporting period:

a. A description of all meetings held at each region during the month to include actions.

2.4.8 Appendices

The monthly Progress Report for Sustainment shall contain an appendix of acronyms and an appendix of supporting files to substantiate the information in the report.

2.5 Deliverable Format – All Contracts/Task Orders

The Contractor shall prepare the Program Schedule deliverable in Microsoft Project (version 2010 or Newer) and Portable Document Format (PDF).

The Progress Report deliverable shall contain a Title Page, Table of Contents, and numbered pages. The Contractor shall prepare the Progress Report deliverable in Microsoft Word and PDF.

Files submitted to the AT/FP Ashore Remedy System shall adhere to the following file naming convention:

AAAABBBBBBBC…CDDDEEEEFFFFF.GGG

Where A = CDRL Number, B = Last 4 digits of Contract Number and, if applicable, 3 digit Task Order Number, C = Region Name, D = 3 Digit Month Abbreviation, E = 4 Digit Year, F = Revision or Version Number, and G = File Name Extension.

Example Contract only: A0021201CNRMAJun2013Rev01.pdf (Do not use spaces).

Example Task Order: A0021201012CNRMAJun20113Rev01.pdf (Do not use spaces)

3.0 KEY DELIVERABLE SUBMITTAL DATES AND METHOD OF DELIVERY – All Contracts/Task Orders

The following requirements are individually applicable to the specific type of contract being executed under the AT/FP Ashore Program.

3.1 Program Schedule and Progress Report Deliverable Submittal Dates and Method of Delivery for AT/FP Ashore Execution Contracts/Task Orders, i.e., AT/FP Ashore C4I/EM and CBRN Systems Contracts/Task Orders and AT/FP Ashore PS/AC Systems Contracts/Task Orders are provided as follows:

Deliverables shall be submitted in accordance with the dates identified in Appendix D, Data Requirements Checklist and DED Package.

The Contractor’s initial submission of the Program Schedule shall be submitted as a CDRL into the AT/FP Ashore Remedy System. Upon approval by the Government, the Contractor’s initial Program Schedule submission will become the approved baseline schedule in accordance with the Contract PWS and, if applicable, Task Order PWSs. Once approved, the Contractor shall synchronize the approved Program Schedule with the AT/FP Information Module (AIM) via Microsoft Project version 2010 (or newer). The Contractor shall thereafter, on a monthly basis, update the Program Schedule on the AT/FP Information Module (AIM) Portal to reflect the Contractor’s progress as it pertains to the Contract or, if applicable, Task Order; however, this update does not change the approved baseline schedule that the Contractor is required to be in compliance with in accordance with this Contract PWS and, if applicable, Task Order PWSs. The approved baseline schedule can only be changed through written approval of the AT/FP Ashore Sustainment Director.

The Contractor shall submit the Progress Report monthly into the AT/FP Ashore Remedy System. The Contractor shall also provide all deliverables via electronic submission to the Contracting Officer.

3.2 Program Schedule and Progress Report Deliverable Submittal Dates and Method of Delivery for AT/FP Ashore Sustainment Contracts are provided as follows:

Deliverables shall be submitted in accordance with the dates identified in Appendix D, Data Requirements Checklist and DED Package.

The Sustainment Contractor’s initial submission of the Program Schedule shall be submitted as a CDRL into the AT/FP Ashore Remedy System. Upon approval by the Government, the Sustainment Contractor’s initial Program Schedule submission will become the approved baseline schedule in accordance with the Contract PWS. Once approved, the Sustainment Contractor shall synchronize the approved Program Schedule to include the Preventive Maintenance Schedule with the AT/FP Information Module (AIM) Portal via Microsoft Project version 2010 (or newer). The Sustainment Contractor shall thereafter, on a monthly basis, update the Program Schedule to include the Preventive Maintenance Schedule on the AT/FP Information Module (AIM) Portal to reflect the Sustainment Contractor’s progress as it pertains to the Sustainment Contract; however, this update does not change the approved baseline schedule that the Sustainment Contractor is required to be in compliance with in accordance with the Sustainment Contract PWS. The approved baseline schedule can only be changed through written approval of the AT/ FP Ashore Sustainment Director.

The Sustainment Contractor shall submit the Progress Report monthly into the AT/FP Ashore Remedy System. The Sustainment Contractor shall also provide all deliverables via electronic submission to the Contracting Officer.

4.0 ACCEPTANCE CRITERIA – All Contracts/Task Orders

The following is the minimum acceptance criteria:

Deliverable meets all requirements from Section 2.0 and Section 3.0.

Deliverable meets the general review criteria (e.g., pages numbered, free of formatting and spelling errors, clearly written, no incomplete sections, etc.). Table of Contents depicts the correct page number, including Appendices or enclosures (e.g., Appendices and Enclosures are correctly labeled and referenced in Table of Contents).

Deliverable Expectation Document (DED) for

AT/FP Ashore Program Contract CDRL A009 Accident Prevention Plan

DED A009

AT/FP Ashore Deliverable Expectation Document (DED) for CDRL A009 Accident Prevention Plan

Date Pages Section Ver. Reason for Change Entered by

04/02/2012 1 Initial Release A. Martin

07/02/2012 All 2 Updated for consistency with the requirements of U.S. Army Corps of Engineers EM 385-1-1, Appendix A.

A. Martin

08/27/12 All 3 Total rewrite to provide more specific requirements.

A. Martin

11/01/12 All 4 Rewrite to clarify some requirements and to break out the requirements for Sustainment Contracts and Execution Contracts separately.

A. Martin

12/08/15 1, 3, 5 2.3.1, 2.3.2, 2.4 4 Administrative updates. W. Azzinari

03/29/19 All 5 Updated by Follow-on Contracts Working Group

A. Rock

04/16/19 All 5 Incorporated small changes K. Nash

Subject: Deliverable Expectation Document (DED) for AT/FP Ashore Program Contract

CDRL A009 Accident Prevention Plan

Version No: 5 Revision No: 0

Revision Date:

20190416

This document provides acceptance criteria for the Accident Prevention Plan (APP) Contract Data Requirements List (CDRL) deliverable to be submitted by the Contractor as required by the AT/FP Ashore Program Contract Performance Work Statement (PWS). The acceptance criteria define the requirement for the Government acceptance of the deliverable. This document also clarifies the expected content of the CDRL deliverable and recommends a format to ensure the CDRL deliverable submittal meets the requirements and specifications derived from the AT/FP Ashore Program Contract PWS.

2.0 DELIVERABLE DESCRIPTION

The Accident Prevention Plan (APP) is a site and system specific plan that applies to all personnel and work-related activities operating in and around all Navy sites/installations worldwide. The plan is intended to result in the establishment and maintenance of a safe and healthful working environment for all employees working at Navy sites/installations worldwide.

2.1 Applicable Standards

• U.S. Army Corps of Engineers, Safety and Health Requirements, EM 385-1-1 is the governing standard for this contract. The most current version of this manual is available at:

• http://www.usace.army.mil/SafetyandOccupationalHealth/SafetyandHealthRequirementsManual.aspx

• ANSI/ASSE A10.38 Basic Elements of an Employer's Program to Provide a Safe and Healthful Work Environment.

• FAR 52.236-13, Accident Prevention Clause cited in the AT/FP Ashore Program Contract.

• Occupational Safety and Health Administration (OSHA) regulations (29 CFR Part 1926 and 29 CFR Part 1910).

• U.S. Department of Transportation's Manual on Uniform Traffic Control Devices (MUTCD).

• NAVFACINST 5100.11J, 0306 Contractor Mishap Investigating and Reporting.

2.2 References

The NAVFAC Headquarters Safety website provides the Contractor with Safety resources, accident reporting forms, and Contractor forums and training. The information is advisory in nature and does not supersede the requirements of the applicable standards in section 2.1. The NAVFAC Headquarters Safety website is available at:

https://portal.navfac.navy.mil/portal/page/portal/navfac/navfac_ww_pp/navfac_hq_pp/navfac_sf_pp.

The Activity Hazard Analysis (AHA) form to be used for this contract is available at:

http://www.usace.army.mil/SafetyandOccupationalHealth/ActivityHazardAnalysis.aspx.

2.3 Deliverable Requirements

2.3.1 Requirements for Sustainment Contracts

The Contractor's safety program for Sustainment Contracts shall consist of two tiers: a Regional APP which shall contain generic Activity Hazard Analysis (AHAs), and Installation APPs, which shall contain AHAs tailored to the site conditions at each Installation. The Installation AHAs shall be specific to the hazards associated with the activities/tasks to be performed at the installation. The contractor's technicians who will perform the work are required to complete the AHAs for hazards associated with http://www.usace.army.mil/SafetyandOccupationalHealth/SafetyandHealthRequirementsManual.aspx http://www.usace.army.mil/SafetyandOccupationalHealth/SafetyandHealthRequirementsManual.aspx https://portal.navfac.navy.mil/portal/page/portal/navfac/navfac_ww_pp/navfac_hq_pp/navfac_sf_pp https://portal.navfac.navy.mil/portal/page/portal/navfac/navfac_ww_pp/navfac_hq_pp/navfac_sf_pp http://www.usace.army.mil/SafetyandOccupationalHealth/ActivityHazardAnalysis.aspx http://www.usace.army.mil/SafetyandOccupationalHealth/ActivityHazardAnalysis.aspx activities or tasks, and submit the AHAs to the PWO/FEAD, or designated representative for acceptance. The Installation AHAs are to be completed prior to the performance of the work.

The Contractor’s safety organization shall at a minimum consist of the following:

• Two (2) full-time Corporate Safety and Health Officers (CSHO), one responsible for CONUS activities and one responsible for OCONUS activities. These individuals shall have overall responsibilities for management of all aspects of the Safety Program within their area of responsibility. These individuals shall at a minimum meet all requirements stated in

• EM385-1-1, paragraph 01.A.17 Contractor Site Safety and Health Officer (SSHO). Each individual shall be qualified to stand in for the other and shall travel to regions to perform necessary oversight of the safety program.

• The Contractor shall designate a Regional Safety Officer to be responsible for oversight of the Safety Program in each region/area as defined in the Contract PWS and Task Order PWSs. The Regional Safety Officer is a collateral responsibility and this individual may have other responsibilities within the assigned region/area of responsibility. The Regional Safety Officer shall at a minimum have completed the OSHA 30-Hour training course.

• The Regional Safety Officer shall designate a Site Safety and Health Officer (SSHO) to be responsible for the safety and health for the specific project/site. SSHO shall at a minimum meet all the requirements stated in EM 385-1-1, paragraph 01.A.17.

• Site safety management shall be a collateral duty assigned to the Contractor’s on-site supervisor or Quality Control manager. All contractor employees shall receive safety and health indoctrination as required by EM 385-1-1 01.B.02. When required by the AHA, a competent/qualified person shall be on site at all times when that activity is being performed.

The Contractor’s Safety Plan shall conform to EM 385-1-1 section 01 and will be structured as follows:

• The Contractor shall prepare a Regional APP and Installation APPs using the outline, following the order, and addressing applicable activities in EM 385-1-1, Appendix A.

• The Regional APP shall be prepared by Qualified Person(s) and shall include "generic" AHAs and competent/qualified person training requirements for all activities to be performed under the contract.

• An Installation APP for each Installation (site) identified in the Contract PWS and Task Order PWSs shall be prepared by a Qualified Person. Each Installation APP shall identify specific activities to be performed at each Installation (site), contain AHAs tailored to meet specific site conditions and be specific to the hazards associated with the activities/tasks to be performed at the installation, and list the competent/qualified persons at each Installation required to be on site per the AHA. The contractor's technicians who will perform the work are required to complete the AHAs. The Contractor shall indicate, by name, the competent/qualified person(s) who will be on-site for a particular activity when submitting the AHAs for the site. The Installation AHAs shall be completed prior to the performance of the work.

• The Contractor shall incorporate activities requiring on-site presence of competent/qualified persons on the Contractor’s progress schedule/execution plans.

• The Contractor’s Safety Plan shall be compiled as follows: An Accident Prevention Plan (APP) for each Region with tabbed appendices for each Installation APP within that Region. The tabbed appendices shall include all site specific information for each Installation with detailed Accident Hazardous Activities (AHAs) for all hazardous activities expected to take place at the Installation.

• The Contractor’s Corporate SSHOs are responsible for the preparation and approval of the Regional and Installation APPs and all AHAs. The Regional and Installation APPs with attached AHAs and other appropriate documentation required by EM 385-1-1, and other references cited in EM 385-1-1, and this contract shall be submitted to the designated NAVFAC office for acceptance. Note: Government Designated Authority (GDA) and Safety and Occupational Health Office (SOHO) referenced in the EM 385-1-1 for this contract are the designated NAVFAC office.

• The APPs shall address accident investigations/accident reporting. The Contractor shall conduct an accident investigation for 1) recordable injuries and illnesses, 2) Medical treatment administered by a physician or by registered professional personnel under the standing orders of a physician (Medical treatment does not include first aid treatment even though provided by a physician or registered personnel.), 3) property damage accidents resulting in at least $20,000 in damages, and

4) near misses as defined in EM 385-1-1, to establish the root cause(s) of the accident. Complete the applicable NAVFAC Contractor Incident Reporting System (CIRS) form, and electronically submit via the NAVFAC Enterprise Safety Applications Management System (ESAMS). The Contracting Officer’s Representative (COR) will assist the Contractor in obtaining access to ESAMS and will provide copies of any required or special forms. Contractor SSHO will contact the Base/Site Safety Manager (SSM) for help regarding the entry of the report to ESAMS.

• The Contractor shall update/revise the APPs and AHAs as required due to changes in personnel, changing conditions, changes in regulations, or any other reason which would prompt a change. All changes shall be approved by the Regional Safety Officer and Corporate SSHOs and submitted to the designated NAVFAC office for acceptance.

2.3.2 Requirements for Execution Contracts

The Contractor’s safety organization shall at a minimum consist of the following:

• A Corporate Safety and Health Officer (CSHO) with overall responsibility for the safety program in all Regions and Installations defined in the Contract PWS and Task Order PWSs. This individual shall have overall responsibilities for management of all aspects of the Safety Program within the area of responsibility. The individual shall at a minimum meet all requirements stated in EM-

• 385-1-1, paragraph 01.A.17.

• Site safety management shall be a collateral duty assigned to the Contractors on-site supervisor or Quality Control manager. All contractor employees shall receive safety and health indoctrination as required by EM 385-1-1 01.B.02. When required by the AHA, a competent/qualified person shall be on site at all times when that activity is being performed.

The Contractor’s Safety Plan shall conform to EM 385-1-1 section 01 and shall be structured as follows:

• The Contractor shall prepare a Regional APP which shall contain generic AHAs, and Installation APPs which shall contain AHAs tailored to the site conditions at each Installation. The APPs shall use the outline, follow the order, and address applicable activities in EM 3851-1, Appendix A.

NOTE: Paragraph 11 of Appendix A does not apply to this contract.

• The Regional APP shall be prepared by Qualified Person(s) and shall include "generic" AHAs and competent/qualified person training requirements for all activities to be performed under the contract.

• An Installation APP for each Installation (site) identified in the Contract PWS and Task Order PWSs shall be prepared by a Qualified Person. The Installation AHAs shall be specific to the hazards associated with the activities/tasks to be performed at the installation. The contractor's technicians who will perform the work are required to complete the AHAs for the hazards associated with the activities/tasks and submit the AHAs to the PWO/FEAD, or designated representative for acceptance. The Installation AHAs are to be completed prior to the performance of the work.

• The Contractor shall incorporate activities requiring on-site presence of competent/qualified persons on the Contractor’s progress schedule/execution plans.

• The Contractor’s Safety Plan shall be compiled as follows: An Accident Prevention Plan (APP) for each Region with tabbed appendices for each Installation APP within that Region. The tabbed appendices shall include all site specific information for each Installation with detailed Accident Hazardous Activities (AHAs) for all hazardous activities expected to take place at the Installation.

• The Contractor’s CSHO is responsible for the preparation and approval of the Regional and Installation APPs and all AHAs. The Regional and Installation APPs with attached AHAs and other appropriate documentation required by EM 385-1-1, and other references cited in EM 385-1-1, and this contract shall be submitted to the designated NAVFAC office for acceptance. Note:

Government Designated Authority (GDA) and Safety and Occupational Health Office (SOHO) referenced in the EM-385-1-1 for this contract are the designated NAVFAC office.

• The APPs shall address accident investigations/accident reporting. The Contractor shall conduct an accident investigation for 1) recordable injuries and illnesses, 2) Medical treatment administered by a physician or by registered professional personnel under the standing orders of a physician (Medical treatment does not include first aid treatment even though provided by a physician or registered personnel.), 3) all property damage accidents, and 4) near misses as defined in EM 385-1-1, to establish the root cause(s) of the accident. Complete the applicable NAVFAC Contractor Incident Reporting System (CIRS) form, and electronically submit via the NAVFAC Enterprise

• Safety Applications Management System (ESAMS). The Contracting Officer’s Representative (COR) will assist the Contractor in obtaining access to ESAMS and will provide copies of any required or special forms. Contractor SSHO will contact the Base/Site Safety Manager (SSM) for help regarding the entry of the report to ESAMS.

• The Contractor shall update/revise the APPs and AHAs as required due to changes in personnel, changing conditions, changes in regulations, or any other reason which would prompt a change. All changes shall be approved by the SSHO and submitted to the designated NAVFAC office for acceptance.

2.4 Deliverable Format

The Contractor shall provide the deliverable associated with CDRL A009 in Microsoft Office Word and in Portable Document Format (PDF).

Files submitted to the AT/FP Ashore Remedy System shall adhere to the following file naming convention:

AAAABBBBBBBC…CDDDEEEEFFFFF.GGG

Where A = CDRL Number, B = Last 4 digits of Contract Number and 3 Digit Task Order Number, C = Region Name, D = 3 Digit Month Abbreviation, E = 4 Digit Year, F = Revision or Version Number, and G = File Name Extension.

Example: A0305025CNRMAJun2011Rev01.pdf (Do not use spaces)

The Contractor shall also create hardcopies of the Regional APP and generic AHAs; and the Installation (Site) APPs and the AHAs specifically tailored to each activity. These hardcopies shall follow the format in EM 385-1-1 Appendix A and be provided to the FEC and each Installation. Example follows:

• Three ring binder that contains a hardcopy of the Regional Accident Prevention Plan organized in Tab Sections 1 through 9 as follows:

1. Signature Sheet.

2. Corporate and Regional Safety Organization, identifying corporate SHOs and Regional Safety Officers by name and qualification.

3. Statement of Safety and Health Policy.

4. Responsibilities, Lines of Authority, and procedures for risk analysis, APP/AHA review and updating, accident and near-miss analysis, and other plans required by the EM 385-1-1.

5. Subcontractors and Supplier safety policy and requirements.

6. Training.

7. Safety and Health Inspections.

8. Plans (Programs, Procedures) Required by the Safety Manual.

9. Generic AHAs.

• Three Ring Binder that contains a hardcopy of the Installation APP organized in Tabs as follows:

1. Signature Sheet

2. Corporate and Regional Safety Organization identifying Regional Safety Manager and Competent /Qualified persons by name and qualification.

3. Statement of Safety and Health Policy.

4. Responsibilities, Lines of Authority, and procedures for risk analysis, APP/AHA review and updating, accident and near-miss analysis, and other plans required by the EM 385-1-1.

5. Subcontractors and Suppliers safety requirements.

6. Training.

7. Safety and Health Inspections.

8. Specific Information for each Installation

a. Accident Reporting, including all NAVFAC and Installation forms.

b. Plans (Programs, Procedures) Required by the Safety Manual.

c. AHAs, listing Competent/Qualified persons by name and qualification.

d. OCONUS equivalent safety practices.

3.0 KEY DELIVERABLE SUBMITTAL DATES AND METHOD OF DELIVERY

Deliverables shall be submitted in accordance with the dates identified in Appendix D, Data Requirements Checklist and DED Package.

The Contractor shall electronically provide all deliverable submissions to the Administrative Contracting Officer (ACO) and the AT/FP Ashore Remedy System.

4.0 ACCEPTANCE CRITERIA

The following are the minimum acceptance criteria:

• Deliverable meets all requirements in Section 2.0 and 3.0.

• Deliverable meets the general review criteria (e.g., pages numbered, free of formatting and spelling errors, clearly written, no incomplete sections, etc.). Table of Contents depicts the correct page number, including Appendices or enclosures (e.g., Appendices and Enclosures are correctly labeled and referenced in Table of Contents).

AT/FP Ashore Program Contract CDRL A010 Quality Control Plan

DED A010

Subject: Deliverable Expectation Document (DED) for AT/FP Ashore Program Contract CDRL A010 Quality Control Plan

Version No: 2

Revision No: 0

Revision Date:

20190329

AT/FP Internally Originated Document

Deliverable Expectation Document (DED) for AT/FP Ashore Program Contract CDRL A010 Quality Control Plan

DED A010

Document Change History Record

Date Pages Section Ver. Reason for Change Entered by

9/24/12 1 Initial Release A. Martin

3/29/19 ALL ALL 2

Reviewed by Follow-on Contracts Working Group

A. Rock3/29/19

7/10/20 ALL ALL 3 Additional verbiage added for Incident Ticket accuracy T. Jasso

DED A010

1.0 INTRODUCTION

This document provides acceptance criteria for the Quality Control Plan Contract Data Requirements List (CDRL) deliverable to be submitted by the Contractor as required by the AT/FP Ashore Program Contract Performance Work Statement (PWS). The acceptance criteria define the requirement for the Government acceptance of the deliverable. This document also clarifies the expected content of the CDRL deliverable and recommends a format to ensure the CDRL deliverable submittal meets the requirements and specifications derived from the AT/FP Ashore Program Contract PWS.

2.0 DELIVERABLE DESCRIPTION

The Quality Control Plan describes the Contractor’s plan to ensure a quality product is provided to the Government. The plan includes the processes, practices, procedures, and methodologies employed by the Contractor on the Contract.

2.1 Applicable Standards

ISO-9001 Quality Management Systems -- Requirements

ITIL v4 or later - Service Management Practices - Incident Management

2.2 Deliverable Requirements

The Contractor shall establish and maintain a complete Quality Control (QC) program in accordance with the provisions specified herein. The Contractor’s QC Program shall provide an effective and efficient means of identifying and correcting problems throughout the entire scope of project operations for the Contract.

The Contractor’s QC Program shall address the following requirements:

Accurate documentation of work processes, procedures, and output measures.

A systematic process for assessing compliance with performance objectives and standards as defined in the AT/FP Ashore Program Contract and Performance Assessment Plan & Functional Assessment Plan (FAP).

Accurate documentation of quality inspections conducted throughout the execution of work.

A systemic process for ensuring accurate information is recorded in Incident tickets identifying root cause, resolution of the ticket and identification of any and all assets related to the incident.

Contractor corrective actions and process adjustments to be implemented as driven by Government assessments or Contractor self-assessments.

The Quality Control Plan shall include a formal statement of the Contractor’s Quality Control Policy and a description of the Contractor’s Quality organization including a chart which details individual personnel by name, quality organizational roles, responsibilities, and qualifications.

The Plan shall include a list of outside organizations, such as testing laboratories, architects, and consulting engineers that will be employed by the Contractor, a description of the services/products these firms will provide, and a description of how the Contractor plans to manage these firms to ensure the quality of the services/products.

The plan shall identify potential and actual problem areas and resulting corrective actions throughout the life of the contract. It shall provide for inspections and testing that will ensure compliance with the Contract.

The Plan shall identify all methods of reporting Quality activities to the Government including periodicity and any Contractor standard forms to be used for this reporting.

DED A010

The Quality Control Plan shall be consistent with the Contractor’s submissions for CDRL A006, System Testing Plans and the System Requirements Verification Matrix (SRVM) in the applicable Performance Specifications of the Contract.

The Plan shall describe the practices and procedures to be followed for reporting, tracking, and resolving problems and issues identified in products,…