Professional Documents
Culture Documents
Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions 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 or entity 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 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 AVEVA Solutions Ltd or its subsidiaries. All other rights are reserved to AVEVA Solutions Ltd 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 Ltd. Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice 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 Ltd. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product 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 by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective licence agreements, and in accordance with the relevant User 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 its subsidiaries, 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 or logo belongs to its respective owner.
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
General Routing Path (RPATH). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5 General Route Path Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5
12.0
Creating Standards (Engineering Criteria) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Secondary Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating ASL Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating ASL Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
12.0
iii
12.0
iv
12.0
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
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 Minimum System Requirements.
1:1
12.0
1.4
1:2
12.0
Access platforms, Stairs and Ladders Administrator Guide Overview of ASL Functionality
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.
2:1
12.0
Access platforms, Stairs and Ladders Administrator Guide Overview of ASL Functionality
2.1
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 users interaction with the 3D model environment and the relevant attributes are managed through the database hierarchy by the ASL application.
2.2
2:2
12.0
Access platforms, Stairs and Ladders Administrator Guide Overview of ASL Functionality
2.3
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
2:3
12.0
Access platforms, 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
2.4.2
2.4.3
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.
2:4
12.0
Access platforms, Stairs and Ladders Administrator Guide Overview of ASL Functionality
2.5
2.6
2:5
12.0
Access platforms, Stairs and Ladders Administrator Guide Overview of ASL Functionality
2:6
12.0
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
3.1.1
Administrator Tasks
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 MDBs where the administrator will be creating and modifying standards and the user will be creating ASL assemblies
3:1
12.0
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
3:2
12.0
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
3:3
12.0
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, SemiPublic 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).
3:4
12.0
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
3:5
12.0
3.1.8
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.
3:6
12.0
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.
3:7
12.0
3:8
12.0
Access platforms, Stairs and Ladders Administrator Guide Stair Tower (STRTWR) Assembly
4
4.1
4:1
12.0
Access platforms, Stairs and Ladders Administrator Guide Stair Tower (STRTWR) Assembly
4.2
4.2.1
4.2.2
4.2.3
4:2
12.0
Access platforms, Stairs and Ladders Administrator Guide Stair Flight (STRFLT) Assembly
5
5.1
5:1
12.0
Access platforms, Stairs and Ladders Administrator Guide Stair Flight (STRFLT) Assembly
5.2
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.
5:2
12.0
Access platforms, Stairs and Ladders Administrator Guide Stair Flight (STRFLT) Assembly
5.2.1
5.2.2
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.
5:3
12.0
Access platforms, Stairs and Ladders Administrator Guide Stair Flight (STRFLT) Assembly
5:4
12.0
Access platforms, Stairs and Ladders Administrator Guide Ladder (LADDER) Assembly
6
6.1
6.2
6.2.1
6.2.2
6:1
12.0
Access platforms, Stairs and Ladders Administrator Guide Ladder (LADDER) Assembly
6.2.3
6.2.4
6.2.5
6.2.6
6:2
12.0
Access platforms, Stairs and Ladders Administrator Guide Platform (PLTFRM) Assembly
7
7.1
7.2
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;
7:1
12.0
Access platforms, Stairs and Ladders Administrator Guide Platform (PLTFRM) Assembly
7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
7.2.6
7.2.7
7:2
12.0
Access platforms, Stairs and Ladders Administrator Guide Handrail (HANDRA) Assembly
8
8.1
8.2
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
8:1
12.0
Access platforms, Stairs and Ladders Administrator Guide Handrail (HANDRA) Assembly
8.2.2
8.2.3
8.2.4
8.2.5
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
8.2.8
8.2.9
8:2
12.0
Access platforms, Stairs and Ladders Administrator Guide Handrail (HANDRA) Assembly
8.2.10
8.2.11
8:3
12.0
Access platforms, Stairs and Ladders Administrator Guide Handrail (HANDRA) Assembly
8:4
12.0
Index
A
Access Set (ACCSET) . . . . . . . . . . . . . . 4:2 ACCSET . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 Administrative preconditions . . . . . . . . . . . . . . . . . . 2:3 Administrator access permissions . . . . . . . . . . . . . 3:1 tasks . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 APPDAR . . . . . . . . . . . . . . . . . . . . . . . . . 3:3 APPLDW . . . . . . . . . . . . . . . . . . . . . 2:3, 3:1 APPLICATION . . . . . . . . . . . . . . . . . . . . 2:3 Application Data and Templates . . . . . . . 2:4 Application Data Area (APPDAR) . . . . . . 3:3 Application Data Worlds (APPLDW) . . . . 2:3 ASL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 default storage area form . . . . . . . . . 3:2 elements . . . . . . . . . . . . . . . . . . . . . . 2:1 hierarchy . . . . . . . . . . . . . . . . . . . . . . 2:2 ASL Assemblies . . . . . . . . . . . . . . . . . . . 2:2 hierarchical relationships . . . . . . . . . 2:2 simplified parameterisation . . . . . . . . 2:2 ASLADMIN team . . . . . . . . . . . . . . . . . . . 3:1 ASLCONFIG database . . . . . . . . . . . . . . 3:1 ASLSbStandard . . . . . . . . . . . . . . . . . . . 3:4 ASLStandard . . . . . . . . . . . . . . . . . . . . . . 3:4 Assembly Data World (APPLDW) . . . . . . 3:1
Create ASL Assemblies . . . . . . . . . . . . . . . . ASL Selections . . . . . . . . . . . . . . . . New Secondary Standard . . . . . . . . New Setting . . . . . . . . . . . . . . . . . . . New Standard . . . . . . . . . . . . . . . . . Standards (Engineering Criteria) . . .
D
Database Hierarchy ASL Assemblies . . . . . . . . . . . . . . . . Ladder . . . . . . . . . . . . . . . . . . . . . . . Platform . . . . . . . . . . . . . . . . . . . . . . Stair Flight . . . . . . . . . . . . . . . . . . . . Stair Tower . . . . . . . . . . . . . . . . . . . DDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . DDSE . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Selected Secondary Standard . . . . . Selected Setting . . . . . . . . . . . . . . . . Selected Standard . . . . . . . . . . . . . . Description Handrail Elements . . . . . . . . . . . . . . Ladder Elements . . . . . . . . . . . . . . . Platform Elements . . . . . . . . . . . . . . Stair Flight Elements . . . . . . . . . . . . Stair Tower Elements . . . . . . . . . . . Description field . . . . . . . . . . . . . . . . . . . Design Data Set (DDSE) . . . . . . . . . . . . 2:2 6:1 7:1 5:1 4:1 2:4 3:4 3:4 3:7 3:3 8:1 6:1 7:1 5:2 4:2 3:5 3:4
C
Cage Segment (CAGSEG) . . . . . . . . . . . 6:2 CAGSEG . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 Copy Selected Secondary Standard . . . . . 3:4 Selected Standard . . . . . . . . . . . . . . 3:4
E
Extension to Design Data . . . . . . . . . . . . 2:4 External Frame (EXTFRM) . . . . . . . . . . 7:2
Index page i
12.0
EXTFRM . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
P
Platform Database Hierarchy . . . . . . . . . . . . . Feature (PLFEAT) . . . . . . . . . . . . . . Grid (PLTGRD) . . . . . . . . . . . . . . . . Opening (PLOPEN) . . . . . . . . . . . . . Platform (PLTFRM) Assembly . . . . . . . . PLFEAT . . . . . . . . . . . . . . . . . . . . . . . . . PLOPEN . . . . . . . . . . . . . . . . . . . . . . . . . PLTFRM . . . . . . . . . . . . . . . . . . . . . . . . . PLTGRD . . . . . . . . . . . . . . . . . . . . . . . . . POS . . . . . . . . . . . . . . . . . . . . . . . . . . . . POSTSE - Post Set . . . . . . . . . . . . . . . . Product Compatibility . . . . . . . . . . . . . . . Properties . . . . . . . . . . . . . . . . . . . . . . . . PTOLER . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 7:2 7:2 7:2 7:1 7:2 7:2 7:1 7:2 2:2 8:3 1:1 3:4 2:4
G
General Route Path Element . . . . . . . . . 2:5 General Routing Path (RPATH) . . . . . . . 2:5 Getting Started . . . . . . . . . . . . . . . . . . . . 3:1
H
HANDRA . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 Handrail Database Hierarchy . . . . . . . . . . . . . 8:1 Handrail (HANDRA) Assembly . . . . . . . . 8:1 How to Use this Guide . . . . . . . . . . . . . . 1:2 HRFEAT - Handrail Feature . . . . . . . . . . 8:2 HRGATE - Handrail Gate . . . . . . . . . . . . 8:2 HRKPSE - Handrail Kick Plate Set . . . . . 8:2 HRPANE - Handrail Panel . . . . . . . . . . . 8:2 HRPNSE - Handrail Panel Set . . . . . . . . 8:1 HRPOST - Handrail Post . . . . . . . . . . . . 8:3
R
RAIL - Rail . . . . . . . . . . . . . . . . . . . . . . . RAILSE - Rail Set . . . . . . . . . . . . . . . . . . RATTA . . . . . . . . . . . . . . . . . . . . . . . . . . RATTA - Route Attachment . . . . . . . . . . References . . . . . . . . . . . . . . . . . . . . . . . Route Attachment (RATTA) . . . . . . . . . . RPATH . . . . . . . . . . . . . . . . . . . . . . . . . . Rung Set (RUNGSE) . . . . . . . . . . . . . . . RUNGSE . . . . . . . . . . . . . . . . . . . . . . . . 8:2 8:2 7:2 8:2 1:1 7:2 2:5 6:1 6:1
I
Internal Frame (INTFRM) . . . . . . . . . . . . 7:2 INTFRM . . . . . . . . . . . . . . . . . . . . . . . . . 7:2 Introduction . . . . . . . . . . . . . . . . . . . . . . . 1:1
K
KICKPL Kick Plate . . . . . . . . . . . . . . . . . 8:2
S
Secondary Standards . . . . . . . . . . . . . . . Selections for ASL application form . . . . Setting Type . . . . . . . . . . . . . . . . . . . . . . Stair Flight (STRFLT) Assembly . . . . . . Stair Flight Database Hierarchy . . . . . . . Stair Landing (STRLNG) . . . . . . . . . . . . Stair Stringer (STRSTR) . . . . . . . . . . . . Stair Tower (STRTWR) Assembly . . . . . Stair Tower Database Hierarchy . . . . . . Standards . . . . . . . . . . . . . . . . . 3:2, 3:3, Standards for ASL application form . . . . Storage Areas . . . . . . . . . . . . . . . . . . . . STRFLT . . . . . . . . . . . . . . . . . . . . . . . . . STRLNG . . . . . . . . . . . . . . . . . . . . . . . . . STRSTR . . . . . . . . . . . . . . . . . . . . . . . . . STRTWR . . . . . . . . . . . . . . . . . . . . . . . . STRU . . . . . . . . . . . . . . . . . . . . . . . . . . . SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . System Evaluation engineering criteria . . . . . . . . . . . . . System/User responsibility . . . . . . . . . . . 3:4 3:6 3:7 5:1 5:1 4:2 5:3 4:1 4:1 3:4 3:2 3:2 5:1 4:2 5:3 4:1 2:2 2:3 2:3 2:3
L
LADDER . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Ladder Cage (LDRCAG) . . . . . . . . . . . . . . . 6:2 Database Hierarchy . . . . . . . . . . . . . 6:1 Exit (LDREXT) . . . . . . . . . . . . . . . . . 6:2 Rung (LDRRUN) . . . . . . . . . . . . . . . 6:2 Stringer (LDRSTR) . . . . . . . . . . . . . . 6:1 Ladder (LADDER) Assembly . . . . . . . . . 6:1 LDRCAG . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 LDREXT . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 LDRRUN . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 LDRSTR . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
O
Open Feature (OPENFE) . . . . . . . . . . . . 7:2 OPENFE . . . . . . . . . . . . . . . . . . . . . . . . . 7:2 ORI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Index page ii
12.0
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
12.0
Index page iv
12.0