Final Design Documents Submittal. 41 Developer shall combine the RFC packages for the entire Project upon completion of all design 42 Work into a Final Design Documents package. The purpose of the Final Design Documents 43 Submittal is to create a single package of the design Plans for the entire Project, for ADOT 44 record-keeping purposes. Developer shall organize the RFC Submittals for individual Work 2 assembled in a manner similar to the standard construction documents typically provided to 3 ADOT for conventional project bidding.
Appears in 2 contracts
Samples: apps.azdot.gov, apps.azdot.gov
Final Design Documents Submittal. 41 36 Developer shall combine the RFC packages for the entire Project upon completion of all design 42 Work into a Final Design Documents package. The purpose of the Final Design Documents 43 38 Submittal is to create a single package of the design Plans for the entire Project, for ADOT 44 39 record-keeping purposes. Developer shall organize the RFC Submittals for individual Work 2 40 items, components, elements, or phases such that the Final Design Documents Submittal is 41 assembled in a manner similar to the standard construction documents typically provided to 3 42 ADOT for conventional project bidding.
Appears in 1 contract
Samples: apps.azdot.gov
Final Design Documents Submittal. 41 10 Developer shall combine the RFC packages for the entire Project upon completion of all design 42 Work into a Final Design Documents package. The purpose of the Final Design Documents 43 12 Submittal is to create a single package of the design Plans for the entire Project, for ADOT 44 13 record-keeping purposes. Developer shall organize the RFC Submittals for individual Work 2 14 items, components, elements, or phases such that the Final Design Documents Submittal is 15 assembled in a manner similar to the standard construction documents typically provided to 3 16 ADOT for conventional project bidding.
Appears in 1 contract
Samples: apps.azdot.gov