American Society of Highway Engineers 2016 Fall Technical Seminar

Transcription

1 American Society of Highway Engineers 2016 Fall Technical Seminar University Club November 10 th, :30 PM

2 INTRODUCTION

3 Agenda Registration: 12:00 pm Lunch 12:30 pm Presentation 1: 1:00 2:30 pm Designing North Carolina s Roads in the new Era Oak Thammavong, Assistant Project Design Engineer, Roadway Design Support & Development, NCDOT Description: We will be taking a look at what s changing with our current workflows and providing a glimpse of perhaps what a typical Roadway Engineer work environment would be like using the latest OpenRoads Technology and OpenRoads Designer CONNECT Edition from Bentley. Questions: 15 minutes Break: 2:45 3:00 pm

4 Agenda Presentation 2: 3:00 4:30 pm Moving Projects Online with NCDOT Ellen H. Dickson, PMP, Manager, Engineering Content Management, NCDOT Description: Learn about how NCDOT and its engineering partners are moving online together using first SharePoint and later Bentley s ProjectWise. New online Preconstruction project sites are being established to allow organized storage, exchange and collaboration on project content. This presentation will demonstrate the capabilities and uses of the new sites and explain NCDOT s future direction using SharePoint. Questions: 15 minutes Adjourn: 4:30 pm

5 ASHE Fall Luncheon 2016 Designing North Carolina s Roads Oak Thammavong NCDOT Roadway Design Unit

6 Dawn of the New Era The Sunrise Sunset Paradox 2

7 Planned Implementation (Launching) Several Years in the Making 3

8 Milestones in the Technology Timeline PAST PRESENT FUTURE GEOPAK GPK/COGO Criteria XS SS2/SS3/SS4 Corridor Modeling Civil Geometry (near) CONNECT Editions ORD 4

9 Why Target OpenRoads Designer CONNECT Edition? Limited Timeframe and Resources for Development, Standardization, Policy Changes, Training, & Implementation New Workspace & Worksets 64-bit Architecture for Significant Performance Boost New Ribbon Base GUI Most Complete Version of ORD GPK-less Geometry D&C Manager (DDB) no longer needed for Drafting, Payitems, & Alignment Layout New Superelevation Engine 5

10 Native Style in SS3/SS4 No Longer Needed 7 New Feature Types/Definitions (SS3/SS4 only 3) Doc Center for Plan Preparation Tools Dynamic Labeling (XS, Plan, Profile, etc.) New ICM File Format (SS3 SS4 CONNECT?) More Flexible Export Options for AMG (Trimble, TopCon, [ future Carlson & Leica DC Integration? ]) No Corridor Modeling and Roadway Designer Dialog Boxes No GEOPAK, InRoads, or MX No Criteria 6

11 System Requirements for ORD CONNECT 7

12 32-bit vs. 64-bit Definition: The ability of the CPU to handle large amounts of random access memory (RAM). For example, the 64-bit version of Windows can process RAM more effectively than the 32-bit system. 8

13 Software: Application vs. OS Both the Application (Microstation) and the Operating System (Windows) must both be designed using the 64-bit architecture to take full advantage of the processing power. Source: Blender Modeling 3D Graphics 9

14 Hardware: CPU Multi-Processor Enabled Processing is divided into the number of available CPU cores (hyperthreading) to further gain significant boost in performance and speed. Intel Desktop CPU (6 th Generation Skylake) i3 Dual Core, 3.3 GHz, 4MB L2 Cache i5 Quad Core, GHz with Turbo Boost, 6MB L2 Cache i7 Quad Core, GHz with Turbo Boost, 8MB L2 Cache 10

15 Typical Conservative Results 60 Input: DVD 9 Output: DVD min 23 sec 55 min 16 sec DVD-Cloner 64-bit DVD-Cloner 32-bit 11

16 What does it mean to be CONNECTED? 12

