1、*USACE / NAVFAC / AFCESA / NASA UFGS-01 32 01.00 10 (August 2008)-Preparing Activity: USACE SupersedingUFGS-01 32 01.00 10 (July 2007)UNIFIED FACILITIES GUIDE SPECIFICATIONSReferences are in agreement with UMRL dated July 2008*SECTION TABLE OF CONTENTSDIVISION 01 - GENERAL REQUIREMENTSSECTION 01 32
2、01.00 10PROJECT SCHEDULE08/08PART 1 GENERAL1.1 REFERENCES1.2 SUBMITTALS1.3 QUALITY ASSURANCEPART 2 PRODUCTS (Not Applicable)PART 3 EXECUTION3.1 GENERAL REQUIREMENTS3.1.1 Approved Poject Schedule3.1.2 Schedule Status Reports3.1.3 Default Terms3.2 BASIS FOR PAYMENT AND COST LOADING3.3 PROJECT SCHEDULE
3、 DETAILED REQUIREMENTS3.3.1 Critical Path Method3.3.2 Level of Detail Required3.3.2.1 Activity Durations3.3.2.2 Design and Permit Activities3.3.2.3 Procurement Activities3.3.2.4 Mandatory Tasks3.3.2.5 Government Activities3.3.2.6 Activity Responsibility Coding (RESP)3.3.2.7 Activity Work Area Coding
4、3.3.2.8 Contract Changes/Requests for Equitable Adjustment (REA) Coding (MODF)3.3.2.9 Contract Line Item (CLIN) Coding (BIDI)3.3.2.10 Phase of Work Coding (PHAS)3.3.2.11 Category of Work Coding (CATW)3.3.2.12 Definable Features of Work Coding (FOW1, FOW2, FOW3)3.3.3 Scheduled Project Completion and
5、Activity Calendars3.3.3.1 Project Start Date3.3.3.2 Schedule Constraints and Open Ended Logic3.3.3.3 Early Project CompletionSECTION 01 32 01.00 10 Page 1Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-3.3.4 Interim Completion Dates3.3.4.1 Start Phas
6、e3.3.4.2 End Phase3.3.4.3 Phase “X“ Hammock3.3.5 Default Progress Data Disallowed3.3.6 Out-of-Sequence Progress3.3.7 Negative Lags and Start to Finish Relationships3.3.8 Calculation Mode3.3.9 Milestones3.4 PROJECT SCHEDULE SUBMISSIONS3.4.1 Preliminary Project Schedule Submission3.4.2 Initial Project
7、 Schedule Submission3.4.3 Design Package Schedule Submission3.4.4 Periodic Schedule Updates3.4.5 Standard Activity Coding Dictionary3.5 SUBMISSION REQUIREMENTS3.5.1 Data CDs3.5.2 Narrative Report3.5.3 Approved Changes Verification3.5.4 Schedule Reports3.5.4.1 Activity Report3.5.4.2 Logic Report3.5.4
8、.3 Total Float Report3.5.4.4 Earnings Report by CLIN3.5.5 Network Diagram3.5.5.1 Continuous Flow3.5.5.2 Project Milestone Dates3.5.5.3 Critical Path3.5.5.4 Banding3.5.5.5 S-Curves3.6 PERIODIC SCHEDULE UPDATE MEETINGS3.6.1 Update Submission Following Progress Meeting3.6.2 Status of Activities3.6.2.1
9、Start and Finish Dates3.6.2.2 Remaining Duration3.6.2.3 Percent Complete3.6.2.4 Logic Changes3.6.2.5 Other Changes3.7 REQUESTS FOR TIME EXTENSIONS3.7.1 Justification of Delay3.7.2 Submission Requirements3.7.3 Additional Submission Requirements3.8 DIRECTED CHANGES3.9 WEEKLY PROGRESS MEETINGS3.10 OWNE
10、RSHIP OF FLOAT3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS- End of Section Table of Contents -SECTION 01 32 01.00 10 Page 2Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-*USACE / NAVFAC / AFCESA / NASA UFGS-01 32 01.00 10 (August 2008)-Preparing Acti
11、vity: USACE SupersedingUFGS-01 32 01.00 10 (July 2007)UNIFIED FACILITIES GUIDE SPECIFICATIONSReferences are in agreement with UMRL dated July 2008*SECTION 01 32 01.00 10PROJECT SCHEDULE08/08*NOTE: This guide specification covers the requirements for the preparation and maintenance of the project sch
12、edule for construction projects or design-build construction projects.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.Remove information and requirements not requi
13、red in respective project, whether or not brackets are present.Comments and suggestions on this guide specification are welcome and should be directed to the technical proponent of the specification. A listing of technical proponents, including their organization designation and telephone number, is
14、 on the Internet.Recommended changes to a UFGS should be submitted as a Criteria Change Request (CCR).This guide specification includes tailoring options for construction and design-build construction projects. Selection or deselection of a tailoring option will include or exclude that option in the
15、 section, but editing the resulting section to fit the project is still required.*PART 1 GENERAL*NOTE: Selection of the optional requirements in this guide specification should be coordinated with Construction Division to ensure that the schedule requirements are appropriate for the complexity of th
16、e constructability portion of the BCOE review. See ER 415-1-11. Paragraphs may not be removed from SECTION 01 32 01.00 10 Page 3Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-this specification except as noted.If it is desired to monitor a Contracto
17、rs schedule by use of an in-house program, this will require use of the Standard Data Exchange Format (SDEF). Use of proprietary systems will not be specified. See ER 1-1-11, Appendix A.*1.1 REFERENCES*NOTE: This paragraph is used to list the publications cited in the text of the guide specification
18、. 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 Wizards Check Reference feature when you add a RID outside of the Sections Reference Article to automatically place the reference in t
19、he Reference Article. Also use the Reference Wizards 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 l
20、isted 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)ECB 2005-10 (2005) Scheduling Requirements for Testing of Mechanical Systems in ConstructionER 1-1-11 (1995) Prog
21、ress, Schedules, and Network Analysis Systems1.2 SUBMITTALS*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
22、 quality control.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 Contractors Quality Control system. Only add a
23、“G” if the SECTION 01 32 01.00 10 Page 4Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-submittal is sufficiently important or complex in context of the project.For submittals requiring Government approval on Army projects, a code of up to three char
24、acters 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 Of
25、fice); “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.Choose the first bracketed item for Navy, Air Force and NASA projects, or choose the second bracketed item for Army projects.*Gove
26、rnment approval is required for submittals with a “G“ designation; submittals not having a “G“ designation are for Contractor Quality Control approval.information only. When used, a designation following the “G“ designation identifies the office that will review the submittal for the Government. Sub
27、mit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:SD-01 Preconstruction SubmittalsProject Schedule; G; G, _1.3 QUALITY ASSURANCEDesignate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and prepar
28、ation of reports. The authorized representative shall be experienced in schedulinghave previously developed, created, and maintained at least 2_ electronic schedules for projects similar in nature and complexity to this project and shall be experienced in the use of the scheduling software that meet
29、s the requirements of this specification.PART 2 PRODUCTS (Not Applicable)PART 3 EXECUTION3.1 GENERAL REQUIREMENTS*NOTE: Selection of construction or design-build construction text required.*Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CO
30、NSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project, including the SECTION 01 32 01.00 10 Page 5Provided by IH
31、SNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-design and construction sequences, is required. The scheduling of constructiondesign and construction is the responsibility of the Contractor. Contractor management personnel shall actively participate in its develop
32、ment. Subcontractors and suppliersDesigners, Subcontractors and suppliers working on the project shall 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.3.1.1 Approved Poject ScheduleUse the
33、approved Project Schedule to measure the progress of the work and to aid in evaluating time extensions. Make the schedule cost loaded and activity coded. The schedule will provide the basis for all progress payments. If the Contractor fails to submit any schedule within the time prescribed, the Cont
34、racting Officer may withhold approval of progress payments until the Contractor submits the required schedule.3.1.2 Schedule Status ReportsProvide a Schedule Status Report on at least a monthly basis. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, t
35、he Contractor shall take steps necessary to improve its progress including those that may be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting Officer may require the Contractor to increase the number of shifts, overtime operations,
36、 days of work, and/or the amount of construction plant, and to submit for approval any supplementary schedule or schedules as the Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.3.1.3 Default TermsFailure of the Contractor to comply with the requ
37、irements of the Contracting Officer shall be grounds for a determination, by the Contracting Officer, that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the contract. Upon making this determination, the Contracting Officer may
38、terminate the Contractors right to proceed with the work, or any separable part of it, in accordance with the default terms of the contract.3.2 BASIS FOR PAYMENT AND COST LOADINGUse the schedule as the basis for determining contract earnings during each update period and therefore the amount of each
39、 progress payment. Lack of an approved schedule update, or qualified scheduling personnel, will result in the inability of the Contracting Officer to evaluate contract earned value for the purposes of payment. Failure of the Contractor to provide all required information will result in the disapprov
40、al of the preliminary, initial and subsequent schedule updates. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, eac
41、h payment period, until such revisions to the Project Schedule have been made. Activity cost loading shall be reasonable, as determined by the Contracting Officer. The aggregate value of all activities coded to a contract CLIN shall equal the value of the CLIN on the Schedule.SECTION 01 32 01.00 10
42、Page 6Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-3.3 PROJECT SCHEDULE DETAILED REQUIREMENTSThe computer software system utilized to produce and update the Project Schedule shall be capable of meeting all requirements of this specification. Failu
43、re of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule.3.3.1 Critical Path MethodUse the Critical Path Method (CPM) of network calculation to generate the Project Schedule. Prepare the Project Schedule using the Precedence Diagram Method (P
44、DM).3.3.2 Level of Detail RequiredDevelop the Project Schedule to an appropriate level of detail. Failure to develop the Project Schedule to an appropriate level of detail, as determined by the Contracting Officer, will result in its disapproval. The Contracting Officer will consider, but is not lim
45、ited to, the following characteristics and requirements to determine appropriate level of detail:3.3.2.1 Activity DurationsReasonable 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 shall have Original Durations (OD) greater than 20 work days or 30 calend
