Project Assist

Icon:

Introduction

Project Assist assesses alignments in the drawing and predicts how those alignments should be used in string based designs.  Both the alignment name and geometry are considered in the software assessment for alignment usage.  Project Assist will learn based on the confirmed alignment usage.

After the alignment usage is determined, Project Assist then proceeds to build a Workflow to relate all those alignments to each other to: generate strings, apply templates, add variations and batter/daylight overrides, add section sampling, build models and create a Thread.  The Workflow form describes the processes that Project Assist will apply to build the models, with the user able to make changes to strings and the associations between alignments and strings. 

Project Assist speeds up the creation of strings, application of variations and building of Models, letting the user focus on the vertical design and production outputs.  Project Assist also simplifies many processes that would be undertaken manually, by summarising how alignments could be used and simplifying the creation inputs.

Project Assist can be operated at any time through the lifecycle of the project, so users are encouraged to start small and build up the design controls by adding more alignments and running Project Assist.  Any alignments already used to create a string or used as a Road section control will not be shown again in Project Assist.

Common Road String controls are well supported, such as for including saw cuts, left/right pavement edge controls, footpath alignments and property edge/extent of works limits. 

Independent string control can also be applied and automatically included in a Model, with the added ability to adopt elevations from a surface model. 

Islands (including to define roundabouts) are also supported - these are 'cut' into the base design model and a new Built Model is created to incorporate them. 

Existing (non designed) features can be included to facilitate connection with designed strings.  The expectation is that 'Existing' features described in Project Assist will enable intersection connections to apply (kerb returns and road string elevation matching).

On each operation, Project Assist will create a Thread, uniquely named (or named by the user).  The Thread contains the list of commands applied to each string and construction of Models, allowing for rapid recalculation of multiple activities that generated the original results. 

Video Resources

To fully appreciate the processes of Project Assist and the approaches to different design scenarios, it is recommended to review videos stored at the following link:

   Project Assist Videos 

Project Assist - Intelligence and Learning

Project Assist applies learned behaviour to assess how users want to use alignments.  Based on geometry and the alignment names, Project Assist will suggest how the alignment is intended to be used in design.

It learns from the way each user names alignments - every time Project Assist is run it will learn from the outcomes of the previous operation and modify it's behaviour.  What this means is that, over time, consistent alignment naming conventions will result in the correct alignment types being applied on new projects.

Prerequisites to Running Project Assist

Project Assist can be run multiple times in the lifecycle of a project, and operates on the following basis:

1. An 'existing' surface has been created in the drawing and describes the shape of the existing terrain.  All Strings created in Project Assist will need to reference a base (existing) surface

2. At least one alignment has been created, describing a design feature for the project.  Users are encouraged to create multiple alignments.

Alignment Usage Options

Users are encouraged to create multiple alignments for controlling different aspects of a design, such as:

• For Road Strings, alignments describe the centreline of the string.  Edits can be applied to the Road Strings by the inclusion of additional alignments, including:

  • Alignments that describe the edge of the Road Edge (the Code to apply to is as defined in the Active Drawing Settings > Design Settings > Default Point Code Intersection Connections)

  • Alignments that attach to a Road Edge but need to be modelled as a separate string with cross sections (such as 90 degree angle parking bays, or a car park that connects to the edge of a Road). 

  • Alignments that describe the footpath/sidewalk, for horizontal and/or vertical control

  • Alignments that describe a pavement saw cut, usually added to enable road widening (the cut is placed at the edge of the existing pavement, with the intent to extend with new pavement to increase the overall road width)

  • Alignments that describe the Property Boundary or extents of the design

• For Kerb Returns and Cul-de-sacs.  Initially added as a Road Edge or String Control, ticking on Kerb Return or Cul-de-sac will set the alignment to be created as a kerb return or cul-de-sac string.

• For independent string design of features such as dish drains draped onto the existing/design surface, or other features that are designed somewhat independently of any other network (Road, Kerb) string cross sections.  For these cases, the alignment is NOT associated with a Road String

• For including islands (as well as roundabout island strings).  When an Island is selected as the string type, the software will initially match elevations to the base design model, then create a new Model that includes the islands and removes any codes that conflict with the island (like a paste, islands typically sit on top of other designs.  Like a paste, they often replace designed strings/codes.  A common case is a median island sitting on top of a designed road, where the median straddles the original road centreline)

• For emulating Existing (no Design) Roads

  • These are included to allow the designed elements to match into existing features that are not being designed (such as a designed road finishing at the edge of an existing road, or redesigning a road and needing to blend the kerb returns back to an existing side road).

  • These are not intended to be used in any design capacity, except to facilitate connection of designed strings back to existing elevations.  All 'Existing' type features will have their elevations matched to the existing surface

  • Alignments that describe Existing Road Centrelines (the software enables connection of kerb returns and designed roads to the centreline).  When a centreline is used, a Template can be applied, and the road edges and footpaths can be associated with alignments and matched to the existing surface elevations.  This is very useful for the cases where existing side roads need to reconnect with designed main (continuous) roads

  • Alignments that describe existing road edges (these can be used to control widths for an Existing Road Centreline OR provide direct connections for incoming designed roads, including enabling kerb return creation)

  • Alignments that describe existing footpaths/sidewalks (these can be used to control widths for the existing footpath/sidewalk locations and are usually associated with an Existing Road Centreline string).

Automated Model Creation

Project Assist will create up to three Built Models, pending the user requirements for the design:

• Total Model

  • Roads, kerb returns and cul-de-sacs can all be included in an automated model called TotalModel.  This model will automatically trim the Roads to accommodate the inclusion of kerb returns and cul-de-sacs. 

  • Project Assist will create this model when users add Roads with Variations (widen to alignment, match codes to strings) and Batter Overrides, as well as Kerb Returns and Cul-de-sacs

