1 / 15

MicroStation / InRoads Demonstration

MicroStation / InRoads Demonstration. Gary Holeman Senior Design and Automation Engineer Gary.M.Holeman@odot.state.or.us. ACEC Suggested Topics for Discussion. Practical Tips for Better Use Pull down menus How ODOT implements What do Contractors have to do, specifically

baby
Download Presentation

MicroStation / InRoads Demonstration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MicroStation / InRoads Demonstration Gary Holeman Senior Design and Automation Engineer Gary.M.Holeman@odot.state.or.us

  2. ACEC Suggested Topics for Discussion • Practical Tips for Better Use • Pull down menus • How ODOT implements • What do Contractors have to do, specifically • Where are their choices • Plan Sheets

  3. Ambiguous Topics for Discussion • Practical Tips for Better Use • Pull down menus • How ODOT implements • What do Contractors have to do, specifically • Where are their choices • Plan Sheets

  4. Practical Tips for Better Use • New MDL – SScloud • Places a defined cloud around an area. • InRoads .ini’s • Some are not set to ODOT’s standards, or perhaps I should say some are. • InRoads Standards committee/CAD Standards Committee. • Seed Files

  5. InRoads Standards committee • Working on configuring InRoads to conform as close as possible to the CAD Standards • In Planning, a manual similar to the Contract Plans Development Guide, for InRoads.

  6. CAD Standards Committee • Manage change to ODOT’s CAD Standards • Review existing standard for errors and omissions

  7. Seed Files • MicroStation Seed Files • C:\Program Files\odot_space\Standards\seed • InRoads Seed files • C:\Program Files\odot_space\ENG_APP\InRoads

  8. Pull down menus • Navigation of the menus • If missing menus what to do • If inconsistencies what to do • Order Of Precedence • Plan Menus • Quick Guide • CPDG and other manuals/guides • When all else fails, e-mail or call.

  9. How ODOT implements • Changes to ODOT Workspace • Internally we update once per month if there are any changes. • As ODOT moves to using By-Level Symbology, the symbology will change with the workspace. • Changes do not need to be incorporated into projects in advanced stages, unless specifically noted. • Example, Highway Engineer Stamp on Title Sheet.

  10. Changes to ODOT Workspace • ODOT maintains an incomplete list of consultants using our workspace. • If your firm uses the workspace, but doesn’t get announcements of updates, please e-mail me • If your firm gets the announcement, but to the wrong person, please e-mail me

  11. What do Contractors have to do, specifically • Define the 305 spec in relation to MicroStation/InRoads deliverables. • Talk about SP 305. • SP 305 will be re-written. • Inroads Standards • TC Names

  12. Where are their choices • Contract Plans Development Guide • Bridge • Traffic • GeoEnvironmental • Geotech • Hydraulics • Roadside Development • Environmental • Etc.

  13. Plan Sheets • CPDG • What makes a Quality Deliverable? • Consistency. • Follow CPDG • Use ODOT WorkSpace

  14. ODOT WorkSpace ftp://ftp.odot.state.or.us/isb/appeng/MicroStation/Version8/

  15. Key Contact List • Region Designer/Drafter • Gary Holeman, Automation Engineer Gary.M.Holeman@odot.state.or.us 355 Capitol St. NE, Room 222 Salem, OR 97301 (503)986-3758 • Dave Polly, Standards Engineer David.J.Polly@odot.state.or.us 355 Capitol St. NE, Room 222 Salem, OR 97301 (503)986-3738

More Related