Common use of SCHEDULE DEVELOPMENT Clause in Contracts

SCHEDULE DEVELOPMENT. 9 The Parties will use the Project Schedule for planning and monitoring the progress of the Work, 10 and theto verify Draw Requests in accordance with Article 13 of the Agreement. The Project 11 Schedule serves as the foundation for the Monthly Progress Schedule. Developer shall 12 coordinate with Governmental Entities when developing and maintaining the Project Schedule 13 and shall make provisions for adjacent projects and Governmental Entities comments. 14 Developer shall ensure that the Project Schedule reflects the following information: 15 A. Activity Identification. Activities must be assigned consistent descriptions, identification 16 codes, and sort codes. Sort code schemes (a) are subject to ADOT’s prior consent, (b) 17 must group activities using meaningful schemes defined by Developer and ADOT, and 18 (c) must designate lead responsibility for each activity, and (d) clearly identify each 19 Project Schedule Submittal. Resubmissions of Project Schedules must use the same 20 revision number as the original submission individually identified by a sequential 21 appended letter (A, B, etc.), as an indication of a revised version. Developer shall 1 identify Work being performed by Disadvantaged Business Enterprise (DBE) firms as 2 separate CPM activities.

SCHEDULE DEVELOPMENT. 9 The Parties will use the Project Schedule for planning and monitoring the progress of the Work, 10 and theto to verify Draw Requests in accordance with Article 13 of the Agreement. The Project Schedule 11 Schedule serves as the foundation for the Monthly Progress Schedule. Developer shall 12 coordinate with 12 Governmental Entities when developing and maintaining the Project Schedule 13 and shall make 13 provisions for adjacent projects and Governmental Entities comments. 14 Developer shall ensure 14 that the Project Schedule reflects the following information: 15 A. Activity Identification. Activities must be assigned consistent descriptions, identification 16 codes, and sort codes. Sort code schemes (a) are subject to ADOT’s prior consent, (b) 17 must group activities using meaningful schemes defined by Developer and ADOT, and 18 (c) must designate lead responsibility for each activity, and (d) clearly identify each 19 Project Schedule Submittal. Resubmissions of Project Schedules must use the same 20 revision number as the original submission individually identified by a sequential 21 1 appended letter (A, B, etc.), as an indication of a revised version. Developer shall 1 2 identify Work being performed by Disadvantaged Business Enterprise (DBE) firms as 2 3 separate CPM activities.

SCHEDULE DEVELOPMENT. 9 8 The Parties will use the Project Schedule for planning and monitoring the progress of the Work, 10 Work and theto to 9 verify Draw Requests in accordance with Article 13 12 of the Agreement. The Project 11 Schedule serves as 10 the foundation for the Monthly Progress Schedule. Developer shall 12 coordinate with Governmental Entities 11 when developing and maintaining the Project Schedule 13 and shall make provisions for adjacent projects 12 and Governmental Entities Entities’ comments. 14 Developer shall ensure that the Project Schedule reflects the 13 following information: 15 A. : 14 Activity Identification. Activities must shall be assigned consistent descriptions, identification 16 codes, 15 and sort codes. Sort code schemes (a) are subject to ADOT’s prior consentapproval, (b) 17 must shall group 16 activities using meaningful schemes defined by Developer and ADOT, and 18 (c) must shall designate lead 17 responsibility for each activity, and (d) clearly identify each 19 Project Schedule Submittal. 18 Resubmissions of Project Schedules must shall use the same 20 revision number as the original 19 submission individually identified by a sequential 21 appended letter (A, B, etc.), as an indication 20 of a revised version. Developer shall 1 identify Work being performed by Disadvantaged Business Enterprise (DBE) firms as 2 separate CPM activities.;