APPENDIX E

Review Procedures

This appendix contains sample review procedures for model integrity, modeling standards, survey, discipline design, and clash detection and spatial coordination. The procedures assume a particular approach to agency standards and review documentation [e.g., using a Model Element Table (MET)]. Complex review procedures, such as reviewing rebar, may need a detailed and more robust procedure to be defined through an agency’s implementation of review processes. Best practices include incorporating the review initiation process into each procedure and understanding process and product controls when choosing software to implement these procedures.

Review Initiation

Core competencies for initiating review:

• ID CDE5: Place review files in the appropriate location for the reviewer.

Review Initiation Procedures

1. Consult the project quality management plan to identify the individuals who will be acting as reviewers and provide notice that they will be receiving a review packet.
2. Thoroughly check your own work.
3. Contact the Building Information Modeling (BIM) manager to verify that the reviewer has necessary access privileges to execute and document the review.
4. Establish a review folder: Create or use an existing review folder to hold the review documentation in the common data environment (CDE).
5. Copy files to review into this folder, or provide an index of files with their locations in this folder.
6. Create review documentation files. These are the review artifacts that will be used to document the review and collect the markup. Documentation files should clearly indicate standards for the models being reviewed.
7. Notify the reviewer that files are ready for review.

Modeling Standards Review

Core competencies for executing this review:

• ID GDC1: Apply and interpret agency standards.
• ID CDE1: Apply model standards to navigate the CDE file structure.
• ID CDE2: Apply file naming conventions to identify the correct file.
• ID CDE3: Apply CADD manual to identify dependent files in the federated model.

• ID CDE4: Open a federated model using the correct workspace.
• ID CDE6: Use the appropriate software to display metadata associated with a model.
• ID DS1: Knowledge of CADD software element types.
• ID DS2: Knowledge of how software organizes and stores content for the model type.
• ID DS3: Apply model development standards to determine what types of objects contain the content.
• ID CD2: Use a software feature to execute preconfigured clash detection routines.
• ID CD3: Apply the design manual to determine appropriate clearances between objects.
• ID CD4: Configure a rule set to check for clashes between groups of model elements.
• ID GDC2: Apply and interpret discipline-specific design requirements.
• ID GDC3: Apply and interpret interdisciplinary project requirements and scope.
• ID GDC6: Execute preconfigured review procedures for the specific review type.
• ID CAD1: Apply file naming conventions that identify the model type.
• ID CAD2: Identify the correct software to open a file.
• ID NAV1: Use a software feature to pan through a model.
• ID NAV2: Use a software feature to zoom in or out of a model.
• ID NAV3: Use a software feature to orbit the viewpoint of a model.
• ID NAV4: Use a software feature to navigate through a model in a 3D view.

Review Procedures

1. View the file metadata and verify that project identifiers (e.g., project number and names) and other required metadata are applied to each file.
2. Locate individual discipline-specific model files, and open them in the appropriate software.
3. Verify the workspace settings.
   1. Verify the correct seed/template file was used.
   2. Verify coordinate system and units.
   3. Verify the correct design standards are loaded.
4. For each element type, isolate the content and view the properties to verify the correct model element types and styles or element templates have been applied.
   1. Work systematically—model element type by model element type—and record the checks by filling out a column in the MET to identify the reviewer and date of review.
   2. Assemble issues and/or comments in the review documentation.
5. For each element type, verify the elements have been developed to the appropriate LOIN per the model development standards and/or BIM Execution Plan (BEP).
   1. Work systematically—model element type by model element type—and record the checks by filling out a column in the MET to identify the reviewer and date of review.
   2. Select individual model elements to view the properties to verify that the required attributes are populated.
   3. View element geometry to verify the LOIN.
   4. Assemble issues and/or comments in the review documentation.

Model Integrity Review

Core competencies for executing this review:

