Construction data packet overview
Last updated: 2023-11-01
Requirement: The designer shall create a Construction Data Packet for each let project with a geospatially accurate reference alignment. Submitted data required for a project is dependent on the scope of the project. See Table 43.4 for recommended data by project type. See Table 43.3 for accepted file formats. Unused layers and referenced data should not be included in the Construction Data Packet.
Terminology
AMG: Automated Machine Guidance. The most common uses of AMG on WisDOT construction projects are for earthwork grading and aggregate placement. AMG paving applications are emerging on our projects also.
Construction Data Packet (CDP): Digital data files with survey, design, and staking information. CDPs are delivered with the design project, and are provided to bidders at project advertisement.
DTM: Digital Terrain Model. An object used to represent terrain in Civil 3D and other civil engineering software. DTMs consist of an irregular network of 3D triangle faces developed from 3D points and 3D breaklines (linear terrain features).
3D Surface Model: Construction Data Packet representation of terrain. Proposed work surface models consist of a DTM, breakline file, and surface boundary file. Existing ground surface models consist of a DTM, and a surface boundary file.
Design Model: Construction Data Packet representation of proposed work terrain. Design models are required to contain Top and Datum surface models.
Construction Model: DTMs employed by the contractor(s) in AMG and other construction operations. Contractors are responsible for construction model development.
Purpose
CDPs contain design survey information, roadway design information, and construction staking reports. Formats used are consumable in survey systems used for construction staking, and in contractor software used in advanced model-based workflows. Some of the information in a CDP is provided elsewhere, in roadway plans for example, so what is the purpose of CDPs? In many cases, the traditional construction contract document sources of the design information (typically the plan) requires the re-creation of data if it is to be used in other systems. When the survey, design, and staking information is packaged in the formats specified for the CDPs, meaningful project data is transferred directly into contractor systems, creating opportunities for increased efficiency in construction project activities. Other types of CDP information may not be readily available in Plans, but can be extracted from the design project data and shared with contractors to allow for additional efficiencies. Generally, any WisDOT project with a construction reference line should have a CDP associated with it.
WisDOT shares CDPs with our contractors for convenience. While the CDP is a contractual design project deliverable, it does not have construction contract document status for construction projects. If there is a discrepancy between the information in the plan and the information in the CDP, the contractor is required to build the project according to the plan. Typically, contractors invest time and effort in the verification of the CDP , comparing it to the plan as the plan is the contractual document. The Department needs to make sure the CDP delivered is consistent with the plan. The WisDOT roadway design workflows were developed with this primary goal in mind.
In order to have a more thorough understanding of the purpose of the CDP, a conversation about the intended uses of the information provided in the packet is needed. WisDOT has received feedback from contractors regarding benefits of using the CDPs. Much of the pre-bid benefit of CDPs comes from the existing ground surface model and the proposed work surface models. These models are delivered in highly portable data formats, and can be used directly in contactor software with very little data import effort. Within minutes contractors have a complete representation of existing and proposed terrain and are now enabled to prepare bids in ways they haven't been able to in the past, as most contractors will not invest in proposed work model development until they've won the bid. They can use this information to analyze and confirm the project quantities. They can get a more accurate account of the distribution of earthwork volumes of a project, which can help plan various aspects of construction operations to a much greater level of detail than projects without Design Models. They can assess operational alternatives to optimize the project game plan of how to conduct operations. This deeper level of plan helps contractors reduce the unknowns about the project which reduces risk. Risk reduction in the competitive bidding environment results in more competitive bids.
Construction Data Packet uses don't stop with the Letting, the benefits extend into construction project activities. Automated Machine Guidance applications use the Construction Model DTM surfaces to define proposed work. The Design Model proposed work surface models in the CDP give contractors a head start in the development of their construction models. On WisDOT projects, contractors often do not use the Design Model surfaces directly in their operations. Direct design model surface usage does happen occasionally, but it seems to be more the exception than the rule. Contractors are employing AMG in different ways. The structure of Construction model surfaces, the feature representation, and the level of detail can all vary from one contractor to the next. The reasons for these differences in AMG methodology depend upon who is asked, but there is a common underlying reason – contractors want to gain a competitive advantage over their counterparts. The use of AMG has evolved and matured in contractors independent organizations. They have invested in equipment and hardware, and they have also invested in the education and training of staff. Contractors want to protect those investments by retaining their methodologies. WisDOT wants to support and facilitate this kind of innovation when possible, and at the very least, foster an environment that allows innovation to occur.
In the early days of 3D Design at WisDOT, The Department had a goal of delivering 100% construction ready surface models in Design Models. As experience has grown, WIsDOT has come to understand there are differences in how contractors use AMG, and these differences are sometimes reflected in their construction models. There is no single surface model concept that will work for all contractors on all types of projects. This understanding of how AMG technologies are being employed on WisDOT projects has reduced the importance of high levels of precise detail in the DTM component of Design Model surface models, and has increased the importance of proposed surface model breakline delivery. Breaklines are the foundation of surface model development, and providing those foundational elements directly from our design data gives contractors a base platform from which they can develop construction models.
The post-bid benefits of our CDPs aren't limited to design model surfaces and AMG technology uses, construction staking contractors use CDP staking reports and other design information to streamline their processes too. The CDP staking data is formatted for easy import into survey systems, and makes design data transfer much more efficient compared to manual transfer from plan sheets. Design Model surfaces have uses in construction staking also, allowing for establishment of proposed grade anywhere on a project.
Finally, the models in our CDPs can facilitate better communication on our construction projects. Communication between all project staff, engineering and contractor. And, models are particularly useful in communicating project information with non-industry people such as property owners, local officials, businesses, and other stakeholders who aren't familiar with our traditional plan sheet representations of project concepts.
Requirements
| Requirements | Standards |
|---|---|
| Submittal process | FDM 19-10-43.2 Construction Data Packet Submittal |
| List and description of digital design data Categories | FDM 19-10-43.5, Table 43.2 Digital Data Exchange Categories |
| File formats for data in each Category | FDM 19-10-43.5, Table 43.3 Digital Data Exchange Accepted Formats by Category |
| Digital data provided based on project type | FDM 19-10-43.6, Table 43.4 Recommended Electronic Project Data by Project Type |
| Construction Data Packet directory structure | FDM 15-5 Attachment 3.1 CADDS AutoCAD Civil 3D Project Folder Structure Standard |
| Transmittal document to contractors "Civil 3D Metadata Sheet for WisDOT Project - Construction Data Packet" (includes directory structure and file naming conventions) | C3DKB WisDOT Civil 3D forms |
| Construction Data Packet Feedback | C3DKB WisDOT Civil 3D forms |
Workflows
Warning: Contractor data files are files exported from design files. They do not have a live connection to the files they were created from. They only need to be generated for P.S.& E. delivery.
The const folder structure is embedded in the WisDOT Civil 3D project template.
Refer to Attachment 1 - File Information in the Civil 3D Metadata Sheet for WisDOT Project - Construction Data Packet document for a description of the information included in each data export.
| Data | Folder | Exported File | Training Link |
|---|---|---|---|
| Construction Data Packet metadata sheet | const | Construction Data Packet metadata sheet | |
| Field Control Data - Survey control points | const\CD-BaseData | < Construction_ID >-SurvCtrl.xml | Export LandXML files |
| Field Control Data - Datum documentation | const\CD-BaseData | < Construction_ID >-DT1773.docx | Geodetic references documentation |
| Existing Surface - DTM | const\CD-BaseData | < Construction_ID >-Surf-Ex.xml | Export LandXML files |
| Existing Surface - Boundary | const\CD-BaseData | < Construction_ID >-Surf-Ex-Bndry.dwg | Export ACAD DWG files |
| Existing Topography - General | const\CD-BaseData | < Construction_ID >-Topo-Ex.dwg | Export ACAD DWG files |
| Existing Topography - Utilities | const\CD-BaseData | < Construction_ID >-Uti-Ex.dwg | Export ACAD DWG files |
| Reference Line / Profile - Mainlines | const\CD-Design\CD-AliProf | < Construction_ID >-AliProf-RL.xml | Export LandXML files |
| Reference Line / Profile - Edgelines | const\CD-Design\CD-AliProf | < Construction_ID >-AliProf-Pavt.xml | Export LandXML files |
| Superelevation Data | const\CD-Design\CD-AliProf | < Construction_ID >-Super-Ali-< Ali Name >.csv or .xlsx | Export alignment superelevation data |
| Proposed Point Data | const\CD-Design | < Construction_ID >-Pts-< Location Desc >.xml | Export LandXML files |
| Proposed Roadway Features | const\CD-Design | < Construction_ID >-Pavt.dwg | Export ACAD DWG files |
| Proposed Structure Horizontal Features | const\CD-Design | < Construction_ID >-Struct.dwg | Export ACAD DWG files |
| Proposed Surface - Datum Breaklines / Boundary | const\CD-Design\CD-Surface | < Construction_ID >-Datum-Breaklines-< Const-Stg >.dwg | Extract design surface breaklines |
| Proposed Surface - Datum DTM | const\CD-Design\CD-Surface | < Construction_ID >-Datum-Surf-< Const-Stg >.xml | Export LandXML files |
| Proposed Surface - Top Breaklines / Boundary | const\CD-Design\CD-Surface | < Construction_ID >-Top-Breaklines-< Const-Stg >.dwg | Extract design surface breaklines |
| Proposed Surface - Top DTM | const\CD-Design\CD-Surface | < Construction_ID >-Top-Surf-< Const-Stg >.xml | Export LandXML files |
| Proposed Surface - Top Rural Driveway Breaklines / Boundary | const\CD-Design\CD-Surface | < Construction_ID >-Top-Breaklines-RuralDwy.dwg | Extract design surface breaklines |
| Proposed Surface - Top Rural Driveway DTM | const\CD-Design\CD-Surface | < Construction_ID >-Top-Surf-RuralDwy.xml | Export LandXML files |
| Proposed Cross Section Data | const\CD-Design\CD-X-Section | < Construction_ID >-Slp-Stk-< Ali >-< Const-Stg >.xlsx | Export cross section slope stake files |
| Earthwork Data | const\CD-Design\CD-X-Section | < Construction_ID >-EWK-< Ali >-< Const-Stg >.xlsx | Copy earthwork data spreadsheet |
| Right-of-Way Monumentation - Points | const\CD-RW | < Construction_ID >-Pts-Ult-RW.xml | Export LandXML files |
| Right-of-Way Monumentation - Lines | const\CD-RW | < Construction_ID >-Ult-RW.dwg | Export ACAD DWG files |
| Zip const folder for submittal | const | < Construction_ID >-cdp.zip | Create Zip file of ConstData folder for delivery |