Overview

ASE Civil [generally] relies on profile design data from road centerline components to drive the vertical design of the remaining offset components. Design Markers on all alignment components are used to store elevation values at key locations along the road. The Design Markers also store 'Paving Feature' defiinitions. When ASE's paving data is shared, the completed definition of the profile data for all alignment components (the Paving Model file) is recorded both in the vertical design drawing and in the ASE project data folder. This data is referenced as-needed by many of the remaining project stages and tasks, such as Profile Generation, Corridor Modeling, Plan Labeling, Pad Management and more. For these reasons, establishing finished centerline design data is an important step in the progression of the project work-flow.

 

ASE provides two options for creating and managing centerline design data

  • Direct Marker Editing

  • C3D Syncronization\

 

Direct Marker Editing

 

Overview

ASE Civil does not provide direct support for profile-based design methods. When manipulating Marker elevations directly, editing must be made from a plan-view orientation of the street. In later versions of ASE Civil, centerline profile design is more effectively managed using Civil 3D 'Layout Profiles'.

Goal

Edit Marker elevations as-needed to establish and manage finished profile design control.

Prerequisites

Vertical design drawing

ASE project data folder assignment

Alignments accessible

Design Markers in-place

The Design Marker(s) selected must be a Parent (if Constrained) or Neutral

Procedure

  1. Zoom to the Design Marker(s) to be edited

  2. Select one of the Marker editing options from the menu

  3. Perform the editing within the context of your selection

  4. Repeat this process for all Markers on each component of each alignment that will be used as PVI or Intersection paving feature definitions

Result

The Design Marker(s) edited will be adjusted to the desired elevation(s)

Related Topics

Constraints as cross-slope controls

 

C3D Synchronization

 

Overview

ASE Civil centerline profile design is much more effectively managed using Civil 3D 'Layout Profiles'. After Markers have been set and PVI or Intersection paving features have been defined on an alignment, synchronization with a Civil 3D Layout Profile can affect vertical displacement of the qualifying Design Markers on the alignment. Synchronization will simultaneously control elevations of ALL qualifying Markers on ALL components of the alignment.

Advantages

The benefits of using this method for profile design are manifold. Here are just a few:

Profile-Based Design Capability

Even though plan-view design is sufficient in many cases, the majority of engineers and designers are more comfortable (and more productive) creating road designs from a profile-view. This new enhancement enables that capability and increases the ergonomic appeal of road design using ASE Civil.

Design Simplification

Using ASE's Constraints as a comprehensive road design tool is effective. However it can tend to be confusing to those who are not highly-experienced with the Constraints system, espcvially when applied in this mode of vertical design control. Long Constraint hierarchies can become very complex. Despite the long-standing reliability and accuracy of ASE Civil's network grading control tools, errors can be introduced into the design logic itself, simply because a lengthy Constraint hierarchy effected a change where it may not have been intended. 

Shorter Design Time

Compared to Constraints-based profile design, engineers and designers implementing the ASE Civil's synchronization enhancement could potentially save even more project resources as a direct result of the following aspects of the synchronization system:

Fewer Constraints

Using Layout Profiles to control Design Marker elevations yields a significant reduction in the dependency on Constraints for both longitudinal and lateral control of profile design components, simply because these elements no longer need to be created for profile design directly.

Passive Offset Profile Design

Synchronization of Markers with Layout Profiles forces each eligible Marker to adjust its elevation based on its offset distance from the centerline component. Since predefined, independent (Left/Right) lateral controls are available for road cross-slope control, Constraints are no longer required for this purpose, saving even more design time.

Fewer Flow Labels

When using profile synchronization, pavement cross-slopes are managed site-wide through the Sync Preferences dialog. As a result, Flow Labels no longer need to be created between Markers on different components at common stations.

 

Considerations

Engineers and designers utilizing this method for road profile design should be aware of the following intrinsic anomolies and limitations relative to the system and the design logic as applied to a subdivision project containing intersecting roads and transition regions:

Markers at Corridor Interfaces

Markers used for PVI (GB) or Intersection paving feature definition at interfaces between two separate alignments will usually sync' to different elevations for each alignment. This is expected whenever the Marker's offsets are different depending on the active alignment. Always be mindful that the last profile sync'd will be the controlling alignment.