• ID CDE1: Apply model standards to navigate the CDE file structure.
• ID CDE2: Apply file naming conventions to identify the correct file.
• ID CDE3: Apply CADD manual to identify dependent files in the federated model.
• ID CDE4: Open a federated model using the correct workspace.
• ID CDE6: Use the appropriate software to display metadata associated with a model.

• ID SC1: Knowledge of how CADD workspaces support model development.
• ID SC2: Apply CADD standards to identify the correct workspace and software for different models.
• ID SC3: Open CADD software in the correct workspace.
• ID DS1: Knowledge of CADD software element types.
• ID DS3: Apply Model Development Standards to determine what type of objects contain the content.
• ID CD1: Apply CADD Standards to select appropriate pre-configured clash detection routines.
• ID CD2: Use a software feature to execute pre-configured clash detection routines.
• ID CAD1: Apply file naming conventions that identify the model type.
• ID CAD2: Identify the correct software to open a file.
• ID NAV1: Use a software feature to pan through a model.
• ID NAV2: Use a software feature to zoom in or out of a model.
• ID NAV3: Use a software feature to orbit the viewpoint of a model.
• ID NAV4: Use a software feature to navigate through a model in a 3D view.

Review Procedures

1. Locate each discipline-specific model, and open to review in the appropriate software.
2. Open the other review documents (e.g., checklist, comment log, MET).
3. Check the geometric accuracy of each element or line.
   1. Work systematically—model element type by model element type—and record the checks by filling out a column in the MET to identify the reviewer and date of review.
   2. Isolate model elements to verify linework is contiguous and the geometry represents appropriate location, elevation, and slope.
   3. Record anomalies in the comment log.
4. Check the completeness of content of each element.
   1. Work systematically—model element type by model element type—and record the checks by filling out a column in the MET to identify the reviewer and date of review.
   2. Use the MET and review checklist to verify all elements required for the project are included in the model.
   3. Isolate model elements to verify there are no duplications of 2D or 3D geometry or elements.
   4. Record anomalies in the comment log.
5. Locate the federated model file, and open it to review in the appropriate software.
6. Check the federation of discipline-specific models. Work through the federation model checklist to check and record the outcomes for items such as the following:
   1. In the federated model file, verify the discipline-specific models have federated with the correct origin and coordinate system.
   2. Open the reference dialog to verify that the model has federated all required reference files correctly.
   3. Cycle through the saved views.
   4. Zoom to the horizontal extents of the model to check that all content lies within the project limits.
   5. Rotate the model in three dimensions to check that elements lie within the expected elevation range.
   6. Evaluate the interface between individual design elements and surrounding design elements for proper assembly.
   7. Verify individual elements do not overlap or have inappropriate gaps with connecting elements.
   8. Record anomalies in the comment log.

7. In the federated proposed surface file, check the proposed surface accuracy. Work through the surface checklist to check and record the outcomes for items such as the following:
   1. Check surface triangulation accuracy by viewing surface contours, breaklines, and triangulation.
   2. Verify that grading disturbance is contained within the right of way (ROW) or easement lines.
   3. Verify that the surface does not have spikes or sudden slope changes or holes.
   4. Record anomalies in the comment log.
8. Prepare review documentation for the back checker.
   1. Confirm that all review documentation and finalized review checklists are in the review folder.
   2. Update the project quality management plan with hyperlinks to the files that were reviewed and the review documentation (e.g., completed checklists, comment logs, and METs).
   3. Notify the project manager or project quality manager that the review is complete and ready for the back checker.

Survey: Geodetic

