<?xml version="1.0" encoding="windows-1252"?><SEC xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://si.ksc.nasa.gov/sidownloads/xml/specsintactSEC.xsd"><MTA NAME="SUBFORMAT" CONTENT="NEW"/><HDR><AST/><BRK/>
USACE / NAVFAC / AFCESA / NASA      UFGS-01 32 16.00 20 (April 2006)<BRK/>
                                    ------------------------------<BRK/>
Preparing Activity:  <PRA>NAVFAC</PRA>         Replacing without change<BRK/>
                                    UFGS-01320N (December 2003)<BRK/>
<BRK/>
<HL4>UNIFIED FACILITIES GUIDE SPECIFICATIONS</HL4><BRK/>
<BRK/>
<AST/><BRK/></HDR>
<BRK/>
<HL4>SECTION 01 32 16.00 20</HL4><BRK/>
<BRK/>
<STL><TAI OPT="NAVFAC DESIGN BUILD">[DESIGN AND ]</TAI>CONSTRUCTION PROGRESS DOCUMENTATION</STL><BRK/>
<DTE>04/06</DTE><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  This guide specification covers the requirements for <SCP>the preparation 
and use of Design-Build Schedules and Design-Bid-Build Schedules and as such 
must be edited for the acquisition method used</SCP>.<BRK/>
<BRK/>
Edit this guide specification for project specific requirements by adding, deleting, 
or revising text.  For bracketed items, choose applicable items(s) or insert 
appropriate information.<BRK/>
<BRK/>
Remove information and requirements not required in respective project, whether 
or not brackets are present.<BRK/>
<BRK/>
Comments and suggestions on this guide specification are welcome and should 
be directed to the technical proponent of the specification.  A listing of <URL HREF="http://65.204.17.188/report/ufgs.html">technical 
proponents</URL>, including their organization designation and telephone number, is 
on the Internet.<BRK/>
<BRK/>
Recommended changes to a UFGS should be submitted as a  <URL HREF="http://65.204.17.188/projnet/cms/public.html">Criteria Change Request 
(CCR)</URL>.</NPR><BRK/>
<AST/><BRK/></NTE>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  Coordinate with Section 01200 PRICE AND PAYMENT PROCEDURES.  Edit paragraphs 
only where specific project information is required.</NPR><BRK/>
<BRK/>
<NPR>Coordinate selection of the scheduling specification (either 01 32 16.00 20 
or 01 32 17.00 20) with the administrating ROICC Office.  Consult with the administering 
ROICC Office to determine if an Equipment Delivery Schedule will be used on 
this project or if the simplified Network Analysis Scheduled specified in this 
Section will be used.</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<PRT><TTL>PART 1   GENERAL</TTL><BRK/>
<BRK/>
<SPT><TTL>1.1   SUBMITTALS</TTL><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  Review submittal description (SD) definitions in Section 01 33 00 SUBMITTAL 
PROCEDURES and edit the following list to reflect only the submittals required 
for the project.  Submittals should be kept to the minimum required for adequate 
quality control.<BRK/>
<BRK/>
A “G” following a submittal item indicates that the submittal requires Government 
approval.  Some submittals are already marked with a “G”.  Only delete an existing 
“G” if the submittal item is not complex and can be reviewed through the Contractor’s 
Quality Control system.  Only add a “G” if the submittal is sufficiently important 
or complex in context of the project.<BRK/>
<BRK/>
For submittals requiring Government approval on Army projects, a code of up 
to three characters within the submittal tags may be used following the "G" 
designation 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 Resident Office; and "PO" for Project 
Office.  Codes following the "G" typically are not used for Navy,  Air Force, 
and NASA projects.<BRK/>
<BRK/>
Choose the first bracketed item for Navy, Air Force and NASA projects, or choose 
the second bracketed item for Army projects.</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<TXT>Government approval is required for submittals with a "G" designation; submittals not having a "G" designation 
are [for Contractor Quality Control approval.][for information only.  When used, a designation following the 
"G" designation identifies the office that will review the submittal for the Government.]  The following shall 
be submitted in accordance with Section <SRF>01 33 00</SRF> SUBMITTAL PROCEDURES:</TXT><BRK/>
<BRK/>
<LST><SUB>SD-01 Preconstruction Submittals</SUB></LST><BRK/>
<BRK/>
<ITM><SUB><TAI OPT="NAVFAC DESIGN BUILD">[Design and ]</TAI>Construction schedule</SUB>; <SUB>G</SUB></ITM><BRK/>
<BRK/></SPT>
<SPT><TTL>1.2   <SUB><TAI OPT="NAVFAC DESIGN BUILD">[DESIGN AND ]</TAI>CONSTRUCTION SCHEDULE</SUB></TTL><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  Select the first bracketed option when a line or bar chart is sufficient 
to administer the project.  Generally, line and bar chart construction schedules 
should only be specified for very simple, low dollar value projects.  Select 
the second bracketed option when a CPM is desired to administer the project.  
Consult with the ROICC to determine form of construction schedule desired.</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<TXT>Prior to the start of work, prepare and submit to the Contracting Officer for acceptance a <TAI OPT="NAVFAC DESIGN BUILD">[design and ]</TAI>construction 
schedule in the form of a [progress chart] [Critical Path Method (CPM), Network Schedule] in accordance with 
the terms in Contract Clause "FAR 52.236-15, Schedules for Construction Contracts," except as modified in this 
contract.</TXT><BRK/>
<BRK/></SPT>
[<SPT><TTL>1.3   EQUIPMENT DELIVERY SCHEDULE</TTL><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  Delete this requirement if a Network Analysis Schedule will be required 
on this project.</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<SPT><TTL>1.3.1   Initial Schedule</TTL><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  Specify less time for short term projects.  Specify more time for projects 
having extensive equipment requirements.</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<TXT>Within [30] [_____] calendar days after acceptance of the proposed [design and ]construction schedule, submit 
for Contracting Officer acceptance a schedule showing procurement plans for materials and equipment.  Submit 
in the format and content as prescribed by the Contracting Officer, and include as a minimum the following information:</TXT><BRK/>
<BRK/>
<ITM INDENT="-0.33">a.  Description.</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">b.  Date of the purchase order.</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">c.  Promised shipping date.</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">d.  Name of the manufacturer or supplier.</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">e.  Date delivery is expected.</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">f.  Date the material or equipment is required, according to the current construction schedule.</ITM><BRK/></SPT>
</SPT>]<BRK/>
[<SPT><TTL>1.4   NETWORK ANALYSIS SCHEDULE (NAS)</TTL><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  Delete this requirement if an Equipment Delivery Schedule will be required 
on this project.  Determine the minimum number of activities based on the complexity 
of the project, but should be no more than one activity for every $5,000 of 
contract value.</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<TXT>[The Contractor shall use the critical path method (CPM) to schedule and control construction activities.  The 
Network shall have a minimum of [_____] construction activities.  The scheduling software that will be utilized 
by the Government on this project is [SureTrak by Primavera Systems, Inc.][Primavera Project Planner (P3) by 
Primavera Systems, Inc.].  Notwithstanding any other provision in the contract, schedules submitted for this 
project must be prepared using either Primavera P3 or Primavera SureTrak (files saved in Concentric P3 format).  
Submission of data from another software system where data conversion techniques or software is used to import 
into Primavera's scheduling software is not acceptable and will be cause for rejection of the submitted schedule.  
The schedule shall identify as a minimum:</TXT><BRK/>
<BRK/>
<ITM INDENT="-0.33">a.  <TAI OPT="NAVFAC DESIGN BUILD">[Design and ]</TAI>Construction time for all major systems and components;</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">b.  Each activity shall be assigned its appropriate Responsibility Code;</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">c.  Each activity shall be assigned its appropriate Phase Code;</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">d.  Major submittals and submittal processing time; and</ITM><BRK/>
<BRK/>
<ITM INDENT="-0.33">e.  Major equipment lead time].</ITM><BRK/>
<BRK/>
<SPT><TTL>1.4.1   CPM Submittals and Procedures</TTL><BRK/>
<BRK/>
<TXT>Submit all network analysis and updates in hard copy and [on electronic media that is acceptable to the Contracting 
Officer.  The project schedule will also be posted in the format specified as an Adobe PDF file with no relationship 
lines displayed in the graphic].  The network analysis system shall be kept current, with changes made to reflect 
the actual progress and status of the construction.</TXT><BRK/>
<BRK/></SPT>
</SPT>]<SPT><TTL>1.5   UPDATED SCHEDULES</TTL><BRK/>
<BRK/>
<TXT>Update the construction schedule and equipment delivery schedule at monthly intervals or when the schedule has 
been revised.  Reflect any changes occurring since the last update.  Submit copies of the purchase orders and 
confirmation of the delivery dates as directed.</TXT><BRK/>
<BRK/></SPT>
</PRT><PRT><TTL>PART 2   PRODUCTS</TTL><BRK/>
<BRK/>
<TXT>Not Used</TXT><BRK/>
<BRK/></PRT>
<PRT><TTL>PART 3   EXECUTION</TTL><BRK/>
<BRK/>
<TXT>Not Used</TXT><BRK/>
<BRK/></PRT>
    <END/><BRK/></SEC>