Markers Eligibility Criteria

ASE Civil will only synchronize the elevations of Markers that satisfy ALL of the following conditions (in order listed):

  1. Markers attached to the alignment

  2. Markers defined as PVI(GB) or Intersection paving features

  3. Markers that are Neutral (not constrained) or (top-level) Parents in a Constraint hierarchy

Sync' Eligibility Override

Enabling the 'Sync Non-GB Parents' option in the Marker Sync Preferences dialog will allow elevation adjustment of Parent Markers that are not defined as eligible paving features.

It's important to note that criteria #1 [attachment] must always apply for any level of eligibility. Attachment is not optional.

Civil 3D Data Availability

If an eligible Marker is located at a station for which no centerline profile data is available, it will be flattened to a zero elevation

Flattening

By default, if a Marker is attached to the alignment, but not eligible for synchronization and not Constrained by a Parent, its elevation will be flattened.

Sync' Logic Diagram

An alternative view of the criteria used to determine Marker sync' eligibility is provided in this flow chart

Vertical Curve (Temporary) Limitations

ASE retrieves FG elevations only from the Civil 3D Layout Profile definition. It does not know if the elevation was within the limits of a vertical defined in Civil 3D or along the profile tangent. For this reason, to ensure that the elevations used for ASE Civil's road profile design model reflect accurate data from the Civil 3D Layout Profile, it's best to refrain from including vertical curvature in the Civl 3D profile geometry. If vertical curves are required, they must be defined using ASE's PVI(GB) paving features.

It's OK to use vertical curves inside Civil 3D's Layout Profiles for a preliminary design iteration, however they should be removed before synchronizing ASE's Design Markers to the Civil 3D design. Failure to do this will result in ASE's sag curves being too shallow and crest curves that are below the required high-point elevation, etc.

The next evolution of this enhancement to profile design will automatically detect vertical curvate in the the Civil 3D layout Profile and apply it directly to the paving feature definitions within ASE's composite paving model.

Civil 3D PVI (Temporary) Limitations

ASE Civil cannot yet detect the PVI definitions in the Civil 3D Layout Profile. The PVI's defined in ASE are automatically placed at the key-point locations as provided by the Base Map Control data. If additional PVI's are required in the Civil 3D Layout Profile design that are not coincident with an existing alignment key point, additional Design Markers must be individually placed at the same station in the vertical design drawing to ensure that the PVI's in the Civil 3D Layout Profile are accurately reflected in ASE Civil's paving feature definitions. A PVI location in ASE's feature definitions are not yet coordinated with the PVI locations within the Civil 3D Layout Profile. This is a very important concept to keep in mind when using Civil 3D to control ASE Design Marker elevations.

Civil 3D Intersections

When releasing vertical control to Civil 3D Layout Profiles it's very important to note that alignments that pass through a common coordinate MUST reflect IDENTICAL elevations. It's unknown whether or not Autodesk have provided tools to ensure that vertical displacement errors between intersecting Layout Profiles are managed automatically by their application. Since this is not applicable to ASE Civil's vertical control systems, it's up to the engineer or designer to practice quality control in areas where Civil 3D Layout Profiles cross or interface.

Constraints Usage

Constraints are fully compatible with synchronization and may still be used to support design integrity in transition areas. They are especially useful in intersection curb returns, knuckles, cul-de-sacs, pavement warps/asymmetrical pavement sections, superelevations and any region of the road design that requires a consistent grade, slope or elevations difference that supersedes the Civil 3D Layout Profile controlling elevations.

Goal

Edit eligible Design Marker elevations from a Civil 3D Layout Profile to establish and manage finished profile design control within ASE Civil.

Prerequisites

Vertical design drawing

ASE project data folder assignment

Alignments accessible

Design Markers in-place

PVI and/or Intersection paving feature definitions

Procedure

  1. Set the current alignment

  2. Select the Marker Sync' option

Result

All eligible Design Marker elevations on all components of the current alignment will be adjusted to match the corresponding Civil 3D Layout Profile centerline elevations, with respect to their offset distance and the cross-slope values stored in ASE Civil's sync' preferences.