• ID GDC1: Apply and interpret agency standards.
• ID GDC5: Apply and interpret survey and geodetic control standards.
• ID GDC3: Apply and interpret interdisciplinary project requirements and scope.
• ID DS4: Knowledge of how CADD software organizes information using levels/layers.
• ID SURF4: Apply the design or survey manual to identify surface computation standards.
• ID SC1: Knowledge of how CADD workspaces support model development.
• ID SC2: Apply CADD standards to identify the correct workspace and software for different models.
• ID SC3: Open CADD software in the correct workspace.
• ID NAV1: Use a software feature to pan through a model.
• ID NAV2: Use a software feature to zoom in or out of a model.
• ID NAV3: Use a software feature to orbit the viewpoint of a model.
• ID NAV4: Use a software feature to navigate through a model in a 3D view.

Review Procedures

1. Locate individual survey file, and open it to review in appropriate software.
2. Compare the content in the model to the content in the surveyor’s notebook and to the requirements in the survey manual. Proceed sequentially through the various types of content and document both that the content has been reviewed and any issues identified.
   1. Display the control monuments to check that the locations of the primary and secondary controls are distributed around the project to support an accurate localization.
   2. Verify the elevations and coordinates on the primary and secondary controls.
3. Verify that file metadata is complete and matches the survey report.

Survey: Topographic Features and 3D Surfaces

Core competencies for executing this review:

• ID CAD1: Apply file naming conventions that identify the model type.
• ID CAD2: Identify the correct software to open a file.
• ID NAV1: Use a software feature to pan through a model.

• ID NAV2: Use a software feature to zoom in or out of a model.
• ID NAV3: Use a software feature to orbit the viewpoint of a model.
• ID NAV4: Use a software feature to navigate through a model in a 3D view.
• ID GDC1: Apply and interpret agency standards.
• ID GDC3: Apply and interpret interdisciplinary project requirements and scope.
• ID GDC2: Apply and interpret discipline-specific design requirements.
• ID GDC6: Execute preconfigured review procedures for the specific review type.
• ID DS4: Knowledge of how CADD software organizes information using levels/layers.
• ID SURF4: Apply the design or survey manual to identify surface computation standards.
• ID SC1: Knowledge of how CADD workspaces support model development.
• ID SC2: Apply CADD standards to identify the correct workspace and software for different models.
• ID SC3: Open CADD software in the correct workspace.

Review Procedures

1. Locate individual survey file, and open it to review in appropriate software.
2. Compare the content in the model to the content in the surveyor’s notebook and to the requirements in the survey manual. Proceed sequentially through the various types of content, and document both that the content has been reviewed and any issues identified.
   1. Verify that the existing topographical features follow the appropriate survey feature codes listed in the survey manual and meet agency CADD standards.
   2. Isolate and select topographical features to view property information and verify that the information is complete and within anticipated parameters.
   3. Compare modeled features to notes in the field book.
   4. Verify that topographic features are set to triangulate or not triangulate appropriately according to the survey manual.
   5. View the surface triangulation and compare to the points and breaklines to verify that the triangles correspond with the surface boundary and breaklines.
   6. Display surfaces with triangles and contours. Review visually for spikes, holes, irregularities (e.g., large areas triangulated uniformly), or obscured areas.
3. Verify that all review documentation is finalized, and transmit it back to the originator.

Survey: Land Boundaries and ROW

Core competencies for executing this review:

• ID GDC1: Apply and interpret agency standards.
• ID GDC3: Apply and interpret interdisciplinary project requirements and scope.
• ID GDC2: Apply and interpret discipline-specific design requirements.
• ID GDC4: Apply and interpret agency survey standards.
• ID DS4: Knowledge of how CADD software organizes information using levels/layers.
• ID SC1: Knowledge of how CADD workspaces support model development.
• ID SC2: Apply CADD standards to identify the correct workspace and software for different models.
• ID SC3: Open CADD software in the correct workspace.
• ID NAV1: Use a software feature to pan through a model.
• ID NAV2: Use a software feature to zoom in or out of a model.
• ID NAV3: Use a software feature to orbit the viewpoint of a model.
• ID NAV4: Use a software feature to navigate through a model in a 3D view.

Review Procedures

