Attachment 0003 Appendix B Division 1 SPECS 2025-2923 KING DRIVE.pdf

Rock Island Arsenal Specifications

PR #2025-2923

Repair King Drive – Grade and Pave

APPENDIX B

US Army Garrison‐Rock Island Arsenal

Directorate of Public Works Engineering and Services Division

AMIM‐RIP‐G

1 Rock Island Arsenal

Rock Island, IL 61299‐5000

USACE / NAVFAC / AFCEC / NASA UFGS-01 30 00 (November 2020)

Change 1 - 08/21

Preparing Activity: NAVFAC Superseding UFGS-01 30 00 (August 2015) UFGS-01 30 00.05 20 (March 2013)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

References are in agreement with UMRL dated January 2022

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/20, CHG 1: 08/21

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 COLOR BOARDS FOR AIR FORCE PROJECTS

1.4 VIEW LOCATION MAP

1.5 PROGRESS AND COMPLETION PICTURES

1.6 MINIMUM INSURANCE REQUIREMENTS

1.7 SUPERVISION

1.7.1 Superintendent Qualifications

1.7.2 Minimum Communication Requirements

1.7.3 Duties

1.7.4 Non-Compliance Actions

1.8 PRECONSTRUCTION MEETING CONFERENCE

1.8.1 Attendees

1.9 POST AWARD KICKOFF (PAK) MEETING

1.9.1 PAK Meeting Outcomes

1.9.2 PAK Meeting Contractor Attendees

1.10 DESIGN PRESENTATION/DEVELOPMENT (DP/D)

1.11 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)

1.11.1 Red Zone Checklist

1.11.2 Meetings

1.12 EXPORT LICENSES FOR OVERSEAS PROJECTS

1.13 WAIVER FOR WORKER'S COMPENSATION

1.14 PARTNERING

1.14.1 Facilitated (Formal) Partnering

1.14.2 Team-Led (Informal) Partnering

1.15 PERFORMANCE ASSESSMENT PLAN (PAP)

1.16 MOBILIZATION

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 30 00 Page 1

-- End of Section Table of Contents --

SECTION 01 30 00 Page 2

USACE / NAVFAC / AFCEC / NASA UFGS-01 30 00 (November 2020)

Change 1 - 08/21

Preparing Activity: NAVFAC Superseding UFGS-01 30 00 (August 2015) UFGS-01 30 00.05 20 (March 2013)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

References are in agreement with UMRL dated January 2022

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/20, CHG 1: 08/21

NOTE: This guide specification covers general administrative and procedural requirements for Contractor management and coordination.

Adhere to UFC 1-300-02 Unified Facilities Guide Specifications (UFGS) Format Standard when editing this guide specification or preparing new project specification sections. Edit this guide specification for project specific requirements by adding, deleting, or revising text. For bracketed items, choose applicable item(s) or insert appropriate information.

Remove information and requirements not required in respective project, whether or not brackets are present.

Comments, suggestions and recommended changes for this guide specification are welcome and should be submitted as a Criteria Change Request (CCR).

NOTE: This section contains tailoring for NAVY, NAVFAC EURAFCENT, NAVFAC FE, NAVFAC MAR, NAVFAC SE, ARMY, AIR FORCE, NASA, DESIGN-BUILD, DESIGN-BID-BUILD and NAVY DESIGN-BUILD. Where an Editor's Note states a paragraph is tailored for a Service or project type, the content of the paragraph, or a portion of the paragraph, is suited specifically to be included only for that Service or project type.

PART 1 GENERAL

1.1 REFERENCES

SECTION 01 30 00 Page 3

NOTE: This paragraph is used to list the publications cited in the text of the guide specification. The publications are referred to in the text by basic designation only and listed in this paragraph by organization, designation, date, and title.

Use the Reference Wizard's Check Reference feature when you add a Reference Identifier (RID) outside of the Section's Reference Article to automatically place the reference in the Reference Article. Also use the Reference Wizard's Check Reference feature to update the issue dates.

References not used in the text will automatically be deleted from this section of the project specification when you choose to reconcile references in the publish print process.

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2014) Safety -- Safety and Health Requirements Manual

U.S. NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)

15 CFR 772 Definition of Terms

15 CFR 773 Special Licensing Procedures

1.2 SUBMITTALS

