Appendix D2 New Install 20200224.pdf

AT/FP Ashore Sustainment Contracts – New Installation ECPs

Data Requirements Checklist and DED Package

Appendix D2

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 TOA Monthly In

AIM 20200309 V5 1

A005 Installation Design Plan – 35 Percent Design -210 INST None 20190909 V6 1

A005 Installation Design Plan – 100 Percent Pre-Final Design -180 INST None 20190909 V6 1

A005 Installation Design Plan – 100 Percent Final Design (For Construction) -30 INST None 20190909 V6 1

A006 System Testing Plans -210 INST 10 SOVT 20190329 V4 1

A007 As Built Drawings 30 AEA None 20190329 V3 1, 3

A008 System Operations, Maintenance, and Training Manuals 10 AEA None 20190329 V2 1

A009 Accident Prevention Plan 30 TOA None 20190416 V5 2

A010 Quality Control Plan 30 TOA None 20190329 V2 1

A030 Environmental Plan 30 TOA None 20190329 V3 2

A033 Completed Asset Data Template -10 SOVT None 20190411 V4 1

A040 Risk Management Framework (RMF) Assessment and Authorization (A&A) /Fleet Readiness Certification Board (FRCB) Package

-150 INST None 20191219 V3 4

A041 Closeout Package 45 AEA None 20190329 V3 4

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

Note 2 - Single document for each Region containing all Projects for each Base/site; submitted in Remedy for each Project Name in that Region and at that Base/Site.

Note 3 – CDRL A007 requires twenty (20) working days for Government review.

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

Last BMT Approval Date 20200309

CHANGE

RECORD

20200309 Updated all DEDs to Latest Version.

AEA – After Equipment Acceptance INST – Installation

TOA – Task Order Award SOVT – System Operational Verification Test

20200309 Sustainment Contracts - New Install ECPs App D2 Data Requirements Checklist.docx

Deliverable Expectation Document (DED) for

AT/FP Ashore Program Contract CDRL A002 Program Schedule and Progress Report

DED A002

Subject: Deliverable Expectation Document (DED) for AT/FP Ashore Program Contract CDRL A002 Program Schedule and Progress Report

Version No: 5 Revision No: 1

Revision Date:

20200224

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

DED A002

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).

DED A002

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-

AW

AR

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

DED A002

Milestone

Remedy Loaded with Project Assets Complete

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.

DED A002

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.

DED A002

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

DED A002

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:

DED A002

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, DED A002

d. Updates if any to the identified technology, 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,

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

DED A002

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).

Program Contract CDRL A005 Installation Design Plan (IDP)

DED A005

Date Pages Section Ver. Reason for Change Entered by

02/03/12 1 Initial Release A. Martin

08/27/12 5

2.2.2

2.2.2

Table 1

2.3

2 Clarified drawing requirements.

Corrected UFC number.

Added requirement for SPIDER Tracking Number.

Added Section number reference.

A. Martin

11/14/12 Various 3 Updated to include detailed Preliminary Design Review and Critical Design Review requirements

M. Holmes

02/25/14 1-10

Section 2

Section 3

4 Updated to allow for the use of the 35% Drawing Template and change A/E/C CAD Standard Release 4.0 to 5.0

Updated to allow submission of large native files to AIM

M. Jahn

V.

Racanelli

03/29/19 ALL ALL 5 Updated by Follow-on

Contracts Working Group

A. Rock

09/09/19 ALL ALL 6 Update to latest version of

UFC reference

T. Cullison

Subject: Deliverable Expectation Document (DED) for AT/FP Ashore Program Contract CDRL A005 Installation Design Plan (IDP)

Version No: 6

Revision No: 0

Revision Date:

20190919

1.0 INTRODUCTION

This document provides acceptance criteria for the Installation Design Plan (IDP) 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) and 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 PWS and Task Order PWSs.

2.0 DELIVERABLE DESCRIPTION

