Access platforms Stairs and Ladders User Guide.pdf

7/28/2019 Access platforms Stairs and Ladders User Guide.pdf

1/74

Access platform, Stairs and LaddersUser Guide


2/74

Disclaimer

Information of a technical nature, and particulars of the product and its use, is given by AVEVASolutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim

any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.

Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person orentity for any actions, claims, loss or damage arising from the use or possession of any information,particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

Copyright

Copyright and all other intellectual property rights in this manual and the associated software, and everypart of it (including source code, object code, any data contained in it, the manual and any otherdocumentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained inthis document is commercially sensitive, and shall not be copied, reproduced, stored in a retrievalsystem, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where suchpermission is granted, it expressly requires that this Disclaimer and Copyright notice is prominentlydisplayed at the beginning of every copy that is made.

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

The AVEVA products described in this guide are to be installed and operated strictly in accordance withthe terms and conditions of the respective licence agreements, and in accordance with the relevantUser Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.

First published September 2007

AVEVA Solutions Ltd, and its subsidiaries

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

Trademarks

AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised

use of the AVEVA or Tribon trademarks is strictly forbidden.AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or itssubsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product, its name orlogo belongs to its respective owner.

AVEVA Solut ions Ltd


3/74

Access platforms, Stairs and Ladders User Guide

Contents Page

12.0i

Access platforms, Stair s and Ladder s User Guide

User Guide

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Assumpti ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1User Interface Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

How the Guide is Organised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Graph ical Previews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

On Screen Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Storage Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Creating Ins tances of Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2

Stair Tower Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Create Stair Tower Definit ion Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Direction and Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Installation Sense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Select Configuration Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Perform Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3Create Tower Steel Layout Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3

Tower Layout Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5Column SPEC details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5


4/74

12.0ii


Create Stair Land ing Layout Defini tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6Stair Landing Installation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7

Catalogue and Assembly Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7Create Stair Flight Layout Defini tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9Stair Flight Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9Stair Flight General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10Perform Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10

Stair Flight Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

Create Stai r Flight Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2

Installation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2Position and Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2Modify Leg Going. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4Perform Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6

Ladder Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1

Create Ladder For m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Position and Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Installation and Assembly Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Evaluate Ladder Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3Create Ladder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3Ladder Side Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Pick Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5Delete Selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5Display dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5Back to Modify Ladder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5

Back to Main Ladder Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5Modify Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6

Platform Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

Create Platform Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2Define Platform Geometry Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2Create Platform Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4

Back to Main Platform Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4


5/74

12.0


ii i

Platform Opening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4Create Opening Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5

Define Opening Geometry Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:6Modify/Delete Selected Opening Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7Handrail for Current Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8

Modify Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8Modify Platform Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9Modify Platform Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10Modify Platform Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11Modify Platform Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:12Modify Openings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14

Handrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14Delete Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14

Handrail Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1

Create Handrail Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Rail Spacing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3

Handrail Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:5Copy Path of Owner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:5

Copy Path of Picked Item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:6Insert Corner/Segment Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7Set Current Vertex Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7Move Current Vertex Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7Remove Current Vertex Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7Remove Picked Vertices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8Remove all Vertices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8Extend Start/End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8Shift Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8Gates Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8Create Handrail Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:9

Gates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:9Add Gate Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:9Position Gate Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:10Remove Gate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11

Modify Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11Handrail Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11Handrail Geometry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11

Gates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11


6/74

12.0iv


Split Handrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11Extend Handrail End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12

Split Single Rails(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12Delete Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12Handrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12Gate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12

Handrail Assembly Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1

Regular Handrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1

Panelised Handrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1

Basic Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1

Posts (HRPOST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2

Rails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2

Kick Plates (KICKPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3

Handrail Termination (HRTERM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3

Panels (HRPANE) of Panelised Handrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:4

Panels (HRPANE) of Non-panelised Handrail . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:6


7/74

Access platforms, Stair s and Ladders User GuideIntroduction

12.01:1

1 Introduction

This section 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 whatknowledge they will need before they start. The section provides an overview of the mainfunctionality that the application introduces.

1.1 Intended AudienceUsers who are new to the ASL application should use this guide to understand thefunctionality of the application and the concepts employed by the system in the evaluation of the standards or 'engineering criteria' that the assemblies conform to.

1.2 AssumptionsUsers of the ASL must have read/write access to the project databases.

It is assumed that:

The user has a basic knowledge of PDMS DESIGN. The user is familiar with the basic graphical user interface (GUI) features as described

in Getting Started with PDMS.

1.2.1 User In ter face Workflow

Each task panel has additional information relevant to that specific task the user and theapplication are currently engaged in, the concept being one of 'Progressive disclosure', i.e.not presenting the user with too much information on one form but simply presenting it in amore intuitive way that mirrors the work flow process associated with the creation ormodification of that particular task.

1.3 References This section lists other documents that provide supporting or complementary information tothis guide.

AVEVA Product Minimum System Requirements.

Structural Design User Guide.


8/74

12.01:2

Access platforms, Stair s and Ladders User GuideIntroduction

1.4 How the Guide is Organised This guide is divided into sections, as follows:

Getting Started explains how to get started with the ASL application.

Stair Tower Assembly explains how to create a Stair Tower assembly.

Stair Flight Assembly explains how to create a Stair Flight assembly.

Ladder Assembly explains how to create a Ladder assembly.

Platform Assembly explains how to create a Platform assembly.

Handrail Assembly explains how to create a Handrail assembly.


9/74

Access platforms, Stair s and Ladders User GuideGetting Started

12.02:1

2 Getting Started

This section explains how to get started with the ASL application. It describes theapplication to provide the DESIGN user with the necessary data to create assemblies in the3D model.

2.1 Graphical Previews The application and all of the ASL assemblies provides a generic mechanism that allows theuser to visualise and rationalise the net effect of the layout by modifying various attributes orsizes by generating a graphical preview of the changes prior to the user committing them tothe database.

2.2 On Screen DimensionsA common tool, available on many ASL forms and task panels is the Measure icon:

This allows the fixed value or derived value assigned to the standard to be displayed in thegraphical view and includes the attribute description as indicated on the forms;

The detailed attributes are determined by their defaults, i.e. evaluated by the engineeringcriteria such that the value complies with the conditions or constraints defined against it,these conditions or constraints can include max/min, valid values, PML expressions,optimised values or real values. Each of the corresponding gadgets has tool tips to providefeedback to the user of the numerical range defined by the engineering criteria for thatparticular attribute.

The direction attribute is not defined by the standard; this is a system default which isderived by the application via the positions of the principle work points.

2.3 Storage AreasBefore any assembly geometry can be created a storage area should be assigned. Tomanage the setting of the storage areas, select Settings>ASL Storage Area from themenu toolbar to display the ASL Defau lt Storag e Ar ea form.

This form is used by the user for controlling where the system stores the standards and theinstanced assemblies in the 3D model.


10/74

12.02:2


2.4 Creat ing Instances of Assemblies The functionality of the ASL application provides the means to quickly create, modify andverify the suitability of particular designs or layouts of rule based assemblies for the ASLelements.

The ASL functionality is a sub application of the Structures application. To access ASL,select Design>Structu res>Access, Stairs and Ladders from the main toolbar.


11/74


12.02:3

The specific forms for the creation of the following elements and their members aredisplayed either by selecting them from the Create, Modify or Toolbar options from the maintoolbar.

Stair Tower (STRTWR) Stair Flights (STRFLT) Ladder (LADDER) Platform (PLTFRM) Handrail (HANDRA)


12/74

12.02:4


The modification functionality of the ASL application is accessed from the Modify>ASLelement pull down.

The form shown below is typical of the layout of all the ASL forms. All can be docked andallow the user to Create, Modify or Delete the ASL elements via 'link labels' that guide theuser through the main tasks associated with the purpose of the ASL elements and their subelements.


13/74


12.02:5

The links are context sensitive to the current location in the hierarchy where they becomeactive when situated below a STRU hierarchy; this is the owning element for all the ASLassemblies. When any of the ASL assemblies is the current element the relevant link willhighlight for the appropriate Create, Modify or Delete task.


14/74

12.02:6



15/74

Access platforms, Stair s and Ladders User GuideStair Tower Assembly

12.03:1

3 Stair Tower Assembly

3.1 Create Stair Tower Definition FormFrom the main toolbar, select Create>Stair Tower to display the Create Stair Tower Definition form.


16/74

12.03:2


3.1.1 General Attri butes

The Create Stair Tower Definition form allows the user to set the general attributes, suchas Name, Description, Function and Area. The form also identifies the tasks associated withthe Stair Tower elements.

3.1.2 Di rect ion and Locat ion

The application assumes that the Stair Tower direction is constrained to a rotation about thevertical axis for example N45E, W13S and the application will not allow the user to set a nonvertical direction, in that event the application will issue an error message before resettingthe format back to the default direction.

The Pick Position link will activate the Positioning Control mechanism allowing the user toset the position with respect to any elements in the Design Database.

The positioning control task panel supports both the plant and ship grid (XYZ, ENU andMarine) co-ordinate system where the default position of the Stair Tower is positioning at thebase elevation in the geometrical centre of the Stair Tower as indicated by the axesindicator. The default direction or the Stair Tower is north though this can be changed by theuser.

3.1.3 Installation Sense

The installation sense of the Stair Tower allows the rotation of the Stair Flights and StairLanding to be rotated in either a Clockwise or An ti -Clo ckwise sense. When used inconjunction with Direction it allows the Stair Tower to be manipulated to suit the layoutrequirements for managing the various layouts of Flight direction and Landing orientation.

3.1.4 Select Conf igurat ion Type

This toggle determines whether or not the application creates supporting steel for the Stair Tower.

If the Tower Steel Layout Configur ation radio button is active, the application will create anetwork of beams and columns whose layout and spacing is derived by the layout of theStair Flight and Stair Landing centres and the elevations of the Stair Landings Top of Steel or


17/74


12.03:3

Finished Floor Levels. The sizing of the Column and Beam profiles is set to a defaultspecification reference though the user is free to select any profile type from the catalogue.

If the Stair Landing Configuration radio button is active, the application will not create anysupporting network of beams and columns, this scenario would exist where the Stair Flightspass through a Deck or Floor where the hole through which the Stair Flights pass has beenengineered to accommodate the Stair Tower and Flights.

3.1.5 Perform Task

Select Create Stair Tower Element to commit the changes made on this form to thedatabase and take the user to the Create Tower Steel Layout Definition form.

Selecting Back to Main Task will not commit these changes to the database and will takethe user back to the Main Stair Tower Tasks form.

3.1.6 Create Tower Steel Layout Definition

The Create Tower Steel Layout Definition form is responsible for managing the sizing andpositioning of Stair Landing elevations.


18/74

12.03:4


A graphical representation or preview in the 3D canvas of the Stair Tower reflecting theinformation in the form which can be modified by the user to suit the layout of the adjacentmodel data to which the Stair Tower is being defined.

The graphical preview is based on the engineering criteria defined in the 'ASL standards'and these values will be written to the appropriate attributes of the Stair Tower.

To minimise the degree of post creation modification the Stair Tower functionality provides agraphical preview prior to the creation of the detailed representation of the final design, thisworkflow has been adopted to enable the user to modify the Stair Tower as required bychanging specific dimensions, directions or selections, and can also include the creation of additional entry or exit points as maybe required by adjacent model data or accessrequirements.

The form and the graphical preview indicated above shows how the dimensions from theactual engineering criteria defined by the relevant standard have been used to give arealistic geometric preview of the Stair Tower, the graphical representation indicates;

The Position and orientation of the Stair Tower The overall size (Xlength, Ylength and Height) of the Stair Tower The number off and elevations of the supporting Beams


19/74


12.03:5

The form also demonstrates the concept of 'progressive disclosure' of the information anddata that has been applied by both the user and by the system from the current standard tothe attributes of the Stair Tower. The tasks associated with the creation and modification of

the Stair Tower have been grouped into collapsible 'task' panels to minimise the amount of information visible at any time. The form layout also simplifies the workflow by grouping thetasks by specific actions; the following headings will describe in more detail the function of the task panes.

3.1.7 Tower Layout At tr ibu tes

The overall sizing of the Stair Tower is not controlled by the engineering criteria, theseproperties are user definable and can be edited by the user which are then previewedgraphically on the screen.

3.1.8 Column SPEC detai ls

The Column Profile and Column Justification fields have preset values, these can bechanged to any other profiles reference using the Section Profile Selection form. Selectthe Select SPEC for Column link to display the Section Profile Selection form.


20/74

12.03:6


3.2 Create Stair Landing Layout Definition The Create Stair Landing Layout Definition form is responsible for managing the layout

and detail definition of the Stair Landings.

A graphical preview of the Stair Landings is presented to the user showing the layout of theStair Landing and Handrailing and also indicates:

The Stair Flight and Stair Landing centreline distances The Stair Landing configuration and rotation sense The Stair Landing elevations

The main functions of the tasks shown on this form are described below.


21/74


12.03:7

3.2.1 Stair Landing Instal lat ion Details

Landing Configuration

This option allows the user to visualise the different installation scenarios for Stair Landingsand associated Stair Flights prior to committing the installation to the database. As eachconfiguration is selected the graphical preview is updated to reflect the change.

Landing Attributes

The Stair Landing attributes manage the sizing of the Stair Landing which can be edited andpreviewed graphically. The Stair Landing Thickness is managed by the value defined in thecurrent Standard and is subject to the checking mechanism of the min/max criteria such thatif the user attempts to input a value that exceeds the criteria the system will provideappropriate feedback.

Tower Layout Details The values populated in the Tower Layout Details are values that are managed by thecurrent Standard or they have been derived as a result of the Stair Tower layout such as the

Tower (X and Y) length attributes.

3.2.2 Catalogue and Assembly Details

The user must select the Assembly data for Stair Flights, Stair Landings and Handrails todefine the Stair Tower. This mechanism provides the maximum flexibility in that the user andthe system are not constrained to individual Standards referencing individual Assemblies.

Tie-Up Beam Selection Details

This defines the 'Tie-up' beam that was not part of the previous elevation beam data and iscoincident with the Landing Length supporting the unsupported span of the Stair Landing.


22/74

12.03:8


The default profile is as indicated in the form below though the user can specify a differentprofile and justification.

Stair Landin g Assembly Selection There are a number of different Stair Landing Assemblies in the AVEVA supplied standarddata for ASL, these are located in the following Application Data World (APPLDW) hierarchyand can be selected using the Stair Landing gadget above, provided that is that theAdministrator has added them to the users 'ASL selection'.

Handrail As sembly Selection

The Handrail are also located in the APPLDW and can be selected using the Handrailgadget. This will update the graphical preview with the appropriate graphic.

Perform Task

Select Create Stair Landi ngs to commit the changes made on this form to the databaseand take the user to the Create Stair Flig ht L ayout Definitio n form.

Select Back to Tower Steel Definition to take the user back to the Create Tower SteelDefinition form.



23/74


12.03:9

3.3 Create Stair Flight Layout Definition The Create Stair Fligh t Layout Definiti on form is responsible for managing the layout and

detail definition of the Stair Flights including the hand railing.

3.3.1 Stai r Fl igh t Assembly

This option allows the user to define the particular Stair Flight and Handrail types used in the

detail representation of the Stair Tower.


24/74

12.03:10


3.3.2 Stair Flight General Attr ibutes

The Route Stair Flight to Landings link activates the routing of the Stair Flights along thecentreline distances defined in the previous tasks, the lower and upper work points of theStair Flights are coincident with the Finished Floor Level of the Stair Landing.

Once the Stair Flights have been routed the attributes of each Flight element are populatedin the attribute fields with the evaluated properties, the user can use the Flight Segmentstoggle to switch between the various Flight segments.

3.3.3 Perform Task

Select Create Stair Flight to commit the changes made on this form to the database andtake the user back to the Route Stair Flight to L andings form.

Select Back t o Tower Steel Definit ion to take the user back to the Create Stair LandingDefinition form.



25/74

Access platforms, Stair s and Ladders User GuideStair Flight Assembly

12.04:1

4 Stair Flight Assembly

4.1 Create Stai r Fl ight FormFrom the main toolbar, select Create > Stair Flig ht to display the Create Stair flight form.


26/74

12.04:2



The Create Stair Flight form allows the user to set the general attributes, such as Name,Description, Function, Purpose and Area. The form also identifies the tasks associated withthe Stair Flight elements.

4.1.2 Instal lat ion Opt ions

The four installation types, Straight , L-Shaped, S-Shaped and U-Shaped address themajority of the installation scenarios for Stair Flights. If an installation option has not beenset and the user has defined the Lower and Upper work points, the application will promptthe user to select an installation option against which the evaluation will be based.

The Left/Right Option becomes active if either the L-Shaped or U-Shaped installation optionis selected. On selecting the Left Option the subsequent Flight turns left from the Previousone.

4.1.3 Pos it ion and Di rect ion

The Position and Direction task panel provides both graphically interactive and explicitmethods for positioning the lower and upper work points that define the Stair Flight, asshown in the diagram above the origin of the Stair Flight is coincident with the intersection of the Lower WP and the plane of the lower pick at the midpoint between the Stringers.

Selecting either the Lower or Upper Position link will activate the Positioning Controlmechanism for graphical selection of the work points and population of the position gadgetsin the form.

Explicit positioning either via the Upper or Lower WP is supported and the system will checkthe results of the new position against the engineering criteria of the Stair Flight to thecriteria of the current specification and if valid the Stair Flight will be re-positioned. The

default Flight Direction or the Stair Tower is north though once the Stair Flight has beencreated it is set by the application based on the positions of the lower and upper workpoints. Having input the Upper Work Point position using either the explicit of graphicalmethod and the position gadget has been populated the Lower Work Point Position gadgetbecomes active.


27/74


12.04:3

Selecting the Plane toggle changes the options displayed to the user for selecting the LowerWorking Point. The user can now specify a plane and direction onto which the Upper WorkPoint will be projected.

The selected position value is used to position either the landing or the landing stringer TOS, based on the selection made in FFL/TOS. Landing is either Flushed or placed above

the Landing Stringer based on the selection made in Flush with Landing / Above Landing. The same applies for the Upper Work Point as well. Both these landings and theintermediate landings if any will be of thickness provided in the Landing thickness.

The U-Flight Offset is the distance till which the U-Type Stair Flight extends along theNormal direction between the picked points. If the user does not click Pick position for thedistance or enters a value then the Offset value is derived using optimum values.

4.1.4 Modify Leg Going

The Stair flight Leg Going form is displayed when the Lower Extension , Upper Extension , Lower Landing Length or Upper Landing Length linklabels in Stair FlightDetail Attrib utes form are clicked.


28/74

12.04:4


To update the change the calculated Length after modification should be the same as theActual Length along that direction at before modification.

4.1.5 Assemblies The Assemblies task panel identifies the Stair Flight assembly data being used to create theinstances in the design model. The current standard to which the Stair Flight assembly isbeing evaluated against is indicated in the main menu bar.

Select Stair Flight Detail Attributes to display the Stair Flight Detail Attributes form,which stores both the criteria from the standard such as Width and Headroom for example,and the evaluated criteria based on the positions of the work points. These attributes appeargreyed out and therefore are not modifiable as they have been evaluated and validated bythe system and subsequent manual overrides could easily invalidate the assembly.


29/74


12.04:5

In the example shown above the Stair Flight actually consists of two flight segments as thesystem has determined that one flight does not meet the satisfactory validation of the criteriaand therefore required two flight segments with the insertion of an Intermediate Landing .

The Intermediate Landing by default is positioned at the midpoint between the lower andupper work points, the user can toggle between the two Flight segments which will refreshthe attribute gadgets below.

The Upper Elevation gadget stores the elevation of the Intermediate Landing element, thisis a transition element between the Flight Segments, the requirement for an IntermediateLanding and is determined by the system evaluation of the criteria. The Pick option to theright of this gadget allows the user to modify the position of the Intermediate landing andsubject to the validity of the criteria the Stair Flight and the Flight Segments will be modifiedto suit. The new elevation can be manually input or graphically selected using the positioncontrol object.


30/74

12.04:6


4.1.6 Perform Task

Evaluate Stair Fligh t

Select Evaluate Stair Flight to check the validity of the Stair Flight against the criteriadefined in the current Standard, if the Stair Flight assembly is valid the system will display agraphical representation of the Stair Flight showing both the lower and upper work pointsand the number of Flight segments associated with the Stair Flight.

The system provides additional checking and will not allow the lower and upper work pointsto be on the same elevation, where there are positional irregularities the system will provideappropriate feedback before performing a check against the criteria.

Create Stair Flight

When the user is satisfied with the layout of the Stair Flight and the system has validated thecriteria, the Stair Flight can be created and the detail representation of the Stair Flight andHandrail will be that previously defined in the Assemblies task.


31/74


12.04:7

Back to Stair Flig ht Tasks

Selecting Back to Stair Flight Tasks will not commit these changes to the database andwill take the user back to the Main Stair Tower Tasks form.


32/74

12.04:8



33/74

Access platforms, Stair s and Ladders User GuideLadder Assembly

12.05:1

5 Ladder Assembly

5.1 Create Ladder FormFrom the main toolbar, select Create>Ladder to display the Create Ladder form.

The system behaviour for the evaluation starts when the user defines the lower and upperwork points using either the explicit or graphical positioning mechanism, the system thendetermines the vertical distance (Overall Rise) between these two graphical positions andchecks and validates the results against the engineering criteria of the Ladder to the criteriaof the current Standard. If the system analysis validates the values against the engineeringcriteria the system will create the Ladder and populate the attributes with the appropriatedata.


34/74

12.05:2



The Create Ladder form allows the user to set the general attributes, such as Name,Function, Area and Number. The form also identifies the tasks associated with the creationof the Ladder.

5.1.2 Pos it ion and Di rect ion

The position and origin of the Ladder is located at the bottom of the ladder midway betweenthe Ladder Rungs and has pseudo attributes defining the position of the lower and upperwork points.

Position

The Lower Work Points and Upper Work Points links will activate the Positioning Controlmechanism allowing the user to set the position with respect to any elements in the Design

Db and the positioning control task panel supports both the plant and ship grid (XYZ, ENUand Marine) co-ordinate system. The Plane option also provides the ability to identify aplane onto which the Upper work Point will be projected which is determined by the pitch of the Ladder. The default direction or the Ladder is north though this can be changed by theuser.

Direction

The default direction of the Ladder is set to North though this can be modified by the user torotate the Ladder around its vertical axis.

5.1.3 Instal lat ion and Assembly Options

The Installation options for the Ladder are defined by the exit location at the top of theLadder, the exit direction has a direct influence on the design and layout of the cage (whereone has been deemed necessary by the evaluation of the Ladders height). The applicationand the Assembly data allow for four kinds of exit direction; Front, Back, Left and Right. Theconvention of Left and Right is where the user is standing at the base of the Ladder, facing itas if to climb the ladder.

Depending on the type of exit type selected this will adjust by extending or reducing thelength of the Ladder Stringers and the number of Ladder Rungs to suit.


35/74


12.05:3

5.1.4 Evaluate Ladder L ink

Once the Lower and Upper Work Points have been defined the Evaluate Ladder willpreview the graphical representation of the Ladder so the user can visualise the layout of the Ladder and can view the resultant 'Detailed Attributes' below.

Detailed Attri butes

These attribute values represent the engineering criteria defined in the standard and areevaluated based on an upper and lower or max/min allowable values defined by theAdministrator. Once the Ladder definition has been evaluated and validated by the systemthe attributes for the Ladder are populated in the detailed attributes form shown below.

5.1.5 Create Ladder Selecting the Create Ladder link commits the creation of the Ladder to the database uponwhich the form will change to include a link to create side exits.


36/74

12.05:4


5.1.6 Ladder Si de Exi ts The four links on the side exits form below provide the functionality to create, modify, deleteand graphically highlight the Ladder Exit graphic on the Ladder, additional descriptions aregiven below:

5.1.7 Create

Three of the four link options are by default greyed out and only when a Ladder Exitelement has been created will the Pick position , Delete selected and Displaydimensions be highlighted. Once Create has been selected the system will create a newLadder Exit field in the forms grid object, the elevation of which will be set to 0 until the user


37/74


12.05:5

uses the Pick position to graphically pick a position or edits the elevation directly in theforms grid object.

If the user edits the explicit position within the form grid object the Pick position and Deleteselected will become un-highlighted.

5.1.8 Pick Position

Pick position allows the user to enter the graphical selection mode and using the positioningcontrol and graphically pick an elevation defining the Upping component or elevation of theLadder Exit.

The system will re-evaluate the design based on the changes and if the changes conform tothe engineering criteria defined in the standard the system will commit the changes to theLadder Exit, Cage Segment and Ladder and will create an Entry/Exit location in the Ladderwith a clearance Headroom of 2200mm as defined in the engineering criteria.

5.1.9 Delet e Sel ected

This allows the user to delete the selected Ladder Exit, upon deleting the Ladder Exit fromthe Ladder the system will re-evaluate the standard or engineering criteria and update thegraphical view.

5.1.10 Display dimensions

The Display dimensions option simply toggles on/off the display text for Side exit, Headroomand distance to the previous Cage Segment.

5.1.11 Back to Modify Ladder The Back to Modify Ladder link takes the user back to the main Create Ladder formexcept that the form title has changed to Modify Ladder and contains the same informationfor the modification of the installation scenarios, position, direction and other attributes.

5.1.12 Back to Main Ladder Tasks

The Back to Main Ladder Tasks link takes the user back to the Main Ladder Tasks form,allowing the user to access all of the Create, Modify and Delete functionality.


38/74

12.05:6


5.1.13 Modify Specifications

The Modify Specifications form allows the user to modify the specification reference of theprofiles used in the definition of the Ladder Stringer, Cage profile and Rungs profile.


39/74


12.05:7


40/74

12.05:8



41/74

Access platforms, Stair s and Ladders User GuidePlatform Assembly

12.06:1

6 Platform Assembly

6.1 Create Platform Form The Platform functionality of the ASL application provides the means to quickly create andassess the suitability of particular designs or layouts of Platform assemblies and will be auseful design tool in the initial laying out and detail design phases of a project.From the main toolbar, select Create>Platform to display the Create Platform form.


42/74

12.06:2



The Create Platform form allows the user to set the general attributes, such as Name,Description and Thickness. The form also identifies the tasks associated with the Platformelements.

6.1.2 Position

The Cursor link prompts the user to Pick platform position from the graphical preview, theresultant position is the origin of the platform. The position toggle FFL (Finished Floor Level)and TOS (Top of Steel) manages the elevation of the platform and positions the top of thePlatform Grid at the FFL elevation and the top of the steel profile of the External Frame.

6.1.3 Define Platform Geometry Link

The user defines the geometry of the platform by selecting the Define Platform g eometrylink to display the Define Platform Boun dary form.


43/74


12.06:3

From the Shapes option gadget the user can define geometry conforming to a basic shapetemplate with user input or graphically populated sizes, the shape templates include;

Rectangle L Shape Circle Free Form Polygon

Each of the shape templates can be toggled using the 'Origin:' toggle, this will move theshape template graphically from corner to corner, depending on the shape selected, andfrom the graphical previews the user can select the appropriate origin of the Platform.

Where no geometry currently exists this is reflected in the form.

Where a P latform shape is asymmetric the form provides the capability to mirror thegeometry in either the 'X' or 'Y' directions.

When the information is complete the Platform has not yet been created in the database asthe information has been stored in the platform object, selecting the Define PlatformBoundary link will take the user back to the Create Platform form to pick and confirm thecreate platform link. This creates the Platform element in the database and writes theinformation contained in the form to the Platform attributes. The Create Platform form willupdate to inform the user that the platform geometry has been defined and displays theoverall X/Y size of the platform


44/74

12.06:4


6.1.4 Create Platform Link

Selecting the Create Platform link will create the Platform element in the Database andpopulate the attributes of the Platform element with the information defined in the formsabove.

6.1.5 Back to Main Platform Tasks

Selecting Back to main Platform tasks will not commit these changes to the database andwill take the user back to the Main Platform Tasks form.

6.2 Platform Opening The number of Platform Opening elements is managed by the Platform Opening formindicated below, where the number of Platform Openings is displayed in the grid object of the form. The Platform Openings form provides the necessary functionality to create, modifyand delete the Platform Opening elements.


45/74


12.06:5

6.2.1 Create Open ing L ink

A new Platform Opening is created by selecting the Create Opening link. The systemcreates a Platform Feature and the first Platform Opening element in the database, thedefault position or origin of the Platform Opening is coincident with the position/origin of thePlatform. The user can then adjust the position of the Platform Opening using the formshown below, the position is managed as an XY offset from the origin of the Platform.


46/74

12.06:6


6.2.2 Define Opening Geometry Link

After setting the position of the Platform Opening the user then defines the shape of theopening within the Platform, this is consistent with the functionality for defining the shape of the Platform in that is utilises the Routing Path element.

The Shape definition can be defined using the shape selection templates or by free forminteractive sketching using the Pick corner points link, any changes made refresh thegraphical preview of the shape, size and position of the Platform Opening. Where thegraphical preview refreshed with each change made in the form but is not committed to thedatabase until the Define Platform Opening Bou ndary link is picked.

Picking the Define Platform Opening Boun dary link returns the user to the previous statusof the Create Openin g form for the user to commit the changes to the database. It is only atthis stage that the physical changes are committed to the Platform object and the graphicsare updated.


47/74


12.06:7

6.2.3 Modify/Delete Selected Opening Link

The number of Platform Opening elements per Platform is displayed in the PlatformOpenings form indicated below and when highlighted in the form grid object using the rightmouse button or the arrow head icon adjacent to the entry, the graphical representation isupdated with an on screen marker so the user can distinguish the relevant Platform Openingbeing modified or deleted.

The Modification options allow the user to change both the position and size of the PlatformOpening using the forms and functionality described above.

The Delete Selected Opening link deletes the instance of the Platform Opening from the

database and the system updates the graphical representation of the Platform.


48/74

12.06:8


6.2.4 Handrai l for Current Platform

Upon completion of the Platform layout the functionality provides the ability to trace theboundary of the Platform with Handrail, please refer to the next section; Handrail assemblywhich describes in more detail the functionality provided by the Handrail application.

6.3 Modify Tasks The Modify Tasks present the same workflow concepts and form design layouts aspreviously described in the Create tasks. The only difference in the form appearance is the

Ap pl y Ch ang es to accept the modifications made and 'Discard Changes' link to cancel the

changes and maintain the original state.


49/74


12.06:9

6.3.1 Modify Platform Def init ion

Picking the Platform Definitio n link allows the user to modify data such as Name, Function,Direction, Thickness and Position.


50/74

12.06:10


6.3.2 Modify Platform Geometry

Having created the platform boundary this form provides the user with the ability to insert,move or delete POINTRE elements that define the boundary of the Platform.

This is identical to the functionality provided by the Handrail application, please refer to therelevant section for further information.


51/74


12.06:11

6.3.3 Modi fy Platform Layout

The main detail of the Platform is defined by the spacing and directions managed by theInternal/External Frame and Plate Layout form. This form allows the user to modify theseattributes and to visualise the changes with the graphical aids prior to accepting thechanges and committing them to the database.


52/74

12.06:12


6.3.4 Modify Platform Detai l

The steel profile Specification References for the Primary and Intermediate spans aremanually modifiable to any profile specification in the profile catalogue via a selectionmechanism on the Primary Span Profile , Intermediate Span Profile and Profile links,allowing the user to select directly from the steel profile catalogue.


53/74


12.06:13

Plate Detail

The Plate Detail tasks allows the user to set the plate (grating) thickness and to visualise viathe graphical aids the representation and layout of the plate size (this can be modified in theModify > Layout task panel.

Internal Frame Detail

The Internal Frame Detail tasks allow the user to define and set the profile specification andthe justification for the primary and intermediate spans and to preview the span spacing anddirections. The default aid colour graphic for the Primary direction is turquoise and theintermediate span is represented by the red graphical aids and to distinguish between the

two directions the aids can be toggles on or off using the Draw option.


54/74

12.06:14


External Frame Detail

The External Frame Detail tasks allow the user to define and set the profile specification andthe justification for the GENSEC that defines the boundary frame for the Platform, thedefault aid colour graphic for the External Frame is Orange.

6.3.5 Modify Openings

Refer to Platform Opening for a description of the modification of P latform Openings.

6.3.6 Handrail

For more detail about the functionality provided by the Handrail application, refer to Handrail Assembly .

6.4 Delete Tasks6.4.1 Platform

Delete Platform link will highlight the current Platform element in Red in the graphical viewand prompt the user with a Confirm message 'Do you really want to delete the currentplatform?' where a 'Yes' prompt will delete the instance of the Platform from the database.


55/74

Access platforms, Stair s and Ladders User GuideHandrail Assembly

12.07:1

7 Handrail Assembly

7.1 Create Handrail Form The Handrail functionality of the ASL application provides the means to create and assessthe suitability of particular designs or layouts of Handrail assemblies and is a useful designtool in the initial laying out and detail design phases of a project.From the main toolbar, select Create>Handrail to display the Create Handrai l form.


56/74

12.07:2


The Create Handrail form takes the user straight into the boundary definition taskassociated with tracing the path of the Handrail, for the purposes of documentation selectthe Back to main Handrail tasks to present the Main Handrail Tasks form.


57/74


12.07:3

The Create Handrail form allows the user to decide which data to use, either the Defaultrepresentation which is a core based representation requiring no detail geometry or anaccurate detail representation which is held in the ASL Application Data World. Theadvantage of the Default representation is that there is no delay in defining a conceptuallayout for Handrailing as there is no catalogue or Assembly data requirements.

The Post data describes the layout and spacing of the Handrail Post elements, this data ispart of the standard or engineering criteria that is evaluated when Handrail assemblies arecreated or modified. The system will not allow these values to fall outside the range of themax/min of the values stored in the standard for that attribute; attempts to change thesevalues beyond the criteria will prompt the system to return an error message reminding the

user of the allowable ranges. The Rail data settings allow the user to modify the number of Rails and their spacing usingthe Spacings grid, this only applies to the default representation as the Detailrepresentation is determined by the ASL standard. See more detailed descriptions below

All the graphical feedback is presented on screen using graphical aids so the user canlayout the information and have a real time preview of the resultant geometry prior tocommitting the changes to the database. The user can also be certain that the engineeringcriteria of the graphical preview have been validated by the system.

7.1.1 Rail Spacing

The option to Add, Remove or Modify the elevations of the existing Rails only becomesactive when the Template option at the top of the form is set to Default, the Default


58/74

12.07:4


representation can be used during the conceptual stages of the project before thefabrication details for the Handrailing is known, or simply for visualisation purposes. If thedefault representation is used the user can at any time change the representation back to

the Detail representation as per the Default, project or User standards defined in theApplication Data World.

The appropriate spacings for Rails rail should be highlighted in the grid object and the 'Use',option saves this as the current rail spacing selection, the spacing attribute or dimensionsshown in the form grid object is referenced from the zero datum.

The Default representation of Handrail is still evaluated against the Standard or engineeringcriteria defined in the Standard and any user modifications are automatically validated bythe rule checking engine and appropriate feedback is returned to the user. Inputting datathat exceeds the criteria will result in an error message.


59/74


12.07:5

7.2 Handrail Geometry The Handrail Geometry form provides the functionality for creating the boundary in a

variety of ways including free form graphical sketching or by tracing existing boundaryelements.

7.2.1 Copy Path of Owner

For a faster and more efficient means of defining a Handrail certain boundary elementsdefined using a Routing Path have their boundaries copied directly by the system to definean open or closed boundary of the Handrail. The Copy Path of Owner link will present a


60/74

12.07:6


graphical preview of the Handrail, this might be used when tracing the boundary of theowning Platform, the preview will number the vertexes and the system will prompt the userto graphically select a vertex to define the start and end. This provides a quick means to

exclude certain facets of the Handrail as indicated below; alternatively the Closed option willclose the boundary.

The system prompt requesting the user to define the Start/End positions of Vertex 1 for theStart and Vertex 6 for the End will define the following path shown on the left; the Closeoption is shown on the right.

Once the graphical preview has been displayed the link for modifying the Handrail geometrybecome active, these provide the user with the functionality to highlight the individualvertex's and perform the specific actions.

7.2.2 Copy Path of Picked It em

Similar in concept to the Copy Path of Owner , this allows the user to trace the path of apicked item, typically this might be a Panel element.


61/74


12.07:7

7.2.3 Inser t Corner /Segment Link

The Insert Corner/Segment functionality provides the user with the ability to free form sketchthe path or boundary (using the close option) of the Handrail using the graphics of the 3Dview. The system prompts the user in the status bar to graphically pick vertexes or edgesalong which the route will updates with each new selection. If the 'Closed' toggle is checkedthe system will display the graphics in terms of a boundary definition, unchecked displays apath definition. The 'escape' key will exit from the free form sketching functionality and thesystem will activate the modification options if any further editing of the path or boundary isrequired.

To save the route definition to the database, select the Ac cept Changes link followed by theBack t o Create Handrail link to Create Handrail.

7.2.4 Set Current Ver tex Link

Where the user wishes to select a vertex to modify selecting the Set Current Vertex link willgraphically highlight the numbers and position of all the vertexes and the system will promptthe user in the Status bar to Pick VERTEX to be made current: When the user identifies thenew vertex the system will update the graphical preview to show the 'Current Vertex'. Theuser can now perform any of the modify operations.

7.2.5 Move Current Ver tex Link

Selecting this link will graphically highlight the position on the Handrail of the current vertexand the system will prompt the user in the Status bar to P ick position the vertex to be moved

to: When the user identifies the new position the system will update the graphical preview of the handrail for the user to accept or discard the changes.

7.2.6 Remove Current Ver tex Link

Picking this link will remove the current vertex and graphically highlight the new path of theHandrail which will draw the new path which start and ends at the vertex position before andafter the vertex that has been removed. The system then updates the graphical preview of the handrail for the user to accept or discard the changes.


62/74

12.07:8


7.2.7 Remove Picked Ver tices

The Remove Picked Vertices link once selected, displays a prompt to Pick start VERTEXof sequence to be deleted : and once the vertices to be deleted have been selected thesystem presents a confirmation message to the user for them to confirm the option of deletion. Where the conformation is accepted and the Ac cep t Chang es ' has been selectedthe system will remove the graphical preview of the handrail and commit any changes to thedatabase.

7.2.8 Remove al l Ver ti ces

The Remove all Vertices link will highlight all the vertices in the handrail definition andpresent a confirmation message OK to remove all handrail verti ces , accepting this optionand Ac cept Ch anges will delete the Handrail from the database.

7.2.9 Ext end Start /End

This link will highlight the vertices at the start and end of the Handrail with a Start and Endon screen graphic and prompt the user to Pick handrail end to be extended and onceidentified will prompt the user to identify a new position for the vertex

7.2.10 Shi ft Offset

This link is an 'In/Out' button that repositions the Kick Plate (where one has been used in theHandrail definition) to the Inside or Outside of the Handrail Post. The layout of the Handrailwill then be updated to suit.

7.2.11 Gates L ink

The functionality to create Handrail Gates can be displayed from this location on the CreateHandrail form as indicated in the image above or from the Main Handrail Tasks form alsoindicated above. Either call for this functionality will call the same form as indicated anddescribed below.


63/74


12.07:9

7.2.12 Create Handrail Link

This will commit any new additions to the database made by the user and previewedgraphically by the system, these additions are stored in the appropriate object forsubsequent use, and picking the Create Handrail link will commit these changes to thedatabase. This is slightly different to modifications subsequently made where the formdisplays the Ac cept/Discard Changes link, this is the only difference between theappearances of the Create and Modify forms.

7.3 Gates

7.3.1 Add Gate Link

Adding an access opening to a Handrail element using the functionality in the form belowwill create the Handrail offspring of Handrail Feature for the ownership and management of Handrail Gate elements of which there can be multiple Handrail Gate elements per HandrailFeature.

Populating the form grid object with the Handrail Gate data is done using the Ad d Gate link,once picked the system will prompt the user to 'Pick position to insert GATE:' as indicatedbelow. A graphical indication on the Handrail element will derive a position along theHandrail path and a graphical preview of the position and size will be displayed along with anumerical identifier corresponding to the number of Handrail Gate's in the Platform Feature.

The X/Y position of the Handrail Gate is derived by the system from the path of the RoutingPath element, the Handrail Gate origin is at the centre of the opening and coincident withthe Platform elevation.

The data for 'Width' in the form grid object is the default size for the 'Width' attribute and can

be modified directly in the form grid by highlighting and editing in place.Accepting the changes will commit the changes to the database and the system will updatethe graphics after first resolving the post spacing due to the addition of the Handrail Gateopening.


64/74

12.07:10


7.3.2 Posit ion Gate Li nk

The position of the Handrail Gate can be modified interactively with graphical picks. Pickingthe Position Gate link will generate a system prompt to the user to 'Pick position of GATE tobe moved to:'. The graphical pick will present a graphical preview of the new position andaccepting the changes will commit the changes to the database and the system will updatethe graphics and resolve the post spacing due to the modification of the Handrail Gate.

To exit from the position gate prompt without graphically highlighting a new position can beinterrupted by pressing the Escape key.


65/74


12.07:11

7.3.3 Remove Gate

In order to remove the instance of an Handrail Gate from the database the field in the formgrid object should be highlighted with the right mouse button, picking the Remove Gate linkwill then preview the new layout of the Handrail without the Handrail Gate. Accept Changeswill commit the changes to the database and the system will update the graphics andresolve the post spacing due to the deletion of the Handrail Gate.

7.4 Modify Tasks

7.4.1 Handr ai l Def inition

Please refer to the Create Handrail description of the functionality for more information,notice the only difference is in the Accep t/Discard ch anges .

7.4.2 Handr ail Geometr y

Refer to Handrail Geometry .

7.4.3 Gates

Refer to Gates .

7.4.4 Split Handrail

Selecting Split Handrail prompts the user to Pick element to s plit Handrail: . Where thereis an intersection of the element being split on and the Handrail the system will present a


66/74

12.07:12


confirmation message OK to split Handrail , accepting this will result in the Handrail beingsplit into two separate Handrail elements.

The user can additionally set a Clearance on Split , this is defined in the Handrail criteriaand the default setting is 100mm.

The system will update the Handrails in line with the criteria for Post spacing and adjust tosuit, where the Handrailing has Handrail Gate elements the positions of these will bemanaged and maintained by the system.

7.4.5 Extend Handrai l End

Refer to the Extend Start/End .

7.4.6 Sp li t Single Rai ls (s)

Where splits to individual Rails are required the user can identify elements where theyintersect with the Rail, selecting the Split Singl e Rail(s) link from the Main Handrail Tasksform prompts the user to Pick element to sp lit sin gle rails(s) of Handrail: . Once selectedthe system presents a user confirmation for OK to split Rail(s)? and the Rail(s) are splitwith the Clearance on Split as defined in the criteria.

In the case of splitting individual Rails the owning Handrail element is maintained as theowner and no modification to the hierarchy are made as is the case with splitting handrails.

7.5 Delete Tasks

7.5.1 Handrail

To delete a Handrail navigate to a Handrail and pick the Delete Handrail link, the systemwill highlight the Handrail in red and present a user confirmation form to accept or decline.Accepting the request will instruct the system to delete the database instance of theHandrail.

7.5.2 Gate

Picking this link will highlight Handrail Gate elements owned by the Handrail and the systemwill prompt the user to graphically identify the Handrail Gates to delete. The system will thenprompt the user to confirm the deletion of the Handrail Gate and then resolves the Handraildetail.


67/74

Access platforms, Stair s and Ladders User GuideHandrail Assembly Rules

12.08:1

8 Handrail Assembly Rules

The handrail assembly template exists as HANDRA item below APPLDATA hierarchy. Twobasic types are recognised by the application, regular (non-panelised) and panelised.

8.1 Regular HandrailIf the assembly contains post (HRPOST) elements and any number of RAILs, it is treated bythe application as a regular "non-panelised" handrail. Optionally it can contain kick plates(KICKPL) or in-fill panels (HRPANE).

8.2 Panelised HandrailIf the assembly contains panels (HRPANE) and does not contain any post or rail then it isrecognised as "panelised". Optionally it can contain kick plates.

8.3 Basic Principles The assembly (HANDRA) is not copied to design instance as a whole, each handrailmember (HRPOST, RAIL, KICKPL, HRTERM, HRPANE) is created as a copy of the itemfrom the assembly. The reference from the design instance of handrail to the assemblytemplate is established via attribute ASSTMP. Each handrail member has the samereference to the item it has been copied from.

All members can have XOFFset value set. If the value is positive it is assumed that theoffset will be made away from the imaginary shape formed by handrail boundary/path (e.g.edge mounted post).


68/74

12.08:2


If the value is negative then the offset is made inside (e.g. floor mounted post). If theimaginary shape is anti-clockwise the offset value is shifted (multiplied by -1) by theapplication in order to keep the actual offset.

8.4 Posts (HRPOST) The first HRPOST below the handrail assembly is used as a template for all posts within the

design instance of handrail, the others, if any are ignored. The post is placed along the RPATH by setting the ZDIStance and position reference toPOINTR where the zdistance is measured from. So the HRPOST should be constructedsymmetrically along its Z-axis and the lower end of post should be at its origin. If the offset isneeded then ZOFFset or XOFFset of HRPOST can be specified. The application does notmodify the offsprings of HRPOST directly, it only sets principle attributes of HRP OST andthen evaluates the attribute rules.

The attributes of HRPOST that are set by the application:

POSREF

ZDIS

XOFF (only the sign can be changed while the absolute value is kept).All other attributes keep their initial value as specified in the assembly.

8.5 Rails There can be any number of rails within the template assembly and all of them will becopied to design instance. Each rail is defined by a start and end position reference toPOINTR within RPATH and its elevation (ZOFF) measured from associated segment of RPATH.

The RAIL element has no members, its physical shape is defined by specification reference(SPREF) to catalogue profile. The offset of RAIL is handled by the same way as HRPOST.

Positive offset (edge mounted post) Negative offset (floor mounted post)


69/74


12.08:3

The attributes of RAIL that are set by the application:

STAREF

ENDREFXOFF (conditionally shifted only)

All other attributes keep their initial value.

8.6 Kick Plates (KICKPL)Definition of kick plate is similar to rails. The first KICKPL within the assembly is relevantand will be copied to all design instances of kick plate below handrail. The KICKP L will bemade only on horizontally running segments of handrail. The same principles are applied tooffset. J ustification of KICKPL should be set to p-line that is in the middle of bottom side of the profile (e.g. BOS). The offset justification (e.g. LBOS or RBOS) will not be shifted by theapplication.

The attributes of KICKPL that are set by the application:

STAREF

ENDREF

XOFF (conditionally shifted only)

All other attributes keep their initial value

8.7 Handrail Termination (HRTERM)

Basic definition HRTERM is similar to HRPOST in some aspects. It has reference toPOINTR (POSREF) and ZDIStance. The HRTERM can be placed to the end and/or start of the handrail that is not closed. The HRTERM on handrail start has POSREF set to firstPOINTR of handrail RPATH while ZDIS is set to zero. HRTERM on handrail end hasPOSREF set to POINTR next to the last and ZDIS is set to length of last segment so that itsposition is the same as position of last POINTR of RPATH. The application does not alterthe offsprings of HRTERM directly, it only sets principle attributes of HRTERM andevaluates rules.

The origin of HRTERM should be as depicted below. To enable skewed HRTERM (e.g.termination of handrail along stairs) the application computes and set the value of attributeANGLE that should be deployed within attribute rule definitions of HRTERM members.Similarly the BANGLE attribute (rotation about Z-axis) should be used to enable rotation of HRTERM as it does not have attribute ORI. All its members should have the rule forattribute ORI reflecting the current value of BANGLE. The application automatically sets itsvalue to 180 degrees when HRTERM is placed at the start, otherwise it is set to zero.

The array attribute RAILTRIM is used by application to trim the matching adjacent RAILScounted from below. If the attribute is not set then no RAIL will be trimmed.


70/74

12.08:4


The offset is handled by usual way.

The attributes of HRTERM that are set by the application:

POSREF

ZDIS

ANGLE (sloping angle - zero if adjacent segment is running horizontally)

BANGLE (to flip HRTERM at start)

XOFF (conditionally shifted)

All other attributes keep their original value.

8.8 Panels (HRPANE) of Panelised HandrailHRPANE is positioned along RPATH using position reference to POINTR and ZDIStancemeasured from that POINTR.

The length of HRPANE is expected to be defined using value of attribute PANESIZE[1]along Y axis of local coordinate system (as depicted below). The value of PANESIZE[1] willbe set by application for every instance o panel. The height definition using PANESIZE[2] isnot obligatory but it is recommended. The value of PANESIZE[2] is not altered by theapplication.


71/74


12.08:5

The skewing of HRPANE should be enabled using attribute RISE (see below) which is setby application.

Note: The length calculated by the application is always the actual length of HRPANE, notthe length projected onto horizontal plane.

When HRPANE is placed at curved segment edge, its local Y axis is aligned tangentially tothe curve by default. The application calculates and sets the attribute BANGLE so that the

other end of HRPANE matches the curved segment. As it does not have attribute ORI itcannot be rotated explicitly so all members of HRPANE (e.g. GENSECs) should have rulefor attribute ORI to enable the rotation.


72/74

12.08:6


It is expected by the application that HRPANE has defined its minimum/maximum length aswell as the default value. It should be held within DDSE element (below HRPANE) as DDATelement. The following attributes have to be set:

PURP DFLT

DKEY LENG

PTYP DIST

DDDF

MAXMIN[1]

MAXMIN[2]

There can be any number of HRPANE below single assembly with different max/mindefinition assuming the lengths are connected. The application will then select the bestfitting panel for every instance.

The max/min definition is not copied to design instance and it is always extracted from theassembly via ASSTMP reference attribute.

If no max/min length definition is found below HRPANE then it is treated as fixed length andthe length is taken from value of PANESIZE[1] of assembly. If the value is not set theHRPANE is ignored by the application.

8.9 Panels (HRPANE) of Non-panelised HandrailHRPANEls can be used to fill the gap between posts and rails. They are placed to straightsegments only. The same principles are applied as mentioned above. In this case theconcept of max/min definition is not used; the application will calculate and set the value asdistance between two posts. The number of such panels within assembly shouldcorrespond to number of rails. Also the value of their ZOFFset and height (PANESIZE[2])should correspond to ZOFFset of rails.

List of attributes of HRPANE that are set by the application:

POSREF

ZDIS

PANESIZE[1] (length of panel)

RISE

BANGLE (for panelised handrails only)


73/74

Index

12.0Index page i

Access platforms, Stair s and Ladders User Guide

A

ASL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1default storage area . . . . . . . . . . . . . 2:1

Assemblies . . . . . . . . . . . . . . . . . . . . . . . 4:4Assumptions . . . . . . . . . . . . . . . . . . . . . . 1:1

C

Access platforms Stairs and Ladders User Guide.pdf

Documents