NOTE: Review Submittal Description (SD) definitions in Section 01 33 00 SUBMITTAL PROCEDURES and edit the following list, and corresponding submittal items in the text, to reflect only the submittals required for the project. The Guide Specification technical editors have classified those items that require Government approval, due to their complexity or criticality, with a "G." Generally, other submittal items can be reviewed by the Contractor's Quality Control System. Only add a "G" to an item if the submittal is sufficiently important or complex in context of the project.

For Army projects, fill in the empty brackets following the "G" classification, with a code of up to three characters to indicate the approving authority. Codes for Army projects using the Resident Management System (RMS) are: "AE" for Architect-Engineer; "DO" for District Office (Engineering Division or other organization in the District Office); "AO" for Area Office; "RO" for

SECTION 01 30 00 Page 4

Resident Office; and "PO" for Project Office. Codes following the "G" typically are not used for Navy, Air Force, and NASA projects.

The "S" classification indicates submittals required as proof of compliance for sustainability Guiding Principles Validation or Third Party Certification and as described in Section 01 33 00 SUBMITTAL

PROCEDURES.

Choose the first bracketed item for Navy, Air Force, and NASA projects, or choose the second bracketed item for Army projects.

NOTE: For Navy DB projects, delete 01 33 00, SUBMITTAL PROCEDURES, and replace with UFGS 01 33

00.05 20 CONSTRUCTION SUBMITTAL PROCEDURES and UFGS

01 33 10.05 20 DESIGN SUBMITTAL PROCEDURES.

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are [for Contractor Quality Control approval.][for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.] Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

NOTE: For projects in the NAVFAC PAC Area of Operation, and for the submittals identified as SD-01 Preconstruction Submittals, remove the "G" designation.

View Location Map

Progress and Completion Pictures

Design Submittal Packaging

Performance Assessment Plan (PAP)

SD-04 Samples

NOTE: The following item is tailored for use only on Air Force projects. Do not use this paragraph in Design-Build projects.

Color Boards; G[, [_____]]

1.3 COLOR BOARDS FOR AIR FORCE PROJECTS

SECTION 01 30 00 Page 5

NOTE: This Article is tailored for Air Force. Use for Air Force projects only.

Submit five sets of color boards within 90 calendar days after Contract Award. Each set of boards must include samples of colors and finishes of interior surfaces, such as walls, floors, and ceilings. Present the samples on 200 by 270 mm 8 by 10-1/2 inches boards (modules) with a maximum spread of 600 by 810 mm 24 by 31-1/2 inches for foldouts. Design modules to fit in a standard loose-leaf, three-ring binder. Where special finishes such as architectural concrete, carpet, or prefinished textured metal panels are required, submit samples not less than 300 mm 12 inches square with the board. If more space is needed, more than one board per set may be submitted. Certify that the color samples have been reviewed in detail, and that the color samples are in strict accordance with contract drawings and specifications, except as may be otherwise explicitly stated. Submittal of color samples does not relieve the Contractor of the responsibility to submit samples required elsewhere herein.

1.4 VIEW LOCATION MAP

Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

1.5 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. [Include aerial photographs. ]Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in [JPEG][_____] file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten different viewpoints selected by the Contractor unless otherwise directed by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names. Photographs provided are for unrestricted use by the Government.

1.6 MINIMUM INSURANCE REQUIREMENTS

NOTE: Do not use this paragraph for projects at Guantanamo Bay.

Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance under this contract. Provide other insurance coverage as required by [State ]Portugal Guam Diego Garcia BIOT law.

SECTION 01 30 00 Page 6

1.7 SUPERVISION

1.7.1 Superintendent Qualifications

NOTE: For first and second bracketed items, choose 10 years and 5 years respectively, for most projects. Fill in brackets and coordinate with Construction Manager/Resident Engineer for Army and NASA projects or ROICC/FEAD for Navy projects to determine if more experience is needed for larger, complex projects, or less, for simple, less costly projects.

NOTE: The second paragraph below contains tailoring for ARMY, NAVY and NASA projects based on the QUALITY CONTROL Section that applies for that Service. Include the second bracketed paragraph when Superintendent is permitted to also serve as Quality Control Manager.

Provide project superintendent with a minimum of [10][_____] years experience in construction with at least [5][_____] of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

[ For projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section 01 45 00.00 10 01 45 00.00 20 01 45 00.00 40 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.

]1.7.2 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of Contract work.In addition, if a Quality Control (QC) representative is required on the Contract, then that individual must also have fluent English communication skills.

