Chapter 2

CHAPTER 2
Overview of the Stairs, Ladders and Handrail Application
The Stairs, Ladders, and Handrails (SLH) application allows designers to create and modify detailed access
and demarcation components within 3D models. The application is integrated with other AVEVA E3D
structural utilities.
2.1
Principles Employed in the Application
There are a number of features employed in the AVEVA E3D SLH application.
Standards and Defaults.
Pre-defined assembly elements.
Two representation modes.
Progressive disclosure concepts.
2.1.1
Standards and Defaults
AVEVA E3D SLH utilises Standards and Defaults to control the creation of stair, ladder and handrail
elements within the 3D model.
The Standards used by AVEVA E3D SLH are a set of geometric constraints. National, project, or industry
standards can be used in the determination of geometry for stair, ladder, and handrail elements. Any
number of standards may be used in a project.
Defaults provide an interpretation of a referenced standard and allow SLH Administrators to implement
preferred working practises. This gives SLH Administrators control over the displayed and pre-populated
options within forms for a number of SLH elements.
The values used within a Default must comply with the maximum and minimum values of the Standard it
references. In addition, SLH Administrators may stipulate valid values for certain geometric parameters. For
example, the width between stair stringers may be limited to a series of values that coincide with the width of
supplied stair treads.
Defaults are also used to associate assemblies with standards. The range of elements available for
selection in the Creation and Modification forms will be governed by the Default selected.
Forms relating to the settings Standards and Defaults are only accessible to SLH Administrators. An
example of these forms and a typical user form referencing a default and standard are shown overleaf.
Copyright 2013.
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
11
www.aveva.com
AVEVA Everything3D (2.1)

Stairs, Ladders and Handrail Modelling TM-1813
Detailed guidance on the administration of the AVEVA E3D SLH application is provided in the
TM-1864 AVEVA Everything3D Stairs, Ladders and Handrail Administration training guide.
2.1.2
Assemblies
AVEVA E3D SLH utilises a range of pre-defined assemblies to represent SLH model elements. A number
of sample assemblies are provided. Further assemblies can be created using SLH assembly constructors in
conjunction with standard catalogue and template functionality. A typical assembly selection is displayed
below.
Copyright 2013.
12
www.aveva.com

The ability to modify the representation of SLH elements is subject to the mode of operation being used and
the degree of customisation applied to user defined assemblies.
2.1.3
Representation Modes
The AVEVA E3D SLH application enables elements to be created in Layout mode or
Detail mode, as described in the following sections.
2.1.3.1 Layout Mode

Layout mode allows designers to implement a range of SLH elements, compliant to the referred standard,
without the need to specify an exact representation. The representation is intended as an indicative
display and its representation cannot be significantly modified by the user. The created elements do not own
traditional structural elements (e.g. sections, panels) and assemblies containing such elements cannot be
selected.
As with all SLH elements, aid graphics are used
to provide an initial representation of the
elements geometry, position and orientation.
Elements created in Layout mode can be clash
checked, reported on, and displayed in
drawings.
Due to the use of default representations,

detailed Material Take Off reports cannot
be generated for items created in Layout
mode.
Elements created in Layout mode can be converted to fully detailed elements at a later stage.
Copyright 2013.
13
www.aveva.com

2.1.3.2 Detail Mode

Detail mode enables designers to provide greater accuracy and representation to modelled elements. A
range of assembly options, governed by the default selected, allow the designer to view and select the exact
representation of the element. The range of assemblies available in detailed mode is controlled by the SLH
Administrator.
Model elements created in Detail mode cannot be converted to Layout mode. Equally, Layout mode
elements that are converted to Detail mode can never be reverted to Layout mode.
Copyright 2013.
14
www.aveva.com

2.1.4
Progressive Disclosure
Progressive disclosure concepts are used to provide the user with suitable information and options at
appropriate times in the design process. The forms used in the AVEVA E3D SLH application are designed
to guide the user through the design process while still allowing flexibility to review previously entered
information and allow editing. Each form utilises a number of context sensitive pages reflected in the top
section of the form.
Visual references, as to progress through the design process,
are provided at the top of the form. Successfully completed
pages are marked with a blue tick, while outstanding
mandatory information is noted by an orange triangle. The
user can navigate between pages using Next and Back link
labels or by clicking the link labels relating to successfully
completed pages.
Where possible, feedback relating to options selected and
information entered is provided within the form.
In addition, any fields that cannot be populated are greyed out.
Where mandatory fields are not completed, or incorrect

information is entered into the form, the user will be prevented
from navigating to subsequent pages.
Copyright 2013.
15
www.aveva.com

2.2
Accessing the AVEVA E3D SLH Application
AVEVA E3D SLH may be started by using the start menu icons or the desktop icons (provided both options
were selected on installation). Both methods display the E3D Login form.
After entering suitable login credentials the E3D interface is displayed.
Copyright 2013.
16
www.aveva.com