The IDP is comprehensive in identifying the steps required to integrate and install both Government and Contractor furnished material and equipment and achieve a fully functional system in accordance with the AT/FP Ashore Performance Specification (P-Spec), the AT/FP Ashore Program Contract PWS, and site specific details in the Task Order PWS. This DED is applicable to all Task Orders issued under an AT/FP Ashore Program Contract. . IDP documentation delineates all system configurations and interfaces and permits engineers, technicians and administrators to locate and interpret diagnostic indicators, trace electronic signal flow, evaluate parameters and settings, measure and verify signal levels with sufficient speed and accuracy so as to restore operation and maintain optimal system performance.

The IDP is submitted three times. First as an IDP 35% Design followed by the IDP 100% Pre- Final Design and finally as the IDP 100% Final Design (For Construction) submittal. The IDP 100% Final Design (For Construction) drawings are the updated 100% Pre-Final Design drawings that are submitted to the Government after the Critical Design Review (CDR).

The respective IDPs (35% Design and 100% Pre-Final Design) will be reviewed by the Government prior to and will be a basis of discussion at the Preliminary Design Review (PDR) and Critical Design Review (CDR) respectively. The Contractor will develop PDR and CDR briefs and present them during the PDR and CDR events, respectively, to ensure that adequate design progress, maturity and compliance warrants proceeding. The 100% Final Design (For Construction) IDP review is an informal review to ensure that the issues and/or deficiencies noted at CDR have been adequately addressed prior to construction/installation.

The systems developed for the AT/FP Ashore Program can either be defined as Command, Control, Communications, Computers, and Intelligence (C4I) or as electronic systems or sub-systems that interface with a Navy C4I system or network. For this reason, the IDPs shall follow guidance from the FRCB Handbook (SPAWAR M-3090.2A). There are two types of systems classified in M-3090.2A and they are as follows:

M-3090.2A 3rd Party Installations

M-3090.2A defines 3rd Party submissions as all projects excluding those funded or executed by a SPAWAR Team. The IDP for 3rd Party submissions shall include a single set of Design drawings containing both Facilities (Construction) and Systems details following the requirements detailed in paragraph 2.2.2 and Table 1.

M-3090.2A OCF Installations

M-3090.2A defines OCF submissions as jobs funded directly to SPAWAR System Centers where SPAWAR System Centers perform the installation.

The IDP for OCF submissions shall include a set of Design drawings made up of two (2) parts: a Systems Design drawing set following the SPAWAR Shore Installation Process Handbook (SIPH) Version 3.0, and a Facilities

Design (Construction) drawing set following DoD UFC 1-300-09N and A/E/C CAD Standard Release 5.0 detailed in Paragraph 2.2.3 and Table 2.

2.1 Applicable Standards (Unless Otherwise Specified Use Latest Version)

2.1.1 Applicable Standards for M-3090.2A 3rd Party Installation Task Orders

UFC 1-200-01, Change 2, General Building Requirements

UFC 1-300-09N, Change 8, Design Procedures

UFC 3-200-10N, Civil Engineering, Section 3-2.4

UFC 3-501-01, Change 2, Electrical Engineering

UFC 3-580-01, Telecommunications Building Cabling Systems Planning and Design

UFC 4-022-01, Security Engineering: Entry Control Facilities/Access Control Points

UFC 4-022-02, Selection and Application of Vehicle Barriers

UFC 3-301-01, Structural Engineering

UFC 3-550-01, Exterior Electrical Power Distribution

UFC 4-021-01, Design and O&M: Mass Notification Systems

NFPA 730, Guide for Premises Security

NFPA 731, Standard for the Installation of Electronic Premises Security Systems

ASME Y14.100-2004 (R2009), Engineering Drawing Practices

UFC-2-000-05N (formerly NAVFAC P-80.3 E) Facility Planning Factor Criteria for Navy and Marine Corps Shore Installations, Appendix E, Airfield Safety Clearances

Design Drawings in accordance with NAVFAC guidelines and applicable standards posted at Whole Building Design Guide, Computer-Aided Design and Drafting (CADD) Library and NAVFAC CADD Resources (A/E/C CAD Standard, Release 5.0), available at http://www.wbdg.org/ccb/browse_org.php?o=78.