1.7.3 Duties

NOTE: This paragraph contains tailoring for Red Zone for NAVY and AIR FORCE use. Include the term "Red Zone meetings" for NAVY and AIR FORCE projects only.

SECTION 01 30 00 Page 7

The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend Red Zone meetings, partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.7.4 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to ensure timely completion.

Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.8 PRECONSTRUCTION MEETING CONFERENCE

NOTE: The title of this paragraph, and the paragraph below is tailored for NAVY to use "Meeting" and tailored for ARMY and NASA to use "Conference."

NOTE: This paragraph includes tailored phrases for both Design-Bid-Build and Design-Build projects.

Immediately after awardUpon completion of design and design acceptance by the government, prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction MeetingConference. The meetingconference must take place within [35][_____] calendar days after award of the contract, but prior to commencement of any work at the site. The purpose of this meeting conference is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to:

daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out. Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.

1.8.1 Attendees

Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.

1.9 POST AWARD KICKOFF (PAK) MEETING

NOTE: This Article is tailored for NAVY

SECTION 01 30 00 Page 8

DESIGN-BUILD projects. Include this Article and paragraphs for Navy Design-Build projects only.

Immediately after award, coordinate with the Contracting Officer a time and place for the PAK Meeting. The PAK meeting must be held within [35][_____] calendar days after contract award and prior to commencing work. If mutually agreed upon by the Contractor and the Government, the PAK Meeting may be held concurrently with the Design Presentation/Design Development Meeting or Concept Design Workshop (CDW) whichever is required.

1.9.1 PAK Meeting Outcomes

a. Integrate the Contractor and all client representatives into the project team.

b. Achieve consensus from the project team on any issues and concerns with the Contractor's technical proposal and the User's functional requirements.[ Confirm the design is within the project budget.]

c. Review the administrative requirements of the contract that are critical during the design phase.

d. Establish clear lines of communication and points of contact for Government and Contractor team members.

e. Obtain an acceptable conceptual design including floor and site plans, signed by the client, Contractor and other key team members.

NOTE: Select 01 32 17.00 20 if a cost-loaded Primavera P6 schedule is required for the project -this specification Section applies primarily to MILCON projects and any other similar projects with multiple disciplines working simultaneously. Select 01 32 16.00 20 if a non-cost-loaded P6 schedule or a Microsoft Project schedule (cost-loaded or non-cost-loaded) is required - this specification applies to small projects, either simple or complex, that would not benefit from the use of a cost-loaded Network Analysis Schedule (NAS).

f. Review the project design schedule and design package requirement, design submittal packaging, and preliminary construction schedule in accordance with Section [01 32 17.00 20 COST-LOADED NETWORK ANALYSIS

SCHEDULE (NAS)][01 32 16.00 20 SMALL PROJECT CONSTRUCTION PROGRESS

SCHEDULES]. Discuss design milestones and events that will be included in the Quality Control Communication Plan.

g. Establish clear expectations and schedules for facility turnover, providing DD Form 1354 asset management records, eOMSI submittals, Guiding Principle Validation, Third Party Certification (if applicable), and training of Government maintenance personnel.

h. Establish procedure for design packages reviews, Contractor's resolution to comments, and Government's role in review of packages.

SECTION 01 30 00 Page 9

NOTE: Insert the bracketed paragraphs below ONLY if Concept Design Workshop (CDW) is required.

[ i. Establish clear expectations for the Concept Design Workshop as established in UFGS 01 31 19.05 20 CONCEPT DESIGN WORKSHOP (CDW).

][j. Establish clear expectations for Design Model presentations for projects implementing Building Information Management/Modeling (BIM).

]1.9.2 PAK Meeting Contractor Attendees

NOTE: If a Commissioning Authority is used, delete the first bracketed option. If a Commissioning Authority is not used, delete the second bracketed option.

The following Contractor personnel must attend the PAK meeting; Project Manager, Project Scheduler, Lead Designer-of-Record (DOR), Design Staff responsible for each architectural/engineering discipline when facility design is discussed, Superintendent, QC Manager,[ and the] DQC Manager[ and the Commissioning Authority (CA)]. Optional attendees include:

Principal, Assistant Project Manager, major subcontractors and specialized supplemental QC personnel.