17 Welcome to CONNECT 13

18 New Workspace & New Workset Possibly??? Workspace: NCDOT STDS, NCDOT CONFIG Workset: Roadway English, Roadway Metric 14

19 GUI - Current SS2 SS3/SS4 15

20 GUI CONNECT (Ribbons) 16

21 New Feature Definitions and Types (DGNLIB) What exactly is a feature, a feature definition, and a feature type? In layman s term, a feature is any element that is drawn in Microstation which may represent a real-world object. It is defined by: How the object is to be displayed, e.g. level, color, style, etc. How the object is to be quantified and computed. What type of data or functions are ad-hoc to the object. For example, the road centerline feature will be on a certain level, with the built-in function to annotate stations and tick marks. A superelevation feature may contain AASHTO values, as well as other pertinent information to calculating superelevation. 99.9% of Microstation elements/objects will be featurized. 17

22 New Feature Types 3 Feature Types in SS3/SS4 10+ Feature Types in ORD CONNECT 18

23 No Left Turns Coined by Bentley, Left Turns refers to the process of going back to legacy procedure to complete a task, e.g. processing GEOPAK cross sections for earthwork and needing the GPK to layout XPL sheets. 19

24 No Left Turns Means No Regression Period! 20

25 21

26 Sun Setting of the GEOPAK DDBs with ORD CONNECT 22

27 Retiring the GEOPAK DDBs with CONNECT New Features to support X-Attributes for payitems? No Need for SS3/SS4 Native Style Support Horizontal and vertical alignments, as well as cross section labeling and any other labeling functions, can use the Annotation Group function defined as a Feature definition for laying out the alignment(s). 23

28 Manage Annotations Workspace/Workset Provided 24

29 Drawing Production Tab and Annotation (New Doc Center for Plans Production) 25

30 Most new annotation function in CONNECT supports dynamic labeling, e.g. stations and tick marks automatically shift when the alignment shifts. Recently this function was upgraded to CONNECT for the dynamic cross sections annotation (not in SS3/SS4). 26

31 Sun Setting of the GEOPAK GPKs with ORD CONNECT 27

32 Preparing for a GPK-less Civil Geometry World Horizontal and vertical alignments are usually stored in the GPK database as a binary file. Beginning with SS3 with OpenRoads Technology, these types of information are stored in the DGN file graphically. Furthermore, the methods used to create the project geometry in the old Coordinate Geometry (COGO) is replaced with the hew Civil Geometry alignment feature. Out with the Old (SS2/SS3/SS4): Geopak GPK (binary) Geopak COGO (abstract) 28

33 Reset and Reboot with a New Fresh Start In with the New (CONNECT): Civil Geometry 29

34 What We Know About Civil Geometry Vertical Alignment (Profile) stored in the same DGN file as the Horizontal ALN Only one user can access a DGN file at a time (Microstation Limitation) Can Persist back to the GPK in SS3/SS4. Not warranted in ORD CONNECT. Rule dependent for dynamically updating (EOT depending on the CL) Ability to read COGO inputs: Store & Locate, Incomplete, Open Alignments Primarily intended as a drafting feature. Alignment layout (station labels and tick marks) for plan prep accomplished with Manage Annotation/Group (CONNECT) Ability to incorporate AASHTO values as Design Standards, e.g. min curve radius, min L/K value for profile, min superelevation rate based on design speed. As intended in SS3/SS4, Civil Geometry alignments are used a drafting feature. Left turns were necessary to layout the alignment stationing and tick marks (double lines). CONNECT Civil Geometry alignments is an exclusive Alignment Feature and can be laid-out as is. Use with Civil Accudraw is Highly Recommended. 30

35 Accounting for Civil Geometry DGN Base Because Civil Geometry is DGN base, file referencing is necessary to perform GPK-like functions. A possible file/folder structure scenario may include the following. For Bridge Projects: Civil Geometry Alignments can be stored in the DSN file as a Microstation Design Model or in the Default Model. Superelevation can be stored in the DSN file as a Microstation Design Model or Default Model. The existing ground Terrain Model can be stored in the DSN file as a Microstation 3D Design Model. 31