1. Locate the individual boundary file to check, and open it to review in appropriate software.
2. Compare the content in the model to the content in the deed search and to survey manual requirements. Proceed sequentially through various types of content (either grouped by legal boundary type or by deed record), and document both that the content has been reviewed and any issues identified.
   1. Confirm that the model’s geometry matches the legal description in the deeds. Select the feature and view property information to verify the bearings and distances in the linework.
   2. Review the linework annotations, and compare them to the property records.
   3. Assemble issues and anomalies in review documentation.
   4. Confirm that proposed ROWs or easements are displayed properly and encompass the necessary areas to construct and maintain the project.
   5. Confirm that the proposed geometry in the model is consistent with the proposed plats/legal descriptions for property acquisition.

Discipline Design Review

Core competencies for executing this review:

• ID GDC1: Apply and interpret agency standards.
• ID GDC2: Apply and interpret discipline-specific design requirements.
• ID GDC3: Apply and interpret interdisciplinary project requirements and scope.
• ID GDC6: Execute preconfigured review procedures for the specific review type.
• ID DC1: Apply the design manual to determine which calculations are model-based.
• ID DC2: Apply model development standards to determine the correct inputs for calculations.
• ID DC3: Access the reporting feature to display the inputs and results of model-based calculations.
• ID SC1: Knowledge of how CADD workspaces support model development.
• ID SC2: Apply CADD standards to identify the correct workspace and software for different models.
• ID SC3: Open CADD software in the correct workspace.
• ID NAV1: Use a software feature to pan through a model.
• ID NAV2: Use a software feature to zoom in or out of a model.
• ID NAV3: Use a software feature to orbit the viewpoint of a model.
• ID NAV4: Use a software feature to navigate through a model in a 3D view.

Review Procedures

1. Locate the federated model file, and open it to review in the appropriate software.
2. Use 3D navigation tools to visually inspect the model.
   1. Look for visual anomalies that are inconsistent with the project requirements in terms of scope, functionality, and design intent.
   2. Work systematically—model element type by model element type—and record the checks by filling out a column in the MET to identify the reviewer and date of review.
3. For calculations that were performed outside the model, verify that the model matches the calculations.
   1. Isolate individual design elements to review property data (e.g., dimensions, materials, material properties) or use measurement tools to measure lengths, areas, or angles.
   2. Check that model geometry matches project and design requirements. Document the model dimensions or values next to the design calculation.

4. For calculations performed within the model, verify that the correct resource files (e.g., design tables) were used.
   1. Open the discipline-specific calculation report and verify all inputs (e.g., design tables).
   2. Reviewers should run any reports not provided by the design team.
   3. Isolate individual design elements to review property data (e.g., alignment curve lengths) and verify that they comply with design standards.
   4. Add the reviewer’s name and date to the calculation report to document the review. Add any comments or markup to the comment log and, if appropriate, to the calculation report.
   5. Follow agency quality assurance and quality control procedures for checking calculations, including any software-automated calculations provided as reports.
5. Isolate individual design elements to review property data (e.g., pay items, materials) and conformance to agency design standards (e.g., sign placement).
   1. Work systematically—model element type by model element type—and record the checks by filling out a column in the MET to identify the reviewer and date of review.
6. Use 3D navigation tools to visually inspect the project while working through a constructability review checklist.
   1. Visually inspect for potential construction issues with surrounding elements.
   2. Visually inspect or use measuring tools to verify that there is sufficient room to maintain assets when they are in service, including a staging area and room for traffic control.
   3. Work systematically—model element type by model element type—and record the checks by filling out a column in the MET to identify the reviewer and date of review.