[1.10 DESIGN PRESENTATION/DEVELOPMENT (DP/D)

NOTE: Insert the paragraph below for Design Presentation/Development ONLY if a Concept Design Workshop (CDW) is NOT required. If a CDW is required, do not insert this paragraph and use UFGS

01 31 19.05 20 CONCEPT DESIGN WORKSHOP (CDW).

The Contractor must lead discussions to develop an understanding of the facility design that the accepted technical proposal represents with the Government users and maintainers of the facility. Develop site plans, floor plans, exterior finish materials, and building elevations to conduct working sessions with the Government meeting attendees. The purpose of the DP/D Meeting is to confirm the appropriateness of the facility design and develop acceptable alternatives if changes are needed. The Contractor must anticipate that Government Facility Users represented at the DP/D Meeting will provide additional functional information. Incorporate functional design changes into the facility design as required to meet the needs of the Users. At the end of the DP/D Meeting the Contractor must provide either assurance that the updated design can be built within the budget or identify potential cost modification items and establish a follow-on DP/D Meeting to finalize a design that will include trade-offs to bring the project within the budget. The following Contractor key personnel must attend the Design Presentation: Project Manager, Project Scheduler, Cost Estimator, Lead Designer of Record, Design Staff responsible for each architectural/engineering discipline when facility design is discussed, Major Subcontractors, and DQC.

Demonstrate ability to achieve identified Guiding Principle sustainability

SECTION 01 30 00 Page 10 goals and also Third-Party Certification sustainability goals, if applicable. Provide Preliminary Sustainability Notebook, refer to Section 01 33 29 SUSTAINABILITY REQUIREMENTS AND REPORTING for requirements.

]1.11 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)

NOTE: Use this paragraph for NAVY and AIR FORCE (AFCEC/CF) projects. This paragraph is tailored for NAVY and AIR FORCE use.

Meet with the Government to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start planning the turnover process at the Pre-Construction Conference meeting with a discussion of the Red Zone process and convene at regularly scheduled NRZ Meetings beginning at approximately 75 percent of project completion.

Include the following in the facility Turnover effort:

1.11.1 Red Zone Checklist

a. Contracting Officer's Technical Representative (COTR) will provide the Contractor a copy of the Red Zone Checklist template.

b. Prior to 75 percent completion, modify the Red Zone Checklist template by adding or deleting critical activities applicable to the project and assign planned completion dates for each activity. Submit the modified Red Zone Checklist to the Contracting Officer. The Contracting Officer may request additional activities be added to the Red Zone Checklist at any time as necessary.

1.11.2 Meetings

a. Conduct regular Red Zone Meetings beginning at approximately 75 percent project completion, or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first.

b. The Contracting Officer will establish the frequency of the meetings, which is expected to increase as the project completion draws nearer.

At the beginning, Red Zone meetings may be every two weeks then increase to weekly towards the final month of the project.

c. Using the Red Zone Checklist as a Plan of Action and Milestones (POAM) and basis for discussion, review upcoming critical activities and strategies to ensure work is completed on time.

d. During the Red Zone Meetings discuss with the COTR any upcoming activities that require Government involvement.

e. Maintain the Red Zone Checklist by documenting the actual completion dates as work is completed and update the Red Zone Checklist with revised planned completion dates as necessary to match progress.

Distribute copies of the current Red Zone Checklist to attendees at each Red Zone Meeting.

[1.12 EXPORT LICENSES FOR OVERSEAS PROJECTS

NOTE: Include the following paragraph in projects

SECTION 01 30 00 Page 11 at overseas locations.

Obtain individual export licenses and project export licenses required by the Department of Commerce regulations (15 CFR 772 and 15 CFR 773) so that no delays are experienced in shipping from the United States of America to a foreign country. For additional information, the Contractor may contact one of the U.S. and Foreign Commercial Service District Offices of the Department of Commerce which are located in almost every State.

][1.13 WAIVER FOR WORKER'S COMPENSATION

NOTE: Include the following paragraph in projects for overseas locations, except Guantanamo Bay.

In addition to FAR 52.228-4 Workers' Compensation and War-Hazard Insurance Overseas, the Secretary of Labor has granted a waiver. The waiver does not apply to employees who are hired in the United States, or who are residents, or citizens of the United States.

]1.14 PARTNERING

NOTE: Select one of two possible choices for the Level of Partnering. Coordinate with the Project Manager/ Design Manager and Construction Manager to determine whether Formal or Informal Partnering should be used.