The SLH application is accessed by selecting STRUCTURES from the discipline
options list on the Quick Access Toolbar. The four tabs that make up the
STRUCTURES discipline are displayed.
The STAIRS LADDERS HANDRAIL tab contains the SLH application specific
functions.
2.3
The STAIRS LADDERS HANDRAIL tab will generally be referred to as the SLH tab in this training
guide.
The SLH User Interface
As with many other AVEVA E3D applications, SLH is a Microsoft Office Fluent based user interface.
A series of tabs are displayed at the top of the screen. Some tabs are common across all design disciplines,
while other tabs are specific to the application being used. The STAIRS LADDERS HANDRAIL tab is one of
four tab in the STRUCTURES discipline and is the focal point for creation and modification of SLH elements.
Within the STAIRS LADDERS HANDRAIL tab, key functions are held in Groups (e.g. Create, Modify,
Tools). Specific functions are invoked by clicking the appropriate button in each group.
Once the user clicks the required button a task form will be displayed. The form will usually be docked to the
right hand side of the UI.
Copyright 2013.
17
www.aveva.com

2.4
SLH Form Layout and Features
Throughout the AVEVA E3D SLH application, common form layout and features have been used, an
overview of which is given in the following sections. The general layout of both the Create and Modify forms
are the same.
The top section of the form allows Representation Mode
selection and displays the pages to be completed as part
of the creation process. The number of pages will vary with
both the element type and Representation Mode being
used.
The mid-section of the form allows users to enter

information pertinent to the page being considered. This
may consist of text fields, graphical selection processes,
and checkbox options.
The lower section of the form provides summary

information (when available) and provides action buttons
and link labels to facilitate the creation or modification
process.
A small number of forms available within the application do not adhere to the common functions. Where
this is the case additional explanation will be provided in the relevant section of the guide.
Copyright 2013.
18
www.aveva.com

Some fields or buttons in the forms may be inactive.

Inactive fields or buttons are greyed out and usually arise
as a result of:
Missing mandatory information in a page.
Geometry errors in component creation.
Default settings made by an Administrator.
On successful completion of a page the text displaying the name of the page in the top part of the form
changes to become a link label. This allows the user to navigate between completed pages and edit any
previous settings.
Similar functionality is reflected in the summary frame at the bottom of the form. Successfully selected
geometry parameters change to link labels; allowing the user to navigate to the appropriate page and edit
the parameter.
Copyright 2013.
19
www.aveva.com

Some other common form functions are explained below:
Mandatory indicates mandatory information is still required.
Completed indicates that mandatory information is completed.
Autonaming names the element being created using pre-defined naming rules.
Show Dimension displays a graphical aid showing the geometry parameter being considered.
Checkbox Allows users to toggle options in forms.
Flip allows the user to change the direction of the element.
Next link label that takes the user to the next page of the form.
Back link label that takes the user to the previous page of the form.
Copyright 2013.
20
www.aveva.com

2.5
Data Hierarchy and Element Types
The data hierarchy employed by SLH is similar to that used by other structural utilities. A brief overview of
the SLH hierarchy is provided below.
Before physical model elements can be created a number of administrative elements must be in place.
Administrative elements divide the model into structured areas and own the geometric elements that make
up the physical representation of the model.
As with all AVEVA E3D databases, the uppermost element is the World represented symbolically as /*.
SITE and ZONE elements are also required to own hierarchy elements relating to the structural disciplines.
Typical Stairs, Ladders, and Handrail Hierarchy

Structure (STRU), Framework (FRMW), or Sub-frame (SBFR) elements are all legal owners of SLH
elements. Within the SLH hierarchy further administrative elements exist for Handrail (HANDRA), Stair
Flights (STRFLT), and Ladders (RLADDR).
The data components owned by these items will vary depending on the mode used to create the elements
and the type of SLH element created.
Mode and element specific hierarchies are provided in relevant chapters.
Copyright 2013.
21
www.aveva.com

This page is intentionally left blank
Copyright 2013.
22
www.aveva.com

Chapter 2

Uploaded by

Copyright:

Available Formats

You might also like

Chapter 2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 2

Uploaded by

Copyright:

Available Formats

CHAPTER 2

Overview of the Stairs, Ladders and Handrail Application

Principles Employed in the Application

Standards and Defaults.

Pre-defined assembly elements.

Two representation modes.

Progressive disclosure concepts.

Standards and Defaults

AVEVA Everything3D (2.1)

AVEVA Everything3D (2.1)

2.1.3.1 Layout Mode

Due to the use of default representations,

AVEVA Everything3D (2.1)

2.1.3.2 Detail Mode

AVEVA Everything3D (2.1)

In addition, any fields that cannot be populated are greyed out.

Where mandatory fields are not completed, or incorrect

AVEVA Everything3D (2.1)

Accessing the AVEVA E3D SLH Application

After entering suitable login credentials the E3D interface is displayed.

AVEVA Everything3D (2.1)

The SLH User Interface

AVEVA Everything3D (2.1)

SLH Form Layout and Features

The mid-section of the form allows users to enter

The lower section of the form provides summary

AVEVA Everything3D (2.1)

Some fields or buttons in the forms may be inactive.

Missing mandatory information in a page.

Geometry errors in component creation.

Default settings made by an Administrator.

AVEVA Everything3D (2.1)

AVEVA Everything3D (2.1)

Data Hierarchy and Element Types

Typical Stairs, Ladders, and Handrail Hierarchy

Mode and element specific hierarchies are provided in relevant chapters.

AVEVA Everything3D (2.1)

This page is intentionally left blank

You might also like