SPAWAR M-3090.2A, Fleet Readiness Certification Board (FRCB) Handbook

Applicable Standards listed in AT/FP Ashore Performance Specifications (P- Specs).

2.1.2 Applicable Standards for M3090.2A OCF Task Orders

UFC 1-200-01, Change 2, General Building Requirements

UFC 3-301-01, Structural Engineering

UFC 1-300-09N, Change 8, Design Procedures, UFC 3-120-10N, Interior Design

UFC 3-501-01, Electrical Engineering

UFC 3-580-01, Telecommunications Building Cabling Systems Planning and Design http://www.wbdg.org/ccb/browse_org.php?o=78

UFC 3-580-10, Navy and Marine Corps Intranet (NMCI) Standard Construction Practices

UFC 3-600-01, Fire Protection Engineering for Facilities

UFC 4-021-01, Design and O&M: Mass Notification Systems

UFC 4-021-02NF, Security Engineering: Electronic Security Systems

UFC 3-301-01, Structural Engineering

UFC 3-550-01, Exterior Electrical Power Distribution

NFPA 730, Guide for Premises Security

NFPA 731, Standard for the Installation of Electronic Premises Security Systems

ASME Y14.100-2004 (R2009), Engineering Drawing Practices Facilities Design Drawings in accordance with NAVFAC guidelines and applicable standards posted at Whole Building Design Guide, CAD Library and NAVFAC CADD Resources (A/E/C CAD Standard, Release 5.0), available at http://www.wbdg.org/ccb/browse_org.php?o=78.

Systems Design Drawings in accordance with SPAWAR Shore Installation Process Handbook (SIPH) version 3.0, Appendices Q1 and Q2. The SIPH is provided as GFI for only SPAWAR-installed systems.

SPAWAR M-3090.2A, Fleet Readiness Certification Board (FRCB) Handbook

Applicable Standards listed in AT/FP Ashore P-Specs.

2.2 Deliverable Requirements

IDP documentation shall contain sufficient detail for interpretation, reviews, excavation/ fabrication/installation, troubleshooting, and maintenance of the system to be installed, relocated, or modified per the AT/FP Ashore Program Contract PWS and Task Order PWSs or other AT/FP Ashore funded Task Orders. This documentation shall:

Provide hardware and software interfaces between new AT/FP equipment to be installed and existing Government AT/FP equipment, including installation utility interfaces and data protocol used to transmit information.

Provide the location of vegetation, infrastructure, utilities, and equipment (new or existing) affected by or needed for planning purposes by this project.

Identify any known constraints or dependencies to those installation events due to real-time facility modifications or other required changes.

Provide a detailed bill of materials listing all of the equipment, systems hardware, and software required to meet the AT/FP Ashore P-Specs and site specific requirements for the project. Note: for components and assemblies developed by the Contractor for use on AT/FP projects the data sheets or drawings prepared using ASME Y14.100.2004_R2009 must be approved prior to them being used in the design.

Provide comprehensive and complete drawings and descriptions in sufficient detail for systems and equipment installation, maintenance and repair.

Provide System Data Flow Diagrams detailing the type of information shared between systems and sub-systems, both within the system itself as well as with external systems. Provide additional requirements specified in Table 1 and Table 2 per the submission schedule listed thereon.

2.2.1 Preparation, Submission, and Review Procedures

The following procedures shall be followed for preparation, submission, and review of the IDP design drawings:

1) Contractor prepares and submits the IDP 35% Design drawings.

a. On AT/FP Access Control Point - Automated (ACP-A) projects the GFI 35% Drawing Template shall be used to create the 35% CDRL A005 submission. The 35% Drawing Template can be downloaded at http://www.ursfiles.com/dm/index.php?interface=download&hash=3790267a75be 333847a6fd36ca8126f5.

2) Government reviews the IDP 35% Design drawings and provides comments.