The two Partnering Level options are:

1. Facilitated (Formal): Recommended for use on high risk, high visibility, compressed duration, technical complexity, or standalone contracts over approximately $15M. Facilitated by a third-party independent Formal Partnering Facilitator consultant paid for by Contractor. Contractor includes costs for facilitator, room rental and incidental items in bid. Participants pay own costs for meals, lodging and transportation. Partnering "re-groups" held as agreed in charter. Exceptions: When DB Contractor, Government and Supported Commands are already familiar with each other from recent contracts, consider using Informal Partnering.

2. Team Led (Informal): Recommended for use on contracts less than $15M, without high risk, high visibility, compressed performance period, or technically complex characteristics. Exceptions:

When new Supported Commands, new Contractor, first time use of new contract vehicle or other unique contract requirements consider upgrade to Formal Partnering to lessen risk.

NOTE: Partnering is required for all projects.

SECTION 01 30 00 Page 12

NOTE: For projects in the NAVFAC PAC Area of Operation, edit the paragraph by adding the first bracketed item to the paragraph.

[Contractor shall host the partnering session within 45 calendar days of contract award. ]To most effectively accomplish this Contract, the Contractor and Government must form a cohesive partnership with the common goal of drawing on the strength of each organization in an effort to achieve a successful project without safety mishaps, conforming to the Contract, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions. Key Personnel from the supported command, end user, [NAVFAC, PWD, FEAD/ROICC][_____], Contractor, key subcontractors and the Designer of Record are required to participate in the Partnering process.

[1.14.1 Facilitated (Formal) Partnering

NOTE: The subparagraphs below are tailored to include "Pre-construction" meeting for DESIGN-BID-BUILD projects and "PAK" meeting for NAVY DESIGN-BUILD projects.

NOTE: For NAVFAC PAC Area of Operation, remove the first bracketed sentence in list item a. below.

a. [Within [35][_____] calendar days after award and prior to the start of work, ]host a Formal Partnering session with key personnel from the project team including both Contractor and Government personnel. All costs associated with the Partnering session including the third-party independent Facilitator Consultant, meeting room and other incidental items are the responsibility of the Contractor.

b. Before the Facilitated (Formal) Partnering session, coordinate with the Facilitator all requirements for incidental items (such as audio-visual equipment, easels, flipchart paper, colored markers, note pads, pens/pencils, colored flash cards) and have these items available at the Partnering session. Provide copies of any documents required for distribution to all attendees. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.

c. The Initial Partnering Session must be a duration of [one][_____] day and be held at a location off base as agreed to by the Contracting Officer. Partnering session may take place concurrently with the Pre-Construction Post-Award Kickoff Meeting.

d. Facilitator must be experienced in conducting corporate Partnering sessions and must be a third-party independent facilitating consultant

- not an employee of the Contractor. The Facilitator is responsible for leading all aspects of the Partnering session necessary to achieve the Partnering goal.

SECTION 01 30 00 Page 13

e. An outcome of the Partnering session must be an escalation matrix agreed upon by both the Government and Contractor, which identifies key Government and Contractor decision makers by name and anticipated decision durations.

f. Host follow-on Partnering Sessions at three- to six-month intervals or more frequently if needed and lasting generally a half day or less.

Attendees need only be those required to resolve current issues. The same Facilitator used in the Initial Partnering session must lead the follow-on sessions unless an alternative is permitted by the Contractor Officer. All costs associated with follow-on Partnering sessions are the responsibility of the Contractor.

][1.14.2 Team-Led (Informal) Partnering

a. The Contracting Officer will coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel. The Partnering Session will be co-led by the Government Construction Manager and Contractor's Project Manager.

b. The Initial Team-led Partnering session may be held concurrently with the Pre-Construction Post-Award Kickoff meeting. Partnering sessions will be held at a location mutually agreed to by the Contracting Officer and the Contractor, typically at a conference room on-base or at the Contractor's temporary trailer.

c. The Initial Team-Led Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by Contracting Officer.

d. The Partners will determine the frequency of the follow-on sessions.

e. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.

]1.15 PERFORMANCE ASSESSMENT PLAN (PAP)

NOTE: This Article is tailored for use on NAVY DESIGN-BUILD projects only.

The Performance Assessment Plan (PAP) will be used to document design innovation and budget management, provide performance feedback to the Contractor, and as a basis for interim and final evaluations in the Contractor Performance Appraisal Reporting System (CPARS) on-line database.

