Access platforms, Stairs and Ladders

Administrator Guide
AVEVA Solutions Limited

Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.

1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.

1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.

1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.

1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.

Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it
(including source code, object code, any data contained in it, the manual and any other documentation supplied
with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.

All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is
made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.

The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.

© Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall
not be liable for any breach or infringement of a third party's intellectual property rights where such breach results
from a user's modification of the AVEVA software or associated documentation.

AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.

Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
Access platform, Stairs and Ladders Administrator Guide

Revision Sheet

Date Version Comments / Remarks

September 2011 12.1.1 Issued
January 2012 Copyright added to all pages.
Access platform, Stairs and Ladders Administrator Guide
 Access platforms, Stairs and Ladders Administrator Guide

Access platforms, Stairs and Ladders

Administrator Guide

Contents Page

Administrator Guide
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Who Should Use this Guide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Product Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
How to Use this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2

Overview of ASL Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Hierarchical Relationships of ASL Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Simplified Parameterisation of ASL Assemblies . . . . . . . . . . . . . . . . . . . . . . . . 2:2
System Evaluation of Engineering Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Administrative Preconditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
System/User Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Application Data Worlds (APPLDW). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Application Data and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Extension to Design Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Valid Value Elements (VVALUE) Additional Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
General Routing Path (RPATH). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5
General Route Path Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Administrator Access Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Storage Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2

© Copyright 1974 to current year. i 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platforms, Stairs and Ladders Administrator Guide

Creating Standards (Engineering Criteria) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2

Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3
Secondary Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4
Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4
Creating ASL Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5
Creating ASL Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6

Stair Tower (STRTWR) Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

Stair Tower Database Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1
Description of Stair Tower Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Stair Landing (STRLNG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Tower Steel (TWRSTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Access Set (ACCSET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2

Stair Flight (STRFLT) Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1

Stair Flight Database Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1
Description of Stair Flight Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2
Stair Stringer (STRSTR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3
Tread Set (TREADS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3
Tread (TREAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3

Ladder (LADDER) Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

Ladder Database Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Description of Ladder Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Ladder Stringer (LDRSTR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Rung Set (RUNGSE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Ladder Rung (LDRRUN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Ladder Cage (LDRCAG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Cage Segment (CAGSEG). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Ladder Exit (LDREXT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2

Platform (PLTFRM) Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1

Platform Database Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
Description of Platform Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
External Frame (EXTFRM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
Internal Frame (INTFRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
Platform Grid (PLTGRD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
Platform Feature (PLFEAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
Platform Opening (PLOPEN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2

© Copyright 1974 to current year. ii 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platforms, Stairs and Ladders Administrator Guide

Open Feature (OPENFE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2

Route Attachment (RATTA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2

Handrail (HANDRA) Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1

Handrail Database Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
Description of Handrail Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
Handrail Panel Set (HRPNSE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
Handrail Panel (HRPANE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Handrail Kick Plate Set (HRKPSE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Kick Plate (KICKPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Rail Set (RAILSE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Rail (RAIL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Handrail Feature (HRFEAT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Handrail Gate (HRGATE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Route Attachment (RATTA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Post Set (POSTSE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3
Handrail Post (HRPOST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3

© Copyright 1974 to current year. iii 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platforms, Stairs and Ladders Administrator Guide

© Copyright 1974 to current year. iv 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Introduction

1 Introduction

This guide introduces the AVEVA Access platforms, Stairs and Ladders (ASL) application. It
identifies the different types of user who would need to read this guide and sets out what
knowledge they will need before they start. The section provides an overview of the main
functionality that the application introduces.

1.1 Who Should Use this Guide?

Administrators and discipline leads should use this guide to understand the concept of
standards and be able to configure standards that define the engineering criteria that the
Access platform, Stair and Ladder and assemblies will be evaluated against, the standards
are fully configurable and can be applied to suit project requirements or international
standards. This guide will also describe the Assembly World concepts that the Access
platform, Stair and Ladder elements use.
Administrators should have a reasonable knowledge of PDMS database structures where
they might need to configure rules and assembly geometry. A knowledge of PML is required
if they need to set up PML expressions in the engineering criteria.
This guide does not cover product installation. Refer to References.
For details of non administrative process of ASL refer to the Access platform, Stairs and
Ladders User Guide.

1.2 Product Compatibility

The ASL application can be used with the following product:
• AVEVA PDMS DESIGN 12.0SP2.
There is no upgrade path capability of ASL model data based on pre 12.0SP2 versions of
PDMS DESIGN to the 12.0SP2 ASL elements.

1.3 References
This section lists other documents that provide supporting or complementary information to
this guide.
Access platform, Stairs and Ladders User Guide.
Structural Design User Guide.
AVEVA Product System Requirements.

© Copyright 1974 to current year. 1:1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Introduction

1.4 How to Use this Guide

This section describes how to use this guide and outlines what each section covers.

Overview of ASL Functionality introduces the ASL application and concepts.

Getting Started explains how to get up and running quickly with the
ASL application.

Stair Tower (STRTWR) Assembly explains the database architecture, workflow, UI

design concepts and base functionality for creating a
Stair Tower assembly.

Stair Flight (STRFLT) Assembly explains the database architecture, workflow, UI

design concepts and base functionality for creating a
STRFLT assembly.

Ladder (LADDER) Assembly explains the database architecture, workflow, UI

design concepts and base functionality for creating a
Ladder assembly.

Platform (PLTFRM) Assembly explains the database architecture, workflow, UI

design concepts and base functionality for creating a
Platform assembly.

Handrail (HANDRA) Assembly explains the database architecture, workflow, UI

design concepts and base functionality for creating a
Handrail assembly.

© Copyright 1974 to current year. 1:2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Overview of ASL Functionality

2 Overview of ASL Functionality

The ASL application is a PDMS DESIGN application for the DESIGN module that provides a
bespoke database architecture of ASL elements comprising of the administrative elements
below;
• Stair Tower (STRTWR)
• Stair Flights (STRFLT)
• Stair Landings (STRLNG)
• Ladder (LADDER)
• Platform (PLTFRM)
• Handrail (HANDRA)
These elements are the high level administrative elements that are owned by the existing
STRU hierarchy element, these elements with their easily identifiable element type
definition supports the ‘Assembly’ type concept employed throughout the application where
all of the detailed modelling is represented using the existing steelwork objects such as
Gensec, Panel, Template and Fixing. For a detailed explanation of these elements, refer to
the Structural Design User Guide. Throughout the application the workflow associated with
the creation and modification of these elements follows a consistent format through a
common user interface.
The ASL application builds on the existing database concepts and provides 3D model data
in an integrated environment, enabling quick and easy browsing and reporting on that data.

© Copyright 1974 to current year. 2:1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Overview of ASL Functionality

2.1 Hierarchical Relationships of ASL Assemblies

The ASL elements of Stair Tower, Stair Flight, Ladder, Platform and Handrail are all POS/
ORI elements whose hierarchical ownership is that of a STRU. The ASL elements should be
considered as fabrications in their own right as they in turn own specific objects fulfilling an
engineering function whose naming convention reflects the engineering function.
See the hierarchy view and descriptions below:

The descriptions and functions of these elements will be explained in the following sections.
These objects have been architected to suit specific functionality and workflow to provide
definite engineering purpose and their attribute set accurately mirrors the engineering
criteria for that object. The attributes are evaluated by the system in response to the user’s
interaction with the 3D model environment and the relevant attributes are managed through
the database hierarchy by the ASL application.

2.2 Simplified Parameterisation of ASL Assemblies

Provides a simplified means to define parameters or rules (engineering criteria) for complex
steelwork assemblies or fabrications and to de-couple the dependency on assembly
geometry and parametric rules such that any ASL assembly can be managed by any
particular standard responsible for validating and managing the engineering criteria.

© Copyright 1974 to current year. 2:2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Overview of ASL Functionality

2.3 System Evaluation of Engineering Criteria

The basic workflow concepts along with the user and system responsibilities provided by
the application are described and illustrated below;

2.3.1 Administrative Preconditions

• The administrator has the necessary privileges to create or modify criteria or assembly
data and the criteria and assemblies have been defined in the APPLDW.
• The assembly selection has been set up for the DESIGN user.

2.3.2 System/User Responsibility

• The USER uses the application functionality to create, modify or delete assembly data
in the 3D model using the criteria and assemblies in the database.
• The SYSTEM (ASL engine) analyses the positions and verifies the engineering criteria
of the assembly and then creates the instance in the database and maintains the
assembly and its criteria until subsequent modifications are made to the assembly or
data.
• The APPLICATION configures or sizes the parameters of the assembly to suit the
USER input and sets any additional attributes such as references to standards and
assemblies.
• The USER modifies the layout or any of the SYSTEM set criteria.
• The SYSTEM re-evaluates the assembly as per the second step above.

2.4 Application Data Worlds (APPLDW)

For more detailed information regarding Application Data Worlds sets refer to the Design
Reference Manual Creating the Model.
Application Data Worlds and their elements assist applications to store assemblies and
model parts for copying and propagation within a design. They have some similarities with
Templates, but are more general in content.
They are used for ASL assembly data and also by the Piping discipline.

© Copyright 1974 to current year. 2:3 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Overview of ASL Functionality

The Elements available are administrative elements allowing applications to organise data
storage areas of design objects that are not part of the design itself, but supplementary
objects used to create and maintain the model. They will not be accessed (unless
specifically instructed to do so) when performing model queries such as clashing, mass
properties, collections and they are similar to catalogue and in particular Template
definitions.

2.4.1 Application Data and Templates

Templates (TMPLates) can be included in the Application Data World, but only as instanced
templates, NOT template definitions. Such templates can be refreshed from their definitions
using existing (appware and core) driven functions. However there is no core supported
means to refresh copies of Application Data in the real model.

2.4.2 Extension to Design Data

DDAT elements have a new attribute PTOLER supplying a tolerance value as an alternative
to, or instead of the MAXMIN values which determine the range of valid values when set.
Applications using the Application data will use this value to validate its data.

2.4.3 Valid Value Elements (VVALUE) Additional Attribute

VVALUE, owned by a DDAT can have a Valid Rule set stored in the attribute VALRULE.
VALRULE is an expression attribute that can store an expression that evaluates to a logical
true or false value. If the expression does not evaluate to a logical result, or if there are
errors in the evaluation of the expression then the VALRULE will return FALSE when
queried. The VVALUE element owns a Valid Value attribute (VALIDV) that is an expression
returning a real, logical, text or reference value which supports the owning DDAT element. If
the VALRULE is true or if it is a null expression then this VALIDV will be available to the
DDAT.
VALRULEs are used by the system to control the choice of a Valid Value when property
queries are made on the owning DDAT.
One example of a particular scenario shown below of a DDAT element owning four VVALUE
elements with VALIDV and VALRULEs to control the size of a stiffener which changes in
size due to the length of the stiffener:

VValue VVal expression VALRULE expression

VVALUE 1 ( ID /ANG35x35x15 ) ( LDPR LENG le 1800 )
VVALUE 2 ( ID /ANG40x40x15 ) ( LDPR LENG gt 1800 and LDPR LENG le 2400 )
VVALUE 3 ( ID /ANG45x45x18 ) ( LDPR LENG gt 2400 and LDPR LENG le 3000 )
VVALUE 4 ( ID /ANG50x50x18 ) ( LDPR LENG gt 3000 )

The current set of VALIDValues available for the owning DDAT are the set whose
VALRULes either are unset, or evaluate to TRUE. Those that are not available are those
whose VALRULes either evaluate to FALSE, or whose evaluations generate errors.

© Copyright 1974 to current year. 2:4 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Overview of ASL Functionality

2.5 General Routing Path (RPATH)

The RPATH element provides a multi disciplinary routing concept that provides common
basis for defining any open path or closed boundary based objects in the 3D environment
such as those used in the Platform and Handrail elements.
The primary objective is to provide consistent database schema with predictable behaviour
in the creation of a path or boundary with a robust data consistency and internal checking
mechanism that can persist data during the modification of the path or boundary once it has
been created.

2.6 General Route Path Element

Information specific to the core capabilities of the Routing Path element is available in the
Software Customisation Reference Manual.

© Copyright 1974 to current year. 2:5 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Overview of ASL Functionality

© Copyright 1974 to current year. 2:6 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Getting Started

3 Getting Started

This section describes the application pre-requisites and the administrator responsibilities to
provide the DESIGN user with the necessary data to create assemblies in the 3D model.
To access ASL functionality, launch the DESIGN module and select
Design>Structures>Access, Stairs & Ladders.

3.1 Administrator Tasks

3.1.1 Administrator Access Permissions

In order to create and modify ASL standards the Administrator needs the appropriate
access permissions to the database and the Assembly Data World (APPLDW) data.
Administrator read/write access to the sample criteria and assembly data requires the
‘SYSTEM’ user to be a team member of the /ASLADMIN team and it is this team who own
the /ASLCONFIG database. The sample criteria and assembly data provided with this
release in the ASL APPLDW are created in the ASLCONFIG database.
The ASLCONFIG database should be included in all MDB’s where the administrator will be
creating and modifying standards and the user will be creating ASL assemblies.

© Copyright 1974 to current year. 3:1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Getting Started

3.1.2 Storage Areas

Before any new Standards, secondary standards or assembly geometry can be created a
storage area should be assigned, the system will present a warning message if the
administrator attempts to create a new standard with having previously set the storage area.
To manage the setting of the storage areas, select Settings > ASL Storage Area from the
menu toolbar to display the ASL –Default Storage Area form.
This form is sensitive to the access permissions of the user, if the user is an administrator
the form displays with the area for Standards on the form being visible.

The general user however will not see the setting for Standards as it is an administrators
responsibility.

3.1.3 Creating Standards (Engineering Criteria)

The Standards for Access, Stairs and Ladder application form provides the ability to
create, copy, modify and delete the data. The tasks indicated on the form to Create, Delete
and Copy are sensitive to the user permissions, where access is valid the task based links
are active and where the permissions are invalid the task link will be inactive.
The application will be provided with a sample set of data based on a British Standard which
is the default sample standard for this release. The application will allow the user to create
their own default, user or project standards using the copy and rename functionality on an
existing standard and simply modifying existing the attribute values (Valid value, Max/Min,
Tolerance, Optimum or a PML expression), see below.
The Standards are managed by selecting Settings > ASL Standards and the criteria shown
in the form is visible to the general user but not writable to the general user.

© Copyright 1974 to current year. 3:2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Getting Started

The basic workflow for Creating, Copying or Deleting Standards is managed by this form
and the activities are separated into three tasks;
• Standards
• Secondary Standards
• Properties

3.1.4 Standards

Create a New Standard

Creating a new ASL standard will display a form requesting both the Name and Description
of the Standard which updates the Design Explorer with a new Application Data Area
(APPDAR). There is no limit to the number of APPDAR that an APPLDW can own so the
user the flexibility to create any number of Standards.

Delete the Selected Standard

Deleting the Standard will delete the engineering criteria associated with the assembly data
and where the assembly data has been instanced in the 3D model the rule checking engine
and the ability to intelligently update the ASL assembly will be lost. The instances of the ASL

© Copyright 1974 to current year. 3:3 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Getting Started

assemblies all store and use references against the standard (ASLStandard), secondary
standard (ASLSbStandard) and assembly reference (AssTmpReference) with which they
are defined so deleting the standards or assemblies will delete these references.

Copy the Selected Standard

Copying existing standards provides a quick and efficient method of creating new standards
and simply editing the properties in the form control grid.

3.1.5 Secondary Standards

Create a New Secondary Standard

Having created an ASL Standard (and a corresponding APPDAR) for the encapsulation of
the criteria the Standard can then be sub-divided or categorised into secondary standards,
in this instance the secondary standards capture the different criteria of ‘Public’, Semi-
Public’ and ‘Private’ secondary standards. For example, in the case of a Ladder conforming
to a ‘Public’ secondary standard it would have rigidly defined degrees of freedom in its
allowable tolerances than those specified for a ladder conforming to a ‘Private’ secondary
standard where its criteria are much more generalised.
In database hierarchy terms the Secondary standard is managed by the Application Data
(APPLDA) element.

Delete the Selected Secondary Standard

As with the deletion of the standard, deletion of the secondary standard should only be
undertaken with care as there are instances of the standard and associated geometry in the
2D or 3D environments which will loose their references.

Copy the Selected Secondary Standard

Copying existing secondary standard provides a quick and efficient method of creating new
sub standards and changing the attribute settings for subsequent use.

3.1.6 Properties
Having created the standard and secondary standard; the properties need to be created or
modified depending on the method of creating the Standard/Secondary standard. The
properties manage the engineering criteria against the appropriate attribute for the relevant
ASL object. The engineering criteria of the ASL objects such as STRFLT, Ladder are
defined and managed by the Design Data Set (DDSE) which is owned by the APPLDA. The
DDSE corresponds to an ASL element type which has a separate Tab for managing the
values against the attribute property (Description field).

© Copyright 1974 to current year. 3:4 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Getting Started

The Description field is a listing of the attributes against the STRFLT element. The DDAT
stores the engineering criteria in the form of an expression, Real, Max/min or VVAL, it is this
data in the DDAT elements that effectively parameterises the assembly and what the rule
checking engine performs its analyses against. Indicated below are the expressions the
'Relationship between rise and going' DDAT element stores;

3.1.7 Creating ASL Assemblies

The ASL assemblies should be created in the appropriate Application Data World hierarchy
of the database as this means that they will not be clashed or queried by the system, unless
they have been instanced in the 3D model.
The creation of assemblies will require some knowledge of the Steelwork application and its
existing GENSEC and PANEL elements used for the detail representation of steelwork
together with an understanding of PML syntax. To allow the creation of more complex
assemblies an understanding of the rule syntax would be an advantage where the rules
referred to are identical to the rules and expressions used to create Template elements.

© Copyright 1974 to current year. 3:5 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Getting Started

3.1.8 Creating ASL Selections

The Selections for Access, Stairs and Ladder application form is used to expose the
relevant assemblies to the project, this functionality allows the Standard (Assigned
Standard) and the Assemblies (Assigned elements) to be used in combination and manages
the presentation of this data in the general users application such that the user can decide
which standard and assembly to use. The form also allows new selections to be created,
modified or deleted. It is then the responsibility of the system to manage the checking of the
engineering criteria based on the graphical picks or selections or manual inputs from the
user.

The figure above left shows how the Selections form manages the visibility of the Assembly
elements and provides the functionality for the administrator to promote the Stair Flights and
other ASL assemblies, to the Assigned elements grid. The elements visible in the lower
potion of the form under the heading Assembly elements are not visible to the ASL Design
application and hence the user. This form allows the administrator to assign only those
assemblies that have been authorised for use on the project.

© Copyright 1974 to current year. 3:6 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Getting Started

The Db structure on the Application Data World indicated above right shows the database
explorer and the location and hierarchy associated with the Standards, Secondary
standards and the Assembly data. Notice that both the standards information and the
assembly data are located in adjacent APPDAR under the same APPLDW.

Create a New Setting

Creating a new ASL setting will display a form requesting both the Description of the
setting and the Setting Type which updates the main menu toolbar to inform the user of the
current selection available to use.

The application allows for both Project and User selection settings to be created and the
Description gadget is autonamed based on the Setting type which can be either Project or
User and the autoname is not a hard-coded naming convention so the administrator can edit
the name to a more appropriate name.

The User and Project Selections are saved to the following directory and files;
The user settings are stored in the PDMSUSER directory and the Project settings are stored
in the Project Default path directory, for example; SAMDFLT folder, BASDFLT folder.

Delete the Selected Setting

The user will be prompted to confirm the deletion of the selected setting which will update
the main menu toolbar.

© Copyright 1974 to current year. 3:7 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Getting Started

© Copyright 1974 to current year. 3:8 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Stair Tower (STRTWR) Assembly

4 Stair Tower (STRTWR) Assembly

4.1 Stair Tower Database Hierarchy

The Stair Tower element (STRTWR) is a top level administrative element owned by a STRU
element.
The Stair Tower is a steelwork assembly that enables the user to create a rule based, linear
spiral stair arrangement of Stair Flights (STRTWR) and Stair Landings (STRLNG). A middle
tier hierarchy allows the decomposition of the Stair Tower into its individual assemblies of
Stair Flights and Stair Landings and the existing steelwork elements of GENSEC and
PANEL are used to represent the detail of the 3D model. Refer to the Structural Design User
Guide for further information on the GENSEC and PANEL elements.

© Copyright 1974 to current year. 4:1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Stair Tower (STRTWR) Assembly

4.2 Description of Stair Tower Elements

The elements denoted with the (…) after the element type identification are described in
more detail under the appropriate section heading.

4.2.1 Stair Landing (STRLNG)

STRLNG is owned by the STRTWR and acts as a transition between the multiple Stair
Flights also owned by the STRTWR, the boundary of the Stair Landing element is defined by
the application using the appropriate template within the APPLDW and the upping
coordinate is typically coincident with the Lower and Upper Work Points of the Stair Flight
elements which are defined by the user. The physical representation of the Stair Landing
element is defined using the existing GENSEC and PANEL element.

4.2.2 Tower Steel (TWRSTL)

TWRSTL is used by the STRTWR to manage the layout of the Steel structure of Beams and
Columns supporting the Stair Flight and Stair Landing layout. The primary function of the
Tower Steel is to manage in an intelligent manner the relationships between the Top of Steel
(TOS) elevations of the supporting beams and the associated Finished Floor Levels (FFL)
for Stair Flights or Ladders accessing the Stair Tower.

4.2.3 Access Set (ACCSET)

Access locations in the Stair Tower are defined and managed by the application, the
ACCSET can own any number of Access Points. Access Points are elements that imply a
logical connectivity or reference concept in that they represent the link between the two
locations being accessed from and to. The attributes of the Access Point define amongst
other things the position, orientation, size (clear opening) and also includes an 'Access
reference' for referencing adjacent locations.

© Copyright 1974 to current year. 4:2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Stair Flight (STRFLT) Assembly

5 Stair Flight (STRFLT) Assembly

5.1 Stair Flight Database Hierarchy

The Stair Flight element (STRFLT) is a top level administrative element owned by a STRU
element.
The STRFLT as a steelwork assembly enables the user to create a rule based linear Stair
Flight and it introduces a new middle tier hierarchy to enable the decomposition of the
STRFLT assembly into its logical component parts, the existing lower level elements of
GENSEC and PANEL are used to represent the detail of the 3D model.

© Copyright 1974 to current year. 5:1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Stair Flight (STRFLT) Assembly

5.2 Description of Stair Flight Elements

The following figure shows some of the attributes of the STRFLT and its offspring and the
engineering significance of those attributes to the geometrical representation of the
STRFLT.

Upon creation of the Stair Flight the system will analyse the horizontal (Overall Going) and
vertical (Overall Rise) distances between the Lower and Upper Work Points (LWP/UWP)
and validate these positions against the engineering criteria of the Stair Flight to the criteria
of the current specification. If the system analysis validates the values against the
engineering criteria the system will create the Stair Flight and populate the attributes with
the appropriate data.

© Copyright 1974 to current year. 5:2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Stair Flight (STRFLT) Assembly

5.2.1 Stair Stringer (STRSTR)

STRSTR owns the appropriate number of GENSEC steelwork elements used to model the
main supports of the Stair Flight. The GENSEC's are automatically mitred by the application
at the upper and lower elevations of the STRSTR, dependent upon the relevant 'Selections'
a STRSTR will not be created for a Concrete Stair Flight.

5.2.2 Tread Set (TREADS)

TREADS is used to manage the ownership of individual TREAD elements, in particular
where there is alternating TREAD types though this is more appropriate for the architectural
industry.

5.2.3 Tread (TREAD)

TREAD owns the PANEL steelwork elements used to model the rise or tread in the STRFLT.
The vertical position between the Tread is measured from Top of Plate to the next Top of
Plate and represents the Rise attribute on the STRFLT.

© Copyright 1974 to current year. 5:3 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Stair Flight (STRFLT) Assembly

© Copyright 1974 to current year. 5:4 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Ladder (LADDER) Assembly

6 Ladder (LADDER) Assembly

6.1 Ladder Database Hierarchy

The Ladder element (LADDER) is a top level administrative element owned by a STRU
element.
The LADDER as a steelwork assembly introduces functionality enabling the user to create a
rule based LADDER and also introduces a new middle tier hierarchy to enable the
decomposition of the LADDER into its individual assemblies of Ladder Stringers, Ladder
Rungs, Ladder Safety Cages and Exit locations. Throughout the middle tier hierarchy the
offspring of GENSEC and PANEL are used to represent the detail of the 3D model.

6.2 Description of Ladder Elements

The elements denoted with the (…) after the element type identification are described in
more detail under the appropriate section heading.

6.2.1 Ladder Stringer (LDRSTR)

LDRSTR owns the appropriate number of GENSEC steelwork elements used to model the
main supports of the Ladder.

6.2.2 Rung Set (RUNGSE)

RUNGSE is used to manage the ownership of individual LDRRUN elements; this is
dependent upon the design of the Rung and is intended to support alternating Rung types.

© Copyright 1974 to current year. 6:1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Ladder (LADDER) Assembly

6.2.3 Ladder Rung (LDRRUN)

LDRRUN owns the GENSEC and PANEL steelwork elements used to model the physical
representation of the Rung.

6.2.4 Ladder Cage (LDRCAG)

LDRCAG owns the Cage Segment (CAGSEG) element. Refer to Cage Segment
(CAGSEG).

6.2.5 Cage Segment (CAGSEG)

CAGSEG owns the GENSEC and PANEL steelwork elements used to model the physical
representation of the Cage. By default their will be two Cage Segments, one representing
the Entry/Exit at the top of the Ladder and the other representing the remainder of the Cage
itself, this mechanism allows the Entry/Exit detailing of the Cage to be modified individually
from the remained of the Cage though other modification tasks do act the whole cage. If
subsequent updates to the adjacent model require that new Entry/Exit locations are required
the user can create additional Ladder Exit elements to suit and the system will create
additional Cage Segment elements as appropriate. The Cage Segment also supports an
implied connectivity mechanism using reference attributes to Ladder Exit elements.

6.2.6 Ladder Exit (LDREXT)

LDREXT has no physical offspring but in combination with the CAGSEG provides an
implied logical connectivity or reference concept that manages the link between the
LDREXT and the CAGSEG.

© Copyright 1974 to current year. 6:2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Platform (PLTFRM) Assembly

7 Platform (PLTFRM) Assembly

7.1 Platform Database Hierarchy

The Platform element (PLTFRM) is a top level administrative element owned by a STRU
element.
The boundary outline of the Platform is defined using the Routing Path object as are other
offspring elements of the Platform, additionally it introduces a new middle tier hierarchy to
enable the decomposition of the Platform into its individual assemblies and uses the existing
lower level elements of GENSEC and PANEL to represent the detail of the 3D model.

7.2 Description of Platform Elements

The boundary definition of the Platform is provided by the Routing Path object whose shape
can is defined via a number of ways;
• Shape selection from pre-defined shape template with user input for the appropriate
sizing
• Free form interactive sketching using the Route sketching functionality
• Tracing boundaries derived from other profile elements
The Platform is the administrative element that together with the application manages the
following elements that perform a specific function within the assembly; the offspring of the
Platform are;

© Copyright 1974 to current year. 7:1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Platform (PLTFRM) Assembly

7.2.1 External Frame (EXTFRM)

EXTFRM represents the supporting steel that defines the outer boundary of the PLTFRM
whose physical representation is modelled with the GENSEC element. The EXTFRM is an
administrative element that can represent the EXTFRM geometry with either the GENCES
or PANEL element.

7.2.2 Internal Frame (INTFRM)

INTFRM represents the internal stiffening arrangement for the PLTFRM and the application
provides an intelligent grid object to manage the spacing and directions of the internal
stiffening. The INTFRM also supports the concept of primary and secondary direction for the
span direction of the stiffening and the grid object will manage and store the design intent
such that subsequent modifications to the PLTFRM such as editing the shape will
automatically adjust the Internal Framing to suit. The application also supports GENSEC to
GENSEC connectivity using the FIXING element utilising PLINE rules as per the SCTN to
SCTN functionality.

7.2.3 Platform Grid (PLTGRD)

PLTGRD is responsible for the management of the user defined Panel (Grating) sizes and
presents the user with a graphical representation of the X and Y spacing and layout of the
individual Panel (grate) sizes. The application provides the functionality allowing the user to
split the PLTGRD into individual Panel elements for accurate MTO of Grating quantities for
fabrication or simply represent the PLTGRD as one PANEL element.

7.2.4 Platform Feature (PLFEAT)

PLFEAT owns PLOPEN elements of which there can be multiple openings in any PLTFRM
element. The PLFEAT can also own RATTA elements which at this hierarchical level
provides a connectivity mechanism for the external boundary of the PLTFRM.

7.2.5 Platform Opening (PLOPEN)

PLOPEN is any opening or number of openings in the Platform, whose shape definition and
positioning mechanism using the Routing Path element is identical to that applied to the
PLTFRM element. PLOPEN elements are treated in all cases as negative geometry and
penetrate only the PLTFRM.

7.2.6 Open Feature (OPENFE)

OPENFE is responsible for the ownership of RATTA elements and at this hierarchical level
provides a connectivity mechanism to/from the internal boundary of the PLOPEN.

7.2.7 Route Attachment (RATTA)

RATTA is a connectivity element to provide two way connectivity mechanisms along the
path of a PLFEAT and OPENFE and between other ASL elements that have a logical
association to the boundary of the PLFEAT or OPENFE, such as a LADDER or STRFLT
element.

© Copyright 1974 to current year. 7:2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Handrail (HANDRA) Assembly

8 Handrail (HANDRA) Assembly

8.1 Handrail Database Hierarchy

The Handrail element (HANDRA) is a top level administrative element owned primarily by
the STRU element as well as other administrative elements.
The Handrail introduces functionality enabling the user to create a rule based arrangements
and layouts of Handrails and introduces a new middle tier hierarchy to enable the
decomposition of the Handrail into its individual components. The existing lower level
elements of GENSEC, TMPL and FIXING are used to represent the detail of the 3D model.

8.2 Description of Handrail Elements

The underlying technology responsible for the defining the route of the Handrail element is
the Routing Path element, this will provide the functionality to define an open path or closed
boundary via the following;
• Free form interactive sketching using the Route sketching functionality
• Tracing existing profiles or boundaries
The Handrail is the administrative element that together with the application manages the
following elements that perform a specific function within the assembly and the full
functionality of this application will be available in a later Service Pack product release.
The offspring of the HANDRA are;

8.2.1 Handrail Panel Set (HRPNSE)

HRPNSE is responsible for the ownership and management of multiple HRPANE elements.

© Copyright 1974 to current year. 8:1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Handrail (HANDRA) Assembly

8.2.2 Handrail Panel (HRPANE)

HRPANE is the database element responsible for the representation of 'panelised' sections
of Handrail where the Panel size is determined by its Panel Size attribute. The detail of the
HRPANE is represented using the existing database functionality of TMPL and FIXING
elements and the route of the HRPANE elements is defined using the RPATH routing object.

8.2.3 Handrail Kick Plate Set (HRKPSE)

HRKPSE is responsible for the ownership and management of multiple Kick plate elements
whose physical representation is modelled using a KICKPL element.

8.2.4 Kick Plate (KICKPL)

KICKPL is used to model the detail representation of a kick plate and follows the path of the
HANDRA, the KICKPL references the existing catalogue steel profiles via its SPREF
attribute and the position of the KICKPL is defined with respect to the owning HANDRA in
terms of its position along the path and the offset from the path of the HANDRA.
The KICKPL shares the same underlying attributes and behaviour as RAIL element.

8.2.5 Rail Set (RAILSE)

RAILSE is responsible for the ownership and management of multiple RAIL elements
whose physical representation is modelled using a RAIL element.

8.2.6 Rail (RAIL)

RAIL is used to model the detail representation of the individual RAIL elements and follows
the path of the HANDRA, the RAIL references the existing catalogue steel profiles via its
SPREF attribute and the position of the RAIL is defined with respect to the owning HANDRA
in terms of its position along the path and the offset from the path of the HANDRA.
The RAIL shares the same underlying attributes and behaviour as the KICKPL element.

8.2.7 Handrail Feature (HRFEAT)

HRFEAT owns HRGATE elements. The HRFEAT also owns RATTA elements which at this
hierarchical level provide a connectivity mechanism to/from the boundary of the HANDRA.

8.2.8 Handrail Gate (HRGATE)

HRGATE is an element used to represent access locations along the path of the HANDRA
and there can be multiple HRGATE elements in any HANDRA and the position of the
HRGATE is managed by the application as a position along the RPATH element. HRGATE
elements are managed as negative geometry and penetrate only the HANDRA and
additional detail for the HRGATE is represented using the existing database functionality of
TMPL and FIXING elements.

8.2.9 Route Attachment (RATTA)

RATTA element is a connectivity element to provide two way connectivity mechanisms
along the path of a HRFEAT and between other ASL elements that have a logical
association to the boundary of the HRFEAT such as an HRGATE, LADDER or STRFLT
element.

© Copyright 1974 to current year. 8:2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Handrail (HANDRA) Assembly

8.2.10 Post Set (POSTSE)

The POSTSE is responsible for the ownership and management of multiple HRPOST
elements.

8.2.11 Handrail Post (HRPOST)

HRPOST element represents the post detail which references the existing catalogue steel
profiles as it has a SPREF attribute, the position of the HRPOST is defined with respect to
the owning HANDRA in terms of its position along the path and the offset from the path of
the HANDRA.

© Copyright 1974 to current year. 8:3 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide
Handrail (HANDRA) Assembly

© Copyright 1974 to current year. 8:4 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide

Index

A Create
ASL Assemblies . . . . . . . . . . . . . . . . 3:5
Access Set (ACCSET) . . . . . . . . . . . . . . 4:2 ASL Selections . . . . . . . . . . . . . . . . 3:6
ACCSET . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 New Secondary Standard . . . . . . . . 3:4
Administrative New Setting . . . . . . . . . . . . . . . . . . . 3:7
preconditions . . . . . . . . . . . . . . . . . . 2:3 New Standard . . . . . . . . . . . . . . . . . 3:3
Administrator Standards (Engineering Criteria) . . . 3:2
access permissions . . . . . . . . . . . . . 3:1
tasks . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
APPDAR . . . . . . . . . . . . . . . . . . . . . . . . . 3:3
D
APPLDW . . . . . . . . . . . . . . . . . . . . . 2:3, 3:1 Database Hierarchy
APPLICATION . . . . . . . . . . . . . . . . . . . . 2:3 ASL Assemblies . . . . . . . . . . . . . . . . 2:2
Application Data and Templates . . . . . . . 2:4 Ladder . . . . . . . . . . . . . . . . . . . . . . . 6:1
Application Data Area (APPDAR) . . . . . . 3:3 Platform . . . . . . . . . . . . . . . . . . . . . . 7:1
Application Data Worlds (APPLDW) . . . . 2:3 Stair Flight . . . . . . . . . . . . . . . . . . . . 5:1
ASL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Stair Tower . . . . . . . . . . . . . . . . . . . 4:1
default storage area form . . . . . . . . . 3:2 DDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
elements . . . . . . . . . . . . . . . . . . . . . . 2:1 DDSE . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4
hierarchy . . . . . . . . . . . . . . . . . . . . . . 2:2 Delete
ASL Assemblies . . . . . . . . . . . . . . . . . . . 2:2 Selected Secondary Standard . . . . . 3:4
hierarchical relationships . . . . . . . . . 2:2 Selected Setting . . . . . . . . . . . . . . . . 3:7
simplified parameterisation . . . . . . . . 2:2 Selected Standard . . . . . . . . . . . . . . 3:3
ASLADMIN team . . . . . . . . . . . . . . . . . . . 3:1 Description
ASLCONFIG database . . . . . . . . . . . . . . 3:1 Handrail Elements . . . . . . . . . . . . . . 8:1
ASLSbStandard . . . . . . . . . . . . . . . . . . . 3:4 Ladder Elements . . . . . . . . . . . . . . . 6:1
ASLStandard . . . . . . . . . . . . . . . . . . . . . . 3:4 Platform Elements . . . . . . . . . . . . . . 7:1
Assembly Data World (APPLDW) . . . . . . 3:1 Stair Flight Elements . . . . . . . . . . . . 5:2
Stair Tower Elements . . . . . . . . . . . 4:2
C Description field . . . . . . . . . . . . . . . . . . . 3:5
Design Data Set (DDSE) . . . . . . . . . . . . 3:4
Cage Segment (CAGSEG) . . . . . . . . . . . 6:2
CAGSEG . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Copy
E
Selected Secondary Standard . . . . . 3:4 Extension to Design Data . . . . . . . . . . . . 2:4
Selected Standard . . . . . . . . . . . . . . 3:4 External Frame (EXTFRM) . . . . . . . . . . 7:2

© Copyright 1974 to current year. Index page 1 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide

EXTFRM . . . . . . . . . . . . . . . . . . . . . . . . . 7:2 P
Platform
G Database Hierarchy . . . . . . . . . . . . . 7:1
General Route Path Element . . . . . . . . . 2:5 Feature (PLFEAT) . . . . . . . . . . . . . . 7:2
General Routing Path (RPATH) . . . . . . . 2:5 Grid (PLTGRD) . . . . . . . . . . . . . . . . 7:2
Getting Started . . . . . . . . . . . . . . . . . . . . 3:1 Opening (PLOPEN) . . . . . . . . . . . . . 7:2
Platform (PLTFRM) Assembly . . . . . . . . 7:1
PLFEAT . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
H
PLOPEN . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
HANDRA . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 PLTFRM . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
Handrail PLTGRD . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
Database Hierarchy . . . . . . . . . . . . . 8:1 POS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Handrail (HANDRA) Assembly . . . . . . . . 8:1 POSTSE - Post Set . . . . . . . . . . . . . . . . 8:3
How to Use this Guide . . . . . . . . . . . . . . 1:2 Product Compatibility . . . . . . . . . . . . . . . 1:1
HRFEAT - Handrail Feature . . . . . . . . . . 8:2 Properties . . . . . . . . . . . . . . . . . . . . . . . . 3:4
HRGATE - Handrail Gate . . . . . . . . . . . . 8:2 PTOLER . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
HRKPSE - Handrail Kick Plate Set . . . . . 8:2
HRPANE - Handrail Panel . . . . . . . . . . . 8:2 R
HRPNSE - Handrail Panel Set . . . . . . . . 8:1
HRPOST - Handrail Post . . . . . . . . . . . . 8:3 RAIL - Rail . . . . . . . . . . . . . . . . . . . . . . . 8:2
RAILSE - Rail Set . . . . . . . . . . . . . . . . . . 8:2
RATTA . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
I
RATTA - Route Attachment . . . . . . . . . . 8:2
Internal Frame (INTFRM) . . . . . . . . . . . . 7:2 References . . . . . . . . . . . . . . . . . . . . . . . 1:1
INTFRM . . . . . . . . . . . . . . . . . . . . . . . . . 7:2 Route Attachment (RATTA) . . . . . . . . . . 7:2
Introduction . . . . . . . . . . . . . . . . . . . . . . . 1:1 RPATH . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5
Rung Set (RUNGSE) . . . . . . . . . . . . . . . 6:1
K RUNGSE . . . . . . . . . . . . . . . . . . . . . . . . 6:1

KICKPL Kick Plate . . . . . . . . . . . . . . . . . 8:2 S

L Secondary Standards . . . . . . . . . . . . . . . 3:4
Selections for ASL application form . . . . 3:6
LADDER . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Setting Type . . . . . . . . . . . . . . . . . . . . . . 3:7
Ladder Stair Flight (STRFLT) Assembly . . . . . . 5:1
Cage (LDRCAG) . . . . . . . . . . . . . . . 6:2 Stair Flight Database Hierarchy . . . . . . . 5:1
Database Hierarchy . . . . . . . . . . . . . 6:1 Stair Landing (STRLNG) . . . . . . . . . . . . 4:2
Exit (LDREXT) . . . . . . . . . . . . . . . . . 6:2 Stair Stringer (STRSTR) . . . . . . . . . . . . 5:3
Rung (LDRRUN) . . . . . . . . . . . . . . . 6:2 Stair Tower (STRTWR) Assembly . . . . . 4:1
Stringer (LDRSTR) . . . . . . . . . . . . . . 6:1 Stair Tower Database Hierarchy . . . . . . 4:1
Ladder (LADDER) Assembly . . . . . . . . . 6:1 Standards . . . . . . . . . . . . . . . . . 3:2, 3:3, 3:4
LDRCAG . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 Standards for ASL application form . . . . 3:2
LDREXT . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 Storage Areas . . . . . . . . . . . . . . . . . . . . 3:2
LDRRUN . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 STRFLT . . . . . . . . . . . . . . . . . . . . . . . . . 5:1
LDRSTR . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 STRLNG . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
STRSTR . . . . . . . . . . . . . . . . . . . . . . . . . 5:3
O STRTWR . . . . . . . . . . . . . . . . . . . . . . . . 4:1
STRU . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Open Feature (OPENFE) . . . . . . . . . . . . 7:2 SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . 2:3
OPENFE . . . . . . . . . . . . . . . . . . . . . . . . . 7:2 System Evaluation
ORI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2 engineering criteria . . . . . . . . . . . . . 2:3
System/User responsibility . . . . . . . . . . . 2:3

© Copyright 1974 to current year. Index page 2 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Access platform, Stairs and Ladders Administrator Guide

T
Tower Steel (TWRSTL) . . . . . . . . . . . . . . 4:2
TREAD . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3
Tread (TREAD) . . . . . . . . . . . . . . . . . . . . 5:3
Tread Set (TREADS) . . . . . . . . . . . . . . . 5:3
TREADS . . . . . . . . . . . . . . . . . . . . . . . . . 5:3
TWRSTL . . . . . . . . . . . . . . . . . . . . . . . . . 4:2

U
USER . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3

V
Valid Value attribute (VALIDV) . . . . . . . . 2:4
VALRULE . . . . . . . . . . . . . . . . . . . . . . . . 2:4
VVALUE . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
additional attribute . . . . . . . . . . . . . . 2:4

W
Who Should Use this Guide? . . . . . . . . . 1:1

© Copyright 1974 to current year. Index page 3 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.