3) Contractor schedules a PDR at a mutually agreeable time after the Government’s review of the IDP 35% Design drawings to discuss and resolve the Government’s comments.

Following the PDR, the Government approves the IDP 35% Design drawings and authorizes the Contractor to proceed with the detailed design and initial procurement of long lead items.

4) Contractor, using the approved IDP 35% Design drawings as a baseline, prepares and submits the IDP 100% Pre-Final Design drawings.

5) Government reviews the IDP 100% Pre-Final Design drawings and provides comments.

6) Contractor schedules a CDR at a mutually agreeable time after the Government’s review of the IDP 100% Pre-Final Design drawings to discuss and resolve the Government’s comments. Following the CDR, the Government approves the IDP 100% Pre-Final Design drawings and authorizes the Contractor to proceed with the IDP 100% Final Design (For Construction) drawings.

7) Contractor revises the IDP 100% Pre-Final Design drawings to incorporate all changes and recommendations from the CDR. The Contractor then signs and stamps the final IDP 100% Final Design (For Construction) drawings and submits to the Government.

8) Government reviews and approves the IDP 100% Final Design (For Construction) drawings within three weeks and authorizes the Contractor to proceed with the installation. (Note: This authorization presumes that the Contractor will also have met the requirements for approval to install imposed by the DED for CDRL A040, Fleet Readiness Certification Board (FRCB) Package, permitting requirements and site approval.)

9) Contractor submits the approved and stamped IDP 100% Final Design (For Construction) drawings into the AT/FP Ashore Remedy System for record purposes.

2.2.2 Drawing Requirements for M-3090.2A 3rd Party Installations

The M-3090.2A 3rd Party IDP shall contain design drawings which include both facilities design details and systems design details combined in one set of drawings. Revision control of the drawings per ASME Y14.35M or equivalent shall be maintained throughout the project.

The facilities design details shall be contained in A/E/C CAD Standard Table 2-1 Discipline Designators for General (G), Civil (C), and Electrical (E) and other Discipline Designators as applicable. Except for incidental construction associated with ACP-A Projects (Refer to the PWS), 3rd Party Installation drawings shall follow UFC 1-300-09N guidelines. ACP-A Projects that have only incidental construction shall use only the drawing format, NAVFAC drawing number assignments, and A/E/C CAD Standard guidelines from UFC 1-300-09N. All 3rd Party Installations shall follow the guidance for sheet identification for the above Discipline Designators contained in paragraph 2.4 of this DED.

http://www.ursfiles.com/dm/index.php?interface=download&hash=3790267a75be333847a6fd36ca8126f5 http://www.ursfiles.com/dm/index.php?interface=download&hash=3790267a75be333847a6fd36ca8126f5

The systems details shall be entirely contained in A/E/C CAD Standard Table 2-1 Discipline Designator for Telecommunications (T). These drawings shall follow M-3090.2A paragraph 2.4.6 for 3rd Party tasks for guidance.

A cover sheet is required for the complete drawing package. Sheet formatting is described in paragraph 2.4 of this document.

Minimum requirements for the three IDP submissions are:

35% Design - The IDP 35% Design drawings shall contain sufficient content to convey design intent and follow UFC 1-300-09N, paragraph 10-3.2. Minimum requirements for an acceptable IDP 35% Design submission shall consist of the following A/E/C CAD Standard design designator sections:

General Section o Format per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Content per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Cover Sheet – will serve as the Title Page. Sheet Identification Number G-000

Civil Section o Format per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Content per UFC 1-300-09N and A/E/C CAD Std, Release 5.0

Electrical Section o Format per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Content per UFC 1-300-09N and A/E/C CAD Std, Release 5.0

Telecommunications Section o Format per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Content per M-3090.2A, Paragraph 2.4.6

Note: Site Specific requirements (e.g., survey/mapping, landscaping) not covered in the four sections above shall be included in the applicable design designator section and follow format and content as shown above.

