updates to cadd std. and electronic deliverables...a container file functions as the “master”...

34
Updates to CADD Std. And Electronic Deliverables

Upload: others

Post on 23-Jan-2021

4 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std. And Electronic Deliverables

Page 2: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Weather

▰ Hot▰ Cold▰ Wet▰ Dry▰ All of the above.

Page 3: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Whether

▰ I’m going to have to do the presentation

▰ I could find someone to replace me

▰ I was going to have time to complete the presentation

Page 4: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

New Terminology in ORD

▰ MicroStation\InRoads vs OpenRoads Designer (ORD)

▰ Workspace (MS\InRoads) vs Configuration (ORD)

▰ KYTC InRoads SS2 CAD Std. vs KYTC ORD CAD Std.

Page 5: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

New Terminology in ORD

▰ Geometry <- Alignments

▰ Terrain Models <- DTMs

▰ Corridor <- Roadway Designer (.IRD)

Page 6: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

New Terminology in ORD

▰ Control Features

▰ Container Files

▰ SU (SUDA) <- S&S (.SDB)

Page 7: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

https://transportation.ky.gov/CADD-Standards/Pages/default.aspx

Page 8: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

C:\KYTC_ORD_Standards\Organization-Civil\KYTC_Standards_OC

Page 9: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration

Page 10: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std._USTN_CUSTOM_CONFIGURATION

Page 11: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ What version of ORD are you using?

Page 12: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ What version of CADD standards are you using?

Page 13: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ Custom Configuration

KYTC_Standards_WSP

Page 14: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

Page 15: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ WorkSets

Page 16: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ MicroStation Table

Page 17: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ Text Favorites

Page 18: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ Truetype Fonts

▰ Font Placeholder

Page 19: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ Layout Sheet ▰ Cross Section Layout Sheet

Page 20: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

▰ Legend Sheet

Page 21: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Electronic Deliverables

Page 22: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Electronic Deliverables

Page 23: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Electronic Deliverables

Page 24: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Electronic Deliverables

▰ How should we separate alignments, corridors and superelevations?• Each alignment should have its own file.• Superelevation Sections should have their own file.• Each corridor should have its own file.

Page 25: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Electronic Deliverables

▰ KYTC established logical folder structure and file naming

Page 26: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Electronic Deliverables

▰ Geometry ▰ Superelevation ▰ Corridors

Page 27: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Container File

▰ A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc.

▰ A blank file with individual file attached as references.

• Create a container file for ALL Geometry.• Create a container file for ALL Corridors.• Create a container file for ALL Superelevation.

Page 28: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Geometry Container(Use this master file when you want all Geometry) Create 2D blank master file Reference each individual geometry dgn

Page 29: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Corridor Container(Use this master file when you want all Corridors) Create 2D blank master file Reference each individual corridor dgn Reference master geometry container (Live Nesting = 1)

Page 30: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Project Container File

▰ A blank file with individual file attached as references.▰ Contains ALL container files (Geometry, Corridors, Superelevation,

etc.▰ Use as the master model for plan sheets, cross section, design

checks and conflict analysis.

Page 31: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Project Container File Contains ALL container files (Geometry, Corridors, Superelevation, etc. Use as the master model for plan sheets, cross section, design checks

and conflict analysis.

Page 32: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

ORD Training

Page 33: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Updates to CADD Std.

https://transportation.ky.gov/CADD-Standards/Pages/default.aspx

Page 34: Updates to CADD Std. And Electronic Deliverables...A Container file functions as the “Master” file for geometry, corridors, proposed terrain, etc . A blank file with individual

Electronic Deliverables

Questions

[email protected]