|
 |
|
Engineering Systems CADD Support |
|
|
MDT As-Built Creation Issues
MDT As-built creators are running into issues relating to improperly attached reference files.
Communicational method to address this shortfall:
Information intended for internal and external consultant designers:
It has come to our attention that As-Built developers are struggling with CADD files that have non-standard reference file attachments in the design files used to create the as-builts. The non-standard reference file attachments are either improperly attached Cadd Standards files (attached using the Cadd Standards universal naming convention (UNC) instead of the logical prefix for the Cadd Standards location), and/or have files attached from share drives using a UNC to the share or from a folder on the user’s local computer rather than from files loaded into DMS (now PCMS) and attached using a proper logical prefix. This is causing staff to struggle to find solutions and to have to perform unnecessary file cleanup when attempting to create as-builts from design files.
- This is occurring on in-house and consultant designed files.
- This is occurring with regular reference files.
- This is occurring with raster reference files.
We will need designers to please not only focus on getting a PDF out, but also understand a file’s full lifecycle when considering the following:
- Properly attach the reference or detach it if it’s not part of the final package.
Here are instructional links
Enhanced Workspace Overview (Reference Files)
Handling Rasters with PCMS
- Use the “REF Check” macro from the “MDT APPS” pulldown menu.
- Plot from a CPB using the Docuplot “Plot From Network” option to help identify reference file issues. (Not applicable for the consultant community).
- Take note of the reference file validation warnings when uploading files to PCMS.
- Review the “Ref Files” report in PCMS to identify missing folder logicals.
John Pirre
MDT CADD team
|
|
|
|