100% Pre-Final Design - The IDP 100% Pre-Final Design drawings shall follow UFC 1- 300-09N, paragraph 10-4.2. The drawings shall be modified to show complete installation details as well as reflect the mutually agreed upon resolutions to the 35% Design review comments and shall be 100% complete except for the PE certification and quality control stamp. Manufacturer data sheets as well as developed or modified software source code are to be included in the 100% Pre-Final Design submission.

100% Final Design (For Construction) - The IDP 100% Final Design (For Construction) drawings shall follow UFC 1-300-09N, paragraph 10-5.2. The drawings shall be modified to reflect the mutually agreed upon resolutions to the 100% Pre-Final Design review comments. NAVFAC drawing numbers are required on the 100% Final Design (For Construction) design drawings.

Except for incidental construction associated with ACP-A Projects (Refer to the PWS), the General, Civil and Electrical design drawings in this IDP shall be certified, signed and dated by a Professional Engineer (PE) with a PE Stamp per UFC 1-300-09N, Paragraph 2-7, and FAR 52.236-25 to ensure compliance with applicable building codes and federal design standards, or other standards required at the specific installation where the work is to be performed. If there are any technical changes made to these drawings due to the PE certification, the contractor shall notify the Government immediately. The signed stamp shall be included in the IDP 100% Final Design (For Construction) submission of this CDRL.

Additionally, a quality control review shall be conducted on the IDP 100% Final Design (For Construction) drawings per UFC 1-300-09N, Paragraph 10-5.2.2. The Designer of Record (DOR)/ Professional Engineer (PE) who certifies the General, Civil and Electrical design drawings shall perform the quality control review, sign, and date the Quality Control Stamp for these drawings.

The DOR/Systems Engineer shall perform the quality control review, sign, and date the Quality Control Stamp for the telecommunications drawings. The signed stamp shall be included in the IDP 100% Final Design (For Construction) submission of this CDRL.

Refer to Table 1 for complete IDP requirements.

TABLE 1 – IDP REQUIREMENTS FOR M-3090.2A 3RD PARTY INSTALLATIONS AND FACILITIES

DESIGN M-3090.2A OCF INSTALLATIONS

REQUIREMENT

REQUIREMENT

DESCRIPTION

35%

DESIGN

(UFC 1-300-

09N

PARAGRAPH

10-3)

100%

PRE-FINAL

DESIGN

(UFC 1-300-

09N

PARAGRAPH

10-4)

100% FINAL

DESIGN (FOR

CONSTRUCTION)

(UFC 1-300-

09N PARAGRAPH

10-5)

Design Drawings Installation Drawings per Paragraphs

2.2.2 for 3rd Party Installations and 2.2.3 OCF Installations

X

(For ACP-A projects use the GFI 35%

Drawing Template)

X X

Manufacturer Data Sheets for Major Components and/or Assemblies

Data Sheets or Assembly Drawings showing Mechanical, Electrical, Environmental, Reliability Data

X

(Major Components and/or Assemblies only)

X

(All Components and/or Assemblies)

Shop Drawings UFC 1-300- 09N, Paragraph 10-5.2.1

X X

Calculations UFC 1-300- 09N, Paragraph 10-1.6

X X

PE Certification (Not required for incidental construction associated with ACP-A Projects.

Refer to PWS)

UFC 1-300-

09N, Paragraph 2-7

X

TABLE 1 – IDP REQUIREMENTS FOR M-3090.2A 3RD PARTY INSTALLATIONS AND FACILITIES

DESIGN M-3090.2A OCF INSTALLATIONS

REQUIREMENT

REQUIREMENT

DESCRIPTION

35%

DESIGN

(UFC 1-300-

09N

PARAGRAPH

10-3)

100%

PRE-FINAL

DESIGN

(UFC 1-300-

09N

PARAGRAPH

10-4)

100% FINAL

DESIGN (FOR

CONSTRUCTION)

(UFC 1-300-

09N PARAGRAPH

10-5)

Quality Control Review

UFC 1-300-

09N, Paragraph 10-5.2.2