It is the intent of the Government to establish the PAP based on tangible, measurable indicators of outstanding contractor performance, and on commitments made in the Contractor's proposal. The initial PAP may be found on the NAVFAC Design-Build Request for Proposal Website in RFP PART 6 Attachments. Review and finalize the initial PAP during the Partnering Session. During the initial Partnering Session, the Government, the Contractor, the Designer-of-Record, and the Client will establish the PAP.

Following the establishment of the PAP, the Contractor will present it, with his input, for update and discussion at projects meetings which discuss project performance. Submit an updated PAP on a monthly basis with the invoice for that period as a minimum.

SECTION 01 30 00 Page 14

[1.16 MOBILIZATION

NOTE: For projects in the NAVFAC PAC Area of Operation, add the following paragraph. Select the first bracket for DBB and second bracket for DB.

Contractor shall mobilize to the jobsite within [60 calendar days after contract award] [30 calendar days of final site or building design approval]. Mobilize is defined as having equipment AND having a physical presence of at least one person from the contractor's team on the jobsite.

]PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

-- End of Section --

SECTION 01 30 00 Page 15

USACE / NAVFAC / AFCEC / NASA UFGS- 01 32 01. 00 10 ( Febr uar y 2015)

Pr epar i ng Act i v i t y: USACE Superseding 01 32 01. 00 10 ( August 2008)

UNI FI ED FACI LI TI ES GUI DE SPECI FI CATI ONS

Ref er ences ar e i n agr eement wi t h UMRL dat ed Januar y 2023

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER QUALIFICATIONS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

2.1.2.2 Other Than Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Design and Permit Activities

3.3.4 Procurement Activities

3.3.5 Mandatory Tasks

3.3.6 Government Activities

3.3.7 Standard Activity Coding Dictionary

3.3.7.1 Workers Per Day (WRKP)

3.3.7.2 Responsible Party Coding (RESP)

3.3.7.3 Area of Work Coding (AREA)

3.3.7.4 Modification Number (MODF)

3.3.7.5 Bid Item Coding (BIDI)

3.3.7.6 Phase of Work Coding (PHAS)

SECTION 01 32 01.00 10 Page 1

3.3.7.7 Category of Work Coding (CATW)

3.3.7.8 Feature of Work Coding (FOW)

3.3.8 Contract Milestones and Constraints

3.3.8.1 Project Start Date Milestone and Constraint

3.3.8.2 End Project Finish Milestone and Constraint

3.3.8.3 Interim Completion Dates and Constraints

3.3.8.3.1 Start Phase

3.3.8.3.2 End Phase

3.3.9 Calendars

3.3.10 Open Ended Logic

3.3.11 Default Progress Data Disallowed

3.3.12 Out-of-Sequence Progress

3.3.13 Added and Deleted Activities

3.3.14 Original Durations

3.3.15 Leads, Lags, and Start to Finish Relationships

3.3.16 Retained Logic

3.3.17 Percent Complete

3.3.18 Remaining Duration

3.3.19 Cost Loading of Closeout Activities

3.3.19.1 As-Built Drawings

3.3.19.2 O & M Manuals

3.3.20 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.2.1 Design Package Schedule Submission

3.4.3 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data CD/DVDs

3.5.2 Narrative Report

3.5.3 Schedule Reports

3.5.3.1 Activity Report

3.5.3.2 Logic Report

3.5.3.3 Total Float Report

3.5.3.4 Earnings Report by CLIN

3.5.3.5 Schedule Log

3.5.4 Network Diagram

3.5.4.1 Continuous Flow

3.5.4.2 Project Milestone Dates

3.5.4.3 Critical Path

3.5.4.4 Banding

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

3.6.2 Update Submission Following Progress Meeting

3.7 WEEKLY PROGRESS MEETINGS

3.8 REQUESTS FOR TIME EXTENSIONS

3.8.1 Justification of Delay

3.8.2 Time Impact Analysis (Prospective Analysis)

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

3.8.4 Fragmentary Network (Fragnet)

3.8.5 Time Extension

3.8.6 Impact to Early Completion Schedule

3.9 FAILURE TO ACHIEVE PROGRESS

3.9.1 Artificially Improving Progress

3.9.2 Failure to Perform

3.9.3 Recovery Schedule

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

SECTION 01 32 01.00 10 Page 2

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