36 Accounting for Civil Geometry DGN Base Accounting for multi-users being able to work and access the project geometry at the same time for I, R, and U Projects: Similar to the Separate but Linked concept in our Hydro Ditch Delta Trainings. Creation of a new Geometry folder A master ALN DGN file (R2500_RDY_ALN) to reference the individual Civil Geometry DGN file, e.g. R2500_RDY_ALN_Y1.DGN. When the project Geometry is required, such as Corridor Modeling, cutting cross sections, and laying out plan/profile sheets, reference the master ALN file with live nesting depth of 1. Or reference the individual Civil Geometry alignment DGN file directly. Superelevation can be stored in a separate DGN. The existing ground Terrain Model can be stored in a separate DGN. Referencing is required as mentioned above. 32

37 DEMO: Work Mode Views 33

38 3-Port Criteria View 75% Work Mode Views for Corridor Modeling 34

39 Basic 2D & 3D Work Mode (Full View) 35

40 DEMO: Roadway Features Definition DGNLIB 36

41 Element Template vs. Native Styles (SS3/SS4) 37

42 Element Template vs. Native Styles (SS3/SS4) The Feature displayed properties (symbology - including level, color, weight, line style, etc.) are defined by a Microstation Element Template OR GEOPAK Native Style. Technically all Features can be defined with Microstation Element Templates. However if a Feature, such as a section of guardrail, has already been defined as a Geopak DDB, then its displayed properties can be linked back to the respective DDB (RD_Payitems.DDB). This linkage is known as the Native Style. 38

43 Terrain Models New Microstation Element Type New Feature Type and Definition New Level and Symbology Set Graphically Stored in a 3D DGN File Common Usage Convert GEOPAK TIN to a Terrain Model 39

44 DEMO: Roadway Element Template DGNLIB 40

45 Feature Symbologies+ Element Template (CONNECT) 41

46 Why are the GEOPAK DDBs still required in SS3/SS4? Element Templates alone and Native Styles do not support the GEOAPK functions to layout horizontal and vertical alignments, e.g. labeling stations, tick marks, curve data, etc. No Features to support ad-hoc attributes and payitem numbers for Transport. Both required left turns to complete for plan production. 42

47 DEMO: Create Existing Terrain Model from GEOPAK TIN 43

48 Creating Terrain Models from Geopak TIN 44

49 New Microstation Terrain Model Element Type 45

50 DEMO: Create Civil Geometry Horizontal Alignment 46

51 1. Open B5344_Rdy_dsn_1.dgn. 2. Reference the existing ground Terrain Model and make it the Active Surface. 3. Show Reference Adjust Colors in View Controls 4. Optional Three methods to attaching background imagery for design. Google Earth NCDOT OneMap (often interrupted service, refresh the entire state) NCDOT SiD Tiles (refreshes just the tile, dependent on Division and County) 5. Clip raster image. 6. Place HAL using Complex by PI method (Horizontal Geometry). 7. Define Start Station of Verify Design Standards with the Civil Message Center. 9. Fix it or remove Design Standards with Element Info. 10. Offset the centerline with 12 lanes on both side with 4 paved shoulders, using the Single Offset Entire Element command (Horizontal Geometry). 11. Demonstrate Civil Geometry rules and dynamics by moving the PI and changing the curve radius. 12. Display existing profile in View 2. 47

52 DEMO: Importing Horizontal and Vertical Alignments from GPK 48

53 1. Open B5344_Rdy_dsn_2.dgn. 2. Reference the existing ground Terrain Model and make it the Active Surface. 3. Import L and LPRO from the GPK using Import Geometry (General Geometry). 4. Change the Feature Definition to Design HAL. 5. Open View 2 as the Profile View. 6. Change Feature Definition to Design VAL. 7. Verify it is the Active Profile for Chain L. 49

