This appendix contains a collection of 3D modeling terms, definitions, references, synonyms, attributes, and metadata about the design and 3D model–review process and documentation (Table C-1). This vocabulary list can serve as a starting point for agencies to develop their own lists of synonyms. Agencies need to manage their own vocabularies so they can cross-reference different standards.
Table C-1. Review documentation property set.
| Field 1 | Project Identifier |
| Synonyms | Project ID |
| Requirement | Optional |
| Type | String or Integer |
| Contents | 6–40 alphanumeric characters (string) or 0–999,999,999 (integer) |
| Description | A project number or another identifier that can be used to connect review documentation to the project dataset. |
| Field 2 | Document Type |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 3–40 alphanumeric characters |
| Description | The type of document being reviewed (e.g., calculations, design model), which could come from a lookup list. |
| Field 3 | Milestone |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–40 alphanumeric characters (string) |
| Description | The stage of the project development life cycle in which the review occurred. Should be populated by a lookup list. |
| Field 4 | Discipline |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–40 alphanumeric characters (string) |
| Description | The discipline of the content being reviewed. Should be populated using a lookup list. |
| Field 5 | Functional Area |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–40 alphanumeric characters (string) |
| Description | The subdiscipline/functional area of the content being reviewed. Should be populated using a lookup list. Can use the “Functional Areas” taxonomy. |
| Field 6 | Review Type |
| Synonyms | Scope |
| Requirement | Optional |
| Type | String |
| Contents | 6–500 alphanumeric characters (string) |
| Description | A description of the review’s specific purpose. Could be populated using the “Review Type” taxonomy. |
| Field 7 | Review Criteria |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–500 alphanumeric characters (string) |
| Description | The standard against which the review is executed (e.g., code, manual, checklist). |
| Field 8 | Originator |
| Synonyms | Designer, Drafter |
| Requirement | Required |
| Type | String |
| Contents | 6–40 alphanumeric characters (string) |
| Description | The name of the individual responsible for the content being reviewed. The project manager is responsible for implementing the quality management process, but a review may be initiated by a designee, such as a discipline lead or model author. |
| Field 9 | Transmittal Date |
| Synonyms | N/A |
| Requirement | Required |
| Type | Date or String |
| Contents | Date or String |
| Description | The date on which the originator submitted materials for review. |
| Field 10 | Reviewer |
| Synonyms | Checker |
| Requirement | Required |
| Type | String |
| Contents | 6–140 alphanumeric characters (string) |
| Description | The name of the individual responsible for reviewing the content. |
| Field 11 | Review Date |
| Synonyms | N/A |
| Requirement | Required |
| Type | Date or String |
| Contents | >1/1/2020 (date) or 6–40 alphanumeric characters (string) |
| Description | The date on which the reviewer completed their review. |
| Field 12 | Reviewer Title |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–140 alphanumeric characters (string) |
| Description | The reviewer’s professional title, included as a way to demonstrate the reviewer’s expertise to justify their position as a reviewer. Some DOTs have seniority requirements for conducting specific review types. |
| Field 13 | Reviewer Credentials |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–140 alphanumeric characters (string) |
| Description | The reviewer’s credentials (i.e., certifications or other qualifications). Some DOTs require specific types of reviewers to be professional engineers. |
| Field 14 | Back Checker |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–140 alphanumeric characters (string) |
| Description | The name of the person who goes over the reviewer’s comments and markup and resolves issues or areas of nonconcurrence. This person may be the originator. May not be required for early design reviews. |
| Field 15 | Back Check Date |
| Synonyms | N/A |
| Requirement | Optional |
| Type | Date or String |
| Contents | > 1/1/2020 (date) or 6–40 alphanumeric characters (string) |
| Description | The date the back checker completed the back check. |
| Field 16 | Corrector |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–140 alphanumeric characters (string) |
| Description | The name of the person who made corrections in the design documents. This person may be the originator. |
| Field 17 | Verifier |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–140 alphanumeric characters (string) |
| Description | The name of the person who verified that corrections were adequately addressed. This person may be the reviewer. |
| Field 18 | Verification Date |
| Synonyms | N/A |
| Requirement | Optional |
| Type | Date or String |
| Contents | > 1/1/2020 (date) or 6–40 alphanumeric characters (string) |
| Description | The date that corrections were verified. |
| Field 19 | Certifier |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–140 alphanumeric characters (string) |
| Description | The name of the discipline lead or design manager who certifies that the design was completed to the agency’s specifications and within a comprehensive quality management framework. Typically, only final deliverables are certified. |
| Field 20 | Certification |
| Synonyms | N/A |
| Requirement | Optional |
| Type | Boolean |
| Contents | Yes/No |
| Description | Yes/No, indicates whether the certifier has certified the design. |
| Field 21 | Certification Date |
| Synonyms | N/A |
| Requirement | Optional |
| Type | Date or String |
| Contents | >1/1/2020 (date) or 6–40 alphanumeric characters (string) |
| Description | The date on which the design was certified. |
| Field 22 | Auditor |
| Synonyms | N/A |
| Requirement | Optional |
| Type | String |
| Contents | 6–140 alphanumeric characters (string) |
| Description | The name of the person who audits the project’s quality documentation. |
| Field 23 | Audit Date |
| Synonyms | N/A |
| Requirement | Optional |
| Type | Date or String |
| Contents | >1/1/2020 (date) or 6–40 alphanumeric characters (string) |
| Description | The date on which the auditor audited the quality documentation. |