X

Software Source Code

All software source code developed under this AT/FP Ashore Program Contract to include customization of COTS applications or GFI Logic

X X

NAVFAC

Drawing Numbers

UFC 1-300-

09N, Paragraph 10-5.2

X

2.2.3 Drawing Requirements for M-3090.2A OCF Installations

The M-3090.2A OCF IDP shall consist of two separate and distinct sets of drawings: a Facilities IDP Design set of drawings and a Systems IDP Design set of drawings. Revision control of the drawings per ASME Y14.35M or equivalent shall be maintained throughout the project.

The Facilities IDP Design set of drawings shall follow the guidance of Paragraph 2.2.2 above with the exception that no Telecommunications section is to be included with this submission. These drawings shall follow UFC 1-300-09N guidelines as well as A/E/C CAD Standard Release 5.0.

Sheet Identification for these Discipline Sections shall follow guidance contained in Paragraph 2.4 of this document.

The Systems IDP Design set of drawings shall follow the guidance of SPAWAR M-3090.2A for OCF installations and the SPAWAR Shore Installation Process Handbook (SIPH) v.3.0 Appendices Q1 and Q2 for format and content.

Minimum requirements for the three IDP submissions are:

35% Design -

Facilities IDP Design drawings (See Table 1) -

The Facilities IDP 35% Design drawings shall contain sufficient content to convey design intent and follow UFC 1-300-09N, Paragraph 10-3.2 guidance. Minimum requirements for an acceptable Facilities 35% Design submission shall consist of the following:

General Section o Format per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Content per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Cover Sheet – will serve as the Title Page. Sheet Identification Number G-000

Civil Section o Format per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Content per UFC 1-300-09N and A/E/C CAD Std, Release 5.0

Electrical Section o Format per UFC 1-300-09N and A/E/C CAD Std, Release 5.0 o Content per UFC 1-300-09N and A/E/C CAD Std, Release 5.0

Systems IDP Design Drawings (See Table 2) -o The Systems IDP 35% Design drawings shall at a minimum:

Include a SIPH Code 020 Installation Master Drawing section with enough detail to convey design intent

Include a SIPH Code 040 Floor Plan and Elevations section with enough detail to convey design intent

Include a SIPH Code 060 Simplified Block Diagram section with enough detail to convey design intent

Include a shell (at least the first sheet) of the remaining SIPH Codes identified in Table 2

100% Pre-Final Design - The Facilities IDP 100% Pre-Final Design drawings and the Systems IDP 100% Pre-Final Design drawings shall be the modified IDP 35% Design drawings showing complete installation details in all sections as well as reflect the responses to the IDP 35% Design review comments and shall be 100% complete. The Facilities IDP 100% Pre-Final Design drawings shall follow UFC 1-300-09N, Paragraph 10-4.2. Manufacturer Data Sheets as well as developed or modified software source code are to be included in the IDP 100% Pre-Final Design submission. See Table 1 for Facilities IDP Design drawing requirements and Table 2 for System IDP Design drawing requirements.

100% Final Design (For Construction) - The Facilities IDP 100% Final Design (For Construction) drawings and the Systems IDP 100% Final Design (For Construction) drawings shall be the IDP 100% Pre-Final Design drawings modified to reflect the responses to the IDP 100% Pre-Final Design review comments. The Facilities IDP 100% Final Design (For Construction) drawings shall follow UFC 1-300-09N, Paragraph 10-5.2.

NAVFAC drawing numbers which are required on the Facilities IDP 100% Final Design (For Construction) drawings.

The General, Civil and Electrical design drawings in the Facilities IDP 100% Final Design (For Construction) submittal shall be certified, signed and dated by a Professional Engineer (PE) with a PE Stamp per UFC 1-300-09N, Paragraph 2-7, and FAR 52.236-25 to ensure compliance with applicable building codes and federal design standards, or other standards required at the specific installation where the work is to be performed. If there are any technical changes made to these drawings due to the PE certification, the contractor shall notify the Government immediately.