SECTION 01 32 01.00 10 Page 3

USACE / NAVFAC / AFCEC / NASA UFGS- 01 32 01. 00 10 ( Febr uar y 2015)

Pr epar i ng Act i v i t y: USACE Superseding 01 32 01. 00 10 ( August 2008)

UNI FI ED FACI LI TI ES GUI DE SPECI FI CATI ONS

Ref er ences ar e i n agr eement wi t h UMRL dat ed Januar y 2023

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

NOTE: Thi s gui de speci f i cat i on cover s t he r equi r ement s f or t he pr epar at i on and mai nt enance of t he pr oj ect schedul e f or const r uct i on pr oj ect s or desi gn- bui l d const r uct i on pr oj ect s.

Adher e t o UFC 1-300-02 Uni f i ed Faci l i t i es Gui de Speci f i cat i ons ( UFGS) For mat St andar d when edi t i ng t hi s gui de speci f i cat i on or pr epar i ng new pr oj ect speci f i cat i on sect i ons. Edi t t hi s gui de speci f i cat i on f or pr oj ect speci f i c r equi r ement s by addi ng, del et i ng, or r evi s i ng t ext . For br acket ed i t ems, choose appl i cabl e i t em( s) or i nser t appr opr i at e i nf or mat i on.

Remove i nf or mat i on and r equi r ement s not r equi r ed i n r espect i ve pr oj ect , whet her or not br acket s ar e present.

Comment s, suggest i ons and r ecommended changes f or t hi s gui de speci f i cat i on ar e wel come and shoul d be submi t t ed as a Criteria Change Request (CCR) .

TO DOWNLOAD UFGS GRAPHI CS f or at t achment t o t hi s section Go t o http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/forms-graphics-tables

PART 1 GENERAL

NOTE: Coor di nat e sel ect i on of t he opt i onal r equi r ement s i n t hi s gui de speci f i cat i on wi t h Const r uct i on Di v i s i on t o ensur e t hat t he schedul e r equi r ement s ar e appr opr i at e f or t he compl exi t y of t he const r uct abi l i t y por t i on of t he BCOE r evi ew.

See ER 415- 1- 11. Do not r emove par agr aphs f r om t hi s speci f i cat i on except as not ed.

SECTION 01 32 01.00 10 Page 4

I f i t i s desi r ed t o moni t or a Cont r act or ' s schedul e by use of an i n- house pr ogr am, t hi s wi l l r equi r e use of t he St andar d Dat a Exchange For mat ( SDEF) . Use of pr opr i et ar y syst ems wi l l not be speci f i ed. See ER 1- 1- 11, Appendi x A.

1.1 REFERENCES

NOTE: Thi s par agr aph i s used t o l i s t t he publ i cat i ons c i t ed i n t he t ext of t he gui de speci f i cat i on. The publ i cat i ons ar e r ef er r ed t o i n t he t ext by basi c desi gnat i on onl y and l i s t ed i n t hi s par agr aph by or gani zat i on, desi gnat i on, dat e, and t i t l e.

Use t he Ref er ence Wi zar d' s Check Ref er ence f eat ur e when you add a Ref er ence I dent i f i er ( RI D) out si de of t he Sect i on' s Ref er ence Ar t i c l e t o aut omat i cal l y pl ace t he r ef er ence i n t he Ref er ence Ar t i c l e. Al so use t he Ref er ence Wi zar d' s Check Ref er ence f eat ur e t o updat e t he i ssue dat es.

Ref er ences not used i n t he t ext wi l l aut omat i cal l y be del et ed f r om t hi s sect i on of t he pr oj ect speci f i cat i on when you choose t o r econci l e r ef er ences i n t he publ i sh pr i nt pr ocess.

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (2017) Administration -- Project Schedules

1.2 SUBMITTALS

NOTE: Revi ew submi t t al descr i pt i on ( SD) def i ni t i ons i n Sect i on 01 33 00 SUBMI TTAL PROCEDURES and edi t t he f ol l owi ng l i s t , and cor r espondi ng submi t t al i t ems i n t he t ext , t o r ef l ect onl y t he submi t t al s r equi r ed f or t he pr oj ect . The Gui de Speci f i cat i on t echni cal edi t or s have cl assi f i ed t hose i t ems t hat r equi r e Gover nment appr oval , due t o t hei r compl exi t y or cr i t i cal i t y, wi t h a " G. " Gener al l y, ot her submi t t al i t ems can be r evi ewed by t he Cont r act or ' s Qual i t y Cont r ol Syst em. Onl y add a “ G” t o an i t em, i f t he submi t t al i s suf f i c i ent l y i mpor t ant or