54 DEMO: Corridor Modeling 50

55 1. Open B5344_Rdy_dsn_2.dgn. 2. Set a 3-view work mode screen. 3. Create Corridor and add Template Drops. 4. Show Cross Section View on View Apply Parametric Constraint to Pavement Width. 51

56 DEMO: Creating and Applying Superelevation 52

57 1. Open B5344_Rdy_shp.dgn. 2. Reference the file B5344_Rdy_dsn_2.dgn. 3. Create Superelevation Sections (Corridor Modeling). 4. Open B5344_Rdy_dsn_2.dgn. 5. Reference B5344_Rdy_shp.dgn. 6. Assign Superelevation to Corridor (Context Sensitive Tool or Corridor Modeling). 7. Show only available superelevation points (Superelevation Flag). 8. Add temporary Dimension in Cross Section View to show superelevation rates. 9. Note the superelevation reference file cannot be detached. Reference file can be undisplayed to maintain superelevation for the corridor. 53

58 Cross Sections Dynamics Video (4.5 min) Dynamic Cross Section in CONNECT 54

59 IRD Converter SS2 Corridor Modeling project can be converted to OpenRoads with a IRD Convert in SS3. SS4, and CONNECT. It is expected Roadway Design Managers will make the following recommendations, depending of the project schedule: Most new NCDOT Corridor Modeling projects can begin to use OpenRoads Technology..Few older NCDOT Corridor Modeling projects should be finished with SS2. Most NCDOT Corridor Modeling projects before Right of Way Phase or 75% Plans can use the IRD Converter to upgrade to OpenRoads Technology. 55

60 Waiting for CONNECT EAP 1 (Q November 2016) EAP 2 (Q1 2017) Commercial Release (???) First True 64-bit Architecture New Doc Center Plans Preparation Tools Additional Feature Types/Defs/Capabilities New Civil Sheeting Procedure New Superelevation Engine New Dynamic Cross Section and Labeling No GEOPAK DDB Requirements No GPK Requirements No Criteria No Left Turns Period! First ORD Delta Training: Intro to Civil Geometry and Civil Accudraw 56

61 Questions? Oak Thammavong NCDOT Roadway Design Unit 57

62 NC DOT Engineering Content Management Preconstruction Project Sites Ellen Dickson

63 Agenda New Preconstruction Project Sites What Is Changing and Why Preconstruction Project Site Model Where We Are Today Future Direction How you can benefit 2

64 Announcing: NCDOT Preconstruction Project Sites To facilitate project delivery through enhanced collaboration between NCDOT and its partners, online Preconstruction Project Sites are being established for every transportation project. Each Preconstruction Project Site will allow: Registered users (internal and external) to submit, review, and modify project files based on their roles; A consistent way to organize project files statewide; Rapid and comprehensive searching of all project files; Transfer of large files; Versioning of project documents; and Access to project files from mobile devices. The initial rollout includes support for the planning portions of the project; support for additional disciplines & project phases will follow. 3

65 Previous Operating Model Division 01 Division 02 Division 03 Division 04 Division 05 CENTRAL DOT PRECONSTRUCTION UNITS Division 06 Division 07 Division 08 Division 09 FTS Media PEFs Professional Engineering Firms (Consulting Firms) Division 10 Division 11 Local Copy of Project Store Structure Division 12 4 Project Store Structured, mapped network drive Division 13 Division 14 Divisions responsible for < 5% of STIP projects

66 Decrease in central staff Increase in outsourcing Increase in division authority CENTRAL DOT PRECONSTRUCTION UNITS New Operating Model FTS Media PEFs Professional Engineering Firms (Consulting Firms) Project Store Structured, mapped network drive Div Proj Local Copies of Project Store Structure Consulting firms now have a much larger role. 5 Divisions now responsible for more projects and more complexity than ever before: 65% of STIP projects (~20% in $)