• Design Model

  • The addition of independent strings, including strings connected to the road edge (for a parking bay, as an example) or the footpath (where the footpath is best described with it's own cross sections) will result in the creation of a Design Model (Built Model)

  • TotalModel is used as a base.  Codes are removed to include the Strings.

• Design Model with Islands included

  • The addition of islands (islands are typically draped onto the base design model) will result in the creation of another Built Model. 

  • Independent Strings that are set to drape (adopt elevations from) the Design Model

  • The Design Model is used as a base and then edited to include the islands and trim out overlapping codes from the base model

Intersection Creation

The Intersection Manager can be used to set up the kerb returns at each intersection, as well as omit the kerb batters and set all intersections as all-crowned intersections (remove Main Road edge).

Terms Used

• Road Edge.  A Code included in Road String cross sections that typically represents the edge of the road pavement.  This is the Code that other strings connect to (such as kerb/curb returns, cul-de-sacs, side roads, etc.). 
  It is defined in the Active Drawing Settings form > Design Settings > Default Point Code Intersection Connections > Matching Code for Kerbs.

• Saw Cut. A Code included in Road String cross sections that typically describe the place where the existing pavement is cut and new pavement is attached.  At this point there may be an allowance for a crossfall change, or there may be a requirement to maintain a single road pavement crossfall from the centreline to the Road Edge.
  The expected Codes are as described in the Project Assist Settings form > Default Codes tab (Sawcut). 

• Footpath. A Code included in Road String cross sections that typically describes a footpath/sidewalk.  This is assumed to be described using two codes (inside edge and outside edge). 
  The expected Codes are as described in the Project Assist Settings form > Default Codes tab (Footpath inner and Footpath outer).

• Boundary.  A Code included in Road String cross sections that typically describe the property boundary location.
  The expected Codes are as described in the Project Assist Settings form > Default Codes tab (Boundary).

Minimum Requirements - At Least one Road is Required

At least one Road String must be created (or existing) when Project Assist is run.  If no Road String is already in the drawing or is created as part of the process, the following form will display and Project Assist will stop:

Project Setup and Output Reports

When Project Assist is first run, the user is prompted to establish some core settings/behaviours for Project Assist:

• Project Information.  Here users can set the project name, description and designer.  This information is included in the output PDF Report that Project Assist creates

• Settings.  This lists the number of alignments and surfaces that are available in the project.  Most importantly it is here that the user sets the Sampled Surface.   The Sampled Surface is considered to be the existing ground surface for all strings.

If it is required to change these settings after first run of Project Assist, there is a command menu item in the Workflow to reopen this form (File > Project Settings).

Report Output

Once Project Assist has completed all actions in the Workflow a pdf report will be generated. 

The report details every action taken and includes links to video resources describing how the actions are manually applied in the software.  The Project Information is included in the report.

This is a complete list of all actions taken on all strings and models, to generate the final result. 

Project Assist - Alignment Usage and Workflow

There are two core processes that Project Assist goes through:

1. Identifying the intended usage of the alignment (e.g.: Road string, road edge control, existing road CL, etc.).  This is managed via the Alignment Usage form

2. Deciding on the detailed model construction (Road templates, alignment/string application to Road Strings, String Templates, Kerb Return behaviour, Cul-de-sac behaviour, etc.).  This is managed via the Workflow form.

Alignment Usage Form

Project Assist predicts the alignment usage based on the alignment name and geometry.  Use the pick list to change how the alignment should be used.

As the mouse is hovered over each Alignment Name, a highlight will display in the drawing over the alignment, coloured based on the assigned Type.

Information about the intent of each Alignment Type is provided at the top of this form.

Note: The software learns from each use, so applying consistent alignment naming structures and setting the Type will teach Project Assist what different alignments are to be used for (what Type to set).

Workflow Form

This is the core of Project Assist - it is where the decisions are finally made about the structuring of the data.

The Workflow is built with Panels - each Panel describes actions and information for each alignment.

Depending on the alignment usage, options on how to use an alignment will differ.

Workflow Interface Elements

Road Strings

Road Strings are denoted by a light blue Panel with the Road name and this symbol:

Under the Road String Panel will be the basic creation tools for the Road.  Assign the Template, select if the Road should behave as a Resheet or Road Widening (these options only display subject to associated alignments being included).  Alignment requirements for triggering a Resheet or Road Widening option are:

• for Resheet, at least two alignments are needed that define the left and right road edges

• for a Road Widening four alignments are needed (saw cut and road edge alignments left and right of the road centreline).

Click on a Road String panel to collapse all displayed alignments associated with that Road String.  Click again to expand.

Road String Warning/Information Messages

Warning/Information message panels may display in the Workflow to advise users of certain actions that Project Assist has taken, or to explain why Project Assist has defaulted to a suggested application for the alignment. 

Warning/Informational messages display with a yellow background and appear similar to this:

The above information messaging is explaining why a user may consider a particular method for using an alignment that describes a road edge, and the sets this as the default selection (with the user able to override that selection).

There are a number of cases where alignments are not shown in the Workflow, even though they are being used (such as workflow selections that force a certain action for associated alignments).  In these cases, the user will see an information message advising that the alignment/s are being used.  Some typical cases where alignments are displayed in the Alignment Usage form and then are not displayed in the Workflow:

• Road Resheet.  This option is available for a Road String, where two Road Edge alignments (left and right of a Road String) are associated to the Road.  define the Road String as a 'Resheet' road reconstruction project.  In this case, the left and right alignments are automatically used by the Road String to control the left and right road edge offsets and to be used in establishing the road centreline elevations (in a Resheet application, applied via the Auto Profile form in the Vertical Grading Editor, the software will move the centreline up/down to ensure a minimum pavement thickness between two alignments, the left and right edge)

• Road Widening.  This option is available for a Road String, where two Saw Cut alignments and two Road Edge alignments are associated to the Road

• Existing Roads.  Where there are additional Alignments for an 'Existing Road' (this is a String that is included in Design usually for the sole purpose of supporting intersection connections.  It is assumed these have no design elements) then a warning message will display to advise these alignments are being used by the Existing Road CL.  In the Alignment Usage form, users can have the Existing Road CL, as well as road edge controls and footpath/sidewalk controls.  Only the Existing Road CL will display as the others are assumed to be used in the cross sections of the Road String (variations will apply to set the road edge codes to match the surface and use the alignments, and the footpath/sidewalk as well where assigned.

Associated Road String Alignments

Many different alignment types can be associated with the road string and will be listed under the Road String panel, if they are associated to that Road. 

Alignments that can be used to control a Road String include: road edge widening, saw cuts, footpaths/sidewalks, boundaries/batters/daylights.  To achieve these outcomes, they must be Associated with that Road.

Typically, Project Assist will automatically make the Road String association based on alignment geometry (proximity to the Road String, alignment type and having similar directions. 

General characteristics of an associated Road String are as follows:

Highlighted in pink in above is the type of alignment/string control. 

Highlighted in Yellow is confirmation of what Road String it is associated with as well as what Side it is located on (left or right).

Highlighted in Purple is the associate/disassociate button   - clicking on this button will remove the string/s association to a Road. 

Disassociated Strings will be placed under the 'Alignments not associated with roads' panel.
If the String is disassociated, clicking this button will let the user pick a Road String to associate with (the alignment can then be used to modify the cross sections of the selected Road String)

The up and down arrows can be used to reorder the panels.  Each panel is process in order in the Workflow.

When strings are associated to a Road, the Road String cross sections are affected even when users elect to create as a separate string (as shown above).  Normally, what happens is that Codes are removed from the Road cross sections to enable the String cross sections to take control over those ranges.  Let's consider two cases:

1. If an alignment is acting as a Road Edge Connection with full independent string control (with independent cross sections), then the Road String cross sections will be removed, from the edge road code (as defined in the Active Drawing Settings - default would be EB or ETW) outwards.  It is assumed that the String being added will describe the elements working outside from the road edge code

2. If an alignment is acting as a Footpath/Sidewalk with full independent string control (with independent cross sections), then the Road String cross section codes for the footpath/sidewalk will be removed.  It is assumed that the String being added will describe the cross sections of the footpath/sidewalk

The available inputs will differ per alignment type - see below for input controls for different string/alignment types.

Strings Not Associated with a Road

Alignments/Strings not associated with a Road will be listed under this panel in the Workflow:

Any alignment type can be disassociated from a Road String and behave as an independent string (with it's own cross section controls and added to the Design Model built model). 

Alignments being used as Island Strings, as well as Existing Road type alignments, will be listed automatically as not being associated with a Road. 

Note: Kerb returns may also be listed here, but will behave as Kerb Returns in the TotalModel regardless of the road association status.

The available inputs will different per alignment type - see below for input controls for different string types.

Standard Actions

After the specific string and alignment controls are defined, some standard (overall actions) can be applied.  These are separated into different panels:

• Intersections
  
  This will create kerb returns at intersections.  There are some configuration items included here such as the radius, omitting batters and creating intersections that maintain the crowns of both roads (Remove main road edges).  Then the main road edges are removed, the kerb return pavement extends to the main road centreline instead of the main road edge (so the kerb return vertical design will control the pavement crossfall of the main road).  
  
  Click on the Intersection Manager button to enable full edit control of each kerb return at each intersection to be established before creation.

• Create Model Builder Model
  
  Project Assist creates Built Models pending the user selections for how to use the alignments.  Here users can change the names of the models to create, or select to add the Project Assist controls to an existing model.
  Note: Any entries added by Project Assist will be flagged in Model Builder
  

• Build Design Models
  
  This final action is to build all models, as per the configuration under Create Model Builder model as well as the TotalModel (Auto Model command) surface.
  Type in a Min, Triangle Length and tick on Use Boundary Retraction to create a boundary by trimming triangles working from outside in.
  

Ignoring Actions

In the workflow, any alignment or action can be ignored from processing.  When Ignore is ticked on, the String (and in the case of a Road String, all associated alignments) the panel actions will not be included.

When Ignore is ticked on, the event will be highlighted in pale yellow colour.  All associated alignments to a Road String will also change colour and have Ignore ticked on.

Plugins

There is a 'Plugins' button at the bottom of the workflow:

Plugins are optional actions that can be added to the Project Assist processing.  These are additional pieces of code (able to be created with .net) that provide extended functionality supported by the Civil Site Design API.  When a Plugin is added, an additional panel will display in the workflow.

Some included with the software include:

• Model Viewer
  
  If added, another Panel will display in the workflow to facilitate setup of Model Viewer: Primary surface style, base surface style (with option to pick image from drawing)
  A Model Trim action can also be applied.  Tick on to apply - all built models created with Projet Assist will have the Model Trim action applied.  See the Model Trim command for details on the inputs.

• Australian Rural Road
  
  This is available for Australian customers only.  It will apply superelevation to the selected road based on the design speed and maximum superelevation.  There are also options to create sight distance checks, add centreline linemarking based on the sight distance results and add Table Drain entries (Design Data form) for the selected Road String.

Key Settings for Project Assist

See the Settings command for full details on the settings to guide the Project Assist workflow results.  The settings established a number of default behaviours for Project Assist:

• Default templates to apply for different string types, and sampling to apply

• Default Codes to look for to associate with Saw Cuts, Footpath (inner and outer codes) and the Boundary.

• Design constraint controls, for managing crossfalls

• Defaults for creating cul-de-sacs

• Built Model names to apply

Details

Upon selecting the command the following form is displayed:

Project Settings

Project Settings displays on first start of Project Assist.

Alignment Usage Form

Workflow Form

Menu Items
File > Open Workflow	The Workflow actions can all be saved and re-used when Project Assist is re-run.  Use this command to open a form to enable selection and loading of a Saved Workflow
File > Save Workflow	Saves all Workflow actions to file, for re-use on a subsequent run of Project Assist.  A form will display for the workflow actions to be saved to file.  Saved workflow files have extension .paw.
File > Project Settings	Opens the Project Settings form.
Tools > Reset Workflow	Restores all default settings in the workflow and removes all user edits in the workflow
Tools > Remove Associated Alignments (from Road)	Select to disassociate all alignments from a select Road String.  All associated alignments will move into the 'Alignments not associated with roads' panel.  A confirmation form will display to apply this action and then the following form to select the Road to apply this action to:
Tools > Alignment List	Opens a list of all used alignments (including those not displayed in the Workflow) to review and highlight in the drawing Hover over an alignment to highlight in the drawing.  Click Close to close the form.
Tools > Set Thread Name (for current workflow)	Every time Project Assist is run, it will create a Thread describing all the computations.  By default, the thread is automatically named 'Project Assist Rebuild' with a unique identifier added at the end (e.g.: Project Assist Rebuild_3af9). Note: for the Road Assist command, Project Assist does not create a Thread. Use this command to uniquely name the Thread that will be created: Type in a Thread name to use.
Workflow Panels	Below is a list of each Workflow Panel.  These match with the Alignment Usage Type
Road String Panels	Details each Road String and associated alignments
Road String	Ignore Tick on to not create a Road String.  Panel colour will change and Ignore will be set for all associated alignments Information Information includes the Alignment Name and a box with text information on each command option.  Hover over the inputs to see the information about that input. Select Template to Apply Pick list of available CSD Templates to apply to the Road String. This is a road widening project This option will only display if Sawcut and Road Edge type alignments are associated with the Road String.   Inputs Tick on this option to automatically apply variations for a road widening project. When ticked on, Sawcut and Road Edge alignments will be removed from the Workflow list and the following informational panel display   Behaviour Road String created with Template applied Auto Profile (Reference Surface) applied to adopt elevations of the sampled surface, raised by the Thickness specified Variations applied to insert Sawcut code/s to the Road cross sections Variations applied to apply elevations to the Sawcut codes to adopt the elevations of the sampled surface, raised by the Thickness applied Variations applied to set the full position of the Road Edge codes to match to Strings created from the Road Edge alignments Road Edge Strings created Auto Profile (Reference Point) applied to use elevations from the Sawcut code, and the crossfall between the centreline and the Sawcut, to calculate the elevations of the String. Design Constraints applied to show minimum and maximum crossfalls (measured from the Road String centreline) Resheet This option will only display if Road Edge type alignments are associated with the Road String.   Inputs Tick on this option to automatically apply variations for a pavement Resheet. When ticked on, Road Edge alignments will be removed from the Workflow list and an informational panel will display.   Behaviour Road String created with Template applied Variations applied to set the width of the Road Edge codes to match the Road Edge alignments (keeping the crossfall from the assigned Template) Auto Profile (Resheet) applied to assign elevations.  The Resheet will apply elevations to the centreline by moving the centreline up/down to achieve the minimum Thickness (distance above the sampled surface) in the area between the Left Road Edge and Right Road Edge Thickness Enter a value.  This value will be used to raise/lower the design when either Road widening project or Resheet is selected for the Road String Add cul-de-sac at This option will enable inclusion of a cul-de-sac/s to the Road String.   Inputs Tick on this option to enable addition of cul-de-sac strings. When ticked on, select whether to add a Cul-de-sac string at the start, end or both start and end of the Road String alignment   Behaviour Cul-de-sac alignment created using the parameters as per the Project Assist Settings.  Head of cul-de-sac set a small distance inside the Road String alignment start/end. Cul-de-sac String created from the alignment.  Use alignment is applied and a centre point selected using the central radius of the cul-de-sac
Road Edge Connection (or String control)	Ignore Tick on to not apply this action.  Panel colour will change. Information Information includes the action type, Alignment Name and side of the Road alignment.  Hover over the inputs to see the information about that input in the information box. Horizontal control and maintain road crossfall Tick on this option to use the alignment to control the width/offset of the Road Edge code for the Road String.   Inputs Tick on this option to apply.   Behaviour Road String Variations applied to widen the Road Edge Code to match the alignment (crossfall maintained as per the Template) Additional sampling added for the start and end of the road edge alignment Create string for control of horizontal and vertical Tick on this option to create a String from the alignment and use that String to control the offset and elevation of the Road Edge code for the Road String.   Inputs Tick on this option to apply.   Behaviour A String is created from the alignment Auto Profile (Reference Point) applied to use elevations from the Road String centreline, and a constant crossfall (as per the Project Assist Settings) used to calculate the elevations of the String. Design Constraints applied to show minimum and maximum crossfalls (measured from the Road String centreline) as per the Project Assist Settings. Road String Variation applied to set the full position (offset and elevation) of the Road Edge code to match the String created from the road edge alignment Additional sampling added for the start and end of the road edge alignment Create as separate string (assign template) Tick on this option to create a String from the alignment including applying a Template.  Note: This option will be automatically defaulted on if the alignment is not (generally) parallel to the Road String, and creating a separate String would deliver a better modelling result.  A warning message similar to below will display: The Road String cross sections will be edited to remove all Codes outside of the Road Edge Code.  The String will be added to the Design Model. Note: A Profile String is created.  This string will not automatically truncate at intersections or adopt elevations from another string, except as per below.   Inputs Tick on this option to apply.  Additional String controls will display (see below)   Behaviour A String is created from the alignment A Template is applied (user selected as per Template selection below) Auto Profile (Reference Point) applied to use elevations from the Road String centreline, and a constant crossfall (as per the Project Assist Settings) used to calculate the elevations of the String. Design Constraints applied to show minimum and maximum crossfalls (measured from the Road String centreline) as per the Project Assist Settings. Design Model Road String Codes outside of the Road Edge are removed The new String is added to the Design Model Select Template to Apply Only displays if Create as separate string is ticked on. Pick list of CSD Templates to apply to this String.  Section Sample Rate Only displays if Create as separate string is ticked on. Type in a spacing for tangent segments along the String Type in a spacing for arc segments along the String Is kerb return? Tick on if the String is intended to be applied as a Kerb type String.  Panel Inputs will change:   Remove main road edge? By default, kerb returns add a code to describe the kerb pavement (LDUM or RUM).   This is automatically connected to the edge of the main road and the centreline of the side road. Depending on the kerb alignment geometry, it may be preferred to remove the DUM code. Tick on to remove the kerb pavement (DUM) code from the kerb return sections Remove batter Tick on to prevent a daylight/batter code from being included. Select Template to Apply Pick list of CSD Templates to apply to this Kerb String. Selecting 'Auto' will result in the cross sections being created automatically by connecting matching codes on the main and side roads Select Sample Rate Type in a spacing for tangent segments along the String Type in a spacing for arc segments along the String Is cul-de-sac? Tick on if the alignment is intended to be used as a cul-de-sac type String.  All other inputs will be greyed out, except to select kerb return, untick cul-de-sac, detach from the road and move up/down in processing order. Note: It is important for the user to ensure that the alignment is suitable to be used as a cul-de-sac.  Cul-de-sac alignments require to be drawn in a certain direction (CW for left hand drive and CCW for right hand drive) and need to start/end at the Road Edges of the Road String. Click to disassociate (detach) the alignment from the Road String.  See under the heading Not Associated with Road Strings for behaviour when this alignment type is not associated with a Road String. Move this up in the list, so it is processed (added) earlier in the processing of the alignments Move this up in the list, so it is processed (added) later in the processing of the alignments
Footpath Control	Can be used to control the offset, or offset and elevation, of the footpath/sidewalk.  If created as a separate string the 'Footpath' codes (inner and outer) will be removed from the Road String to allow replacement by the separate 'Footpath' string and it's cross sections.  It is assumed the Road String that the Footpath control is associated with has a Footpath (inner) Code (as per the Project Assist Settings - Footpath Templates)   Ignore Tick on to not apply this action.  Panel colour will change. Information Information includes the action type, Alignment Name and side of the Road alignment.  Hover over the inputs to see the information about that input in the information box. Horizontal control and maintain road crossfall (from Template) Tick on this option to use the alignment to control the width/offset of the footpath/sidewalk code/s for the Road String. If only one alignment left or right of the Road String is assigned as a footpath/sidewalk, then changes are applied to the inner 'footpath' code only. Special Note: If two alignments left or right of the Road String are assigned as a footpath/sidewalk, then changes will be applied to the inner 'footpath' code in both cases.  Post creation, users should open the Design Data form and edit the second 'inner' footpath entry to set the change to the apply to the 'outer' footpath code.    Inputs Tick on this option to apply.   Behaviour Road String Variation applied to change the offset of the Footpath Code (inner or outer) to match the alignment (crossfall maintained as per the Template) Additional sampling added to the Road String for the start/end of the alignment Create string for control of horizontal and vertical Tick on this option to create a String from the alignment and use that String to control the offset and elevation of the Road Edge code for the Road String. If only one alignment left or right of the Road String is assigned as a footpath/sidewalk, then changes are applied to the inner 'footpath' code only. Special Note: If two alignments left or right of the Road String are assigned as a footpath/sidewalk, then changes will be applied to the inner 'footpath' code in both cases.  Post creation, users should open the Design Data form and edit the second 'inner' footpath entry to set the change to the apply to the 'outer' footpath code.    Inputs Tick on this option to apply.   Behaviour A String is created from the alignment Auto Profile (Reference Point) applied to use elevations from the next inner code from the Road String (relative to the 'footpath' code, the next inner code), and a constant crossfall (as per the Project Assist Settings) used to calculate the elevations of the String. Design Constraints applied to show minimum and maximum crossfalls (measured from the Road String centreline) as per the Project Assist Settings. Section spacings set to match the Road String Road String Variation applied to set the full position (offset and elevation) of the Footpath Code to match the String created Additional sampling added to the Road String for the start/end of the alignment Create as separate string (assign template) Tick on this option to create a String from the alignment including applying a Template.  The software will apply a 'left' or 'right' template (pending the side of the Road String alignment) as per the Project Assist Settings - Footpath Templates. Note: This option will be automatically defaulted on if the alignment is not (generally) parallel to the Road String, and creating a separate String would deliver a better modelling result.  A warning message similar to below will display: The Road String cross sections will be edited to remove the inner and outer 'Footpath' codes, as well as the Batter/Daylight.  The String will be added to the Design Model. Notes: - A Profile String is created.  This string will not automatically truncate at intersections and will adopt elevations as per below. - Only the inner and outer 'Footpath' codes will be removed from the template.  Codes outside of the footpath/sidewalk will not be removed from the Road String.  These may need to be edited/removed by the user at the completion of the Project Assist process. If a Boundary Code is included, Project Assist can use an alignment to control this code.   Inputs Tick on this option to apply.  Additional String controls will display (see below).   Behaviour A String is created from the alignment A Template is applied (user selected as per Template selection below) Auto Profile (Reference Point) applied to use elevations from the next inner code from the Road String (relative to the 'footpath' code, the next inner code), and a constant crossfall (as per the Project Assist Settings) used to calculate the elevations of the String. Design Constraints applied to show minimum and maximum crossfalls (measured from the Road String centreline) as per the Project Assist Settings. Design Model Road String Codes for the inner Footpath and outer Footpath are removed over the alignment extents of the 'footpath' string Road String Batter/daylight is removed over the alignment extents of the 'footpath' string The new String is added to the Design Model Select Template to Apply Only displays if Create as separate string is ticked on. By default a 'left' or 'right' Footpath Template is applied as per the Project Assist Settings Users can pick a CSD Templates from the list, to apply to this String.  Section Sample Rate Only displays if Create as separate string is ticked on. Type in a spacing for tangent segments along the String Type in a spacing for arc segments along the String Click to disassociate (detach) the alignment from the Road String.  See under the heading Not Associated with Road Strings for behaviour when this alignment type is not associated with a Road String. Move this up in the list, so it is processed (added) earlier in the processing of the alignments Move this up in the list, so it is processed (added) later in the processing of the alignments
Sawcut Control	Can be used to insert sawcut code/s in a Road String.  The 'sawcut' code is assumed to be located before the Road Edge, however if the sawcut code (as defined in the Project Assist Settings) exists in the Road String Template, then the alignment will control this Code.   Ignore Tick on to not apply this action.  Panel colour will change. Information Information includes the action type, Alignment Name and side of the Road alignment.  Hover over the inputs to see the information about that input in the information box. Add Variation to control sawcut Tick on this option to use the alignment to control a sawcut for the Road String.  The sawcut is assumed to be located between the Road String C.L. and Road Edge code. Inputs Tick on this option to apply.   Behaviour Road String Sawcut Code included in the CSD Template that has been assigned to the Road String Variation applied to change the offset of the Sawcut Code (inner or outer) to match the alignment (crossfall maintained as per the Template) Additional sampling added to the Road String for the start/end of the Variation applied No Sawcut Code included in the CSD Template that has been assigned to the Road String Variation applied to Insert the Sawcut Code with Interpolated Elevations (the code is inserted but adopts the elevation of the design surface continuously) Additional sampling added to the Road String for the start/end of the Variation applied Create as a Draped Profile String Tick on this option to use the alignment to control a sawcut for the Road String, with the sawcut providing a potential grade break in the sections.  The sawcut is assumed to be located between the Road String C.L. and Road Edge code.  Inputs Tick on this option to apply.   Behaviour A Draped Profile String is created from the alignment and set to use the sampled surface elevations. Road String Sawcut Code included in the CSD Template that has been assigned to the Road String Variation applied to set the full position (offset and elevation) of the Sawcut code to match the Draped Profile String created from the sawcut alignment Additional sampling added to the Road String for the start/end of the Variation applied No Sawcut Code included in the CSD Template that has been assigned to the Road String Variation applied to Insert a new Code for the sawcut, inserted before the Road Edge code of the Road String Variation applied to set the full position (offset and elevation) of the Sawcut code to match the Draped Profile String created from the sawcut alignment Additional sampling added to the Road String for the start/end of the Variation applied Click to disassociate (detach) the alignment from the Road String.  See under the heading Not Associated with Road Strings for behaviour when this alignment type is not associated with a Road String. Move this up in the list, so it is processed (added) earlier in the processing of the alignments Move this up in the list, so it is processed (added) later in the processing of the alignments
Boundary Line	Can be used to control the Boundary Code applied to a Road String, and to manage the design extents of the Road String (by editing the batter/daylight code).   Ignore Tick on to not apply this action.  Panel colour will change. Information Information includes the action type, Alignment Name and side of the Road alignment.  Hover over the inputs to see the information about that input in the information box. Add Variation to control boundary Tick on this option to use the alignment to control the offset and elevation of the Boundary Code (as defined in the Project Assist Settings) on the Road String.  Inputs Tick on this option to apply.   Behaviour If the Boundary Code exists in the Road String cross sections Variation applied to set the Boundary Code to adopt the elevations of the sampled surface and the offset of the alignment (match code to surface) Additional sampling added to the Road String for the start/end of the Variation applied If the Boundary Code does not exist in the Road String cross sections Variation added to insert the Boundary Code into the Road String cross sections, before the batter/daylight Code Variation applied to set the Boundary Code to adopt the elevations of the sampled surface and the offset of the alignment (match code to surface) Additional sampling added to the Road String for the start/end of the Variation applied Add boundary alignment as batter max offset Tick on this option to use the alignment as a maximum batter/daylight offset limit.  In this case the Boundary Code (as defined in the Project Assist Settings) is not edited. Inputs Tick on this option to apply.   Behaviour Road String Batter Override is applied to the Road String.  Batter/daylight slopes are adopted from the first Template applied to the Road String A maximum offset alignment is also applied to the Batter override entry using this alignment.  Batter/daylight offsets will be restricted to a maximum offset controlled by the alignment geometry. Create as a draped profile string Tick on this option to create a String from the Boundary alignment and use this to control the offset and elevation of the Boundary Code (as defined in the Project Assist Settings) for the Road String. Inputs Tick on this option to apply.   Behaviour A Draped Profile String is created from the alignment and set to use the sampled surface elevations. Road String Boundary Code is removed over the range of the Boundary alignment Batter/Daylight override is applied to remove the batter/daylight over the range of the Boundary alignment Additional sampling added to the Road String for the start/end of the Variation applied Click to disassociate (detach) the alignment from the Road String.  See under the heading Not Associated with Road Strings for behaviour when this alignment type is not associated with a Road String. Move this up in the list, so it is processed (added) earlier in the processing of the alignments Move this up in the list, so it is processed (added) later in the processing of the alignments
Not Associated with Road Strings	Details each alignment to be used as a String, not connected/associated with a Road String.  This suits modelling strings such as roundabouts, islands and footpaths/sidewalks connecting different road string designs, and more.
Island or Roundabout String	These strings will remove codes from the Road Strings, between the Road Edges, to prevent overlap with the added island string.     Ignore Tick on to not apply this action.  Panel colour will change. Information Information includes the action type, Alignment Name and side of the Road alignment.  Hover over the inputs to see the information about that input in the information box. Create as profile string Tick on this option to independently design the vertical geometry.  A best fit vertical design will be applied initially against the sampled surface. Inputs Tick on this option to apply.   Behaviour There are two cases: The island is not contained inside another island.   Behaviour: A String is created from the alignment A Template is applied (user selected as per Template selection below) A best fit vertical design is applied to the String Intersected Road String/s Sampling added to the Road Strings (over the range of the island) to improve modelling where there the island exists. If in an intersection, the Kerb String pavement codes (LDUM/RDUM) are removed Design Model created Total Model base used Strings (excluding islands) added Design Model (with Islands) Created All Codes between the Road Edges of the affected Road String are removed from the model (over the range where they overlap the island) The new String is added to the Design Model The island is contained inside another island.   Where two island type alignments are created, one inside the other, the software will trigger this as a 'Roundabout' String type and automatically treat the outer island as a draped string that references the inner 'Roundabout' string for elevations and modelling.  In the workflow, only the inner island alignment (INNER String) will be displayed for editing (the outer will not display in the workflow) and the following panel will display: Behaviour: A String is created from the OUTER alignment Auto Profile (Reference Surface) applied to assign elevations matching the selected Model/Surface.  Sampling applied as per the Project Assist Settings. A String is created from the INNER alignment A Template is applied (user selected as per Template selection below) Sampling applied as per the Project Assist Settings. A Variation is applied to set the offset and elevation of the Roundabout Pavement Code (LDUM/RDUM) to adopt the offset and elevation of the OUTER String created Auto Profile (Reference Point) applied to use elevations from the OUTER String, and a constant crossfall used to calculate the elevations of the String. Design Constraints applied to show minimum and maximum crossfalls (measured from the Road String centreline) as per the Project Assist Settings. Intersected Road String/s Sampling added to the Road Strings (over the range of the island) to improve modelling where there the island exists. If in an intersection, the Kerb String pavement codes (LDUM/RDUM) are removed Design Model created Total Model base used Strings (excluding islands) added Design Model (with Islands) created All Codes between the Road Edges of the affected Road String are removed from the model (over the range where they overlap the island) The new OUTER String is added to the Design Model The new INNER String is added to the Design Model   Create as a Draped Profile String Tick on this option to drape the string onto the Design Model surface (the model built before adding the islands). Inputs Tick on this option to apply.   Behaviour There are two cases: The island is not contained inside another island.   Behaviour: A Draped Profile String is created from the alignment A Template is applied (user selected as per Template selection below) Elevations are adopted from the selected Model/Surface selected. Intersected Road String/s Sampling added to the Road Strings (over the range of the island) to improve modelling where there the island exists. If in an intersection, the Kerb String pavement codes (LDUM/RDUM) are removed Design Model created Total Model base used Strings (excluding islands) added Design Model (with Islands) Created All Codes between the Road Edges of the affected Road String are removed from the model (over the range where they overlap the island) The new String is added The island is contained inside another island.   Where two island type alignments are created, one inside the other, the software will trigger this as a 'Roundabout' String type and automatically treat the outer island as a draped string that references the inner 'Roundabout' string for elevations and modelling.  In the workflow, only the inner island alignment (INNER String) will be displayed for editing (the outer will not display in the workflow) and the following panel will display: Behaviour: A Draped Profile String is created from the INNER alignment A Template is applied (user selected as per Template selection below) Elevations are adopted from the selected Model/Surface selected. Sampling applied as per the Project Assist Settings. A Profile String is created from the OUTER alignment Auto Profile (Reference Surface) applied to assign elevations matching the selected Model/Surface.  Sampling applied as per the Project Assist Settings. Intersected Road String/s Sampling added to the Road Strings (over the range of the island) to improve modelling where there the island exists. If in an intersection, the Kerb String pavement codes (LDUM/RDUM) are removed Design Model created Total Model base used Strings (excluding islands) added Design Model (with Islands) created All Codes between the Road Edges of the affected Road String are removed from the model (over the range where they overlap the island) The new OUTER String is added The new INNER String is added Draped String Model/Surface Pick list to select the Model/Surface to drape the String/s onto. Note: Where there is an inner and outer string, the outer string will always be draped onto this surface Select Template to Apply Only displays if Create as separate string is ticked on. By default a 'left' or 'right' Island Kerb Template is applied as per the Project Assist Settings Users can pick a CSD Templates from the list, to apply to this String.  Section Sample Rate Only displays if Create as separate string is ticked on. Type in a spacing for tangent segments along the String Type in a spacing for arc segments along the String
Driveway	The Driveway String behaves exactly the same as the Road Edge or String Control, disassociated from any Road String (so, acting as an independent String Control in a model).  See String Control below for details.
---- Existing Feature Constraints ----	Separator for Strings that are added to model existing features such as existing road centrelines, edges and footpaths/sidewalks.  For these string types, there is no capacity to incorporate design elements into these strings with Project Assist - they are assumed to be included to enable connection of design Road Strings (for intersections and the forming of kerb returns)
Existing (no design) Road CL control	These strings can be set as Road Strings, with additional behaviour to drape onto the sampled surface (both the centreline C.L. code as well as the left/right Road Edge Codes and optionally the Footpath (inner) codes).    Ignore Tick on to not apply this action.  Panel colour will change. Information Information includes the action type, Alignment Name and side of the Road alignment.  Hover over the inputs to see the information about that input in the information box. Setup road string as existing (match to existing surface) Tick on this option to drape the string onto the sampled surface and to create it as a Road String (with Road Edge codes for intersection connection). This alignment type can automatically include other alignments that are set as Existing (no design) Road Edge Control, using them to control the offset of the Road Edge codes on this Road String and setting the code elevations to match the sampled surface. If a Template is assigned to this Road String and includes Footpath codes, the Existing (no design) Footpath Control alignments will set the Footpath Codes to use the alignments for code offsets and adopt elevations to match the sampled surface. Associated alignments must fall within the offset tolerance as set in the Project Assist Settings, otherwise they will be treated as independent Strings. Inputs Tick on this option to apply.   Behaviour There are multiple cases: The Template pick list is left blank (no Template assigned).   Behaviour: A Road String is created from the alignment An Auto Profile is applied, setting the elevation of the centreline to adopt the sampled surface Variations will be applied to create a left and right Road Edge Code with a 0.01 offset and zero slope, to enable intersections and kerb returns to form. The Road String is included in the Auto Model surface The Template pick list is populated (a CSD Template is assigned). The Road Edge and Footpath (inner) codes can be set to use  Existing (no design) Road Edge Control and Existing (no design) Footpath Control alignments. Note: if control alignments are not present, the Codes will adopt the offsets and height differences/crossfalls as set by the CSD Template. The following panel will display: Behaviour: A Road String is created from the alignment An Auto Profile is applied, setting the elevation of the centreline to adopt the sampled surface If Existing (no design) Road Edge Control alignment/s are included: Variation/s will be applied for each alignment to set the left/right Road Edge Code to adopt the offset of the Existing (no design) Road Edge Control alignment and elevations of the sampled surface. If Existing (no design) Footpath Control alignment/s are included: Variation/s will be applied for each alignment to set the left/right Footpath (Inner) Code to adopt the offset of the Existing (no design) Footpath Control alignment and elevations of the sampled surface. The Road String is included in the Auto Model surface Create as a Draped Profile String Tick on this option to drape the string onto the sampled surface and add to the Design Model (the model built before adding the islands). Inputs Tick on this option to apply.   Behaviour Behaviour: A Draped Profile String is created from the alignment A Template is applied (user selected as per Template selection below) Elevations are adopted from the Sampled Surface Design Model created Total Model base used The new String is added Select Template to Apply Users can pick a CSD Templates/a> from the list, to apply to this String.  Section Sample Rate Type in a spacing for tangent segments along the String Type in a spacing for arc segments along the String/td>
Existing (no design) Road Edge control	This alignment can be used to control the Road Edge Code for the Existing (no design) Road CL control string. If added to the Existing (no design) Road CL String this workflow message panel will display instead of the Footpath control: Otherwise the following workflow panel will display:   Ignore Tick on to not apply this action.  Panel colour will change. Information Information includes the action type, Alignment Name and side of the Road alignment.  Hover over the inputs to see the information about that input in the information box. Create as a Draped Profile String Tick on this option to drape the string onto the sampled surface and add to the Design Model (the model built before adding the islands). Inputs Tick on this option to apply.   Behaviour Behaviour: A Draped Profile String is created from the alignment Elevations are adopted from the  Sampled Surface. Sampling is applied as per the Island Sampling Rate in the Project Assist Settings Design Model created Total Model base used The new String is added Create as a Road String, so that intersections can form Tick on this option to create it as a Road String (with Road Edge codes for intersection connection) and drape the centreline onto the Sampled Surface.  The Road Edge code offsets will be small, allowing kerb returns to form and match closely to the Road String alignment and adopt elevations of the sampled surface. Inputs Tick on this option to apply.   Behaviour A Road String is created from the alignment An Auto Profile is applied, setting the elevation of the centreline to adopt the sampled surface Variations be applied to create both a left and right Road Edge Code with a 0.01 offset and zero slope, to enable intersections and kerb returns to form. The Road String is included in the Auto Model surface
Existing (no design) Footpath control	This alignment can be used to control the Footpath Inner Code for the Existing (no design) Road CL control string, when a Template is applied to that string and includes a Footpath (Inner) Code (as per the Project Assist Settings - Footpath Templates). If added to the Existing (no design) Road CL String this workflow message panel will display instead of the Footpath control: If this alignment is not associated to the Existing (no design) Road CL string then the alignment will behave exactly as an Existing (no design) Road CL alignment
------------------     Nothing	Select this option to do nothing (ignore) the alignment.
[Alignment types that can be associated with a Road String]	The below alignment types can be associated with, or disconnected from, a Road String.  Below describes their behaviour when not associated with a Road String.
(Road Edge Connection or) String Control	When not associated with a Road String, this type behaves as an independently designed String added to a Model. Behaviour A Profile String is created from the alignment Template applied as per the Template selection Auto Profile/s are applied, pending the Start Connect and End Connect settings Added to Design Model (including Islands) model New String added to the model Overlapping Road String C.L. Code/s will be removed Controls on this workflow panel include: Ignore Tick on to not apply this action.  Panel colour will change. Information Information includes the action type, Alignment Name and side of the Road alignment.  Hover over the inputs to see the information about that input in the information box. Is kerb return? If ticked on, options are deactivated.  Available inputs are as per Road Edge Connection workflow panel above (in Associated to Road String). Is cul-de-sac? If ticked on, options are deactivated.  Available inputs are as per Road Edge Connection workflow panel above (in Associated to Road String). Remove batter? Removes the batter/daylight code from the created string cross sections by adding a Batter/Daylight Override. Select Template to Apply Pick list of CSD Templates to apply to this String.  Section Sample Rate Type in a spacing for tangent segments along the String Type in a spacing for arc segments along the String Start connect? Tick on this option to adopt elevations from the selected Model/Surface for a specified distance working forward from the start of the alignment. Type in a distance to apply. An Auto Profile (Reference Surface) will be applied to the String to assign elevations matching the selected Model/Surface, for the distance specified working from the start.  End connect? Tick on this option to adopt elevations from the selected Model/Surface for a specified distance working backward from the end of the alignment. Type in a distance to apply. An Auto Profile (Reference Surface) will be applied to the String to assign elevations matching the selected Model/Surface, for the distance specified working from the end.  Model/Surface Pick list Pick list to select the Model/Surface to adopt elevations start/end.
Footpath control or String	When not associated with a Road String, this type behaves as an independently designed String added to a Model (same as Road Edge Connection or String Control when not associated to a Road String)
Boundary Line Control	When not associated with a Road String, this type behaves as a draped String, sampled against the Sample Surface and applying a best fit vertical design. There are no inputs.
Standard Actions	Applies actions not specifically related to the alignment processing, such as building models and auto creating kerb returns at intersections.  Standard Actions reside under this panel heading:
Auto Kerb Returns	Enables auto creation of kerb return strings at intersections, including enhanced controls related to the kerb pavement and intersection modelling options.   Ignore Tick on to not apply this action.  Panel colour will change. Default Radius Type in a default radius connecting the Road Edges of the Main and Side Road Strings. Omit batters By default, batters are added to all kerb returns. Tick on to default that slope batters are not applied to any kerb return. Remove main road edges Tick on to create 'All-Crowned' type intersections.  By default the Main Road cross sections, between the left and right Road Edge, are maintained through the intersection.  Tick on to add all new kerb return strings as all-crowned type (centrally crowned) intersections.  The main road edges for these intersections will be removed from the road network model. Interesection Manager The Intersection Manager provides users with control over each kerb return at each intersection.  Click to open the Intersection Manager form.  Note: Kerb returns are not created at this point, so some functions will be disabled in the Intersection Manager form.  Also, the Intersection Manager form will be displayed modally (users cannot zoom and pan in the drawing with the form open).
Create Model Builder Model	Select model names to apply to Built Models created by Project Assist.  Different workflow applications will trigger creation of and addition to different Models.   Ignore Tick on to not apply this action.  Panel colour will change. Name/Select base model Select an already created model to apply the Project Assist outputs to. Users can type directly into this field to set a unique named Base model. Name/Select model with islands Select an already created model to apply the Project Assist outputs to. Users can type directly into this field to set a unique named Base Model (with islands)
Build Design Models	Triggers create/rebuild of all models. Thread Actions - Models set to compute - Update plan drawing of linework and models   Ignore Tick on to not apply this action.  Panel colour will change. Min Triangle Length Set a maximum triangle length to apply a Boundary Retraction of triangles Use Boundary Retraction If ticked on, then triangles will be removed from the surface, working from the outside in, until a triangle is reached with a length less than the Min, Triangle Length.
Plugins	Plugin panels will be displayed under the Plugin heading panel, after being added via the Plugins button.
Cancel	Close without applying
Set Alignment Types	Click to return to the Alignment Usage form.
Settings	Opens the Project Assist Settings form.
Plugins	Opens the Plugins form listing all plugins created for Project Assist.    Plugins List List of plugins.  Select to add this action. Information box Description of what the plugin does Cancel Do not add the Plugin action and return to the workflow Add Action Add the Plugin action and return to the workflow.  An additional panel will display with inputs for this plugin. Plugins cannot be removed after being added, however will have an 'Ignore' tick box to not apply the plugin action.
Compute	Compute all Project Assist Actions. If a report was selected to be included, this will display once all strings and models have been created.