SECTION 01 32 01.00 10 Page 5 compl ex i n cont ext of t he pr oj ect .

For Ar my pr oj ect s, f i l l i n t he empt y br acket s f ol l owi ng t he " G" c l assi f i cat i on, wi t h a code of up t o t hr ee char act er s t o i ndi cat e t he appr ovi ng aut hor i t y. Codes f or Ar my pr oj ect s usi ng t he Resi dent Management Syst em ( RMS) ar e: " AE" f or Ar chi t ect - Engi neer ; " DO" f or Di st r i ct Of f i ce ( Engi neer i ng Di v i s i on or ot her or gani zat i on i n t he Di st r i ct Of f i ce) ; " AO" f or Ar ea Of f i ce; " RO" f or Resi dent Of f i ce; and " PO" f or Pr oj ect Of f i ce. Codes f ol l owi ng t he " G" t ypi cal l y ar e not used f or Navy, Ai r For ce, and NASA pr oj ect s.

The " S" c l assi f i cat i on i ndi cat es submi t t al s r equi r ed as pr oof of compl i ance f or sust ai nabi l i t y Gui di ng Pr i nci pl es Val i dat i on or Thi r d Par t y Cer t i f i cat i on and as descr i bed i n Sect i on 01 33 00 SUBMI TTAL

PROCEDURES.

Choose t he f i r st br acket ed i t em f or Navy, Ai r For ce and NASA pr oj ect s, or choose t he second br acket ed i t em f or Ar my pr oj ect s.

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are [for Contractor Quality Control approval.][for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.] Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications ; G[, [_____]]

Preliminary Project Schedule ; G[, [_____]]

Initial Project Schedule ; G[, [_____]]

Periodic Schedule Update ; G[, [_____]]

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification.

SECTION 01 32 01.00 10 Page 6

2.1.1 Government Default Software

The Government intends to use Primavera P6.

2.1.2 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2.1.2.2 Other Than Primavera

If the contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

NOTE: I f t ai l or i ng opt i ons ar e not desel ect ed, sel ect i on of desi gn- bi d- bui l d or desi gn- bui l d t ext required.

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of design and construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Designers, Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.

SECTION 01 32 01.00 10 Page 7

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Design and Permit Activities

NOTE: I ncl ude t hi s par agr aph i n Desi gn- Bui l d projects..

Include design and permit activities with the necessary conferences and follow-up actions and design package submission dates. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period. Provide at a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work.

Also include review and correction periods associated with each item.

3.3.4 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

SECTION 01 32 01.00 10 Page 8

3.3.5 Mandatory Tasks

NOTE: Sel ect i on of const r uct i on or desi gn- bui l d const r uct i on t ext r equi r ed.

Include the following activities/tasks in the initial project schedule and all updates.

a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).

b. Submission, review and acceptance of features require design completion Submission, review and acceptance of design packages.

c. Submission of mechanical/electrical/information systems layout drawings.

d. Long procurement activities

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

g. Submission and approval of DD1354 data and installed equipment lists.

h. Submission and approval of testing and air balance (TAB).

i. Submission of TAB specialist design review report.

j. Submission and approval of fire protection specialist.

k. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

l. Air and water balancing.

m. Building commissioning - Functional Performance Testing.

n. Controls testing plan submission.

o. Controls testing.

p. Performance Verification testing.

q. Other systems testing, if required.

r. Contractor's pre-final inspection.

s. Correction of punch list from Contractor's pre-final inspection.

t. Government's pre-final inspection.

SECTION 01 32 01.00 10 Page 9

u. Correction of punch list from Government's pre-final inspection.

v. Final inspection.

3.3.6 Government Activities

NOTE: Sel ect i on of const r uct i on or desi gn- bui l d const r uct i on t ext r equi r ed.

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, acceptance, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.7 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 . This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil .

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

3.3.7.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task

SECTION 01 32 01.00 10 Page 10 for the duration of that activity.

3.3.7.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).

3.3.7.3 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.

Activities cannot have more than one Work Area Code.

Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.

3.3.7.4 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.7.5 Bid Item Coding (BIDI)

Assign a…