67 Accessibility goals: Goals to Support Project Delivery Appropriate access by all involved user groups: DOT users (central and division), Consultants (PEFs), and External partners Access from mobile devices Functionality goals: Easy & intuitive to use, fits business processes & terminology Handles large files Tools tailored for CADD design Automation & standardization Everyone works with same reference copy Versioning Backup & recovery, retention management General Content Management goals: Organized online storage and useful tools Ability to navigate to content by discipline Ability to search for content & quickly locate deliverables 6

68 Preconstruction project site model one site per transportation project Agencies Planning Organizations Other external partners Access to SharePoint requires only a web browser. DOT Staff Design Consultants Access to ProjectWise requires a license & use of CADD tools U-5000 U-5000 SharePoint Everything that needs to be accessed by noncadd users ProjectWise (CADD users only) U-5000 Preconstruction Project 7

69 8 Future Direction (subject to change)

70 First Step: SharePoint Sept 2016: Initial rollout on SharePoint > 1000 sites created so far, one per project Each site is built from a common template Initial rollout Benefits: Consulting firms can contribute to some libraries based on assigned role and read the rest DOT & Consultants can store, share and exchange files in a persistent place: Files are not deleted unlike with FTS Multiple groups can access same set of files Initial set of disciplines can be completely moved to SharePoint instead of using Project Store Store ETRACS deliverables here & provide link Quick Reference files, FAQ, useful links Initial rollout Limitations: Other disciplines must share and exchange files or sets of files in the From DOT and To DOT libraries No CADD support yet 9

71 Demo Demo Preconstruction Project Sites Navigation Uploading a file Creating a Document Set Dragging & dropping files Links for ETRACS Project Commitments Preconstruction Help 10

72 Consulting Firm Access 1. Get an NCID at no cost from Login & update password. 2. Contact Diana Feigin to set up (or update) company group, providing primary & backup user administrator name and list of users to be included: names, NCIDs, addresses 3. DOT users on project grant role-based access to consulting firm as a group 11

73 Next Steps on SharePoint Within the next few weeks: Precon Announcements on Preconstruction Home page, to inform users of new features Project Development Collaboration library collaborate with resource agencies & planning organizations (MPOs, RPOs) on environmental documents etc. DOT Restricted library Restricted cultural resources, protected species, plans by others (visible to DOT only) Project Contacts list Keep track of who is working on the project & their contact info New User Survey Incrementally roll out improvements: More document libraries More useful tools Updates to help information Prioritize & enhance model based on User Group Feedback: To volunteer for the Preconstruction User Group, contact Ellen Dickson Monthly meeting in person in Raleigh or join by phone Added Tuesday 11/8 12

74 13 Future Direction (subject to change)

75 14 Future Direction (subject to change)

76 Bentley s ProjectWise SharePoint does not understand CADD internal references. Files (or.zip files) can be stored there, but designers need more NCDOT plans to use ProjectWise for storing and sharing CADD based content. NCDOT is in the process of procuring Use of Bentley s cloud-based managed ProjectWise Design Integration environment Use of additional service offerings: ProjectWise Project Sharing Services ProjectWise Deliverables Management Services engagement with Bentley to help us get started Exact configuration of applications & tools for CADD still under development 15

77 16 ProjectWise Project Sharing Services

78 How you can benefit! Online access to project repositories Easy way to store/transfer large files Access from mobile devices* Simpler standard project structure less complex than today s TIP folders Consistent structure from project to project More libraries and features coming soon! What you can do to get started Get your company set up so DOT users can grant you access to projects Subs can be granted access as well Consider participating in the Preconstruction User Group or otherwise provide constructive feedback *Windows & IOS devices. Android users must use an app, such as SharePlus. 17

79 Detail Slides 18