7. To check quantities, identify pay item units. For weight units, determine if the quantity is based on count, length, area, or volume.
   1. Work systematically—model element type by model element type and pay item number by pay item number—and record the checks by filling out a column in the MET to identify the reviewer and date of review.
   2. For quantity units, isolate and select model elements representing each pay item number, and count the number of selected elements.
   3. For length units, isolate and select model elements representing each pay item number, and display the length property or use measuring tools to sum the lengths or check against the quantity calculation.
   4. For area units, isolate and select model elements representing each pay item number, and display the area property or use measuring tools to sum the areas or check against the quantity calculation.
   5. For volume units, if the volume is based on geometric solids (e.g., concrete), isolate and select model elements representing each pay item number, and display the volume property or use measuring tools to sum the volumes or check against the quantity calculation.
   6. For volume units, if the volume is between two surfaces (e.g., earthworks), isolate the respective top and bottom surfaces, and then use a surface comparison tool to compute the volume between surfaces. Verify that the correct shrink or swell factors are applied in the calculation.
   7. Use the records in the MET to make sure that all model elements have an associated pay item number. If the pay item is not a lump sum quantity, elements should also have an associated quantity.
   8. If unexpected values occur, select all model elements of that type, and look for duplicate elements. Note quantity discrepancies in the comment log, mark up the quantity calculation sheets, or both.
   9. If there are pay items that are not associated with model elements, verify that supplemental documents (e.g., detail sheets, specifications) provide sufficient information for estimating.
8. Verify design information provided in model and supplemental documents do not conflict.

Clash Detection and Spatial Coordination Review

Core competencies for executing this review:

• ID GDC1: Apply and interpret agency standards.
• ID GDC2: Apply and interpret discipline-specific design requirements.
• ID GDC3: Apply and interpret interdisciplinary project requirements and scope.
• ID CD1: Apply CADD standards to select appropriate preconfigured clash detection routines.
• ID CD2: Use a software feature to execute preconfigured clash detection routines.
• ID CD3: Apply the design manual to determine appropriate clearances between objects.
• ID CD4: Configure a rule set to check for clashes between groups of model elements.
• ID CD5: Use a software feature to execute a preconfigured sight distance check.
• ID GDC6: Execute preconfigured review procedures for the specific review type.
• ID CAD1: Apply file naming conventions that identify the model type.
• ID CAD2: Identify the correct software to open a file.
• ID NAV1: Use a software feature to pan through a model.
• ID NAV2: Use a software feature to zoom in or out of a model.
• ID NAV3: Use a software feature to orbit the viewpoint of a model.
• ID NAV4: Use a software feature to navigate through a model in a 3D view.

Review Procedures

1. For each discipline-specific model:
   1. Locate the federated discipline model, and open it to review in the appropriate software.
   2. Select clash rules for the relevant discipline to check for hard (i.e., direct overlap) and soft (i.e., insufficient clearance) clashes.
   3. Run clash detection routines on the review model, and prepare a clash detection report to be included with review documentation.
2. Locate the federated model file, and open it to review in the appropriate software.
   1. Select clash rules for the relevant disciplines to check for hard (i.e., direct overlap) and soft (i.e., insufficient clearance) clashes.
   2. Run clash detection routines on the review model, and prepare a clash detection report to be included with review documentation.
3. Conduct a sight distance check on the federated model. If using automated tools, save the report to the review folder.
4. Run any additional spatial coordination checks required by agency standards, and document the results.
5. Check for conflicts between elements from the same and separate design disciplines (e.g., between road and utilities).
   1. Use 3D navigation tools to visually inspect the model for spatial conflicts, including overlapping elements and elements lacking sufficient buffer space (e.g., clearances between utilities).
   2. Use clash detection tools to thoroughly search for physical clashes between objects. Produce clash reports for all clashes.
   3. Note: There should be standard clash detection algorithms that select specific element types (e.g., reinforcement and post-tensioning cable ducts) for clash detection. The algorithms can check for hard clashes that have a direct overlap in space as well as soft clashes where objects lack sufficient buffer space between them. Both the selection sets (objects to compare) and the rules regarding allowed offsets (zero for a hard clash and a positive value for soft clashes) can be standardized and added to the software workspace.